Re: Launcher crashing
Just this line in the crashlog.
150907 14:24:16 16 Client[0 [NOENT]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
Moderator: MiRai
League of Extraordinary Multiboxers
Posts: 4597
Joined: Sat Feb 15, 2014 11:14 am
Location: In the dining room, with the lead pipe.
bob wrote:It was assumed it was the game rather than the launcher from your initial post.
That said you could try the following:
In the Launcher Options, unselect the On Demand Patching. This should download another 5GB or so.
Make sure Full Screen is not selected either.
Don't tick Fast Launch or Minimize to tray.
Have you set a Proxy for gameplay/patching?
Do you have extra command line parameters.
Can you provide another diagnostic.
League of Extraordinary Multiboxers
Posts: 4597
Joined: Sat Feb 15, 2014 11:14 am
Location: In the dining room, with the lead pipe.
bob wrote:Which InnerSpace version are you running x86 or x64 ? It's never shown up in your diags.
Can you try shutting down the GForceExperience and make sure that the Nvidia driver wont be trying to switch 3d on for STO?
nightshift wrote:I came across this post that seems similar: http://isboxer.com/forum/viewtopic.php?f=24&t=4080
lax wrote:nightshift wrote:I came across this post that seems similar: http://isboxer.com/forum/viewtopic.php?f=24&t=4080
I totally understand and agree that if you go through old posts you will find some that seem similar -- hey an update happened and it is crashing. The log in the post even looks similar, reinforcing this, but apparently that's all that particular log ever says -- you can find numerous posts about that via google on the Steam forums and elsewhere.
However, specifically from the Romulus update in 2013, it was crashing for every single STO player using ISBoxer, due to a change in how the client operates. Unfortunately even though the circumstances around it are very much the same, the issue itself was apparently different. It was easy to solve because, as that thread is testament to, after I patched STO with the Romulus update it also crashed for me and I was able to track it down quickly enough to fix it within hours. You'll note that Ridosaw posted on that thread as well -- he streams STO multiboxing with ISBoxer pretty often now (last 2 days ago) and would almost certainly chime in if there was an issue like this that affects him, as he did last month. I tested it on multiple PCs and different versions of Windows today just to double check.
Does the Cryptic Error window have any way to view the report contents?
Users browsing this forum: No registered users and 1 guest