Author Topic: Crash with FS2open on 2nd mission after training(freespace 1)  (Read 2980 times)

0 Members and 1 Guest are viewing this topic.

Crash with FS2open on 2nd mission after training(freespace 1)
Okay so, I am new to FSopen. I didn't even know this existed. and I've been a MASSIVE fan of all the descent, and freespace games since descent 1 was released. And yes, I am old enough to have bought every game when they were all on the shelves.

That said, I just bought/installed freespace and freespace 2 on Good old Games.

I then followed the instructions listed here:http://joshmccarty.com/2011/08/play-an-enhanced-version-of-descent-freespace-2-with-fs2open/

I've installed every option that the freespace open installer can do (The works:Absolutely everything), and setup the launcer for fs2open as what I believe to be correct (all features on).

It crashes while trying to load the second mission after training (Eve of Destruction), with this error:


For asteroid 'Small Asteroid', detail level
mismatch (POF needs 3)
ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_7_0_RC1-DEBUG.exe! SCP_DumpStack + 354 bytes
fs2_open_3_7_0_RC1-DEBUG.exe! Warning + 416 bytes
fs2_open_3_7_0_RC1-DEBUG.exe! asteroid_load + 424 bytes
fs2_open_3_7_0_RC1-DEBUG.exe! asteroid_create_all + 311 bytes
fs2_open_3_7_0_RC1-DEBUG.exe! game_post_level_init + 80 bytes
fs2_open_3_7_0_RC1-DEBUG.exe! game_start_mission + 373 bytes
fs2_open_3_7_0_RC1-DEBUG.exe! game_enter_state + 550 bytes
fs2_open_3_7_0_RC1-DEBUG.exe! gameseq_set_state + 310 bytes
fs2_open_3_7_0_RC1-DEBUG.exe! game_process_event + 242 bytes
fs2_open_3_7_0_RC1-DEBUG.exe! gameseq_process_events + 152 bytes
fs2_open_3_7_0_RC1-DEBUG.exe! game_main + 782 bytes
fs2_open_3_7_0_RC1-DEBUG.exe! WinMain + 330 bytes
fs2_open_3_7_0_RC1-DEBUG.exe! __tmainCRTStartup + 358 bytes
fs2_open_3_7_0_RC1-DEBUG.exe! WinMainCRTStartup + 15 bytes
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes


any ideas?

 

Offline niffiwan

  • 211
  • Eluder Class
Re: Crash with FS2open on 2nd mission after training(freespace 1)
Sorry, the installer is currently broken, a new one should be ready "soon".  In the meantime please try to install using the guides linked at the top of the page under "Installing FreeSpace Open".

It it still doesn't work after doing that, please post a fs2_open.log (see my sig for a link).
Creating a fs2_open.log | Red Alert Bug = Hex Edit | MediaVPs 2014: Bigger HUD gauges | 32bit libs for 64bit Ubuntu
----
Debian Packages (testing/unstable): Freespace2 | wxLauncher
----
m|m: I think I'm suffering from Stockholm syndrome. Bmpman is starting to make sense and it's actually written reasonably well...

 

Offline Yarn

  • 210
Re: Crash with FS2open on 2nd mission after training(freespace 1)
What you have there is a harmless, nonfatal warning (i.e., not a crash) that you can ignore by clicking "no." It appears only if you use a debug build, which you should not use unless you have a reason to use it (for example, to create a debug log).

Also, the FreeSpace Port doesn't work properly in 3.7 RC1. Instead, use 3.6.18 or the most recent nightly build. It should work properly in 3.7 RC2 (which isn't available yet), though.

And, yeah, don't use that installer. That statement cannot be stressed enough.
"Your fighter is running out of oil.  Please check under the hood and add more if necessary"
--strings.tbl, entry 177

"Freespace is very tired.  It is shutting down to get some rest."
--strings.tbl, entry 178

 

Offline Mongoose

  • Rikki-Tikki-Tavi
  • Global Moderator
  • 212
  • This brain for rent.
    • Steam
    • Something
Re: Crash with FS2open on 2nd mission after training(freespace 1)
If I can ask, where did you see a recommendation to use the installer?  If there's still an information source out there saying that it's the way to go, we should really find it and correct it.

 

Offline niffiwan

  • 211
  • Eluder Class
Re: Crash with FS2open on 2nd mission after training(freespace 1)
he linked to it, it's a blog :p
Creating a fs2_open.log | Red Alert Bug = Hex Edit | MediaVPs 2014: Bigger HUD gauges | 32bit libs for 64bit Ubuntu
----
Debian Packages (testing/unstable): Freespace2 | wxLauncher
----
m|m: I think I'm suffering from Stockholm syndrome. Bmpman is starting to make sense and it's actually written reasonably well...

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: Crash with FS2open on 2nd mission after training(freespace 1)
Am I the only one whose biggest problem with that blog post was that he kept referring to it as "Descent FreeSpace 2"?
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 
Re: Crash with FS2open on 2nd mission after training(freespace 1)
Okay. So. Thanks for the help guys.

Currently, The game is running fine after NOT using the debugging build, minus a few glitches here or there. mostly with wingman commands, sometimes they ignore what I tell them to do. And I'm still using the 3.7 build....I guess until it major-crashes I'll keep using it, unless you guys don't suggest that?

Well I used that installer because I ORIGINALLY searched google for "Descent Freespace Texture" and one of the first links was to that blogs post, and introduced me to FS2open.

