Game crashes after Intro Videos
chris-fuchs opened this issue · comments
Installed CroftEngine like it says in the manual.
The Game crashes after all the intro videos. First the text "creating textures" is beeing shown, after that Tomb Raider. Afer a sec the game crashes.
Windows 10, Intel HD 620 - Tomb Raider 1 run within Steam (opens DoxBox) works fine
Logfile (anonymized)
[2022-11-24 18:54:25.784778 info 0x00003bcc] Check engine data dir: "C:\\Program Files\\CroftEngine\\share\\croftengine"
[2022-11-24 18:54:25.784778 info 0x00003bcc] Engine data dir: "C:\\Program Files\\CroftEngine\\share\\croftengine"
[2022-11-24 18:54:25.800403 info 0x00003bcc] Check engine data dir: "C:\\Program Files\\CroftEngine\\share\\croftengine"
[2022-11-24 18:54:25.800403 info 0x00003bcc] Engine data dir: "C:\\Program Files\\CroftEngine\\share\\croftengine"
[2022-11-24 18:54:25.800403 info 0x00003bcc] Check user data dir: "C:\\Program Files\\CroftEngine"
[2022-11-24 18:54:25.800403 info 0x00003bcc] Check user data dir: "C:\\Users\\anon\\AppData\\Local\\croftengine"
[2022-11-24 18:54:25.800403 info 0x00003bcc] User data dir: "C:\\Users\\anon\\AppData\\Local\\croftengine"
[2022-11-24 18:54:25.800403 info 0x00003bcc] Check user data dir: "C:\\Program Files\\CroftEngine"
[2022-11-24 18:54:25.800403 info 0x00003bcc] Check user data dir: "C:\\Users\\anon\\AppData\\Local\\croftengine"
[2022-11-24 18:54:25.800403 info 0x00003bcc] User data dir: "C:\\Users\\anon\\AppData\\Local\\croftengine"
[2022-11-24 18:54:25.800403 info 0x00003bcc] Check engine data dir: "C:\\Program Files\\CroftEngine\\share\\croftengine"
[2022-11-24 18:54:25.800403 info 0x00003bcc] Engine data dir: "C:\\Program Files\\CroftEngine\\share\\croftengine"
[2022-11-24 18:54:33.710791 info 0x00003bcc] Check user data dir: "C:\\Program Files\\CroftEngine"
[2022-11-24 18:54:33.710791 info 0x00003bcc] Check user data dir: "C:\\Users\\anon\\AppData\\Local\\croftengine"
[2022-11-24 18:54:33.710791 info 0x00003bcc] User data dir: "C:\\Users\\anon\\AppData\\Local\\croftengine"
dmp Dumpfile seems to be not supported to add to this issue, I opened it in WinDbg:
FILE_IN_CAB: croftengine_20221124_184346.dmp
CONTEXT: (.ecxr)
rax=0000000000929000 rbx=0000024ccac7db60 rcx=0000000000929001
rdx=0000000000043000 rsi=0000024cca32d2d0 rdi=0000024cc5a59d70
rip=00007ffe7eae476a rsp=000000d4458fe370 rbp=0000000000000502
r8=0000000000000000 r9=0000000000043000 r10=0000024cca32d1a0
r11=0000000000000001 r12=0000000000000000 r13=0000000000038010
r14=0000000000000002 r15=0000024cc5a59d40
iopl=0 nv up ei pl nz na pe nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202
ig9icd64!RegisterProcTableCallback+0x4f67fa:
00007ffe`7eae476a 418b4008 mov eax,dword ptr [r8+8] ds:00000000`00000008=????????
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffe7eae476a (ig9icd64!RegisterProcTableCallback+0x00000000004f67fa)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000008
Attempt to read from address 0000000000000008
PROCESS_NAME: croftengine.exe
READ_ADDRESS: 0000000000000008
ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000008
STACK_TEXT:
000000d4`458fe370 00007ffe`7eae42e6 : 0000024c`c5a59d40 000000d4`458fe710 0000024c`00000001 00007ffe`7e7427d4 : ig9icd64!RegisterProcTableCallback+0x4f67fa
000000d4`458fe440 00007ffe`7eae7232 : 00000000`000000d8 00000000`00000042 00000000`00001403 00000000`00000000 : ig9icd64!RegisterProcTableCallback+0x4f6376
000000d4`458fe4c0 00007ffe`e18393aa : 0000024c`ca5d4fe0 0000024c`ca5d4ff0 00000000`00000004 0000024c`ca25ee50 : ig9icd64!RegisterProcTableCallback+0x4f92c2
000000d4`458fe500 00007ff7`fda472f0 : 0000024c`ca5d4fe0 0000024c`ca5d4ff0 0000024c`ca25ee50 0000024c`978b44b0 : opengl32!glDrawElements+0x1a
000000d4`458fe540 00007ff7`fdcb8967 : 00000201`00000013 0000024c`ca5d4fe0 0000024c`c6a5e2a0 000000d4`458fe6a0 : croftengine!pybind11::error_already_set::what+0x175b30
000000d4`458fe570 00007ff7`fdd114be : 00000000`00000000 000000d4`458fe6b0 0000024c`bf494b40 0000024c`cabd4ad8 : croftengine!pybind11::error_already_set::what+0x3e71a7
000000d4`458fe5b0 00007ff7`fdd083cd : 00000000`00000000 0000024c`c655dbc0 00000000`00000000 0000024c`c6a32730 : croftengine!pybind11::error_already_set::what+0x43fcfe
000000d4`458fe930 00007ff7`fd955db2 : 00000000`00000000 000000d4`00000000 00007ff7`fe0335b0 00000000`00000008 : croftengine!pybind11::error_already_set::what+0x436c0d
000000d4`458fead0 00007ff7`fdac5e3c : 000000d4`458ff488 000000d4`458ff860 0000024c`bb711060 000000d4`458ff488 : croftengine!pybind11::error_already_set::what+0x845f2
000000d4`458ff3d0 00007ff7`fd9565ae : 000000d4`458ff860 0000024c`c67ccb70 000000d4`458ff808 0000024c`bf483820 : croftengine!pybind11::error_already_set::what+0x1f467c
000000d4`458ff410 00007ff7`fd8d75a7 : 00007ff7`fde855b0 000000d4`458ff550 0000024c`bb7119d8 000000d4`458ff550 : croftengine!pybind11::error_already_set::what+0x84dee
000000d4`458ff450 00007ff7`fde06e77 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffffff`ffffffff : croftengine!pybind11::error_already_set::what+0x5de7
000000d4`458ff970 00007ff7`fde05e2e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : croftengine!pybind11::error_already_set::what+0x5356b7
000000d4`458ffa00 00007fff`0ff374b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : croftengine!pybind11::error_already_set::what+0x53466e
000000d4`458ffa40 00007fff`11d826a1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
000000d4`458ffa70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21
Intel is not supported, use a dedicated graphics card.
@chris-fuchs did this answer your question? If so, I'd like to close this issue, unless you have more information.
Under the assumption that this was a run on an Intel graphics card, and that there is no other graphics card available, I'm closing this as it's a known, un-fixable issue with Intel GPUs.