[nuone]

<Would sincerely appreciate some help>

I am following the steps listed in the installer thread, but I had to fiddle with the damn "Authorizations" Vista blocks me with. Anyways I got the Launcher to save the flag files, but yet it cannot modify the "settings.ini" file. I don't have that file. Where can I download it? The installer thread no longer mentions this file.

[Jeff Vader]

Where have you installed FSO? C:\Program files\ is undoubtedly an error-prone location on Vista. If you've installed FSO to \Program files\, move it away from there. Don't reinstall; a simple cut 'n paste will work and you won't have to redownload everything. C:\games\freespace2\ or something like that would be a good solution.

Also, settings.ini is a file created by FSO to store the settings you've picked in the Launcher. There is little point for other people to be sending you their settings.ini.

[nuone]

I appreciate your timely response. The problem is I did install it int games\freespace folder. Nonetheless I still get that error. By install FSO, do you mean download the builds and placing them in the \freespace2\     folder, no?

[nuone]

If it isn't that the launcher cannot modify the "flag list" or that "mod settings.ini" file or the darn Techroom crashes, or something. I thought FSO was improving the game, not making it impossible to use. With 3.6.9 things worked fantastically, now things are jacked up beyond understanding. We really need to get this act correct. There are conflicting installation procedures, missing and/or outdated files. Cannot write the pilot file, and such. This is rediculous.

Sorry for venting but man, this is frustrating!  

[General Battuta]

Huh? I haven't had a single problem.

Could you walk us through the problems one at a time? Have you tried a clean install? Have you posted a debug log?

Whatever problems there are appear to be on your end.

[General Battuta]

I had this problem once, and solved it by moving the game to C:\Games\FreeSpace2. That didn't do the trick?

[nuone]

Nope. I am using Vista though.

[Qent]

When the launcher wouldn't modify the flags for me, it turned out that it was pointed to an FSO .exe that no longer existed on my hard drive. The only time I remember the tech room crashing was when I was over the ship limit for normal builds. Chances are these aren't your problems, but it's two things to check.

[nuone]

This is my error log.

I have an Intel Core Duo 1.67 Ghz
2 Gigs of Ram
Windows (F*ing) Vista - Home Premium
ATI X1650 (Latest Catalyst drivers)

[attachment deleted by admin]

[Herra Tohtori]

Run the launcher (at least once) as Administrator. That should by all logic enable it to create the files and registry entries required by fs2_open.

The other topic implied you were suffering from techroom crashes, which could be a symptom of a rather common problem. Praytell, do you mayhaps use an ATI Radeon X1*** graphics card? They are having trouble with certain aspects of the latest MediaVP's (note that it befalls directly to ATI's bad decisions in the past rather than any design flaw on behalf of FS2_Open or FreeSpace Upgrade team) which, while they can be fixed on Windows XP, can only be circumvented on Vista and Win7 by disabling the new shader-based rendering system and reverting to the old one with -no_glsl option. But I'm getting ahead of myself, as you haven't even posted your system specifications yet.

As to any other difficulties you are having, please run a debug build, reproduce the crash/problem situation using that and then post the contents of the ..\FreeSpace2\data\fs2_open.log.

[Commander Zane]

Yeah, like specifically reinstalling FreeSpace from scratch at least 12 times when Ctrl + Shift + S quit working when the RC builds for 3.6.10. first showed up, posting logs and confirming that the log was spotless, yet I still have this stupid problem. This never happened on 3.6.9. on my end, then RC1 appears and wham.

[nuone]

This is my error log.

I have an Intel Core Duo 1.67 Ghz
2 Gigs of Ram
Windows (F*ing) Vista - Home Premium
ATI X1650 (Latest Catalyst drivers)

Will run the debug, and post. Appreciate the help.

[attachment deleted by admin]

[General Battuta]

This is my error log.

I have an Intel Core Duo 1.67 Ghz
2 Gigs of Ram
Windows (F*ing) Vista - Home Premium
ATI X1650 (Latest Catalyst drivers)

Your video card is of a type that has serious problems with FSOpen.

That said, could we get a debug log, not an error log? Instructions on how to generate one are available on the troubleshooting/support forum.

[General Battuta]

Yep, you've got one of the bad cards.

[Jeff Vader]

Two different threads handling the same problem can lead to communication difficulties. Merged. Hopefully it is at least as confusing now.

For the crashing issue: http://www.hard-light.net/forums/index.php?topic=56279.msg1180356#msg1180356 , third problem listed.

For the settings.ini problem: Life is much easier, if you run your Windows with an administrator account. A limited account can cause all sorts of funky errors and this could eeasily be included in them.

[nuone]

I am the "Admin," only one user of my rig. Nonetheless, I will stop trying to resolve the issue until I can get a much more powerful graphics card. Say, a Radeon HD 5970? 

[Herra Tohtori]

Just make sure your power supply can handle it... Also, consider that if the rest of the system will form a bottleneck, you won't be getting the full advantage of the speed of your GPU, so it might not be the best move to buy the latest generation card just because it's newest or shiniest.

In addition, like I posted earlier, you could just disable GLSL for the time being; in Launcher's Features tab, under the list entry of Troubleshooting you should find this option, or you can just type -no_glsl in the Custom flags entry. The gameplay will be the same, you just won't be getting the newest and shiniest graphical goodies. It's still better than 3.6.9 because you aren't losing anything, just not gaining the shader lighting.

[Aardwolf]

Oh for crying out loud... Intel integrated cards can run FSO just fine. It's only the GLSL features that they don't support. Turning down a few of the detail settings in the options menu works wonders.

Nonetheless, I am envious of people with better cards. 

[Thaeris]

When I installed FS2/FSO, I installed directly to the program files. The only other problems I had was in getting the program not to be blocked by my anti-virus. With FSO, you don't need to worry about compatibility issues - running compatibility mode with retail might not be a bad thing, though.

That said, if you're still having problems, try a fresh install. By the way, are you installing from disk or from a GOG download?