brekushi wrote:LAX any update on this issue?
If you are also having a problem, it would be wise to provide any information at all because the only person that has reported a problem is nightshift. If there was an update on nightshift's issue, it would be found within this thread.
It was all working without issue before the latest update to STO.
That's the first thing you said and we totally understand that, let's stick to trying to work out the problem though. You're on Windows 10, I'm on Windows 10; you're on 6099 or later, I'm on 6099 or later; I have the latest STO patch, you have the latest STO patch. However, it's crashing for you and not for me, so there is something else besides that information ("it was working before the latest update") that is important to the issue. So far, I cannot reproduce the issue under the same apparent circumstances, and have no technical information on where to begin solving the problem; so what we are trying to do here is find out what is different between us to cause the issue for you and not for me.
I started systematically shutting down every process one by one and tried launching through Innerspace after each shutdown, each try was a failure.
Much quicker just to shut them all down and see if it helped or not. If not, it is a waste of time to shut them down individually.
So, you're saying it crashes .... is there a crash report? Any technical details on the crash itself that you can provide? Is it silent and just closes the game window? If there is a crash report or technical details, please provide that for me.
If not, I would probably check the Windows Event Log and see if there's an application error listed for STO. Microsoft's instructions for opening the Event Viewer are "Open Event Viewer by clicking the Start button, clicking Control Panel, clicking System and Security, clicking Administrative Tools, and then double-clicking Event Viewer. Administrator permission required If you're prompted for an administrator password or confirmation, type the password or provide confirmation.". (You may be able to Win+R and type in "eventvwr") After opening event viewer, expand "Windows Logs" (not "Applications and Services Logs") and click "Application". This should list recent application crashes and other things at the top of the middle area. If there is an entry for the game or launcher from the date/time it failed to launch, select it grab me the XML View under the Details tab at the bottom.
Finally, I understand you say it works to launch directly without Steam. But it shows that E:\Steam\gameoverlayrenderer.dll is loaded in the process; can you try a non-Steam install and see if that changes anything?