Screenshots: http://oi61.tinypic.com/9h893r.jpg http://oi59.tinypic.com/51awqt.jpg http://oi60.tinypic.com/24wvcd1.jpg EDIT: Solved! NOT rFactor2 related bug. It is related with nVidia Inspector, and is not a Build767 only bug, happens on older builds.
Your showing a Renault 3.5 instead of a FormulaISI car, but a nice catch nevertheless. Will try to replicate this once I'm home.
I have the Nvidia Inspector in 8xS setting. Trying just now without it. Additionally: Im running with default Video settings, default PLR/INI files, everything default. Config: 1080p@120Hz, AA=level1, HDR=on, rest=off. EDIT: It is the Nvidia Inspector, nice find!! Tested off= Fixed. Again 8xS mode = bugged again. Tested without AA mode = Fixed again.
You can disable the heat haze completely in the PLR.. "Heat FX Fade Speed":30, "Heat FX Fade Speed#":"Speed at which exhaust heat effects reduce by half (0 to completely disable)", (Watch out for the new JSON file format!)
I had the ''Combined 1x2 Supersampling + 4x Multisampling'' option. I have now the ''4x Multisampling'' option and is working fine. The problem is the supersampling, so I will let it off and problem solved, I dont want the HeatFX disabled. Thanks you.
I don't consider this to be our bug. It's caused by some unusual AA method that is incompatible with the heat haze technique. Solution: don't use this AA method.
+1 I didnt knew about that, and I saw that now, its true that is a old bug, but is not rFactor2 related.
No problem...use a rendering technique that doesn't require these unusual AA settings to get rid of the excessive jaggies and shimmering. You have undoubtedly read the threads around here about this. People aren't resorting to unusual AA settings because they enjoy fiddling. Only super-sampling looks crisp and good, but it kills frame rate. These unusual settings are an attempt at a compromise because normal multi-sampling that most other games look fine with produces a very unsatisfying result in rF2 (and rF1).
