{EQ2}Innerspace with ISboxer, Windows 7 Fatal Error on start

[prindan]

I am getting a fatal error when using innerspace to startup up my eq2 clients. I have EQ2 set to not startup in fullscreen mode but still get the direct 3d fatal error. I did follow the instructions for installing the Dx9 updates as well. Any help would be appreciated.

Thanks,
Mike

[prindan]

the error is:

Everquest 2 has detected an unrecoverable error and must shutdown

<verify>

E:\live\eq2\framework\core\devices\src\directx9renderdevice.ccp

(1318):

Directx error. (DCDERR_INVALIDCALL)

009ec981

[Lax]

1. First and foremost, I would probably check for video driver updates.

2. If you went into the Inner Space game configuration and messed with the display selection setting -- then it's entirely possible that you selected a display that doesn't exist and the game would be unable to set up Direct3D. If you have no idea what I'm talking about with the display selection setting then this is probably not it.

3. If the above doesn't help, then try lowering graphics settings and/or disabling shaders etc if the option is available. In EQ1 for example there used to be a problem with multiboxing and using 2.x pixel shaders, or something like that. And, also in EQ1, there was also a BSOD issue with vertex shaders on NVIDIA video cards and only when multiboxing.

[prindan]

Turns out I messed with the display settings in IS. Now it launches the first character just fine but none of the others. If I use IS to launch another it labels it IS2 but the window setup doesnt occur.

[Lax]

Is this with the "No Patch" profile, or the "Default Profile"? Definitely try the no patch profile if you're currently using the default one. You would select this per Character in ISBoxer

[prindan]

I have them all set to no patch. It only tries to start the one. Could a custom ui mess with ISboxer I am using profit UI atm.

[highlander133]

Similar issue here on Windows 7. I'm getting APPCRASH as soon as the launcher starts. I can load EQ2 outside of IS just fine, though. This just started today - 12 hours ago, I had no problems running through IS.

[highlander133]

Update on the APPCRASH: for some reason, mine seemed to be directly related to Comodo Firewall. I downloaded a Comodo update, then started getting the error. Uninstalled Comodo, rebooted, and IS works just like before. Reinstalled, set Comodo to Training mode to try to see when IS was triggering Comodo, and no warnings popped up, but IS did the same thing again.

[Lax]

Odd. I'll have to see if I can do something about that, thanks for the information.