Hard Light Productions Forums
General FreeSpace => FreeSpace Discussion => Topic started by: ssmit132 on June 18, 2008, 03:35:35 am
-
I get this problem with the first mission in Deus Ex Machina (attached) and the second last mission in Derelict (The one where you destroy the Cthon). I get no messages! There is just an eternal messaging bracket around one ship (In Deus Ex Machina, the shipping point). When I try to open them in FRED2_Open (AFAIK, I originally had this problem a long time ago) it complains that the messages cannot be found, even though they're there in the file, (Derelict example attached) and opening the event editor causes a crash. I'm using FS_Open 3.6.9.
(I've posted this problem before, but no one replied.)
Very annoying as I want to play Deus Ex Machina again! :hopping: :mad:
[attachment deleted by admin]
-
Try some other builds.
-
(I've posted this problem before, but no one replied.)
I was gonna skip posting again, since I have roughly no idea of what's going on. But as an universal guess: you've broken something.
-
If it were me, I would try the following:
1. Run the debug build.
2. Try other campaigns.
3. Try other builds.
Mean while, I am going to check DEM myself.
-
Could it be a currupted pilot file?
I hate that glitch :mad:
-
Could it be a currupted pilot file?
I hate that glitch :mad:
Nope, can't be pilot file problem. He mentioned that the messages don't appear in FRED either.
What build you using?
-
I'm using FS_Open 3.6.9.
-
Maybe me means the .EXEs?
-
:wtf: They're both .exes. And yes, I think he refers to the game engine instead of FRED. And isn't that what we were talking about? Or did I once again misunderstand something crucial?
-
Nah. It was probably me.
-
So let's sum up what we have got so far:
- Messages don't apear in either FRED or In-game (DEM and Derelict)
- FRED says that it can't find any messages.
So, then my conclusion:
- Could you extract that mission file and upload it to HLP? We will take a look at it.
- I tested DEM and Derelict with all builds from 3.6.9-3.6.10 (Including the unofficial builds). I could not find any problems relating to this problem.
Temporary Solution:
- Download DEM and Derelict one more time. Replace the newly downloaded VP with the old ones, and try again. Never heard of a corrupt mission file.
-
Try some other builds.
I'll think I'll try this. I'm sure it's not the mission files, and I recently downloaded DEM again, so it's probably the build. I've attached the mission, though.
If it were me, I would try the following:
1. Run the debug build.
2. Try other campaigns.
3. Try other builds.
Mean while, I am going to check DEM myself.
It's usually only a few missions, I've played a lot of different campaigns lately.
:wtf: They're both .exes. And yes, I think he refers to the game engine instead of FRED. And isn't that what we were talking about? Or did I once again misunderstand something crucial?
Just that it's both In-game and in FRED.
[attachment deleted by admin]
-
Checked the attachd DEM mission file. I confirm that the mission file is ok. Nothing wrong with it.
-
I decided to try a different build, but I'm a bit overwhelmed by the 'Recent Builds' list, and this thread (http://www.hard-light.net/forums/index.php/topic,54584.0.html) is a bit vague (Trunk build? Do I just get the latest one or what?). Which build do you suggest?
-
I currently use this one (3.6.10):
http://www.hard-light.net/forums/index.php/topic,52542.0.html
And if you plan to use that, download launcher 5.5d here:
http://www.hard-light.net/forums/index.php/topic,52691.0.html
-
I tried that build, but still the same problem. I fired up fred2_open_3_6_9_debug.exe with no mods (well, almost none) to see whether it was those that caused the problem, and when I tried to open the file I attached earlier, I got this error:
Assert: Num_messages < MAX_MISSION_MESSAGES
File: J:\src\cvs\fs2_open_3_6_9.final\code\Mission\MissionMessage.cpp
Line: 924
[This filename points to the location of a file on the computer that built this executable]
Call stack:
------------------------------------------------------------------
fred2_open_3_6_9_debug.exe 004f45d3()
fred2_open_3_6_9_debug.exe 004f56ea()
fred2_open_3_6_9_debug.exe 004f65a8()
fred2_open_3_6_9_debug.exe 00433424()
fred2_open_3_6_9_debug.exe 00432908()
fred2_open_3_6_9_debug.exe 009d6e16()
fred2_open_3_6_9_debug.exe 009dd0b5()
fred2_open_3_6_9_debug.exe 009e9095()
fred2_open_3_6_9_debug.exe 009f53b9()
fred2_open_3_6_9_debug.exe 009e8df2()
fred2_open_3_6_9_debug.exe 009bf504()
fred2_open_3_6_9_debug.exe 009bfc31()
fred2_open_3_6_9_debug.exe 00a00f57()
fred2_open_3_6_9_debug.exe 009baf5b()
fred2_open_3_6_9_debug.exe 009ffc9a()
------------------------------------------------------------------
Don't know why it should be complaining, what could I have done to cause this?
-
\FreeSpace2\data\fs2_open.log <<== post that. that's what debug is all about.
-
Num_messages < MAX_MISSION_MESSAGES
Well well well....look what we have got here. Weird....very weird....
Well, this means that there are too many messages inside the mission. But strange, that never happened to me.
-
Num_messages < MAX_MISSION_MESSAGES
Well well well....look what we have got here. Weird....very weird....
Well, this means that there are too many messages inside the mission. But strange, that never happened to me.
It confuses me, too, as I was using the 3.6.9 build suggested on the Wiki (http://www.hard-light.net/wiki/index.php/Installing_fs2_open). (This one (http://fs2source.warpcore.org/exes/3.6.9.rar))
\FreeSpace2\data\fs2_open.log <<== post that. that's what debug is all about.
I tried to run it with the debugger but it crashed when I clicked the button on the pilot select screen.
-
\FreeSpace2\data\fs2_open.log <<== post that. that's what debug is all about.
I tried to run it with the debugger but it crashed when I clicked the button on the pilot select screen.
That was th first step. The other was to post your fs2_open.log.
-
Okay, here it is.
(And this was just with DEM, no other mods (including the core SCP stuff, but it crashed with that anyway) except for some loose ends I didn't account for.)
[attachment deleted by admin]
-
Hmm. Don' know whether this is related to the issue or not (probably not), but you should select Generic Software instead of Generic Hardware from the Launcher's Audio/Joystick tab.
-
Hmm. Don' know whether this is related to the issue or not (probably not), but you should select Generic Software instead of Generic Hardware from the Launcher's Audio/Joystick tab.
Yes, that's known to cause problems, but I'm not sure if it's the cause of this one. Do as Lobo said, however, and see if that helps.
-
After changing that setting (which I don't think helped in this case, just a coincidence) the game allowed me to enter the main hall in 3.6.9 debug, but it crashed when I tried to go into the campaign room. I changed the campaign with the normal exe (incidentally the one that nubbles526 suggested, it didn't come with it's own debug build), and tried debug again, but it crashed while going into the main hall again. I don't think that debug likes DEM!
Attaching the log files for both cases...
[attachment deleted by admin]
-
Debug builds have a tendency to crash, since the sole purpose of their existence is to track errors that occur. After the crash, you simply take a look at the log file. Or post it here so the rest of us can take a look at it.
-
Ummm....how come you do not have all the Media VPs? Or is it just me who is just a stupid n00b.
You are missing Mv_models from what I see. Also, a lot of problems appear inside the models section.
-
Ach, I just took a look at the first one:
Searching root pack 'C:\games\freespace2\scp\a_subspace.vp'
Searching root pack 'C:\games\freespace2\scp\Apollo_HTL.vp'
Searching root pack 'C:\games\freespace2\scp\axm_jad2eb.vp'
Searching root pack 'C:\games\freespace2\scp\axm_JAD_SE2.vp'
Searching root pack 'C:\games\freespace2\scp\Boomerang.vp'
Searching root pack 'C:\games\freespace2\scp\Homesick.vp'
Searching root pack 'C:\games\freespace2\scp\LightspeedFS2.vp'
Searching root pack 'C:\games\freespace2\scp\mv_core.vp'
Searching root pack 'C:\games\freespace2\scp\mv_textures.vp'
Searching root pack 'C:\games\freespace2\scp\Nebulae.vp'
- Move the files beginning with axm_ to \freespace2\JAD.
- Move Boomerang to \freespace2\boomerang.
- Move Homesick to \freespace2\homesick.
You are supposed to have the mods in separate subfolders, so that they won't conflict with each other.
-
That too, Lobo. So I think we've found our problem....
ALSO Homesick is very buggy for SCP. Perhaps thats the little bugger we need to clear.
-
That too, Lobo. So I think we've found our problem....
ALSO Homesick is very buggy for SCP. Perhaps thats the little bugger we need to clear.
Gah! I didn't think of that! I'm very prone to missing things staring me in the face... But that still doesn't account for Debug FRED2 choking on the messages when NO mods are selected at all.
I had another go at the Derelict mission with the VP files moved (and scp/data/missions renamed for extra security), but that still had no messages and had the brackets around Mjolnir 01. In debug I got the same error as I did in FRED2 debug. Log and screen attached.
Ummm....how come you do not have all the Media VPs? Or is it just me who is just a stupid n00b.
You are missing Mv_models from what I see. Also, a lot of problems appear inside the models section.
The reason that I don't have many of the Media VPs is because they take a long time to download on my dial-up connection, and my laptop has problems with having a lot of demanding models/effects. I had a few problems with Blue Planet because of this.
Debug builds have a tendency to crash, since the sole purpose of their existence is to track errors that occur. After the crash, you simply take a look at the log file. Or post it here so the rest of us can take a look at it.
I thought it was prudent to say when it crashed. Isn't that important?
[attachment deleted by admin]
-
Ohh....then I think we have found our problem. The FS2 models aren't fully compatible with SCP. Make sure you get mv_models 3.6.9 or mv_assets for 3.6.10. Then try again.
And yeah
I thought it was prudent to say when it crashed. Isn't that important?
That is important too. That tells us what the problem is. It seems as if the maximum message has been achieved.
Ok, I just thought of some (unlikely) cures if it still doesn't work.
Upgrade your Graphic Card driver to the latest one.
-
Num_messages is the sum of the messages in your messages.tbl + the number in the mission. So if the game is finding a rogue message.tbl with lots of messages in it you can easily crash the game if the mission also has a lot of messages and was also close to the limit.
In other words this is a rogue table/vp problem.
-
Okay. That would certainly be the problem, since I use custom message tables with more messages. :nervous:
I moved the custom messages.tbl out, tested it ... and it worked! It's so good to hear Rebus Station again! ;)
Thanks for all your help, everyone. :yes: :yes:
EDIT: I feel like I should have indicated I had a custom messages.tbl first, sorry about that.
[attachment deleted by admin]