As described in the title, ever since the last patch (7-23-2015), I have tried to launch STO in DirectX 9 mode as I usually do.
I have never had STO work properly under the DirectX 11 options; each time the game tries to run DX11, it
freezes up after the launch screen, forcing me to close the game. But in DirectX 9 mode it works fine for me, so I just run it in that mode.
After the patch, each time that I've attempted to load up STO has led to it freezing blank after the
Star Trek Online: Iconian War title screen. Any further interaction leads to Windows saying that the GameClient.exe isn't working, forcing me to close the program. This is the same thing that has happened to me every time that STO has been reset under DirectX 11 options.
Sure enough, I opened the Gameprefs.pref file in the STO game folder (Cryptic Studios\Star Trek Online\Live\Localdata\Gameprefs.pref) in Notepad and checked the
"PrefEntry SystemSpecs.isDx11Enabled" and
"PrefEntry SystemSpecs.isDx9ExEnabled" lines, and saw that they were set to a value of
"1". As far as I know, running STO in DirectX 9 mode is supposed to have both of those values as
"0", which meant that
the last patch overwrote my Gameprefs file settings.
To make matters worse,
every subsequent attempt to rewrite the Gameprefs file to DirectX 9 settings has been rebuffed when I try to relaunch STO, when the
game client re-rewrites Gameprefs back to DX11 just before freezing:
- I opened the Gameprefs.pref file in the STO game folder in Notepad and edited the "PrefEntry SystemSpecs.isDx11Enabled" and "PrefEntry SystemSpecs.isDx9ExEnabled" lines from a value of "1" to "0". I also have the "PrefEntry GfxSettings.DeviceType" line set to a value of "Direct3D9" instead of Direct3D11. This is supposed to make STO operate using DirectX 9. However, each time I try to launch the STO client, the Gameprefs file is overwritten, just before the game client freezes up. This is confirmed by watching the Star Trek Online\Live\Localdata\Gameprefs.pref file in Windows Explorer, where the Date Modified timestamp changes to the exact time when the STO client reaches the title screen. Reexamining the Gameprefs file indeed reveals that the STO client is reverting the "PrefEntry SystemSpecs.isDx11Enabled" and "PrefEntry SystemSpecs.isDx9ExEnabled" lines to a value of "1", meaning that the game is forcing itself to run DirectX 11.
I proceeded to do everything that I could think of/Google search for to try to make STO run in DirectX9 mode, without success:
- I tried launching STO in Safe Mode, which I've done successfully before when STO has suddenly reverted back to DX11 after previous patches. I usually then just change the Direct X setting from the Options menu in the game client. This time however, Safe Mode STO exhibits the exact same behavior: rewriting Gameprefs to use DX11, just before freezing on the title screen.
- Similar files in the Tribble build folder (Cryptic Studios\Star Trek Online\Playtest\Localdata\Gameprefs.pref) and one of the parent folders (Cryptic Studios\Star Trek Online\Gameprefs.pref) also have the DirectX lines set to a value of "0". Neither file is rewritten by the STO client when launching the game.
- I set the command line option in the STO launcher to "-d3d9" to try to get the game to run that way. Same thing, the game client rewrites the Gameprefs file to use DX11 values, and freezes. The command line option in the launcher remains, but STO still tries to run under DX11 and fails.
- I also tried setting the command line option to "-d3d11Enable 0 -d3d9Enable 0", which should similarly turn off DX11 mode and make STO run with DX9. Slightly different result from before (Yay?): The Gameprefs file is still overwritten by the STO client at launch as before, except only the "PrefEntry SystemSpecs.isDx9ExEnabled" line is changed to a value of "1", while "PrefEntry SystemSpecs.isDx11Enabled" is left at "0"...and promptly freezes again.
- Finally, SUCCESS! (Sort of.) I left the "-d3d11Enable 0 -d3d9Enable 0" command line in while loading the STO client in Safe Mode, which while it still rewrote the "PrefEntry SystemSpecs.isDx9ExEnabled" line to "1" as in the previous step, the game client loaded up to the Character Screen AT LONG LAST. Looking at the Display options menu, it seems to be that the STO client keeps resetting the Video card Display option to "Auto", as opposed to leaving it on "Direct 3d 9" as my selected card. In fact, all of the Display options are reset: Fullscreen mode, Brightness, etc. The result is that STO will keep auto-selecting the newer DirectX option to run on, then freeze up every time.
- Unfortunately even manually setting the "Direct 3d 9" card option in Safe Mode doesn't stick. More attempts to launch STO normally result in the same failed launch behavior as before: overwritting the Gameprefs DX settings, and then freezing up soon after. And even relaunching the game in with the options in the above step results in all of the Display options being reset to default/game freezing values.
The end result then is that because the
STO client is now constantly trying to overwrite my game settings at launch, I now have to launch STO in Safe Mode with some wonky-at-best command line options to even get in the game. And any settings which I do set in that mode are not preserved for my next game session. Which is obviously a less than ideal option.
Comments
So, after several attempts I came here and found this thread. Sure enough, I checked my STO folders and 'Cryptic Studios\Star Trek Online\Playtest\Localdata\Gameprefs.pref' did indeed read that ""PrefEntry SystemSpecs.isDx11Enabled" and "PrefEntry SystemSpecs.isDx9ExEnabled" lines, and saw that they were set to a value of "1".
I then attempted to change the DX11 line to 0, whilst leaving the DX9 line at 1. No effect and endured the same crash/lockup again. And, upon checking Gameprefs.pref again, also noticed that both the lines had reverted to 1 (even though I'd changed the DX11 line and saved it at 0).
Can also verify that my file, in Notepad, also reads "PrefEntry GfxSettings.DeviceType Direct3D9".
Absolutely livid that I can't get into the one and only game I ever play, during a Dilithium Bonus Weekend', which is when I play this game the most!!!
Please fix this!!!!
Vice-Admiral Methos Corinthian
methos71
PLEASE ARC fix it. Especially so that people who actually do spend money on the game can actually play the TRIBBLE game. This issue was happening since before todays maintenance, as I could not log in last night either.
THIS is the only thing that has worked thus far, towards getting me into the game and being able to play it. Yet, it's ridiculous that I'm likely going to have to reset all my graphics preferences each and every time I log on for a game session.
I'm 99.5% certain that this issue is directly related to and caused by whatever supposed 'DX crash fix' went into yesterday's patch, as I had no problems whatsoever with this sort of nonsense prior to yesterday.
In a nutshell, our STO game files are being forcefully overwritten with coded instructions to force Direct X 11 as the game's default GFX setting. And those of us who can't use anything beyond DX 9 are being forced to deal with this nonsensical work-around to play.
This needs fixing now, as anyone and everyone who's limited to DX9 is likely currently facing this issue, whether they're reporting it here or not.
Vice-Admiral Methos Corinthian
methos71
Minimized the game and posted here minutes ago. Then went back to the game and freeze. Only way to get out of STO was to kill it in Task Manager.
This nonsense is beyond absurd in its ineptitude, as a supposed 'Direct X Crash fix'!
Vice-Admiral Methos Corinthian
methos71
And this worked...sorta. The great news is that 'backing out' allowed me to exit the game, restart the launcher (sans 'Safe Mode' and a 'Command Line' fix) and actually launch the game without problems in regular play mode. And this let me enjoy the game without a glitch, with beautiful performance and stellar GFX, all around.
The bad news is that it doesn't stick upon exiting again.
First time I tried, I exited the game from normal mode, fullscreen set and all my in-game GFX settings tweaked accordingly, and it crashed upon restarting the launcher, at the Iconian War splash screen.
Tried a slightly different approach the second go. Did the whole 'Safe Mode' and 'Command Line' routine again. 'Backed out', in Windowed mode again. Exited from there. Restarted the launcher and logged in again without problems. Played for a bit. Then returned to the Character Select screen, reset screen mode to 'Windowed', hit 'Back', then 'Exit'. Restarted the launcher and logged in and simply crashed at the Iconian War splash page again.
At the very least, we've now determined how to at least get the game into 'Normal Mode', rather than 'Safe Mode'. Still not able to permanently make that stick though and I think that's were a fix from Cryptic will have to rid us of this problem.
Vice-Admiral Methos Corinthian
methos71
I should add that I've inquired elsewhere about this issue and Cryptic dev Zeroniusrex is aware of this issue and she's said she'll hopefully look into it tomorrow. So, with any luck, we'll all be able to get back into this game we all love (and sometimes kinda hate), without any complicated work-arounds, come this Thursday or shortly thereafter.
Vice-Admiral Methos Corinthian
methos71
Thanks for directing me to this thread methos71. The explanations go a long way towards keeping the STO version of road rage from taking me down ;D I was beginning to wonder if STO had finally gone the way of the DOOOOM thread.
... Sadly I think I'll pass on all the technical work around, and the free weekly spec point this is going to cost me. I've been discovering I can live without my STO fix, and that other games are actually more fun. I wish that were not true, but as I said... sadly...
Nerfing is Fraud...
Still, I'll wait two more days and hope this week's patch gets me and several others back online.
So there might be a glimmer of light at the end of this tunnel, hopefully.
Vice-Admiral Methos Corinthian
methos71
galacticguards.enjin.com/
Formerly Jewkesman Member from Nov 2009!
I found this link: https://youtube.com/watch?v=CiWL6chvpGk
Decided ok I will watch it...watched it and decided to check to see if it would work...and it did totally for me.....even fixed some sound issues I had....as in....there where times I didn't get dialogue or the sound would cut out...but after I followed the instructions in that video everything worked fine better then fine.
I can only surmise that for me...and for others...windows decided to make a sound library for the video card drivers.....this in turn was causing fatal errors and such as the direct x was literally being told by windows to attempt to use the same driver for both functions...when in fact....it shouldn't need the graphic drivers for the audio.
It explains the messages...I would get where it would say the guid would be missing.....or the not able to make the multiple instances.....to even how the game would go to the starter screen but then crash before going tot he character selection part....as it couldn't start up the graphics because that driver was being simultaneously being used for sound....
So I suggest people take a look at that link video that could be the issue some of you are having.
Power without Perception is Spiritually useless and therefore of no true value.
=^_^=
free jkname
Get the Forums Enhancement Extension!
Idiots.
Vice-Admiral Methos Corinthian
methos71
It gets this far then NOTHING...
- then I changed these lines;
Prefentry SystemSpecs.Isdx11enabled 0
Prefentry SystemSpecs.Isdx9exenabled 0
... then I set gameprefs.prefs to read only. Tried booting STO and got the usual result. Checked my Gamepref.prefs file and the values were not rewritten. Yet STO is still "not responding" in Task manager. Tried this all few times with no change...
???
Nerfing is Fraud...
Pity it didn't work though.
Way I see it, something in last week's patch caused all this. With any luck, something in tomorrow's patch will hopefully fix it. Also tossed into the mix was new driver update from NVidia, which I got today. Haven't tried logging in since the new drivers installed though. Figured it would be best to try again after tomorrow's STO patch.
So, guess it's fingers crossed until then!
Vice-Admiral Methos Corinthian
methos71
I noticed that when setting the gamma and moving the slider, that this affects my desktop settings when I leave the game, so when i raise the gamma to see better i dark places, I leave the game and my desktop is almost whited-out.
WhatI am saying here is that whatever code they've got dealing with the graphics settings it is having issues, even overriding and modifying windows settings when not in STO, and leaving STO and/or ARC doesn't set them back to their default values before making adjustments in STO to play STO (thinking the adjustments were just inside the game).
I do not play through Steam, and am in Vista 64. But in reading what these people are going through, with a file being overwritten when they launch the game, it appears this is caused by an errant code segment meant to assure the integrity of the game's playability when first installed, and is therefore failing to read in, and instead overwriting, the player's existing values and failing to make sure the client adheres to the player's existing settings. I arrive at this conclusion due to how my changing the STO client's gamma option permanently changes the brightness of my desktop and all of the graphics on my computer when it should be only changing the gamma value for STO. This suggests the errant code segment is accessing the global, and not merely the application specific, graphics settings, and that is the initial reason it also overwrites the application specific settings with the assumed global defaults. By what these other players describe above this appears to be what the code is executing at start-up of the game, to initialize and impose the global default settings as though STO had never been installed on that computer before.
My game came up in 1600 x 1200 after new install and patching to play again after 3 years of it being uinstalled, and I had to change the setting to 1920 x 1080 and haven't had a problem. I suggest the difference for me versus these players above is that for them when the client crashes and they run it again to try to get it working, the game's self diagnostic (the one that says a problem was found but doesn't fix it after 20 minutes of file scanning) is probably aware what file was being written, is assuming it would be corrupt and then of course rewrites the file to install the default values, which do not work for these other players so the client crashes, causing a loop of the client failing every time it is run until the client is patched.
I hope Perfect World makes the game assume DX9 as default and only move up if the player makes the choice to do so, and that this would best be accomplished by a prompt that asks prior to setting the application preferences to run in a DX higher than 9, and therefore leaves the values alone if the player clicks the "no" box. If this value needs to be verified, or for some reason with a major patch, to be reset in the future, it'd be good if they had that entire process well coded and ready to be enabled when necessary to assure that players aren't locked out of a game they love merely because of a seemingly untested client graphics diagnostic and automation that appears to have failed to consider the existing players and their client installation preferences.
And your theory is an interesting one Trmcgillicutti. Yet, I can't say that I've noticed any untoward changes to my GFX settings outside of STO. Though, on the occasions I have been able to login, via 'Safe Mode' and that 'Command Line' work-around, I have noticed that I've had to fidget with the in-game brightness slider to regain the look I've long been accustomed to. I prefer to keep my brightness at 125% and it had been looking a touch darker. Upon raising the brightness slider and sliding it back down to 125%, the screen's brightness appeared as it should. Only thing I've noticed that comes anywhere close to what you've suggested.
Vice-Admiral Methos Corinthian
methos71
By the way, thanks to everyone who has posted their feedback/offered suggestions/etc. in this thread so far. It's nice to know that I'm not the only one wrangling with this particularly annoying issue.
Cmdrscarlet, I totally agree with ya that we shouldn't have to jump hoops like this to get into the game. Yet, I can 100% assure that doing the following will neither mess about with your computer or hinder your STO files in any way, whilst still allowing ya to get the game playing in 'Normal Mode'
1. Go into 'Options' in your launcher. Scroll down and check the 'Safe Mode' box. Below that, in 'Command Line', paste this (without the quotes) "-d3d11Enable 0 -d3d9Enable 0". Then make sure to click on 'Save'.
2. Login. At the character select screen click on 'Options' in the lower right-hand corner. Click on the 'Display' tab and select DirectX 9 (I get two options for DX9, plain old DX9 and DX9EX...I've always used plain old DX9). Then click on apply.
3. Then click on 'Back', in the lower left-hand corner, which will return you to the login screen. Click on 'exit' and completely exit the game, closing the launcher window and all.
4. Reopen the launcher, go back to 'Options'. Make sure that 'Safe Mode' is now UNCHECKED. Also erase "-d3d11Enable 0 -d3d9Enable 0" from 'Command Line'. Click on 'Save'.
5. Log back into STO, as you normally would. Voila, you're back in 'Normal Mode'! You'll have to reset all your in-game GFX settings, but this will allow you to play in 'Normal Mode' at least.
Vice-Admiral Methos Corinthian
methos71