Hard Light Productions Forums

General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: TopAce on June 17, 2011, 01:35:59 pm

Title: Debugging methodology
Post by: TopAce on June 17, 2011, 01:35:59 pm

My method is this:
1. Get the most recent _d build (obviously :P)
2. See if there are no error messages till the pilot screen
3. Go through all the custom ships in the F3 window, fixing errors one by one
4. Quit, go back to 2 again to see if I forgot something. If everything is okay...
5. ...sigh of relief

How are ya guys doin' it?

Title: Re: Debugging methodology
Post by: General Battuta on June 17, 2011, 01:37:03 pm

Load the missions tooo

Title: Re: Debugging methodology
Post by: MatthTheGeek on June 17, 2011, 01:51:37 pm

If you have done changes to tables, you might need to resave every mission in FRED (renamed subsystems for example).

Title: Re: Debugging methodology
Post by: Fury on June 17, 2011, 01:59:24 pm

Loading up missions in debug fred2_open is usually best method to catch problems in development phase. It loads up so much more data than simply getting to pilot screen and going through ships one-by-one in the lab.

Once you're past development and into final testing prior to release, finishing each mission in debug build would be smart move. Bugs in complex sexps or scripts may not be caught until they're actually ran in-game. Other bugs that might only get caught while playing include bugs in models, such as buggered up collision detection.

Title: Re: Debugging methodology
Post by: The E on June 17, 2011, 04:04:08 pm

For quick model testing, I have a mission with all the models in it. That will catch all model-related issues.

As for other bugs, since I build all my builds myself, I can launch straight into Visual Studio when an Error comes up that I can't decipher using the log alone.