Hard Light Productions Forums

Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: Solatar on January 02, 2005, 04:18:42 pm

Title: Little question about custom loading screens
Post by: Solatar on January 02, 2005, 04:18:42 pm
I'm trying to FRED a simple mission, and I figured "what the heck?" and took a screenshot of the mission for use as a loading screen (kinda a preview).

I selected it in FRED, but it refuses to show in fs2_open (using fs2_open_T-20041230). It also refuses to stay in the text box in FRED after I save it...

I've put it in data/missions and data/interface, as well as /data.. Is there a specific place I need to put it? Or anything else I need to know? Thanks.

-Solatar

EDIT: it's a 256 color pcx
Title: Little question about custom loading screens
Post by: taylor on January 02, 2005, 05:26:44 pm
What filename are you using for the image?  You set the image for both resolutions or just one?

Not sure what's going on there with FRED clearing the textbox on save but somebody will look at it.
Title: Little question about custom loading screens
Post by: phreak on January 02, 2005, 05:32:52 pm
ill take a look since i implemented it.  mantis it

edit:
make sure you post the mission in question as well as the loading screens.
Title: Re: Little question about custom loading screens
Post by: Goober5000 on January 02, 2005, 05:57:35 pm
Quote
Originally posted by Solatar
I selected it in FRED, but it refuses to show in fs2_open (using fs2_open_T-20041230). It also refuses to stay in the text box in FRED after I save it...
This sounds just like the disappearing squadron info bug from retail FRED2.  Someone probably forgot an UpdateData call.
Title: Little question about custom loading screens
Post by: phreak on January 02, 2005, 06:00:41 pm
:nervous:
Title: Little question about custom loading screens
Post by: Solatar on January 02, 2005, 06:10:52 pm
Filename is SM-01-loadHires.pcx (only in hi-res right now).

I'll post the completed mission here in a while if I can find some webspace, but it's a bit heavy on the MODs...(I was experimenting with Shivan ships, etc...).

I don't think it's mission dependant though, because I've had this problem before.

EDIT: I'll see if I can add it manually in the mission with Notepad.:)
Title: Little question about custom loading screens
Post by: Solatar on January 02, 2005, 06:26:48 pm
Code: [Select]

$Starting wing names: ( "Rama" "Arjuna" "Gamma" )
$Squadron wing names: ( "Rama" "Arjuna" "Gamma" "Delta" "Epsilon" )
$Team-versus-team wing names: ( "Rama" "Zeta" )
$Load Screen 1024: SM-01-loadHires.pcx




Doesn't work however.
Title: Little question about custom loading screens
Post by: phreak on January 02, 2005, 06:59:16 pm
i figured it out.  both $Load Screen 1024: and $Load Screen 640: must be present

Try making a dummy entry that uses the 640 entry for now.

this behavio(u)r has been corrected.
Title: Little question about custom loading screens
Post by: Solatar on January 02, 2005, 09:02:17 pm
I filled in both slots, and although the text disappeared, the loading screens DO show up.:D
Title: Little question about custom loading screens
Post by: phreak on January 02, 2005, 09:33:01 pm
nevermind.  the text boxes work on my end.  dunno what could be causing it.
Title: Little question about custom loading screens
Post by: taylor on January 02, 2005, 11:03:16 pm
What you did works phreak, he just needs a new FRED build.  The text box was getting cleared on parse so both problems were from the same issue which you fixed. :)
Title: Little question about custom loading screens
Post by: Solatar on January 03, 2005, 06:19:19 pm
Well, I'll try to find a more up to date version of FRED, but since it's working fine I won't complain further. Thanks for your help. :)
Title: Little question about custom loading screens
Post by: phreak on January 03, 2005, 08:59:45 pm
well its gonna require a fred build that hasn't been released yet.  you just need to remember to fill in both resolutions for now, even if the other one is just a dummy.