Was messing around with the settings to improve the shadow effects e.g. on cockpit dash without sacrificing performance and when setting Texture Filtering to 8x Anisotropic I get a lighting bug, see screenshots below showing the settings on and off ON OFF SETTINGS
I was able to reproduce it by switching from x4 to x8 Anistropic and back again and now when I went to see if switching to fullscreen would help the bug was gone it seems... Unrelated, when first loading into a session what looks like a 2-pin AC adapter icon appears and disappears, never seen it before and don't now if it's something from rF2, odd...
Ah ok thanks, odd never noticed it before. Is there an FFB meter plugin available for the DX11 build yet?
Was changing settings again to try and improve anti-aliasing on the AI cars and had placed texture filtering at 8x anisotropic once more and the lighting error occurred. Screen and files zipped below
Chris for what it's worth some example settings below that appear to work well for a GTX 970 / Core i5 / 8GB @ 1080/60. These took me a LONG time to figure out, well you know what the rF2 loading screens are like The two images above it are the buggy ones with >= 8X anisotropic, trilinear or bilinear texture filtering. Am still testing on an ongoing basis but for a race against 15-20 AI at Sebring it doesn't look so bad...
Something like this happened to me, too, after I changed some other display settings. I thought it was because I alt-tabbed during loading and started doing something else (lurking the web, watching videos...), because I had no problem if I didn't do anything and just waited looking at the loading screen. [8GB RAM, 980 Ti]
Yes good point and indeed somebody had asked above if the same occurs when in fullscreen rather than borderless. I've been using borderless mode and when I first noticed the issues I wasn't alt-tabbing away from the load screen. I was later while testing to try and improve things but definitely not when it first occurred.
I have seen this bug happening when a setting is changed or when I switched to another resolution. I think it's not aniso as such that is the problem, but rather that something in the shaders break when a setting is changed. One way to solve this is to always empty the shaders and cbash folders in userdata/log folder. This has solved the problem for me 100% of the time, though it's more like a workaround.