- This topic has 27 replies, 2 voices, and was last updated Jan 15, 2026 7:20am by
.
-
Posts
-
@Ralf
FS25 has a visual bug on my system with the official profile that I never saw on the FS22 profile I cloned before you created this profile.In the top left and right of the image, at what seems like random times a transparent square appears in each of those locations. If I look at one of those squares and then move my head up or down, the image section within those two squares is out of line with the rest of the image. I have captured a video and image through the lens and will email it to support if that helps.
I’ll look into. Might be some depth buffer issue.
In the meantime check whether resetting the graphics settings to default helps. I didn’t encounter something like that, so there’s a fairly good chance that some graphics setting triggers the issue. Also make sure not to disable vorpX’s automatic game settings. These often ensure that 3D works as intended.
BTW: At least for me there was no 3D at all with the FS22 profile in FS25. To get that simply turn off 3D in the vorpX menu.
I tried at the default profile settings and it’s actually worse than the settings I’m using. With the FS22 profile, I had a game FOV of 110, vorpx settings were Z-Normal, 3D-Strength 3, Depth Weighting 0.05, Focal Point 75 and Image zoom 1.285. That gave very good 3D for z-normal with no graphical issues at all.
I’ve send a short video of the bug I’m seeing.Try both the game settings and the profile settings at default and DO NOT disable automatic settings.
FOV in FullVR mode is calculated to perfectly match your headset with auto settings. No need to guess it manually. You can’t guess better than the calculation.
That aside:
I’ll look into it.
Try both the game settings and the profile settings at default and DO NOT disable automatic settings.
I did that before reporting and the bug looked worse than the settings I had.
I have a 5090 on the latest drivers but I have tried earlier drivers just to rule that out.
I’ll look into it.
Thanks Ralf.
Please still don’t disable automatic settings, which you apparently did when you dialed in the FOV manually. Just don’t do that. The according huge warning displayed by vorpX exists for a reason.
Also reset the game’s graphics settings to default. Doesn’t matter what you did or did not before, I can only consider your issue a bug if it occurs wben things are set up as they are supposed to be set up. Thanks for your understanding.
If you still encounter your issue after letting vorpX do its job without tinkeríng, please send an e-mail with a trouble shoot data archive to support at vorpx dot com. You can create a trouble shoot data archive in the config app.
As I said in my post above, it happens with everything at default, both game settings and profile settings. The FS22 profile I cloned to run FS 25 worked fine apart from the horizontal coloured lines when removing the headset, which you’ve fixed. I’d continue using that cloned profile but I can’t see any way to do that once an official profile is associated with FS25.
Just so we’re on the same page here, I do not expect to use custom settings and then complain to you something isn’t working correctly or report it as a bug. I’m more than happy to use those custom settings though because in the case of FS25 (with the FS22 profile clone) , I was able to improve the 3D effect a lot, making it playable for my needs.
If you still encounter your issue after letting vorpX do its job without tinkeríng, please send an e-mail with a trouble shoot data archive to support at vorpx dot com. You can create a trouble shoot data archive in the config app.
@Ralf
I have a bit more information that might help you solve this bug. It’s being caused by the mirrors. If I turn the mirrors off, the bug is gone. One mirror active, I can see the bugged area move depending on what mirror is active when rotating my head. I have three mirrors active because in the vehicles I drive, all the mirrors are active at once and I don’t see some of them switching on/off as I rotate my head but that induces the bug.
Great. That explains why I couldn’t replicate the issue. Somewhat funny actually.
While authoring shaders in DX12 vorpX internally pretends that G3D is supported for technical reasons even if it’s not. That in itself wouldn’t be an issue, but in Farming Simulator vorpX disables mirrors in the game’s .ini with G3D since they caused G3D glitches in earlier FS versions that still had G3D support. So for me mirrors got disabled in the .ini during shader authoring automatically due to this leftover settings change, not for you though (or anyone else but me). As a result I didn’t get your issue.
I’ll check wehether I can resolve this without disabling mirrors, but that might not be possible. Sounds like the game re-uses the depth buffer texture for the mirrors. If in doubt, I’ll expand the automatic mirror disabling to Z3D too.
Thanks for the hint!
Thanks Ralf. Just for clarity, when I was using a clone of the FS22 profile for FS25, I didn’t have this bug.
I’ll take that into account. Thanks again for finding the culprit here. As said above if possible I’ll try to resolve this without mirror disabling, just don’t hold your breath for it.
Hi Ralf
I noticed you’ve deployed a fix for this bug in the latest update. It has changed but not gone for me. I’m currently playing on the official kinlaig map but all maps I’ve played are the same. The bug is intermittent depending on map location and direction the vehicle is facing. In some areas/directions there’s no corruption around the mirrors, change direction or map location and some places are really bad. I’m wondering how I can use the clone of FS22 profile I had working because now the exe is associated with the FS25 profile I can see no easy way to do that.
Thanks for looking into this though.
- You must be logged in to reply to this topic.