Hard Light Productions Forums

Hosted Projects - FS2 Required => FreeSpace Conversion => Topic started by: ARSPR on April 24, 2006, 02:02:34 am

Title: compatibility digression
Post by: ARSPR on April 24, 2006, 02:02:34 am
Goober, can you post any of the expected errors/conflicts, please?.

I ask you this because as I have also Port 2.3, I've made another folder for shared components (movies, common fs1 vps, fsport_shine.vp and some more). I load this folder contents with SecondryList in each Port's MOD.INI. In this way my fsport_shine.vp is ALWAYS loaded AFTER fsport2_3.vp or fsport3_0.vp BUT I haven't noticed anything wrong (at least VERY noticeably wrong).

Thank you.
Title: Re: Important Compatibility Notice
Post by: Goober5000 on April 24, 2006, 09:14:17 am
I don't know the expected errors or conflicts.  The only way I discovered it was by naming awakenings.vp to fsport_awakenings.vp.  The name must be fsport-awakenings for it to have proper priority.

This only matters if you have an installed campaign with a file (such as a table or texture) that's supposed to override the main vp.
Title: Re: Important Compatibility Notice
Post by: ARSPR on April 24, 2006, 10:17:24 am
Well I have been digging in fsport3_0_3.vp and in previous fsport_xxx.vp and I've seen that only cruiser01-xxx.pcx and cruiser01b-xxx.pcx are inside both and ARE different; fsport3_0_3 comes with very ugly low res maps. I would take the bitmaps from fsport_hi-res.vp or any other place to update oficial fsport 3.0 release. Or just include all the bitmaps, shinemaps and glowmaps from fspor_shine, _hi-res and _glow to save time and future trouble.

(And if you do that, please remember to include the afterburner trails patch Backslash did: http://www.hard-light.net/forums/index.php/topic,38673.msg801767.html#msg801767)


EDITED:

And I've noticed more strange things in Windows sorting (at least in explorer). With some test files I obtain the following order within FSPort folder:
fsport0hi-res.vp
fsport3_0_3.vp
fsport_hi-res.vp
fsport_missions.vp
fsport-hi-res.vp
kk1.txt
kk_a.txt
kk-a.txt
ll1.txt
ll-.txt
ll_.txt

...


So in my WinXP SP2 _ goes "normally" before - BUT it is always AFTER any number.


Title: Re: Important Compatibility Notice
Post by: Goober5000 on April 24, 2006, 11:11:46 am
Well I have been digging in fsport3_0_3.vp and in previous fsport_xxx.vp and I've seen that only cruiser01-xxx.pcx and cruiser01b-xxx.pcx are inside both and ARE different; fsport3_0_3 comes with very ugly low res maps. I would take the bitmaps from fsport_hi-res.vp or any other place to update oficial fsport 3.0 release. Or just include all the bitmaps, shinemaps and glowmaps from fspor_shine, _hi-res and _glow to save time and future trouble.

That's by design.  The additional VP files are completely optional.

Quote
And I've noticed more strange things in Windows sorting (at least in explorer). With some test files I obtain the following order within FSPort folder:
...
So in my WinXP SP2 _ goes "normally" before - BUT it is always AFTER any number.

Don't worry about what Explorer does.  The only thing that matters is the order in which it's loaded by FS2.
Title: Re: Important Compatibility Notice
Post by: ARSPR on April 24, 2006, 11:46:43 am
Forget what I've said about Fenris and Leviathan textures because they are not normally used. It's not worth to update them in port.

1. Fenris is cruiser01.pof (ships.tbl in fsport3_0_3.vp). This model doesn't exist in port so it is directly loaded from mv_models.vp. But cruiser01.pof in mv_models doesn't use "cruiser01-xxx" textures but "Fenris-xxx".

2. Levy is cruiser01b.pof (ships.tbl in fsport3_0_3.vp) and this model does exist in port. But this time mv_models has a modular table (mv_models-shp.tbm) that changes the model to cruiser01x.pof which is the standar FS2 Levy model. This model doesn't use "cruiser01b-xxx".