bombastinator
Registered
MSI b660m mag mortar (max?)12700 non k, XFX merc 7900xtx
Joined Feb 10, 2008
8,558 Posts
Discussion starter
·
#1
·
5h ago

There is no place to put this on the actual GeForce now forum so I am putting it here in hopes that a search will find it.

fallout 4 on GeForce now has serious problems.
most gamepads even if they connect won’t work, so I am forced to use the virtual gamepad software.
There can be an issue where the virtual gamepad doesn’t “hook” to the game. The buttons do nothing And the game cannot be started.
There is a glitch though. IF one keeps the virtual game pad half close in the select your input pullout, when the play button screen come up, one must hit play then activate the controller BEFORE THE BACKGROUND CHANGES. This is sometimes instant (in which case you are hosed and have to do it again) but sometimes takes a fraction of a second to close, and if you hit the button in that very brief window the virtual gamepad will “hook” and you can play the game. I am not sure what causes the delay to make this possible.

One MUST use mods because there is an unpatched bug that makes the lockpicking mini-game unplayable (If you have invisible lockpicking minigame you’re running at greater than 60 fps somewhere) so an Auto Unlock mod is required. Some company is messing with what mods load, then removing them and making them pay to play, so they effectively hold your game hostage unless you pay. It’s a very low down dirty move. The trick is to never use any of the additions, which include dogs, handmade shotguns, and backpacks. Then WHEN they are removed you simply load the game without the externally removed mods, and the game will still work. If you USE them and they have any effect on where your save is, it will not.
I have complained about each of these 3 problems and in each instance the buck was passed. Nvidia considers it a Bethesda responsibility, and Bethesda considers it a geforce now responsibility. AD Infinitum. The invisible lock picking issue has been in place as long as GeForce one has existed. I remember reading an early initial review where it was there. It is still not fixed. It’s probably an easy fix on nvidia’s part. The initial reviewer thought so. I suspect it has not even been attempted though. At any rate it is still there and must be dealt with.