Inner Space not working for me with Vanguard:SOH

Svaberendk · Post by **Svaberendk** » Wed Aug 11, 2010 9:32 pm

Ok, tried the station launcher set to close down after the game has launched so IS could load another instance. No go. I tried the original executable first since it can load as many instances without having to log out and that was a failure too.

I can't use the old build anymore either for some reason. I have tried deleting the whole folder and replacing it with the older build that worked without patching ofc. Still does the same thing.

As for the console is there a command i need to type in to get additional info?

All it says is "endscript isboxer failed" without adding any other detail as to why

ProdigyGamer · Post by **ProdigyGamer** » Wed Aug 11, 2010 10:08 pm

I tried the new build also Lax but had no luck. from your last post, I was watching IS as VG launched to see what was happening and it shows 3 lines:

Session launched (is20): "C:/Program Files (x86)/Sony/Vanguard/Vanguard.exe"
Session launched (is21) "C:/Program Files (x86)/Sony/Station/LaunchPad.exe"
Session launched (is1): "C/Program Files (x86)/Sony/Vanguard/bin/vgclient.exe"

Is that what Inner Space is supposed to do, try to launch from my VG bin folder?

I did not have ISBoxer installed at all untill this latest update LAx, would that make a difference?

Post by **Lax** » Thu Aug 12, 2010 9:35 am

ProdigyGamer: You don't need ISBoxer if you weren't using it before or planning to use it, I was kind of assuming

I'm not sure your issue is quite the same as Svaberendk's

Build 5225 is now up as a development build. This should fix Svaberendk's current issue, not sure about ProdigyGamer's.

Svaberendk: I will get to the mouse issue you mentioned but check and make sure the game itself isn't set to full screen mode. ISBoxer will force the game into a window with the new builds of IS, but there's a reported bug with the mouse if the game is in full screen and forced into a window (at least with EQ1).

Post by **Lax** » Thu Aug 12, 2010 10:46 am

Okay, build 5227 fixes the forced full screen mouse issue. If the game is in full screen the mouse should work fine now, but you should put it in windowed mode for the best look and feel. Otherwise, the full screen resolution selected in the game is stretched to match the window size, and if it's a different aspect ratio it will look pretty bad

ProdigyGamer · Post by **ProdigyGamer** » Thu Aug 12, 2010 12:30 pm

Lax wrote:ProdigyGamer: You don't need ISBoxer if you weren't using it before or planning to use it, I was kind of assuming I'm not sure your issue is quite the same as Svaberendk's

Build 5225 is now up as a development build. This should fix Svaberendk's current issue, not sure about ProdigyGamer's.

Svaberendk: I will get to the mouse issue you mentioned but check and make sure the game itself isn't set to full screen mode. ISBoxer will force the game into a window with the new builds of IS, but there's a reported bug with the mouse if the game is in full screen and forced into a window (at least with EQ1).

I thought you knew what I was on about lol

In saying that, i have not installed anything else "yet" as I have not been able to get IS to work, so I am back to square one and am out of idea's

Svaberendk · Post by **Svaberendk** » Thu Aug 12, 2010 5:28 pm

First I want to say thanks for the time spent trying to solve this issue for both of us. I know you probably have a lot to try and solve from other people at the same time.

Second. This build works so far with station launcher. It launches and attach itself in windows layout perfectly. The only last issue for me is the mouse cursor. It's still a bit off. It points above where it activates.

Svaberendk · Post by **Svaberendk** » Fri Aug 13, 2010 5:15 pm

Now nothing works. Can't even launch the first instance without a crash. 6 hours ago everything worked just fine even the mouse issue was solved

ProdigyGamer · Post by **ProdigyGamer** » Wed Aug 18, 2010 5:56 am

Any news on this yet Lax?

I know your a busy man and I don't want to pester you but its going on 3 weeks that I have been subscribed and I still can't use Inner Space.

It's frustrating, I would rather the program work than request a refund as I have heard so many good things about IS but paying for something I have not been able to use is annoying bud.

Post by **Lax** » Wed Aug 18, 2010 12:05 pm

Sorry I've been out of town for the last several days, and could not work on this. I can refund you if we don't get Vanguard working for you, but I will be working on it again in the next few days

Svaberendk · Post by **Svaberendk** » Wed Aug 18, 2010 7:14 pm

I respect what you do and the work you put into it to ever ask for a refund. I'll do you one better and subscribe for a year if you get it to work and I can run it for at least a month

.

If you need more participation from my part in form of better info or specific info then please let me know.

Today I completely removed everything and downloaded the bundle again. I did everything over. Running the wizard, creating the team selecting vanguard I can get one instance of it to run again. The second one never loads

