Load-up screen when entering custom planets

[Seamhainn]

Hello!

 

I want to enter a new custom planet (liv_m99ab.mod - Custom Planet#1)). Is there a rule of thump which picture is shown in the load-up screen? Can I influence which picture is shown somehow?

 

Thanks for any help!

[Quanon]

Hello!

 

I want to enter a new custom planet (liv_m99ab.mod - Custom Planet#1)). Is there a rule of thump which picture is shown in the load-up screen? Can I influence which picture is shown somehow?

 

Thanks for any help!

 

I think you might have a look at these 2DA files :

 

- loadscreens

- loadscreenhints

- loadhints

 

And you can change the LoadScreenID in the .are file, I think its default set to 0.

 

So I suspect this number refers to a 2DA row.

 

Not a 100% sure about this, but it might lead you to something.

[Seamhainn]

Thanks, I will look that up!

 

EDIT: It think those .2das don't manipulate the picture, just the hints and such...

[Silveredge9]

It's actually pretty simple. Create your custom loading screen in photoshop, or get one using KTool, and rename it "load_NAMEOFCUSTOMMODULE.tga", then put it in your override.

 

So if the filename of my .mod/rim file was "bos_circus", the filename of the loadscreen would be "load_bos_circus.tga".

[Prime]

And I believe that the image gets stretched in the game, IIRC. So you may have to play around with the proportions a bit...

[Seamhainn]

Erm, the mudule's name is liv_m99ab. I named the file load_liv_m99ab.tga. Unfortunately it does not work.

 

I put it into override. Must it go into the .mod perhaps?

 

Thanks!

[Darth Xander]

Did you remember to change the LoadScreenID in the .are file so it corresponds with the new row of your loadscreens.2da?

[Seamhainn]

I don't get that in loadscreens.2da are just four bmpresrefs. I am confused here...

[Silveredge9]

Erm, the mudule's name is liv_m99ab. I named the file load_liv_m99ab.tga. Unfortunately it does not work.

 

I put it into override. Must it go into the .mod perhaps?

 

Thanks!

Yeah, it doesn't work. It only works if you are replacing a loading screen of an existing module.

 

I'm having this problem with reskinned modules. I have my loading screen tga file in the override folder, and I've edited the loadscreens.2da, adding a new row with what I think is the right information.

 

Still, I don't know where the LoadScreenID in the .are files fits into all of this, there isn't anything in loadscreens.2DA that could link in with this, like a row number or something.

 

What's strange though, is I have a reskinned module where all I did was create my loading screen and rename it to match the name of the .mod file... and it worked. But when I did the same with another reskinning module, it didn't work.

 

So confusing...

[Seamhainn]

NOW, it works for me, Silver. Try it again!

[Silveredge9]

Good news. I've figured out the kinks with it.

 

To add a custom loading screen to a custom module, you do as I said before. Just name the tga file "load_MODULENAME".

 

Before it worked for me on some modules, but not others. After a bit of experimenting here and there, I've figured it out. There seems to be some character limit or something in the filenames of the loading screens.

 

For example the loading screen for the module "bos_mandship2", which was named "load_bos_mandship2" didn't work. Yet when I renamed the mod file to "bos_msp2", and then the load screen to "load_bos_msp2" - Everything worked fine.

 

Anyways, for those interested, this is the loading screen I created. I'm pretty happy with it.

 

[Marius Fett]

Looking good Silver!

 

All we need now is a trailer and some screens!

 

[Quanon]

Anyways, for those interested, this is the loading screen I created. I'm pretty happy with it.

 

Drooltastic stuff Silver.

* hmmm I've seen the stuff on the rightside before *

[Marius Fett]

Hmm...

 

You know what Q, it looks a little familiar to me too...