All Projects FSSCP  wxFRED

View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000780FSSCPFREDpublic2006-02-02 13:562006-02-03 05:19
ReporterShade Assigned ToGoober5000  
PrioritynormalSeveritytweakReproducibilityalways
Status resolvedResolutionfixed 
Summary0000780: FRED does not save wing contents
DescriptionAfter placing ships into a wing, FRED does save the existence of the wing but not which ships are part of it. As a side effect, each time this results in a 'ghost' wing of 0 ships that can't be removed from within FRED itself, rendering that wing name unusable.

Specifically, it seems to happen when the mission is saved, not during wing creation itself, as at that time they can be edited and disbanded as usual.

It does not crash FRED or prevent it from saving the mission, just throws a warning message.

Problem can be fixed by opening mission file in notepad and manually adding in the ship names for each wing (Alpha 1-3 etc.), which lets the mission play. Ghost wings can be removed simply by deleting the empty wing in notepad. It all happens again if the fixed mission is loaded into FRED and saved, though.
Additional InformationWarning message when saving mission: Wing_Objects of "wing" references an illegal object type.

Happens in fred2_open_r-P420060129.exe regardless of installed mods.

System: Athlon X2 4600+, 2GB Ram, GeForce7800GTX.
TagsNo tags attached.

Activities

Goober5000

2006-02-02 17:18

administrator   ~0004637

Last edited: 2006-02-02 17:18

 I put a number of fixes relating to this problem into CVS yesterday, so this may be fixed. Unfortunately as it's not exactly the same as http://lore.maxgaming.net/~scp/mantis/bug_view_page.php?bug_id=0000766 I can't say for sure. Can you check the latest CVS?

edited on: 02-02-06 12:18

Shade

2006-02-02 17:44

developer   ~0004638

Last edited: 2006-02-02 18:05

 Tried the latest I could find with HLP down, fred2_open_r-20060131.exe, and the problem is still there. The exact problem is here in the mission file:

#Wings ;! 1 total

$Name: Alpha
$Waves: 1
$Wave Threshold: 0
$Special Ship: 0 ;!

$Arrival Location: Hyperspace
$Arrival Cue: ( true )
$Departure Location: Hyperspace
$Departure Cue: ( false )
$Ships: ( ;! 1 total
    ""
)
+Hotkey: 0
+Flags:( )


Notice $Ships just has "" where it should have "Alpha 1" to whatever. I used 1 ship for Alpha in this case but tested with several and the number does not matter.

Did some further testing too, and it seems this problem only applies to the first wing in a mission. I added in a beta wing for this test and it was saved to the file with the proper ship information.

[Edit] Tried debug build, which crashed as soon as I tried to save a mission that had nothng but the initially placed fighter after I assigned it to a wing. Uploaded the debug spew. Also, I probably should mention I was using -fredhtl for all these tests.

edited on: 02-02-06 12:47

edited on: 02-02-06 13:03

edited on: 02-02-06 13:05

2006-02-02 18:01

 

FredBug_0000780.txt (952 bytes)    
Assert: num != -1
File: c:\fs2_open\code\mission\missionparse.cpp
Line: 4128
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
    fred2_open_d-20060131.exe 004d7886()
    fred2_open_d-20060131.exe 004d955f()
    fred2_open_d-20060131.exe 004da4a6()
    fred2_open_d-20060131.exe 00428674()
    fred2_open_d-20060131.exe 00428069()
    fred2_open_d-20060131.exe 008cb770()
    fred2_open_d-20060131.exe 008cb54b()
    fred2_open_d-20060131.exe 008cb465()
    fred2_open_d-20060131.exe 008b6c8c()
    fred2_open_d-20060131.exe 008b72c5()
    fred2_open_d-20060131.exe 008ccd2f()
    fred2_open_d-20060131.exe 008c99de()
    fred2_open_d-20060131.exe 00434ac1()
    fred2_open_d-20060131.exe 008ecf7d()
    fred2_open_d-20060131.exe 008b0829()
------------------------------------------------------------------
FredBug_0000780.txt (952 bytes)   

Goober5000

2006-02-02 22:26

administrator   ~0004639

Well yesterday was after that build came out, wasn't it? ;)

Wait for the latest CVS and try again. :)

Shade

2006-02-02 22:53

developer   ~0004640

Well yeah but I figured as I'm in europe there was an offshot chance there be a timezone issue so it was worth a shot. I'll try again once a new build comes out. Not a big problem anyway as the missions work fine in-game after being fixed in notepad.

Goober5000

2006-02-03 05:19

administrator   ~0004641

Well I just tested this in CVS FRED and it worked. :)

Issue History

Date Modified Username Field Change
2006-02-02 13:56 Shade New Issue
2006-02-02 17:18 Goober5000 Note Added: 0004637
2006-02-02 17:18 Goober5000 Status new => assigned
2006-02-02 17:18 Goober5000 Assigned To => Goober5000
2006-02-02 17:18 Goober5000 Note Edited: 0004637
2006-02-02 17:44 Shade Note Added: 0004638
2006-02-02 17:47 Shade Note Edited: 0004638
2006-02-02 18:01 Shade File Added: FredBug_0000780.txt
2006-02-02 18:03 Shade Note Edited: 0004638
2006-02-02 18:05 Shade Note Edited: 0004638
2006-02-02 22:26 Goober5000 Note Added: 0004639
2006-02-02 22:53 Shade Note Added: 0004640
2006-02-03 05:19 Goober5000 Status assigned => resolved
2006-02-03 05:19 Goober5000 Resolution open => fixed
2006-02-03 05:19 Goober5000 Note Added: 0004641