ProdigyGamer · Post by **ProdigyGamer** » Thu Aug 19, 2010 8:33 am

Lax wrote:Sorry I've been out of town for the last several days, and could not work on this. I can refund you if we don't get Vanguard working for you, but I will be working on it again in the next few days

np man, welcome back.

As i said i would much rather get it working, I have been itching to try this out after hearing so many good things and its killing me not being able to use it lol

Apart from formatting my PC I am not sure what there is left for me to do, if you require anything from me please let me know.

Post by **Lax** » Sat Aug 28, 2010 1:19 pm

Sorry again for the delay, I am working on testing this right now. And unfortunately for you two, it's working for me on Vista and Windows 7, using the latest Station Launcher.

ProdigyGamer:
I need some diagnostic info from you. Right click IS and select Console. In the console enter the command "diag" with no quotes. It will open up info in notepad, which you can paste to me here or in email to lax@lavishsoft.com

Svaberendk:

Today I completely removed everything and downloaded the bundle again. I did everything over. Running the wizard, creating the team selecting vanguard I can get one instance of it to run again. The second one never loads

I don't have enough information to tell whether this is due to what I previously explained:

"You can check the main Inner Space console to see why it isn't launching the next one, if you want. If I had to guess, it's probably trying to launch the launcher again, and the launcher is ignoring it because it was already open. To check the console, right click IS and select Console. It logs information there as it tries to launch your character set." From what you said it doesn't sound like you've checked the console for more information.

ProdigyGamer · Post by **ProdigyGamer** » Sat Aug 28, 2010 11:50 pm

Inner Space Kernel 1.10 Build 5227

System:
-----------------------------------
Windows Version: Windows 7 Ultimate//7600.win7_gdr.100618-1621
Process Memory Usage: 54MB
System Physical RAM: 2442/4055MB
Page File: 5926/8108MB
Virtual Memory: 1854/2047MB (Extended: 0MB)
CPU 1: Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz @ 2793MHz
CPU 2: Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz @ 2793MHz
CPU 3: Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz @ 2793MHz
CPU 4: Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz @ 2793MHz
CPU 5: Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz @ 2793MHz
CPU 6: Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz @ 2793MHz
CPU 7: Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz @ 2793MHz
CPU 8: Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz @ 2793MHz
CPU Affinity Mask: 0xFF
Video 1: \\.\DISPLAY1/ATI Radeon HD 5700 Series
Video 2: \\.\DISPLAY2/ATI Radeon HD 5700 Series
Video 3: \\.\DISPLAY3/ATI Radeon HD 5700 Series
Video 4: \\.\DISPLAYV1/RDPDD Chained DD
Video 5: \\.\DISPLAYV2/RDP Encoder Mirror Driver
Video 6: \\.\DISPLAYV3/RDP Reflector Display Driver
Sound: ?
DirectX: 4.09.00.0904
Internet Explorer: 8.0.7600.16385

