NVIDIA Conrol Panel Settings.
#1
Posted 11 September 2014 - 12:39 PM
One example is of course MSTS. I had serious moire issues until I used nvida inspector to clean it up. The only problem is that I may have used too much filtering and it shows in the frame rate and the overall looks of the graphics. Under OR, very little appears to be changing when experimenting with the different settings.
Is there any possibility that a setting in the fx files is somehow overriding the use of the control panel settings?
One issue that I am experiencing under windowed mode is some form of rippling effect in front of the train. This issue is noticeable both from the cab and when in external view. I could provide a screenshot if needed, but the issue does not stand out very well.
Edward K.
#2
Posted 11 September 2014 - 01:02 PM
http://jpeg.cz/images/2014/09/11/YJLtv.jpg
#4
Posted 11 September 2014 - 01:49 PM
Edward K.
#5
Posted 12 September 2014 - 03:41 AM
edwardk, on 11 September 2014 - 12:39 PM, said:
No, NVIDIA's settings always override the app (unless you've specifically selected otherwise in the NVIDIA options). If it seems to not be working, it is either a problem with the profile not being for the correct executable or something has screwed up at NVIDIA's end.
The NVIDIA Control Panel settings have always worked fine for me, though I will say that I normally only make 1 adjustment from the defaults these days: Texture Quality: Best Quality. This is because the default level actually does not do anisotropic filtering correctly so the track textures look bad - but changing this one option fixed that.
#6
Posted 12 September 2014 - 10:27 AM
Open rail graphical properties at 32 - bit set using a shortcut RunActivity
When using Windows 64 bit RunActivityLAA
When Nvidia inspector pays the same as the top of the figure.
Doing representative through Open Rail.exe !!!! Does not work.
#7
Posted 12 September 2014 - 01:13 PM
sampler Image = sampler_state
{
Texture = (ImageTexture);
MagFilter = Linear;
MinFilter = Anisotropic;
MipFilter = Linear;
MaxAnisotropy = 16;
MipMapLodBias = 0;
};
I still have that odd issue though that I believe may be connected with the camera view when in window mode. I have tried various screen shots to try to show this issue, but you can hardly see it.
Edit: Actually the issue I am experiencing is not even in the screen shot. At first I thought the visual anomaly was just hard to see, but it turns out its not present in the screen shot, but it is clearly visible when looking at the track from the inside cab and outside the cab. Is there a possibility that this issue can be caused by an odd camera view problem?
Edward K.
#8
Posted 14 September 2014 - 01:47 PM
----------------
David
#9
Posted 14 September 2014 - 01:54 PM
From 12 September 2014 - 01:13 PM:
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.
#10
Posted 14 September 2014 - 02:13 PM
dforrest, on 14 September 2014 - 01:47 PM, said:
No, you must select RunActivity.exe or RunActivityLAA.exe. If you're using a recent version of the NVIDIA Control Panel, you should see this at the top of the list when adding a profile if you've recently played OR.