Tried last night lot of different graphical settings for optimising VR and found two weird things (another old known, but not reported it before, coz windows/bios). Starting point where everything works nice and fluently on 60Hz VR, just like train with nearly maximized graphics settings and 40 visible but "only" 19 AI + me on track, rain and track as Nurburgring Sprint. Lift to 90Hz and started to drop graphics to get game frame renders match to needed "180 frames", everything went fine until I touch on AA setting, that broke whole game, after lowering from my AA5 setting first to 4 and then to 3 game was having just crazy stuttering, and it didn't recover from it at all, rolling all back to known fluently working 60Hz didn't help, constant stuttering was there to stay. Recover from that I needed to shut down cpu totally and with known good settings aplied before starting game it recovered to normal state. Booting procedure neded tweak, as decribed below. Another way to get random stutters was to start game aftet power up soon as getting windows desktop and stsrting game, if you came from cold start. A way to avoid those is to start cpu from power off state to desktop and do a soft boot, aka rstart cpu from menu, this has been a normal thing for me a long time period, after BIOS introduced RAM timing autoconfig, it will do bit overoptimistic timings (sub timings) on cold DDR4 sticks, and that for I'm normally booting cpu up from cold to desktop and leaving there for few minutes (when all startup sheduled windows parts have run thru) and then restarting cpu and again letting it to run thru all startup stuff before starting any game. So one windows/bios crap and one weird rf2 fail.. Is it on shaders?