Loaded Modules:
-----------------------------------
Module 0x00400000-0x004B1000: C:\Program Files (x86)\InnerSpace\InnerSpace.exe (Thu Aug 12 15:12:18 2010)
Module 0x00890000-0x008AE000: C:\Program Files (x86)\InnerSpace\IS-D3D9Engine.dll (Thu Aug 12 15:10:44 2010)
Module 0x03000000-0x0318B000: C:\Program Files (x86)\InnerSpace\IS-Kernel.dll (Thu Aug 12 15:10:45 2010)
Module 0x03900000-0x03963000: C:\Program Files (x86)\InnerSpace\IS-VirtualInput.dll (Thu Aug 12 15:11:03 2010)
Module 0x05000000-0x0515F000: C:\Program Files (x86)\InnerSpace\ISUI.dll (Thu Aug 12 14:26:46 2010)
Module 0x10000000-0x1001E000: C:\Program Files (x86)\InnerSpace\Lavish.dll (Wed Aug 11 14:53:15 2010)
Module 0x60610000-0x60616000: C:\Windows\Microsoft.NET\Framework\v2.0.50727\fusion.dll (Thu Jun 04 05:16:14 2009)
Module 0x641F0000-0x645A7000: C:\Windows\system32\d3dx9_37.dll (Wed Mar 05 00:54:53 2008)
Module 0x680C0000-0x68327000: C:\Windows\system32\WMVCore.dll (Tue Jul 14 01:09:30 2009)
Module 0x683C0000-0x683F0000: C:\Windows\system32\DINPUT8.dll (Tue Jul 14 01:05:05 2009)
Module 0x688C0000-0x688FD000: C:\Windows\system32\WMASF.DLL (Tue Jul 14 01:12:08 2009)
Module 0x6BB10000-0x6BB19000: C:\Windows\system32\hid.dll (Tue Jul 14 01:05:48 2009)
Module 0x6CD70000-0x6D142000: C:\Windows\system32\atiumdag.dll (Wed Jul 07 01:28:20 2010)
Module 0x6D760000-0x6D8F0000: C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7600.16385_none_72fc7cbf861225ca\gdiplus.dll (Tue Jul 14 01:03:50 2009)
Module 0x6D8F0000-0x6D8F5000: C:\Windows\system32\MSIMG32.dll (Tue Jul 14 01:08:48 2009)
Module 0x707D0000-0x70D61000: C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll (Thu May 13 10:29:46 2010)
Module 0x70DB0000-0x70DC3000: C:\Windows\system32\dwmapi.dll (Tue Jul 14 01:06:15 2009)
Module 0x71910000-0x71976000: C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll (Thu Mar 18 07:39:21 2010)
Module 0x71980000-0x719CA000: C:\Windows\system32\mscoree.dll (Fri Nov 06 05:09:24 2009)
Module 0x71F00000-0x71F38000: C:\Windows\System32\fwpuclnt.dll (Tue Jul 14 01:06:15 2009)
Module 0x72390000-0x723A2000: C:\Windows\system32\dhcpcsvc.DLL (Tue Jul 14 01:04:53 2009)
Module 0x724D0000-0x72550000: C:\Windows\system32\uxtheme.dll (Tue Jul 14 01:11:24 2009)
Module 0x727A0000-0x727DB000: C:\Windows\system32\rsaenh.dll (Tue Jul 14 01:09:52 2009)
Module 0x727E0000-0x727F6000: C:\Windows\system32\CRYPTSP.dll (Tue Jul 14 01:07:09 2009)
Module 0x72800000-0x72805000: C:\Windows\System32\wshtcpip.dll (Tue Jul 14 01:11:54 2009)
Module 0x72820000-0x72826000: C:\Windows\system32\rasadhlp.dll (Tue Jul 14 01:09:42 2009)
Module 0x72850000-0x72857000: C:\Windows\system32\WINNSI.DLL (Tue Jul 14 01:11:31 2009)
Module 0x72860000-0x7287C000: C:\Windows\system32\IPHLPAPI.DLL (Tue Jul 14 01:06:35 2009)
Module 0x72880000-0x728A4000: C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL (Tue Aug 18 18:28:20 2009)
Module 0x728B0000-0x728C2000: C:\Windows\system32\pnrpnsp.dll (Tue Jul 14 01:10:14 2009)
Module 0x728D0000-0x728E0000: C:\Windows\system32\napinsp.dll (Tue Jul 14 01:07:57 2009)
Module 0x728E0000-0x728E8000: C:\Windows\System32\winrnr.dll (Tue Jul 14 01:11:32 2009)
Module 0x728F0000-0x72934000: C:\Windows\system32\DNSAPI.dll (Tue Jul 14 01:05:29 2009)
Module 0x72940000-0x7297C000: C:\Windows\system32\mswsock.dll (Tue Jul 14 01:08:07 2009)
Module 0x72980000-0x72990000: C:\Windows\system32\NLAapi.dll (Tue Jul 14 01:08:12 2009)
Module 0x729D0000-0x72A6B000: C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4927_none_d08a205e442db5b5\MSVCR80.dll (Thu Jun 04 04:52:15 2009)
Module 0x73050000-0x73059000: C:\Windows\system32\VERSION.dll (Tue Jul 14 01:11:07 2009)
Module 0x731B0000-0x734B2000: C:\Windows\system32\atiumdva.dll (Wed Jul 07 01:23:14 2010)
Module 0x734C0000-0x734C9000: C:\Windows\system32\atiu9pag.dll (Wed Jul 07 01:14:45 2010)
Module 0x734D0000-0x73552000: C:\Windows\system32\aticfx32.dll (Wed Jul 07 01:54:08 2010)
Module 0x73560000-0x73566000: C:\Windows\system32\d3d8thk.dll (Tue Jul 14 01:04:40 2009)
Module 0x73570000-0x73733000: C:\Windows\system32\d3d9.dll (Tue Jul 14 01:04:41 2009)
Module 0x74530000-0x74562000: C:\Windows\system32\WINMM.dll (Tue Jul 14 01:11:30 2009)
Module 0x75180000-0x7518C000: C:\Windows\syswow64\CRYPTBASE.dll (Mon Jul 13 23:12:01 2009)
Module 0x75190000-0x751F0000: C:\Windows\syswow64\SspiCli.dll (Fri Dec 11 07:36:33 2009)
Module 0x75440000-0x754C4000: C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7600.16385_none_ebf82fc36c758ad5\COMCTL32.dll (Tue Jul 14 01:06:44 2009)
Module 0x754D0000-0x754F7000: C:\Windows\syswow64\CFGMGR32.dll (Tue Jul 14 01:04:38 2009)
Module 0x75500000-0x7565C000: C:\Windows\syswow64\ole32.dll (Tue Jul 14 01:09:27 2009)
Module 0x75660000-0x75700000: C:\Windows\syswow64\ADVAPI32.dll (Tue Jul 14 01:03:58 2009)
Module 0x75700000-0x75757000: C:\Windows\syswow64\SHLWAPI.dll (Tue Jul 14 01:10:29 2009)
Module 0x758A0000-0x758CD000: C:\Windows\syswow64\WINTRUST.dll (Tue Dec 29 06:53:28 2009)
Module 0x758D0000-0x759C0000: C:\Windows\syswow64\RPCRT4.dll (Tue Jul 14 01:11:23 2009)
Module 0x759C0000-0x75A5D000: C:\Windows\syswow64\USP10.dll (Tue Jul 14 01:11:14 2009)
Module 0x75B50000-0x75CED000: C:\Windows\syswow64\SETUPAPI.dll (Tue Jul 14 01:10:22 2009)
Module 0x75CF0000-0x75D02000: C:\Windows\syswow64\DEVOBJ.dll (Tue Jul 14 01:05:09 2009)
Module 0x75D10000-0x75D56000: C:\Windows\syswow64\KERNELBASE.dll (Tue Jul 14 01:14:07 2009)
Module 0x75D60000-0x75E7C000: C:\Windows\syswow64\CRYPT32.dll (Tue Jul 14 01:07:05 2009)
Module 0x75E80000-0x75F80000: C:\Windows\syswow64\kernel32.dll (Tue Jul 14 01:14:06 2009)
Module 0x75F80000-0x7604C000: C:\Windows\syswow64\MSCTF.dll (Tue Jul 14 01:07:53 2009)
Module 0x76150000-0x761DF000: C:\Windows\syswow64\OLEAUT32.dll (Wed Apr 07 07:07:41 2010)
Module 0x761E0000-0x762E0000: C:\Windows\syswow64\USER32.dll (Tue Jul 14 01:11:24 2009)
Module 0x762E0000-0x7638C000: C:\Windows\syswow64\msvcrt.dll (Tue Jul 14 01:07:59 2009)
Module 0x76390000-0x76FD9000: C:\Windows\syswow64\SHELL32.dll (Tue Jul 27 13:57:01 2010)
Module 0x76FE0000-0x76FE5000: C:\Windows\syswow64\PSAPI.DLL (Tue Jul 14 01:09:34 2009)
Module 0x76FF0000-0x76FF6000: C:\Windows\syswow64\NSI.dll (Tue Jul 14 01:09:45 2009)
Module 0x77000000-0x7700C000: C:\Windows\syswow64\MSASN1.dll (Sat Aug 29 06:52:40 2009)
Module 0x77010000-0x7701A000: C:\Windows\syswow64\LPK.dll (Tue Jul 14 01:11:23 2009)
Module 0x77020000-0x770B0000: C:\Windows\syswow64\GDI32.dll (Tue Jul 14 01:11:20 2009)
Module 0x770B0000-0x7712B000: C:\Windows\syswow64\COMDLG32.dll (Tue Jul 14 01:06:45 2009)
Module 0x77130000-0x77165000: C:\Windows\syswow64\WS2_32.dll (Tue Jul 14 01:11:38 2009)
Module 0x77170000-0x77189000: C:\Windows\SysWOW64\sechost.dll (Tue Jul 14 01:10:28 2009)
Module 0x771C0000-0x77220000: C:\Windows\system32\IMM32.DLL (Tue Jul 14 01:11:21 2009)
Module 0x77620000-0x777A0000: C:\Windows\SysWOW64\ntdll.dll (Wed Mar 24 06:35:08 2010)

Display
-------------------------------------
Driver Info: ATI Radeon HD 5700 Series/aticfx32.dll/8/17/10/1036
Adapter display mode: 1920x1200 D3DFMT_X8R8G8B8
Current display mode: 784x562 D3DFMT_X8R8G8B8 (windowed)
Window viewable size: 784x562
Display Scale: 100.0%x100.0%, Distortion: 0.0%
MaxFPS Foreground: 60 (Calculate)
MaxFPS Background: 30 (Absolute)

ProdigyGamer · Post by **ProdigyGamer** » Sat Sep 04, 2010 4:58 am

Any breakthroughs or luck with this fix yet Lax?

Anything I can do to help with info?

Post by **Lax** » Sat Sep 04, 2010 6:58 am

Build 5241 went live yesterday and could possibly solve your issue. I can't tell for sure because I can't reproduce your issue. Try it and let me know