[scuzzyfuzzy]

Hi, I recently installed everything (using Turey installer), got the game going, everything worked fine from the beginning, tried 2 training missions and now every time I want to start the next mission, the game crashes.


I'm on Win764bit, 2 GB RAM, Radeon 2600XT


 I attached the error log and cpu-z report.


Thanks for the help!


[attachment deleted by admin]

[General Battuta]

Oh dear. Well, have you tried switching to a release build? Ends in -r or -release, instead of -d or -debug.

If that doesn't work, please go into FreeSpace2/data/ and post the fs2_open.log file from there.

Should be able to fix this very fast.

[CommanderDJ]

Yeah. fs2_open.logs are (almost) essential to debugging, and once we have them, problems like this are usually sorted out very quickly.

Also,



Enjoy your stay!

[scuzzyfuzzy]

First of all, thanks for the welcome and for the fast replies...

 
To tell you the truth (in a few more words) I read about FS2 recently on Eurogamer, shed a tear for "the good old times" and shuffled through my dusty old scratched CDs and installed FS2 (on Win7x64
As I read about the scene that revived this amazing game I stumbled across numerous sites with mods and texts about the new Open FS and... well, let's say I am not very young anymore and a lot of that text was a bit too much...
I struck gold with the installer that did everything for me, but honestly, I still can't follow all the various terms regarding... well, everything
So, I must apologize for not doing my homework, I just tried to get it going ASAP...
That's a lame excuse, but please, if you find in you some compassion, please post a few links that could easily explain what -d and -r is, what the different versions are and who the hell FRED is?


Thanks again for the tip, I will try it immediately...
 

[FreeSpaceFreak]

-d builds are used for debugging, they will create a file called "fs2_open.log" in C:\Games\FreeSpace2\data\ (or wherever you installed the files). Post it here if you have problems, that helps the tech support guys a lot.
For regular playing, use an -r (regular) build: it will not report issues to you and it will not crash when something's not right. It also won't write the logfile.
The most recent (stable) version of both the EXEs and the mediaVPs are the 3.6.12 ones; for starters, I suggest you play with these.
FRED is how missions are made, see here on the FreeSpace Wiki; you won't need it if all you want is to play.

[General Battuta]

All you need to do to solve your problem (I think) is to open up the launcher where you configure your resolution and graphics and stuff, hit the 'Browse' button at the top right, and select something that looks like FS2_Open_3.6.12_INF_SSE2_r (not _d or _debug.)

We really need to make these build names more intuitive.

[scuzzyfuzzy]

Thanks guys, I changed to -r and now everything works just great...!



We really need to make these build names more intuitive.


Before I quote and support you on that, may I just say congratulations on a job well done with the complete FSOpen project...



P.S. The whole thing does feel like installing and maintaining Linux, but it doesn't matter because of all you helpfull guys...

Keep up the good work!

[General Battuta]

You can still post the log file from your FreeSpace2/data/ folder. It will help us tell you what additional options you can turn on to make your game even better.

[scuzzyfuzzy]

Here's the log attached, hope it helps...


P.S. Did I mention what an awesome game this is...?

[attachment deleted by admin]

[General Battuta]

You're not running the MediaVPs! If your card can handle it, go to the 'mod' tab in the launcher and select mediavps_3612.

[scuzzyfuzzy]

...and it's working great...

Thanks for the tip...