-
Posts
179 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Store
Articles
A20 Bugs
A21 Bugs
Events
Record Comments posted by q123
-
-
Not sure if it's related, but your log file shows an EOS problem:
2022-06-10T07:55:27 20.857 INF [EOS] Connection test failed: The operation has timed out.
I would have expected "INF [EOS] Login succeeded" instead.
Also running the game with only 1.977 MB VRAM could be some sort of a problem. Always close all background programs which are using VRAM on it's own (Webbrowser etc.).
0 -
True, my game is also not starting if I add the -logfile parameter in the launcher. I just get completly no error message at all. lol.
I tested before only at command line and with a self created link. Both methods should work for her too.
1 -
So, it's the spaces 😀
I've tested it with \Vicky's PC\ and it's working - if you use quotes around the Path:
-logfile "d:\Vicky's PC\7DaysToDie\logs\output_log_client.txt"
and the original path is working too (the missing folder will be created automatically by the game):
-logfile "%AppData%\7DaysToDie\logs\output_log_client.txt"
1 -
hint: starting the exe from the folder will not create an output log for you - unless you add the -logfile parameter yourself 😉
You could do that on the command line or with a seperate link. Here's an example:
"C:\Program Files (x86)\Steam\steamapps\common\7 Days To Die\7DaysToDie.exe" -force-d3d11 -logfile %AppData%\7DaysToDie\logs\output_log_client.txt
0
crash before the game starts
in Bug Pool
Posted
Here is another one with a similar problem:
He also has special characters an a space in his windows user name.