That fix worked for me. But I also had to delete the system folder also. I did shut down steam as told to in another post but I still got the blue screen. I restarted and then launched up RO and the game ran fine now. Thanks.MaryKate&Ashley said:Ok, here's the fix that I got to work. Everyone that I know that has this problem also had the SDK installed. Go to the C:\Program Files\Steam\SteamApps\[yoursteamaccountname]\red orchestra folder, backup anything in there that you may want to save, for example your screenshots folder, demos folder, and you might want to save your system folder. You can probably also just leave those folders alone and it will work... then delete everything else. Most of those files and folders were created by the SDK. After that, and this also may not be necessary, but I backed up and deleted the two redorchestrasdk.gcf files that are in the SteamApps folder. Of course this means you won't be able to use the SDK, but I decided playing the game was more important. After that, restart steam and launch the game and everything should work. If not, you'll have to take it up with Tripwire and/or Steam. Good luck,
MKA
Ike said:I had the same problem, had the SDK beta installed and followed the directions and it worked the first time. Let me summarize what I got from about three posts and put it in one place:
(1) Reboot after a lock-up then exit from Steam
(2) Copy your "user.ini" and "RedOrchestra.ini" files from C://(whatever)/Steam/SteamApps/(username)/RedOrchestra/system; don't leave them in that directory. I copied them to a file in My Documents that I named "RO Backups".
(3) Go back to the RO directory in SteamApps and delete everything in the RO directory, but by "select all" then "delete", don't delete the directory.
(4) Re-boot your computer again.
(5) Check your shortcut on your desktop to be sure there's no extra wording in the shortcut's Properties.
(6) Start the game using your desktop shortcut. You will see that the display is wrong, but that's okay. Try to join a server. If you succeed, exit RO and then go on.
(7) Copy your "RedOrchestra.ini" and "user.ini" files back into the system folder in the RO game folder. You will find those folders there, even though you just deleted all from the "RO" folder.
(8) Start RO again using the shortcut. It should be back to what it was, maybe even a bit better.
Works for me too!
But now i can't use the sdk, right?
And the files .sdk under steam apps?
I can delete them?
Anyway i wait another better release of the sdk develop my mapper dreams....
Bye
Totola
ombas said:my little temp fix...
copy ro folder to another location
redo your roed shortcut to reflect copied location
backup ini files in ro dir
del ro dir
start ro
exit ro
copy in backed up ini files
play ro as normal
use roed from new location
i'm new to ued so i don't know how to extensively test it without the steam installation, but it appears to run fine outside of the steam directory tree and you save your editor work
Rohrmoser said:I also refuse to lose my SDK... So I will wait for a fix and play some cod2 or Source mods!
Sounds like you have a different problem then. Did you try deleting the RO prefetching file? I did that when I had that kind of error before and it worked. There's a thread that talks about that fix.Rex said:this fix did NOT work for me, so I completely wiped RO and SDK from my system, rebooted, did a fresh download of RO, and when I start it up from steam i get the same exact problem: BLUE SCREEN OF DEATH!
any suggestions?
Fooled around....? did you make a fresh playable level and open it in the game to playtest it (ie spawns , objectives, bots etc) or did you only open the editor, make a few things, then close it and go back to playing online. For me I made part of my level, played some more online RO OK,went back to the editor, put spawns etc in and playtested it in a practice match. then when I went to play online agian the game hanged at the connecting (IP address)/index.rom screen.Rrralphster said:I'm not entirely sure if all these people experience the same problem. But I have the feeling it's not the SDK.
For me the problem showed up after the Steam update. I fooled around with the SDK and I could still play the game.
Deleting the SDK is not what I would call a fix! (sorry for sounding so negative, I'm as mad as hell, so please forgive me).