Forum Replies Created
-
Posts
-
Lately the shader editor isn’t always highlighting shader outputs when you select “red” or “green” but “hide” is working so in Fo76 I was able to find parts but not all of the HUD. Like, in inventory the text would be selected by the shader but the text shadows and highlights were another shader I couldn’t find, and the quick-select menu I could find shaders for the roundabout but not for the icons to appear in each position.
When changing between Pixel and Vertex shaders is the menu going through a different list or the same list bit treating differently?
Fallout 76 has the same issue. Yes a profile update was downloaded by VorpX yesterday and used the “import” function in VorpX to revert to default but the problem persists in Fallout 76.
I had used the shader editor before due to some issues with shadows and water (hid what wasn’t showing correctly) and tried to delete all my settings but is there a way to get those to revert to default as well?
The new game update with FSR3 crashes when enabling Frame Generation with VorpX active.
Is a fix possible/coming?
Other than that, no trouble with the new update, even FSR3 is working great just not FG.
Really enjoying this game in VorpX!
@Xoleen It was the config files in “C:\Users\<username>\Documents\My Games\Starfield”, StarfieldCustom.ini and StarfieldPrefs.ini
When you delete them the game will recreate them from defaults the next time you launch.
Launch with VorpX active, and from the main menu open the VorpX menu, set resolution option, save and exit. Next launch, worked perfectly!Update on that Starfield problem I was having: deleted all the config files and this time VorpX was able to update properly — all the FOV and resolutions working as expected!
User error as usual ))))
Game is looking fantastic now, and the gestures are a great addition — good work as usual!
I’ve followed the instructions yet there are no changes made when updating settings in the menu. Resolution doesn’t change after relaunch when changing in the VorpX menu.
Comparing before and after and after relaunching, there are no changes made to the game configuration files, and FOV + tracking are highly distorted.
This is with the Steam version. Is there a particular configuration file VorpX needs to update? Perhaps I have a permissions issue blocking changes.
Great to see more updates!
For the Starfield profile, what are the recommended resolution and FOV settings?
I’d like to try this out but I can’t figure out how to override the default profile to use this one instead.
There is a profile in the latest beta, but I can’t figure out what game resolution and FOV settings to use.
Already looks great, but without proper FOV it’s not really playable yet.
Hey! The beta fixed it perfectly, thanks so much!
It looks like a lot of good new work also, I like the ‘Start Page’ with hints and reminders about the game, that’s a cool improvement.
So, the weird thing is, a week or so after I posted this it was back to working properly in G3D.
But last week, same thing happened: no more G3D, it just acts like flat.
Using “Decent” settings on a 3090. In-game FPS a little higher but not by a lot. So long as it stays over 45 the SteamVR motion compensation seems to keep the headset FPS stable enough for play but more FPS would be better.
One way you could help is to confirm if G3D works for you at all after the latest update.
I.E., is it just me, or did something in the game engine change to break VorpX G3D.
Thanks — and FYI, the FidelityFX pattern mentioned above is a false alarm: though the pattern held across more than a dozen tries at playing, the pattern failed today, so it was just random alignment with what I was trying, apparently.
Will try without the scan, thanks!
I’ve confirmed this odd behaviour five additional times today:
3x: If the game is launched after saving AMD FidelityFX as Low, Medium, or Full in the VorpX profile, it will crash within 1-2 minutes of entering gameplay.
2x: If the game is launched after saving AMD FidelityFX as Off in the VorpX profile, it will run stably for as much as two hours even if AMD FidelityFX is set to Low, Medium or Full during gameplay and selecting “OK” instead of “OK+Save”.
I don’t understand how this could be, but it’s consistent.