All Projects FSSCP  wxFRED

View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000762FSSCPgameplaypublic2006-01-30 19:092006-11-01 04:56
ReporterARSPR Assigned Totaylor  
PrioritynormalSeveritymajorReproducibilityalways
Status resolvedResolutionfixed 
PlatformP4 HT, 1.5 GB RAM, R9800Pro 128OSWindowsOS VersionXP SP2
Summary0000762: Reinforcement calling is broken (c -> 4)
DescriptionStarfox has noticed, and I can confirm it, that at least in "As lightning fall" Reinforcement calling does not work and you need it to finish the mission.

I attach a screenshot where you can see how "4. Reinforcements" appears dark in command window.

Maybe it can be related with 691 bug.
TagsNo tags attached.

Activities

2006-01-30 19:09

 

screen0274.jpg (188,681 bytes)   
screen0274.jpg (188,681 bytes)   

taylor

2006-01-30 20:06

administrator   ~0004565

This is related to something that Goober did to missionparse, but it annoyed me enough last night that I have been fixing a few similar places. This one in particular was an easy one to deal with so I'll go ahead and commit it.

It's not related to 691.

taylor

2006-01-30 20:34

administrator   ~0004566

Ok, should be fixed in next build.

taylor

2006-01-30 20:34

administrator   ~0004567

Fixered.

Goober5000

2006-01-30 20:39

administrator   ~0004569

Oh no! Sorry, I thought I had got all of these. :(

I just saw your fix in my inbox and I just wanted to make sure that worked on your end. Does the wing assignment will work there? I'm not sure if rforce_obj's wing number is set by that point.

Goober5000

2006-01-30 20:40

administrator   ~0004570

Eh, how did I manage to submit a comment after the bug was closed? O.o

Reopening until taylor responds and probably gives me another smackdown. :p

taylor

2006-01-30 20:55

administrator   ~0004571

*SMACK*

Yeah it works, I wouldn't have commited it otherwise. :) And Wings are processed before reinforcements. It worked fine in testing but I did double check that before commit just to be sure.

There are a couple of other similar problems, mainly relating to FRED, and at least one relating to info that doesn't get reset because of init order. The init order one I'm still hacking on as I get time (it's not major though). The FRED one I haven't really touched yet (that "num != -1" thing).

Issue History

Date Modified Username Field Change
2006-01-30 19:09 ARSPR New Issue
2006-01-30 19:09 ARSPR File Added: screen0274.jpg
2006-01-30 19:47 taylor Status new => assigned
2006-01-30 19:47 taylor Assigned To => taylor
2006-01-30 20:06 taylor Note Added: 0004565
2006-01-30 20:34 taylor Note Added: 0004566
2006-01-30 20:34 taylor Status assigned => resolved
2006-01-30 20:34 taylor Resolution open => fixed
2006-01-30 20:34 taylor Note Added: 0004567
2006-01-30 20:39 Goober5000 Note Added: 0004569
2006-01-30 20:40 Goober5000 Status resolved => feedback
2006-01-30 20:40 Goober5000 Resolution fixed => reopened
2006-01-30 20:40 Goober5000 Note Added: 0004570
2006-01-30 20:55 taylor Note Added: 0004571
2006-01-30 20:56 taylor Status feedback => resolved
2006-11-01 04:56 taylor Resolution reopened => fixed