If you have graphic bugs. Check these things first: If you ever had changed something in the nvidia control panel in the past. Your graphic bugs might be still present. - Set your nvidia control panel for rFactor 2 to default !!! It messes with the Config.ini and cache !!! - Clean up your "UserData/log/CBash" and "UserData/log/shader" folder - Remove the player.json and config.ini (cut/past to desktop to keep a back-up) - launche rF2 it will create a new clean config.ini and player.json. - set your graphic settings again: only use settings available in rF2. Quote from Tuttle (ISI Dev) Starting from a clean installation, with a clean player/config file, the best way to proceed with graphics settings is to JUST use ingame settings, pushing on high AA levels and anisotropic filtering x8 or x16 (and of course good track/car quality settings)...and that without overriding anything via inspector and/or CCP. (Also HDR must be ON if you want a proper modern lighting.) This way you can load the game and check how it looks. If you see trees are looking properly (no alpha jaggies) and texture are sharp enough to see details into it (aniso texture filtering), you can decide to be happy (and stop tweaking)...or start experimenting extra settings, outside the game. But this is the time where you can mess with profiles and configs, so you have to check every single step, and every single click you are doing with CCPs and inspectors, to see how things are working. May happen a CCP/Inspector change is going to mess the config.ini and cache... and you can't just roll back from those settings, without cleaning up that file (aka generating a brand new one). Same for the Players.JSON and Transparency AA, or xpaa, using False to make wrong trees looking better and then making correct trees looking wrong. Still, the easy way to make the game looking at best, is to go easy peasy, with standard ingame settings. This is where you are working inside our choices, instead playing with a very big mix of variables we can't control.