Start the game when DLSS Frame Generation is on and the chosen graphics card is not an NVIDIA one.

Four players of 0.10.1 could not start the game again after changing settings: "no usable Vulkan device", exit code 70, until nx2navi.ini was edited or removed by hand. One log shows the case: a laptop with an RTX 3050 and Intel Iris Xe graphics, framegen = dlss and gpu_index = 1, the Intel one. With frame generation on, the device is made through Streamline's interposer, which asks it for VK_NV_low_latency2 and failed with VK_ERROR_EXTENSION_NOT_PRESENT, and nothing else was tried.

A chosen card of another vendor now counts as not usable while the interposer is in use, so the best usable card is taken, as for a chosen card that is gone. Where the card in use is still not an NVIDIA one, or the interposer fails to make the device for another reason, the loader makes it and frame generation is off for the run: the log says why and the settings menu shows it as unavailable, as it does when Streamline's files are missing.

Not run: no PC here has two cards of different vendors. The changed files compile.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

docs/releases/v0.10.2.md

@@ -36,6 +36,10 @@ cards).
 - **Sky-coloured holes in the ground where grass is still loading**, on cards that take the mesh shader fallback: a
   patch of grass or leaves is now left out whole until it is ready, where its depth alone was drawn before
   (`mesh_fallback_hold = 0` brings that back). Not yet confirmed by players with these cards either.
+- **The game not starting after a settings change on a laptop with two graphics cards** ("no usable Vulkan device",
+  code 70, until nx2navi.ini was edited by hand): with DLSS Frame Generation on and the *Graphics card* setting on
+  the card that is not NVIDIA's, the device could not be made. The game now starts on the NVIDIA card, and where
+  there is none, or frame generation cannot be set up, it starts without frame generation and the log says why.
 - **Crashes and hangs found in a review of the whole runtime**; none was seen in our own play, and each fix has a check
   of its own:
   - a crash when the game read memory the lazy write-back was just handing to the GPU (NVIDIA and Intel cards);