BUG: VFX screen is AWOL... is1, is3 - where is is2?

Lax,

I run across this quite often where the 'ghost' processes are causing us to start at a "is" screen number higher than 1 or miss an "is" screen at character set launch, particularly with a 5-man team. What this does is breaks our configs and makes us manually close out all of the windows after the missing "is"es and/or start over.

Would it be possible for Innerspace/ISBoxer to do a wipe of the offending processes prior to launching the character set? This way we might get all of our characters with their SLOT matched to the corresponding "is" VFX screen?

Even when I use the "sessions" command, I see 0 processes found before launch, but still encounter the problem.

If not, any ideas on how to fix this (recurring) issue?

Thanks!

[lax]

Would it be possible for Innerspace/ISBoxer to do a wipe of the offending processes prior to launching the character set?

I need to know what the offending processes are first? This is likely an issue specific to Neverwinter.

I can't wipe everything because re-launching your Character Set is, by design, a way to update instances already there or to re-launch the missing ones in your set.

Would it be possible for Innerspace/ISBoxer to do a wipe of the offending processes prior to launching the character set?

I need to know what the offending processes are first? This is likely an issue specific to Neverwinter.

I can't wipe everything because re-launching your Character Set is, by design, a way to update instances already there or to re-launch the missing ones in your set.

Just reported everything from the crash (about 5-6 crash reports) - hopefully that will help.

It wouldn't suprise me if it is Neverwinter specific since it's such a new game and I know there are still plenty of bugs in the game.

I think I've discovered what is causing the problem... it appears that Innerspace is giving is1 to the launcher instead of the game itself - hence the game executable is starting at is2, or sometimes missing an 'is' screen (because the launcher closes itself, leaving an 'is' missing).

This is evidenced by 'is1' as an active session in the console.

Any way to stop Innerspace from counting the launcher?

[lax]

Yes, I've updated the development build as of now

Right click IS, select Patcher, check "Download development (test) patches" then close and restart Inner Space to let it patch up. This should no longer happen. Let me know

Works great - you're awesome Lax!

[lax]

Actually somehow I think I failed to patch it in until just now. Oops.