Sessions Not Loading

Kannkor

Ogre
With the most recent Innerspace (Build 6255), a lot of people started having problems with Everquest2 not loading.

Lax has been working on a fix for it. If you wish to try it it's on the dev build (6257).

<~Lax> dev build 6257 includes an Inner Space Loader aggressiveness option
<~Lax> people having compatibility issues with games not launching, or freezing, or crashing and such generally at startup, can try setting this to Minimum
<~Lax> generally at startup, but not always at startup.
 

Oren

Member
Not sure if im the only one or not, but this has been an ongoing issue for me for months.

I found an old topic that suggested using an older version of Inner Space (v1.15 Build 6174). Fixed the loading problems for me immediately.

The downside is that i crash noticeably more often.

PS. i did try downloading the most recent version, and the test version that you had suggested above, neither of which fixed the issue for me. so i went back to 6174
 

Multicharacter

Senior Member
When you go to Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers in your registry do you see Everquest II listed Name, and an extension listed under Data 'Ignore Free library extension.dll'? I found when it stops loading sessions if I rename the folder the game is in, then update IS settings to the new path the game suddenly starts working. Eventually I traced it to registry entries in that tree, and I go in and delete it everytime it gets added back in (Windows does it automatically).
 

Cheesy

Well-Known Member
My innerspace updated to build 6257 today and since I've not been able to launch any clients at all. Anybody else experiencing this?
 

Khordach

New Member
My innerspace updated to build 6257 today and since I've not been able to launch any clients at all. Anybody else experiencing this?
I had to set the game configuration to have "Inner Space Loader Aggressiveness" to minimum in the game configuration to get EQ2 to load at all. Now ISXEQ2 won't load, as it says "Inner Space is using ISXDK v35 and this extension was build with a different version"

For the record, I have IS 6258 right now, thinking about downgrading some.
 

EmpireSec

New Member
After the 3/6/2018 Daybreak and other patches, I got the loading problem. However that only happened on two of my three machines. On the two, running the regular Launcher, validating the files, logging in and out of a character, then launching Inner Space worked again. At least until the next day. Windows 10 security patch inadvertently causing Inner Space issues?

Got the two machines properly working by rolling back to Build 6233, from https://www.lavishsoft.com/innerspace/archives
Read thread https://www.isxgames.com/f/threads/crashing-solution.8153/ for general patching instructions.

Thanks Godelpus.
 

EmpireSec

New Member
Outstanding. Thanks Kannkor.

Spoke too soon about machine 1 of 3. Security patch went in, and nothing loaded afterwards. Will try the fix later.
 
Top Bottom