Limbus Company

Limbus Company

Excitebot2000 2023 年 7 月 26 日 下午 8:39
Game crashes on startup?
I've been playing Limbus since launch, and have experienced no issues with the game's performance prior to today (game ran extremely well, didn't ever stutter, 60 fps, etc.). But with the release of the new update, suddenly, I can't seem to launch the game at all, and it crashes immediately when I try to open the game.

Has anyone else experienced similar issues? All my friends seem to have no issues with starting the game and so far it's left me quite confused and frustrated as I was hoping to get to play the new update today.
< >
目前顯示第 16-30 則留言,共 38
Nina Nani 2023 年 7 月 28 日 下午 9:00 
Honestly copying the whole thing might've been overkill
And I probably didn't need to censor anything
But I'm not super computer smart
AzureFlame66 2023 年 7 月 28 日 下午 9:29 
Ok I checked the crash log can anyone help me make sense of this?

The referenced script (Unknown) on this Behaviour is missing!
The referenced script on this Behaviour (Game Object '<null>') is missing!
D3D11 device created for Microsoft Media Foundation video decoding.
<RI> Initializing input.

<RI> Input initialized.

<RI> Initialized touch support.

UnloadTime: 0.724161 ms
Crash!!!
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFE0620DB28)
0x00007FFE0620DB28 (d3d11) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFE0620D8FF)
0x00007FFE0620D8FF (d3d11) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFE0620D821)
0x00007FFE0620D821 (d3d11) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFE0620B9E7)
0x00007FFE0620B9E7 (d3d11) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFE0620B8D6)
0x00007FFE0620B8D6 (d3d11) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFE0620B813)
0x00007FFE0620B813 (d3d11) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFE06207E39)
0x00007FFE06207E39 (d3d11) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFE0620E062)
0x00007FFE0620E062 (d3d11) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFE062112C0)
0x00007FFE062112C0 (d3d11) (function-name not available)
0x00007FFDE40D1401 (msmpeg2vdec) CVIDEOfilter::LoadSurface
0x00007FFDE40D0D5F (msmpeg2vdec) CVIDEOfilter::LoadSurface
0x00007FFDE40E6C73 (msmpeg2vdec) CVIDEOfilter::LoadSurface
0x00007FFDE40E4599 (msmpeg2vdec) CVIDEOfilter::LoadSurface
0x00007FFDE4181E73 (msmpeg2vdec) DllCanUnloadNow
0x00007FFDE41D4011 (msmpeg2vdec) DllCanUnloadNow
0x00007FFDE4179D22 (msmpeg2vdec) DllCanUnloadNow
0x00007FFDE416744B (msmpeg2vdec) DllCanUnloadNow
0x00007FFE0ADA1412 (KERNEL32) BaseThreadInitThunk
0x00007FFE0B475504 (ntdll) RtlUserThreadStart
teamol 2023 年 7 月 28 日 下午 9:35 
(This was written after Nina's log, before AzureFlame's!)

Sadly the log can't extract much useful info. The Cleanup Blit thing seems like the normal process they do before closing the game, as it shows up in my logs too.

There's also nothing much in between the initialization and the cleaning. The best guess we can do is send the log, with the PC infos attached, and hope it can help Project Moon figure out the environment needed to replicate this kind of problem.

The black screen thing reminds me of this though.

https://steamcommunity.com/app/1973530/discussions/0/3771239453240208320/

People had video codec problem, and this solution is asking people to enable K-Lite codec for 64-bit .mp4 playbacks.

It makes sense because first thing after startup the game tries to do is play project moon logo. I can replicate that by disabling in K-Lite codec, but the log reproduces different result, as the messages actually indicate `WindowsVideoMedia error`, etc.

Still, might worth a try to figure out if you have the codecs installed and configured.

If the player.log keeps generating these text while you're in black screen:

Context: CreateObjectFromByteStream Error details: <Empty> Track types: WindowsVideoMedia error 0x800700ea while reading ...

It means there's no needed video codec installed. Otherwise, it could be other causes.
最後修改者:teamol; 2023 年 7 月 28 日 下午 10:13
teamol 2023 年 7 月 28 日 下午 9:37 
引用自 AzureFlame66
Ok I checked the crash log can anyone help me make sense of this?

The referenced script (Unknown) on this Behaviour is missing!
The referenced script on this Behaviour (Game Object '<null>') is missing!
D3D11 device created for Microsoft Media Foundation video decoding.
<RI> Initializing input.

<RI> Input initialized.

<RI> Initialized touch support.

UnloadTime: 0.724161 ms
Crash!!!

It looks like a RAM issue. How much ram do you have?
AzureFlame66 2023 年 7 月 28 日 下午 9:42 
10 out of 14 gigs avalible
teamol 2023 年 7 月 28 日 下午 10:01 
引用自 AzureFlame66
10 out of 14 gigs avalible
my bad it's not RAM. the error messages simply saying they couldn't access the original code (to write it into the log), thus they don't have actual meanings.

Therefore we also can't extract much from that log sadly. Similar to the last suggestion, sending the full log to PM and describe your situation in detail (crashed or stay forever in black until alt+f4, etc. anything)
teamol 2023 年 7 月 28 日 下午 10:16 
Note that supposedly the game underwent an engine upgrade on 27th. That means things worked could now be broken. Just need to wait for Project Moon to figure out the issues, and the logs, describes and environment info from people who actually having issues might help the programmers.
AzureFlame66 2023 年 7 月 28 日 下午 10:20 
Thank you for the help
Nina Nani 2023 年 7 月 28 日 下午 10:25 
引用自 ティーモル
(This was written after Nina's log, before AzureFlame's!)

