[dforrest]

Thank you James, I have found it. Can you tell me what recommended changes to the NVIDIA defaults are recommended for using RunActivityLAA.exe?

[James Ross]

dforrest, on 14 September 2014 - 03:51 PM, said:

Thank you James, I have found it. Can you tell me what recommended changes to the NVIDIA defaults are recommended for using RunActivityLAA.exe?

I don't know about recommended changes but the only thing I change is "Texture filtering - Quality" from the default "Quality" to the much better "High quality". This fixes their broken anisotropic filtering on the track/terrain. I don't change anything else.

[dforrest]

Thank you James.

[edwardk]

Eldorado.Railroad, on 14 September 2014 - 01:54 PM, said:

Maybe the cows have left the barn on this one, but what I can state is that, before you commit any changes in Nvidia Inspector or AMD Catalyst, the Open Rails menu.exe HAS to be stopped. If menu.exe is loaded, changes to Directx are locked out, at least that is my experience. Ditto for changes you make in the registry for Open Rails.

I am going to guess that the secondary issue involving window mode and tracks is not experienced by many here. This of course will make it hard to determine if this issue is a rare bug or if it can be fixed on my end. For starters, I have removed all profiles related to OR and started from scratch, using just the standard control panel. All settings are set when OR is totally shut down. Once I found out my profile was not working right, fixing it solved the antialiasing issue and it shows under both full screen and window mode. The issue I am experiencing under window mode seems to be concentrated on the rails alone. Its a visual anomaly that moves up and down the rail with the camera view. I initially described it as ripples, but it looks more like ridges.



Edward K.