Error creating D3D device ... Ennemy Engage: Comanche Hokum
This game run fine with a Dell LCD 24" in anaglyphic mode but when I switched to the Samsung DLP TV it would not start and gave this popup error:

Error creating d3d device2: DDERR_INVALIDOBJECT

This is a classic heli sim and I've been hoping it would work with the DLP since I don't have the Samsung 2033RXZ monitor. Team NVidia 3DV please fix this or provide a workaround is possible. It would be a great gesture to the S3D sim community (heheh I assume it would be anyway).
This game run fine with a Dell LCD 24" in anaglyphic mode but when I switched to the Samsung DLP TV it would not start and gave this popup error:



Error creating d3d device2: DDERR_INVALIDOBJECT



This is a classic heli sim and I've been hoping it would work with the DLP since I don't have the Samsung 2033RXZ monitor. Team NVidia 3DV please fix this or provide a workaround is possible. It would be a great gesture to the S3D sim community (heheh I assume it would be anyway).

Xeon X5675 hex cores @4.4 GHz, GTX 1070, win10 pro
i7 7700k 5GHz, RTX 2080, win10 pro
Benq 2720Z, w1070, Oculus Rift cv1, Samsung Odyssey+

#1
Posted 07/05/2009 12:17 AM   
Hi what version are you using are you patched to the latest patch?? I would check out SimHQ as they have some of the modders hang out there ..
Hi what version are you using are you patched to the latest patch?? I would check out SimHQ as they have some of the modders hang out there ..

Intel i5 7600K @ 4.8ghz / MSI Z270 SLI / Asus 1080GTX - 416.16 / Optoma HD142x Projector / 1 4'x10' Curved Screen PVC / TrackIR / HOTAS Cougar / Cougar MFD's / Track IR / NVidia 3D Vision / Win 10 64bit

#2
Posted 07/05/2009 03:30 PM   
I patched it to the latest community patch. It only has this problem when switching to DLP I thought it might have something to do with the way 3D Vision works, but it could as well be an issue with the game itself not knowing how to deal with DLP TV as a display device. Thanks for the pointer, I will wander over to simHQ to drop a few lines.
I patched it to the latest community patch. It only has this problem when switching to DLP I thought it might have something to do with the way 3D Vision works, but it could as well be an issue with the game itself not knowing how to deal with DLP TV as a display device. Thanks for the pointer, I will wander over to simHQ to drop a few lines.

Xeon X5675 hex cores @4.4 GHz, GTX 1070, win10 pro
i7 7700k 5GHz, RTX 2080, win10 pro
Benq 2720Z, w1070, Oculus Rift cv1, Samsung Odyssey+

#3
Posted 07/05/2009 08:03 PM   
I was able to get passed the error creating d3d device by changing to a different resolution using the LCD display prior to switching to the DLP display. However here it stuck again, crash.log file details shows an access violation. How the hell do I get to a forbidden memory location by just switching a display device I have no idea.

----start crash.log--
executable build date: May 28 2009
Executable build time: 23:03:56

Crash details:

Location: 00000003
Reason: Access violation
Tried to read from memory location: 0x00000003

Register dump:
EAX: 0x00000003
EBX: 0x063ec540
ECX: 0x00000000
EDX: 0x001857f8
EDI: 0x02daf440
ESI: 0x041d6800
EBP: 0x02daf464
ESP: 0x02daf41c
EIP: 0x00000003


Floating point details:
Control word: 0xffff0e7f
Status word: 0xffff4020
ST(0): 7fe43c3494010000ffff
ST(1): 0010010000000000ffff
ST(2): 0000000000000000ffff
ST(3): 1000000000000000ffff
ST(4): 0000000000000080ff3f
ST(5): bbe8b42c0f920143ffff
ST(6): 0000000000000080ff3f
ST(7): 0000000000000080ff3f

...
some more stack dump here
----------end crash.log---------
I was able to get passed the error creating d3d device by changing to a different resolution using the LCD display prior to switching to the DLP display. However here it stuck again, crash.log file details shows an access violation. How the hell do I get to a forbidden memory location by just switching a display device I have no idea.



----start crash.log--

executable build date: May 28 2009

Executable build time: 23:03:56



Crash details:



Location: 00000003

Reason: Access violation

Tried to read from memory location: 0x00000003



Register dump:

EAX: 0x00000003

EBX: 0x063ec540

ECX: 0x00000000

EDX: 0x001857f8

EDI: 0x02daf440

ESI: 0x041d6800

EBP: 0x02daf464

ESP: 0x02daf41c

EIP: 0x00000003





Floating point details:

Control word: 0xffff0e7f

Status word: 0xffff4020

ST(0): 7fe43c3494010000ffff

ST(1): 0010010000000000ffff

ST(2): 0000000000000000ffff

ST(3): 1000000000000000ffff

ST(4): 0000000000000080ff3f

ST(5): bbe8b42c0f920143ffff

ST(6): 0000000000000080ff3f

ST(7): 0000000000000080ff3f



...

some more stack dump here

----------end crash.log---------

Xeon X5675 hex cores @4.4 GHz, GTX 1070, win10 pro
i7 7700k 5GHz, RTX 2080, win10 pro
Benq 2720Z, w1070, Oculus Rift cv1, Samsung Odyssey+

#4
Posted 07/05/2009 10:44 PM   
Scroll To Top