So I went with his suggestions as far as what to use to install. The game looks GREAT right now however...

Also, the game IS Descent: Freespace, isn't it?

 

Offline Jeff Vader

  • The Back of the Hero!
  • Moderator
  • 212
  • Bwahaha
Re: Crash with FS2open on 2nd mission after training(freespace 1)
Also, the game IS Descent: Freespace, isn't it?
The first game was "Descent: FreeSpace – The Great War" or "Conflict: FreeSpace – The Great War", depending on your country. This was because there was already a compression utility called "Freespace" on the market. They had to add something to the name to avoid legal issues and with Volition's previous Descent series of space shooter games being popular, it was used to gain some attention. Dunno who came up with "Conflict" or why, but that's what it was called at least here.

The second game was "FreeSpace 2". Nothing more, nothing less.
23:40 < achillion > EveningTea: ass
23:40 < achillion > wait no
23:40 < achillion > evilbagel: ass
23:40 < EveningTea > ?
23:40 < achillion > 2-letter tab complete failure

14:08 < achillion > there's too much talk of butts and dongs in here
14:08 < achillion > the level of discourse has really plummeted
14:08 < achillion > Let's talk about politics instead
14:08 <@The_E > butts and dongs are part of #hard-light's brand now
14:08 <@The_E > well
14:08 <@The_E > EvilBagel's brand, at least

01:06 < T-Rog > welp
01:07 < T-Rog > I've got to take some very strong antibiotics
01:07 < achillion > penis infection?
01:08 < T-Rog > Chlamydia
01:08 < achillion > O.o
01:09 < achillion > well
01:09 < achillion > I guess that happens
01:09 < T-Rog > at least it's curable
01:09 < achillion > yeah
01:10 < T-Rog > I take it you weren't actually expecting it to be a penis infection
01:10 < achillion > I was not

14:04 < achillion > Sometimes the way to simplify is to just have a habit and not think about it too much
14:05 < achillion > until stuff explodes
14:05 < achillion > then you start thinking about it

22:16 < T-Rog > I don't know how my gf would feel about Jewish conspiracy porn

15:41 <-INFO > EveningTea [[email protected]] has joined #hard-light
15:47 < EvilBagel> butt
15:51 < Achillion> yes
15:53 <-INFO > EveningTea [[email protected]] has quit [Quit: http://www.mibbit.com ajax IRC Client]

18:53 < Achillion> Dicks are fun

21:41 < MatthTheGeek> you can't spell assassin without two asses

20:05 < sigtau> i'm mining titcoins from now on

00:31 < oldlaptop> Drunken antisocial educated freezing hicks with good Internet == Finland stereotype

11:46 <-INFO > Kobrar [[email protected]] has joined #hard-light
11:50 < achtung> Surely you've heard of DVDA
11:50 < achtung> Double Vaginal Double ANal
11:51 < Kobrar> ...
11:51 <-INFO > Kobrar [[email protected]] has left #hard-light []

 

Offline Yarn

  • 210
Re: Crash with FS2open on 2nd mission after training(freespace 1)
And I'm still using the 3.7 build....I guess until it major-crashes I'll keep using it, unless you guys don't suggest that?
Well, if you use FSPort with the current 3.7 build, you will miss out on a bunch of enhancements, such as the FS1 HUD and the FS1 soundtrack. Therefore, when you play FSPort, I strongly recommend you do not play it with the 3.7 build until RC2 is released.
"Your fighter is running out of oil.  Please check under the hood and add more if necessary"
--strings.tbl, entry 177

"Freespace is very tired.  It is shutting down to get some rest."
--strings.tbl, entry 178

 
Re: Crash with FS2open on 2nd mission after training(freespace 1)
Yarn, As I am playing Freespace (1) now, it has the correct soundtrack and the correct HUD...what are you referring to that I'm 'missing'?

 

Offline Yarn

  • 210
Re: Crash with FS2open on 2nd mission after training(freespace 1)
Yarn, As I am playing Freespace (1) now, it has the correct soundtrack and the correct HUD...what are you referring to that I'm 'missing'?
Check out this video of the first mission to see what I mean (skip to 2:44 if it starts at the beginning). The HUD (the center area, specifically) and music that you're getting should be similar to what's in that video. They should not be closer to what's in this video.

Actually, it's possible that you are getting the correct HUD, but if you're using the current 3.7 build to play FSPort (which is the port of FreeSpace 1 ported to FreeSpace 2, so if you are playing FS1 in FreeSpace Open, you are playing FSPort), you won't get the correct music, even if it doesn't sound wrong.
« Last Edit: May 05, 2013, 04:39:06 pm by Yarn »
"Your fighter is running out of oil.  Please check under the hood and add more if necessary"
--strings.tbl, entry 177

"Freespace is very tired.  It is shutting down to get some rest."
--strings.tbl, entry 178

  
Re: Crash with FS2open on 2nd mission after training(freespace 1)
Sorry for the late reply, been busy playing FS1 :) Yeah I went back to the older 3.6 version, and the music went back to the origional FS1 score. However, the HUD was always the FS1 version...no matter, it works now - was because I was using the debug version (DOH).

Anyways, this port of FS1/2 is amazing, I LOVE the details, looks pretty much like a modern game, and I'm enjoying playing through one of my favorite childhood games again! w00t!