Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
https://supportid.beamng.com/
About your note:
Using the OneDrive folder, or any other 'Cloud Service' folder, is a bad idea.
These tends to lock the files when they are syncing them (which happens, usually, as soon any file is added / changes). As the game cache is constantly changing, this is not good as it can cause the cache files to be locked and the game not being able to access them when needed.
58742 is the support id.
Thanks for the clarification, could you add that to thhe warning as well (if there's enough room for it).
If you're not trying to help... then don't bother posting.
Things are often much more complicate then they look from outside.
Some programs threats other programs in different way, and these ways are not often the right ones. Not all programs are compatible with each other, and unfortunately that resides in the way they work and potentially interfere with each other
Said that, we are always pursuing for ways to improve the game's stability and avoid issues with other programs. It's a never-ending task.
Thanks.
When you choose a different folder for your User Folder, did you by chance pick a folder that belongs to another Windows User on your PC?
The game is trying to use this path:
C:\Users\xenit\Documents\BeamNG.drive\
Is 'xenit' your Windows User?
Also, is the launcher working?
If yes, simply try to reset your folder location (Move User Folder > Reset Location)
A2. Yes, that is correct.
A3: Yes, but it didn't work.
Error 1: "Due to a bug in the previous release your userpath may have changed.
Please follow the instructions here to fix the problem."
Error 2: "The default userpath isn't accessible BeamNG will run using an alternative folder.
Please follow the instructions here to fix the problem."
So, you are only getting one error technically. The first one is a consequence of the second message, we need to improve that to be more clear.
Basically, the game is unable to use the Documents/BeamNG.drive folder for some reason.
Something may be blocking it, or there's something wrong somewhere.
In your previous log I saw something strange. It could be related to your issue, so please try this and see if it helps:
https://www.beamng.com/threads/game-just-stopped-working.61843/#post-1013585
And let me know please.
If the issue persists even after deleting that registry key, please provide a new Support ID so that I can check what it says now
You're referring to this key in regedit.exe correct and to search for something called "userpath_override" and edit it correct? I can't, it doesn't exist in the registry editor, the main path to it does, it's just that there is only "(default)", "rootpath" and "version".
My startup.ini is like this:
"; use UTF-8 without BOM as encoding
[filesystem]
; This determines where the User path is.
; This is by default or when empty below "My Documents\BeamNG.drive"
UserPath =
; example for using e:\beamng-user
;UserPath = e:\beamng-user
; example for using a relative path to this folder
;UserPath = \user
; example for local path (same as -nouserpath)
;UserPath = \"
1) There's no registry key forcing a different path, and your startup.ini is not modified.
In this scenario, the game would just use Documents/BeamNG.drive as your 'User Folder' (as confirmed by your game logs)
2)But then you get that "unable to write files" error, which usually indicate something is blocking the game from doing so. Please take particular note of this.
When this happens, the game has a fallback to use "C:\BeamNG.drive_userpath" instead, and you get notified about that.
Can you please send a screenshot of the very first error you posted here?
(unable to write files..")
So that we can see it in full.
Can you also please verify if the game is actually using that folder?
You should see several .log files, as well 'cache / settings / mods' folders.
If yes, then I'd say that the issue is only one, and it's the one mentioned in the second point:
Something on your side is blocking the game from using Documents/BeamNG.drive.
Please double-check that your antivirus, and anything similar that has the ability to interfere with other programs, is not messing with the game by mistake.
We have a list of known programs that could cause issues with the game too, please give it a careful look: https://wiki.beamng.com/Incompatible_Third_Party_Software
If you are unable to find what's causing that, a workaround is to manually specify a custom 'UserPath' in the startup.ini file. A location different from Documents, since something is not allowing the game to use that.
2. I also have Razer (it's Razer, not Razor according to that link) Central with Synapse and Cortex, however, it didn't interfere with i played BeamNG.drive on my Windows 7 laptop.
3. As requested, here's the link to the error message in question:
https://drive.google.com/file/d/1IWvB3YBJEWOi0F6NxUkKgy7Z04QkHJHN/view
4a. Here is the proof to of .log files being used in the default UserPath folder in Documents.
https://drive.google.com/file/d/1vxiPAfv_9tOJxRZLYC3wF1p-Z8sN-U7L/view
4b. As for what's in them. here is beamng.log:
0.00049|L|logging|-----------------------------------------------------------------------------
0.00058|L|logging|-- BeamNG.drive - new - 2019-9-8 -- 16:56:56
0.00061|L|logging|-- v 0.17.1.0.9000 - x64 - build buildbot build 9000 on winbuildbot3 - 29/08/2019 - 11:51:26
0.00063|L|logging|-- Log Format: Time since startup | Message level: D(ebug), I(nfo), W(arning), E(rror), A(lways) | Message"
4c: and here is beamng_launcher.log:
0.00152|L|logging|-----------------------------------------------------------------------------
0.00159|L|logging|-- BeamNG.drive.launcher - new - 2019-9-8 -- 16:55:01
0.00161|L|logging|-- v 0.17.1.0.9000 - x86 - build buildbot build 9000 on winbuildbot3 - 29/08/2019 - 11:51:26
0.00163|L|logging|-- Log Format: Time since startup | Message level: D(ebug), I(nfo), W(arning), E(rror), A(lways) | Message
0.00170|D|baseFS|gameroot = 'C:\Program Files (x86)\Steam\steamapps\common\BeamNG.drive\'
0.00172|D|baseFS|userpath = 'C:\Users\xenit\Documents\BeamNG.drive\' , Reason = win32 registry
0.00177|I|bng_platform_version|Microsoft Windows 10 (v10.0) (build 18362), 64-bit
0.59853|I|showMainUI|Nvidia Driver v=43602 Branch='r435_95'
71.82074|D|launchGame|launched, waiting for it now ...
114.82412|E|launchGame|process finished with exit code: 0x00000001* (see footnote below)
114.82439|E|gameStartupError|BeamNG.drive 0.17.1.0 0x00000001* (see footnote below)
114.82441|E|gameStartupError|0x00000001* (see footnote below)
*NOTE: This is due to me killing it in task manager, it has nothing to do with the error i'm getting.
Those may not be your latest logs, and may be from prior this started happening.
If you go in C:\BeamNG.drive_userpath you should find your actual latest game logs.
All you got indicates the same thing as said previously:
The game is being blocked by some program from using the Documents folder.
Unfortunately there is no way for us to know what program is doing that.
You'll need to find that. May be some particular Avast setting, or may be something else.
If you are not able to find that, a potential workaround is to use the 'startup.ini' file and manually define a path with less chance of being blocked (Documents is a folder that some programs are particularly over-protective with, causing unwanted issues at times)
1a. Here they are then, this is beamng.log:
0.00045|L|logging|-----------------------------------------------------------------------------
0.00051|L|logging|-- BeamNG.drive - new - 2019-9-9 -- 03:50:04
0.00053|L|logging|-- v 0.17.1.0.9000 - x64 - build buildbot build 9000 on winbuildbot3 - 29/08/2019 - 11:51:26
0.00054|L|logging|-- Log Format: Time since startup | Message level: D(ebug), I(nfo), W(arning), E(rror), A(lways) | Message
1b. And here is beamng_launcher.log:
0.00108|L|logging|-----------------------------------------------------------------------------
0.00115|L|logging|-- BeamNG.drive.launcher - new - 2019-9-9 -- 03:49:35
0.00117|L|logging|-- v 0.17.1.0.9000 - x86 - build buildbot build 9000 on winbuildbot3 - 29/08/2019 - 11:51:26
0.00118|L|logging|-- Log Format: Time since startup | Message level: D(ebug), I(nfo), W(arning), E(rror), A(lways) | Message
0.00126|D|baseFS|gameroot = 'C:\Program Files (x86)\Steam\steamapps\common\BeamNG.drive\'
0.00128|D|baseFS|userpath = 'C:\BeamNG.drive_userpath\' , Reason = default_failed Contact support Err=255
0.00134|I|bng_platform_version|Microsoft Windows 10 (v10.0) (build 18362), 64-bit
0.68832|I|showMainUI|Nvidia Driver v=43602 Branch='r435_95'
15.25106|D|launchGame|launched, waiting for it now ...
29.69863|E|launchGame|process finished with exit code: 0x00000001 (Task Manager'd)
29.69867|E|gameStartupError|BeamNG.drive 0.17.1.0 0x00000001 (Task Manager'd)
29.69868|E|gameStartupError|0x00000001 (Task Manager'd)
As said previously, your solution is to either find what is blocking the game from using Documents, or specify a different custom path in the startup.ini
(or let the game keep using the C:\ folder, it will still work fine)
"BeamNG.drive is unable to write files at \BeamNG.drive\
Please verify if any program is denying BeamNG.drive write
access to that location (such as, but not limited to antivirus
software).
Resorting to fallback location: "C\:BeamNG.drive_userpath\"
...again!
And yes, it's allowed through firewall (it's ticked), i checked.
What's "Err=255"...?
If yes, please send your 'startup.ini' file and also a new Support ID so that we can check them:
https://supportid.beamng.com/
I also attached the startup.ini in the zip as well.