Wildstar Free to Play

[tking544]

When I launch the game through IS 32bit the launcher comes up fine but then when i select play I get a crash error.

When I launch the game client through IS 64bit I get an error saying there is no wildstar.exe, even though I have it pointed to the client64 folder and wildstar64.exe. And of course when I try to launch the 32bit launcher nothing happens at all, because I am on the 64bit IS.

Im running Windows 10, maybe thats why I'm having issues, I dont know.

I have read that skipping the launcher in this game is not possible, which is why I think trying to launch in 64bit isnt working.

Thanx for all the help, I really appreciate it, glad i chose this software!

Thomas

[lax]

When I launch the game through IS 32bit the launcher comes up fine but then when i select play I get a crash error.

When I launch the game client through IS 64bit I get an error saying there is no wildstar.exe, even though I have it pointed to the client64 folder and wildstar64.exe. And of course when I try to launch the 32bit launcher nothing happens at all, because I am on the 64bit IS.

Im running Windows 10, maybe thats why I'm having issues, I dont know.

I have read that skipping the launcher in this game is not possible, which is why I think trying to launch in 64bit isnt working.

Thanx for all the help, I really appreciate it, glad i chose this software!

Thomas

I am also running Windows 10. Windows 10 is not the reason you are having issues, no. However, if you put your mouse cursor over the IS icon in the system tray and it says 1.13 Build 6102 instead of 1.14 Build 6103, then what you're describing is expected, and you need to do what I said to switch to the development build.

If you are still having crash issues with Inner Space 1.14 Build 6103, then from here we need to follow standard operating procedure because probably some other program is interfering. I need "Diagnostics for game crashes" (http://isboxer.com/wiki/Diagnostics) from ISBoxer's Help menu.

[tking544]

I have the Dev build and still get the crash when trying to play from the launcher, but only when i launch the game with IS.

Normal game launch: http://pastebin.com/6PKVZ1Pf

IS game launch: http://pastebin.com/jgvQmr66

[tking544]

Here is the crash
http://s23.postimg.org/4d2snxtwb/wildstar_crash.png

[lax]

Here is why it is crashing:

Code:

Application Compatibility flags under HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers:
0 C:\Program Files (x86)\Diablo III\Diablo III.exe: HIGHDPIAWARE
0 C:\Program Files (x86)\NCSOFT\WildStar\Wildstar.exe: ~ WINXPSP2
0 C:\Program Files (x86)\NCSOFT\WildStar\Client64\WildStar64.exe: ~ WIN7RTM

To fix it, remove the Windows compatibility settings from both the WildStar launcher and client executables. You can do that by right clicking them and selecting Properties, and then it's on the compatibility tab.

Otherwise, you can also use RegEdit. Windows+R will bring up the Run program window, put in "regedit.exe" and click OK. Navigate to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers and remove the entries for WildStar

[tking544]

Same issue even after reverting the compatibility

http://pastebin.com/XtVc2D1R

I must be doing something wrong

[lax]

I need the diagnostics for WildStar64.exe as it is what is crashing for you, and not the launcher. Launch the game without IS, and get diagnostics for WildStar64.exe.

But, from here we should probably be shutting down other running programs, including CCC.exe and mom.exe.

[MiRai]

Same issue even after reverting the compatibility

http://pastebin.com/XtVc2D1R

I must be doing something wrong

In addition to what Lax said, there is a list of AMD stuff to shut down:

Code:

2. amdacpusrsvc.exe - Process ID: 1940 (C:\Program Files\AMD\{920DEC42-4CA5-4d1d-9487-67BE645CDDFC}\amdacpusrsvc.exe) [Admin:NO] [x64] [2.15.30.0019] [Advanced Micro Devices] [AMD ACP Binaries]
8. CCC.exe - Process ID: 5360 (C:\Program Files (x86)\AMD\ATI.ACE\Core-Static\CCC.exe) [Admin:NO] [x64] [4.5.0.0] [Advanced Micro Devices Inc.] [Catalyst Control Center: Host application]
26. Fuel.Service.exe - Process ID: 1872 (C:\Program Files\AMD\ATI.ACE\Fuel\Fuel.Service.exe) [Admin:NO] [x64] [1.0.0.0] [Advanced Micro Devices, Inc.] [AMD Fuel Service]
34. MOM.exe - Process ID: 5272 (C:\Program Files (x86)\AMD\ATI.ACE\Core-Static\MOM.exe) [Admin:NO] [x64] [4.5.0.0] [Advanced Micro Devices Inc.] [Catalyst Control Center: Monitoring program]
47. SLSTaskbar.exe - Process ID: 5472 (C:\Program Files (x86)\AMD\ATI.ACE\Core-Static\SLSTaskbar.exe) [Admin:NO] [x86] [1.0.0.1] [Advanced Micro Devices, Inc.] [Eyefinity Taskbar Application]
48. SLSTaskbar64.exe - Process ID: 5540 (C:\Program Files (x86)\AMD\ATI.ACE\Core-Static\SLSTaskbar64.exe) [Admin:NO] [x64] [1.0.0.1] [Advanced Micro Devices, Inc.] [Eyefinity Taskbar Application]

If you're actually running Eyefinity, then you may want to disable that and test.

[tking544]

Okay, I ended all those processes and here is the wildstar54.exe

http://pastebin.com/JuVmehMZ


Here is a pastebin of the wildstar64.exe launched through IS after the crash, it sits suspended until I end task

http://pastebin.com/MSc9AZw4

[lax]

Here is a pastebin of the wildstar64.exe launched through IS after the crash, it sits suspended until I end task

In that case, see if you can get "Diagnostics for game freezes" from the suspended wildstar64.exe. E-mail the file to lax@lavishsoft.com