Sadly the log can't extract much useful info. The Cleanup Blit thing seems like the normal process they do before closing the game, as it shows up in my logs too.

There's also nothing much in between the initialization and the cleaning. The best guess we can do is send the log, with the PC infos attached, and hope it can help Project Moon figure out the environment needed to replicate this kind of problem.

The black screen thing reminds me of this though.

https://steamcommunity.com/app/1973530/discussions/0/3771239453240208320/

People had video codec problem, and this solution is asking people to enable K-Lite codec for 64-bit .mp4 playbacks.

It makes sense because first thing after startup the game tries to do is play project moon logo. I can replicate that by disabling in K-Lite codec, but the log reproduces different result, as the messages actually indicate `WindowsVideoMedia error`, etc.

Still, might worth a try to figure out if you have the codecs installed and configured.

If the player.log keeps generating these text while you're in black screen:

Context: CreateObjectFromByteStream Error details: <Empty> Track types: WindowsVideoMedia error 0x800700ea while reading ...

It means there's no needed video codec installed. Otherwise, it could be other causes.

I don't actually know how to send that information to them

引用自 ティーモル
Note that supposedly the game underwent an engine upgrade on 27th. That means things worked could now be broken. Just need to wait for Project Moon to figure out the issues, and the logs, describes and environment info from people who actually having issues might help the programmers.

I actually didn't know about that
But if that's true
Then I hope it's just the engine being finnicky
Because if not then that might mean my PC can't handle the new engine
I'll end up distorting if that's the case
Tapxynyc 2023 年 7 月 29 日 上午 12:56 
引用自 ティーモル
If the player.log keeps generating these text while you're in black screen:

Context: CreateObjectFromByteStream Error details: <Empty> Track types: WindowsVideoMedia error 0x800700ea while reading ...

It means there's no needed video codec installed. Otherwise, it could be other causes.

I have tried some things and sometimes (but not always which is kinda weird) it hits me with this error:

WindowsVideoMedia error 0x80004004 while reading C:/Program Files (x86)/Steam/steamapps/common/Limbus Company/LimbusCompany_Data/sharedassets0.resource Context: IMFSourceReader::WaitForSample in StepAllStreams Error details: <Empty> Track types: Video Track [1920 x 1080], type: H264
I have tried doing some codec stuff but nothing yet seemed to fix, but as it's not the same error exactly I have to ask if there may be other causes
teamol 2023 年 7 月 29 日 上午 1:58 
WindowsVideoMedia error 0x80004004 while reading C:/Program Files (x86)/Steam/steamapps/common/Limbus Company/LimbusCompany_Data/sharedassets0.resource Context: IMFSourceReader::WaitForSample in StepAllStreams Error details: <Empty> Track types: Video Track [1920 x 1080], type: H264
I have tried doing some codec stuff but nothing yet seemed to fix, but as it's not the same error exactly I have to ask if there may be other causes

Error details: <Empty> really seems tricky! The log couldn't help a lot, but seems like it crashed during video playback.

I googled alot about this error code around Unity community, things were similar but nothing exactly like that, so it'd be a shoot in dark doing everything besides sending bug report to limbussupport@projmoon.com.
最後修改者:teamol; 2023 年 7 月 29 日 上午 2:13
DeadDragon 2023 年 7 月 31 日 上午 3:07 
Same blackscreen here:stress:
最後修改者:DeadDragon; 2023 年 7 月 31 日 上午 3:09
Nina Nani 2023 年 7 月 31 日 上午 7:51 
引用自 DeadDragon
Same blackscreen here:stress:

Welcome to the club
The only recommendation I have is to report the issue to Project Moon at limbussupport@projmoon.com
Like what ティーモル is recommending, I ended up reporting it after the suggestion came, so it's only been a couple of days, but maybe we'll get a response soon.
Hopefully
arrivedxrci 2023 年 7 月 31 日 下午 9:40 
Hopefully when they update the game on Aug. 3, they acknowledge this and FIX THIS. Maybe even extend the event a little bit for us who didn't even get to play the damn game.
arrivedxrci 2023 年 8 月 3 日 上午 5:43 
I checked my crash log today and this is what it says. Is this the PM logo not being able to load?

A crash has been intercepted by the crash handler. For call stack and other details, see the latest crash report generated in:
* C:/Users/NOTLEAKINGNAME/AppData/Local/Temp/ProjectMoon/LimbusCompany/Crashes
WindowsVideoMedia error 0x80004004 while reading C:/Program Files (x86)/Steam/steamapps/common/Limbus Company/LimbusCompany_Data/sharedassets0.resource

Context: IMFSourceReader::WaitForSample in StepAllStreams
Error details: Operation aborted

Track types:
Video Track [1920 x 1080], type: H264
A crash has been intercepted by the crash handler. For call stack and other details, see the latest crash report generated in:
* C:/Users/NOTLEAKINGNAME/AppData/Local/Temp/ProjectMoon/LimbusCompany/Crashes
< >
目前顯示第 16-30 則留言,共 38
每頁顯示: 1530 50

張貼日期: 2023 年 7 月 26 日 下午 8:39
回覆: 38