Atomic Systems

I upgraded my PC this week, and played TS firs the first time since today. Upon using the 2D map I get this strange glitch. If I zoom in as much as I can it disappears (the glitch) and if I zoom right out it also stops but anything in between ends up giving me this. All other aspects of the game run perfectly, no graphical glitches, just when using the 2D map (or as far as I'm aware!)



Does anybody know how to rectify this? I've never seen it before.
Specs to see if it is something on my system:

GPU: Ge Force GTX760
CPU: Intel Core i5 760 @ 2.80GHz
Memory: 16.00GB RAM (15.99 Usable)
Resolution: BenQ 1920x1080, 60Hz
MS Windows 7 Home Premium

I have the second to latest Nvidia drivers, but I try to install the new Ge force updates but get an error saying it's not compatible with my O/S which I've also never had an issue with before.

Had similar problems after altering various settings, can`t remember which now, but reset to default and it cleared all
.
Ken

Hi, drop the game AA to FXAA + 8xMSAA or lower or use override game settings in Nvidia control panel to use higher settings

Avoid in game SSAA settings of any amount to negate this.

If your card supports it use DSR.

It's a problem with the nVidia drivers that manifests itself if you have SSAA enabled in game. Either don't or go back to the last known *working* drivers.... http://forums.uktrainsim.com/viewtopic. ... 0#p1775643 for Peter's findings.

Check out my Nvidia Control Panel Settings here https://www.dropbox.com/sh/sqcyjt0qm870 ... MEP2a?dl=0 zoom in on the images to read them.

To reiterate:
Use any MSAA setting in TS 2016 then NO 2D Map corruption in TS2016 or the editor with any version of the NVidia driver;
Using the latest NVidia drivers, and any SSAA setting in TS 2016 then 2D Map corruption in TS2016 AND the editor
In NVidia Control Panel (or NVidia Inspector) for TS2016 in AA-Mode - use "Override any application setting" - using SSAA settings in TS2016, then NO 2D Map corruption in TS2016 BUT 2D map corruption in the editor
Use the Geforce 347.xx or 350.xx drivers Use any SSAA setting in TS 2016 then NO 2D Map corruption in TS2016 OR in the editor.
pH
There has been no improvement in the NVidia drivers wrt TS2016 (performance and visuals) since the 347.xx/350.xx drivers were issued.

pH

Thank you to everybody who replied. It's sorted now by turning down to the highest FXAA setting. All your replies were/are helpful.

Trev123 wrote:Check out my Nvidia Control Panel Settings here https://www.dropbox.com/sh/sqcyjt0qm870 ... MEP2a?dl=0 zoom in on the images to read them.

Brill, thanks. I've updated my settings to match. Cheers.

I posted your screen shot in Nvidias forum, not that I think it will do any good.

Trev123 wrote:I posted your screen shot in Nvidias forum, not that I think it will do any good.

I don't think it is an nVidia problem, but rather Railworks' supersampling shader that is the fault here.
Railworks general anti aliasing shader is broken and can be corrected by downloading the fix available from UKTS. Therefor I wouldn/t be surprised if the supersampling shader is also broken.

FXAA Eliminator [623425 bytes] - FXAA_Eliminator.zip File ID: 34510 Date: 13 Jul 2015 - 2020 Downloads

There has been no improvement in the NVidia drivers wrt TS2016 (performance and visuals) since the 347.xx/350.xx drivers were issued.

I would have to disagree with you there Pete, I am running the latest drivers and TS now runs ok using DSR. no more TDR's, couldn't use DSR at all under the last several driver releases even with the registry fix!

Smary
I stand corrected but I had no issues running DSR on either the 347.xx or 350.xx drivers.
What I meant that visually in the main for TS2016 those drivers are just as good as later ones.

Fighter Command
It is a nvidia problem as earlier NVidia drivers work OK with any version of TS2016 any OS version - it is just the later ones that caused the issue.
BTW FXAA is not "broken" in TS2016, its just that some simmers didn't like its (Blurring) effects and removed it with that fix.
Sorry, but it is entirely incorrect to suggest that FXAA AA is broken in TS 2016 - it works as it should. SSAA is NOT broken either it works as it should too.
Regards
pH

But Peter, of course it's DTG's problem...everything is! They are, afterall, the easiest target for any problems folk have....much easier than admitting that they may have been doing something wrong.

Martin, TDR's are/were a Windows problem, not something specifically unique to the nVidia drivers though that is where they generally manifested themselves. As Peter says, DSR has not been a problem with older drivers for the majority of users, indicating that your configuration was slightly askew rather than being dodgy drivers.