Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: Gregster2k on August 22, 2005, 04:14:44 pm
-
(http://img333.imageshack.us/img333/3048/oops0ew.jpg)
Self explanitory. I decided to save some video overhead by not using Adveffects.vp and THIS was the result of omitting it.
:D
Latest Media VPs from the SCP website, too. -_-;;
-
Sounds about right. What did you expect to happen? :D
-
I thought Adveffects.vp was optional, considering all the warnings about it slowing down systems (which on mine, it does)
:mad:
-
All the media VP files are optional. The whole damn lot of them. If you don't have them you're going to miss out on certain features though.
You could try looking for some non animated glowmaps. I'm sure there are some packs of those around somewhere.
-
I still find it darn odd that most of the other ships, even the SF Mara (which has a counterpart that is animated in adveffects.vp), have glowmaps w/o adveffects.vp, but the Aeshma, Pegasus and the Cain/Lilith don't.
It looks more like an oversight. The readme told me that adveffects.vp has "animated high-res glowmaps", implying that the other VPs contained static glowmaps for the entire fleet.
-
Ya. I encountered this myself. Its just a simple matter of finding out what the same static glow-map on the Lilith is, extracting it, and renaming it to what the name of the same base texture for the Cain is (with the -glow extension of course).
-
I thought the static glow maps were supposed to be in the MV texture or MV effects pack.
The animated stuff is in the advanced effects pack.
So without it you should still have glow maps. At least static glow maps.
-
I had this problem once when removing adveffects. I just deleted the cache and restarted the game. Did the trick for me...
-
Try what Fenrir said, first.
If that doesn't work, you should be able to fix it pretty easily by extracting the glowmap ani, opening it in aniview, extracting the most-lit frame from it, saving that frame as "cruiser03-glow.pcx" (or "cruiser03x-glow.pcx", I forget which is which), and moving it to freespace2/data/maps.
-
Also, if what Fenrir said doesn't work, please mention it or (Better yet) toss the bug in mantis and assign it to me so I can fixx0r it before the next release.
-
well im headin to bed atm, exhausted after completing Transcend (man that was fun) --- ill try those things tomorrow and let you know how it turns out.
-
Originally posted by DaBrain
I thought the static glow maps were supposed to be in the MV texture or MV effects pack.
They are, at least in the pack I downloaded 3 weeks ago.
-
How is that a problem?
It looks incredibly cool and menacing IMO.
-
The problem is, for that particular mapping (along with a few others) the glowmaps were made after animated glows became standard practice. Proper high-res glows to match those maps were never made (to the best of my knowledge, anyway)
-
Like I said, the static glowmap for the front of the Cain, is identical to the front of the Lilith. Extract and rename... its as simple as that.