Hi, im on 0.15.0.6 and ive just noticed my folder for mods is in a weird place - C:\BeamNG.drive_userpath\mods Yes ive clean reinstalled and no i havent changed the startup.ini file... Ive looked at the beamng-launcher.txt file and this is what it says, "0.00021|L|logging|----------------------------------------------------------------------------- 0.00029|L|logging|-- BeamNG.drive.launcher - new - 4/24/2019 -- 17:08:54 0.00032|L|logging|-- v 0.15.0.6.7990 - x86 - build buildbot build 7990 on winbuildbot_r720 - 13/03/2019 - 11:38:14 0.00034|L|logging|-- Log Format: Time since startup | Message level: D(ebug), I(nfo), W(arning), E(rror), A(lways) | Message 0.00047|D|baseFS|gameroot = 'D:\Games\Just Games\BeamNG.drive-0.15.0.0.7514\BeamNG.drive-0.15.0.6.7990\BeamNG.drive-0.15.0.6.7990\' 0.00050|D|baseFS|userpath = 'C:\BeamNG.drive_userpath\' , Reason = default_failed Contact support Err=255 2.23221|D|launchGame|launched, waiting for it now ..." Err=255? Im guessing thats the issue but what is Err 255?
That path is supposed to be used only in the case something is blocking the game from creating it in the usual location (Documents). Due to a bug, if you don't have that folder in Documents already, the folder gets created at the root of the C drive. That will be corrected in the next update. You can move it using the dedicated button in the launcher
That's how games work. You only need one side to be seen, as the inside isn't visible to you at any time... However, I think the devs would need to put a patch in that spot to make it look like the exhaust has an inside
I'm glad the Nvidia issue is out of the way, but months later and after informing AMD twice, the shading issue still exists on AMD hardware. Is there anything else that can be done besides having to turn shadows or grass off all the time on certain maps?
Yes, multiple Please check the blue text, it has been update some weeks ago. Some users reported that the newest driver have supposedly fixed this once for all. Unfortunately the issue is seemingly from the driver's side.
Interesting, I updated a week ago and had 19.4.1 and (19.4.3 as optional) I updated to 19.4.3 and can confirm that its actually okay now, so thanks!