AnKor's Shader issue

G

grover1

Charter Member
Hi all,

Recently got ETO 1.50 up and running - or so I thought. I keep getting this application error "The application was unable to start correct (0xc0000005). Click okay to close the application" whenever I go to load the game. This issue came up after I installed AnKor's shaders into ETO 1.50.

Any suggestions?

Thanks
 
0.00: Start - DLL Version Nov 23 2019
0.54: D3DWrapper::GetAdapterDisplayMode - 1920, 1080, 60, 22
0.70: D3DWrapper::GetAdapterDisplayMode - 1920, 1080, 60, 22
0.70: D3DWrapper::CreateDevice - NVIDIA GeForce GTX 970 (Driver Version: 27.21.14.6172)
0.70: D3DWrapper::CreateDevice - Hardware Vertex Processing
0.70: D3DWrapper::CreateDevice - Adapter: 0, Type: 1, Flags: 0x43
0.70: D3DWrapper::CreateDevice - Windowed: 0, Width: -65276, Height: 1199562752, Refresh: 0, Format: 8473092, Multisampling: 0
0.70: D3DWrapper::CreateDevice - AutoDepthStencil: 1 Format: 75
0.70: D3DWrapper::CreateDevice - SwapEffect: 1, PresentationInterval: 0, BackBufferCount: 1
0.70: D3DWrapper::CreateDevice - D3D9Ex is disabled.
0.70: D3DWrapper::CreateDevice - CreateDevice call - FAILED. HR = 0x8876086C
0.85: DllMain - Exit.
 
My most recent log with the December 2019 AnKor' shaders. All previous versions work:

0.00: Start - DLL Version Nov 23 2019
0.55: D3DWrapper::GetAdapterDisplayMode - 1920, 1080, 60, 22
0.74: D3DWrapper::GetAdapterDisplayMode - 1920, 1080, 60, 22
0.74: D3DWrapper::CreateDevice - NVIDIA GeForce GTX 970 (Driver Version: 27.21.14.6172)
0.74: D3DWrapper::CreateDevice - Hardware Vertex Processing
0.74: D3DWrapper::CreateDevice - Adapter: 0, Type: 1, Flags: 0x42
0.74: D3DWrapper::CreateDevice - Windowed: 0, Width: 1920, Height: 1080, Refresh: 0, Format: 22, Multisampling: 0
0.74: D3DWrapper::CreateDevice - AutoDepthStencil: 1 Format: 75
0.74: D3DWrapper::CreateDevice - SwapEffect: 1, PresentationInterval: 0, BackBufferCount: 1
0.74: D3DWrapper::CreateDevice - D3D9Ex is disabled.
0.83: FakeDevice::FakeDevice - Available Texture Memory 4072 MB
0.94: create_minidump - Unhandled Exception 0xC0000005 at EIP=0x100100F2 (dll base is 0x67050000)
2.51: DllMain - Exit.
 
Try setting UseD3D9Ex=1 and WindowedMode=1 in d3d8.ini and then run cfs3config.exe to make sure the resolution is set to your screen default.
Then run the game and lets see what's different in the log.
 
0.00: Start - DLL Version Nov 23 2019
0.58: D3DWrapper::GetAdapterDisplayMode - 1920, 1080, 60, 22
0.58: D3DWrapper::GetAdapterDisplayMode - 1920, 1080, 60, 22
0.58: D3DWrapper::CreateDevice - NVIDIA GeForce GTX 970 (Driver Version: 27.21.14.6172)
0.58: D3DWrapper::CreateDevice - Hardware Vertex Processing
0.58: D3DWrapper::CreateDevice - Adapter: 0, Type: 1, Flags: 0x42
0.58: D3DWrapper::CreateDevice - Windowed: 1, Width: 1920, Height: 1080, Refresh: 0, Format: 22, Multisampling: 0
0.58: D3DWrapper::CreateDevice - AutoDepthStencil: 1 Format: 75
0.58: D3DWrapper::CreateDevice - SwapEffect: 5, PresentationInterval: 0, BackBufferCount: 2
0.58: D3DWrapper::CreateDevice - D3D9Ex is enabled.
0.67: FakeDevice::FakeDevice - Available Texture Memory 4095 MB
1.80: create_minidump - Unhandled Exception 0xC0000005 at EIP=0x100100F2 (dll base is 0x66F50000)
4.31: DllMain - Exit.
 
Hi! Sorry for the delay, I don't visit forums often these days.

When you see negative or weird numbers like "Width: -65276, Height: 1199562752" this means you have to run cfs3config and select your display resolution instead of using the default one.
I see your next log already has the correct resolution, but something else goes wrong.

"Unhandled Exception 0xC0000005 at EIP=0x100100F2 (dll base is 0x66F50000)" is a location in the code where the error happened and it might be possible for me to find the cause. But I don't have enough free time these days to dig in the code, so I don't know when I can look into it.

Latest shader versions were pretty stable, so maybe something is missing in the install or something else interferes with it.

"The application was unable to start correctly" is an unusual error for me, I haven't seen it before. Some googling tells that it may be caused by an antivirus scanner blocking the application. My dll modifies cfs3 code at runtime and this may trigger an antivirus because this isn't what dlls normally do, but I think it is unlikely - I don't remember such cases before.
 
Thanks, AnKor. I think something is missing in my install as I've got other issues with the game as well. I'm going to try reinstalling the game and see what happens.
 
You must log in or register to reply here.
Back
Top