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
Can you share your logs so I can take a look at what's up?
- Open your Windows Explorer
- Copy and paste the location of the log file into your Explorer's address bar:
- C:\Users\%USERNAME%\AppData\LocalLow\Voids Within\Dystopika
- Grab the file called Player.log and either post here or visit the Discord[discord.voidswithin.com] to create a bug post
I consider game not starting to be priority 1 and will get it fixed ASAP once I have a log to inspect.
[PhysX] Initialized MultithreadedTaskDispatcher with 24 workers.
Initialize engine version: 2022.3.47f1 (88c277b85d21)
[Subsystems] Discovering subsystems at path D:/SteamLibrary/steamapps/common/Dystopika/Dystopika_Data/UnitySubsystems
GfxDevice: creating device client; threaded=1; jobified=1
Direct3D:
Version: Direct3D 11.0 [level 11.1]
Renderer: NVIDIA GeForce RTX 3080 (ID=0x2216)
Vendor: NVIDIA
VRAM: 10053 MB
Driver: 32.0.15.6603
<RI> Initializing input.
New input system (experimental) initialized
Using Windows.Gaming.Input
<RI> Input initialized.
<RI> Initialized touch support.
[PhysX] Initialized MultithreadedTaskDispatcher with 24 workers.
UnloadTime: 0.363400 ms
Crash!!!
[PhysX] Initialized MultithreadedTaskDispatcher with 8 workers.
Initialize engine version: 2022.3.47f1 (88c277b85d21)
[Subsystems] Discovering subsystems at path D:/SteamLibrary/steamapps/common/Dystopika/Dystopika_Data/UnitySubsystems
GfxDevice: creating device client; threaded=1; jobified=1
Direct3D:
Version: Direct3D 11.0 [level 11.1]
Renderer: NVIDIA GeForce MX250 (ID=0x1d13)
Vendor: NVIDIA
VRAM: 1968 MB
Driver: 32.0.15.6070
<RI> Initializing input.
New input system (experimental) initialized
Using Windows.Gaming.Input
<RI> Input initialized.
<RI> Initialized touch support.
[PhysX] Initialized MultithreadedTaskDispatcher with 8 workers.
UnloadTime: 1.058900 ms
[<b>SETTINGS</b>] [INFO] Resolution: 1280 x 720 @ 60Hz
UnityEngine.Logger:Log(LogType, Object)
I'm trying to figure out what's happening here since that Crash!! is very early in the startup - like before the game itself has even begun initializing. Are there any other details after the Crash!!! in the log?
Is there anything else at play here? Antivirus software? Trying to run inside Linux? System language? Windows version?
Just anything that might help me pinpoint why it's happening here but not elsewhere 🙏
[PhysX] Initialized MultithreadedTaskDispatcher with 12 workers.
Initialize engine version: 2022.3.47f1 (88c277b85d21)
[Subsystems] Discovering subsystems at path D:/SteamLibrary/steamapps/common/Dystopika/Dystopika_Data/UnitySubsystems
GfxDevice: creating device client; threaded=1; jobified=1
Direct3D:
Version: Direct3D 11.0 [level 11.1]
Renderer: AMD Radeon(TM) Graphics (ID=0x1638)
Vendor: ATI
VRAM: 7880 MB
Driver: 31.0.21029.6002
D3D11 device created for Microsoft Media Foundation video decoding.
<RI> Initializing input.
New input system (experimental) initialized
Using Windows.Gaming.Input
<RI> Input initialized.
<RI> Initialized touch support.
[PhysX] Initialized MultithreadedTaskDispatcher with 12 workers.
UnloadTime: 50.378600 ms
[<b>SETTINGS</b>] [INFO] Resolution: 1920 x 1080 @ 60Hz
UnityEngine.Logger:Log(LogType, Object)
- No Antivirus
- Windows 11
- Updated nVidia drivers
- System language is ENG US
- The machine's been through a few reboots since and still same error.
There aren't any further details in the log sadly.
The problems with Whisky/Linux make sense - there is some usage of Windows-standard folders like My Documents that might break it, and officially, Mac and Linux isn't supported at this time.
So, for anyone on just pure Windows 11, if there's anything you can share to help me figure this one out, I'd be grateful:
- Does it crash relatively quick, or does it freeze up for a 10+ seconds?
- Are you doing anything custom/weird with GPU (like overclocking)
- Are there any controllers plugged in?
- Do you have any unique audio devices - Audio IO, USB microphones, etc.
- Do you have multiple displays?
What might also be useful is Windows-level crash info:
Step 1: Locate the Crash Event (after encountering the game crash)
Open Event Viewer: Press Windows + R, type eventvwr, and press Enter.
Navigate to Application Logs: In the Event Viewer, expand the Windows Logs folder and click on Application.
Step 2: Find the Relevant Event
Filter Events: Click on Filter Current Log on the right-hand side. Select Error and Critical under Event level, and then click OK.
Find the Dystopika Crash: Look for entries related to your game. These are often marked by the game’s name or Application Error under the Source column.
Step 3: Obtain the Details
View Event Details: Click on the relevant event to see the details at the bottom.
Copy the Details: Copy the details from the General tab and, if available, from the Details tab in Friendly View mode.
Share details here or send to matt[at]voidswithin.com
Thanks all! I'm sorry, I know this is frustrating (I'm partly going insane over here trying to reproduce it)
Open your Windows Explorer
Copy and paste the location of the log file into your Explorer's address bar:
C:\Users\%USERNAME%\AppData\LocalLow\Voids Within\Dystopika
Upload the file called Player.log to the bug post.
If you don't have visible file extensions configured in your Explorer, it'll just be the file named Player with the type Text Document
Hey there! Sounds like the RenderScale option might have got set too high and there isn't enough VRAM to process. Maybe I should get some better guard rails on that so you don't accidentally crank it too high.
You can reset the render scale by:
1. WIN + R to open run dialog
2. Run Regedit. (Accept the permissions pop-up)
3. Navigate to Computer\HKEY_CURRENT_USER\Software\Voids Within\Dystopika
4. Find the Renderscale entry and right click> Delete. Click Yes to the warning
Next time you run the game it should revert to the default