|
|
Have you tried a 3.6.10 build? This should have fixed months ago. |
|
|
I have tried. Check topic again, I uploaded screenie.... http://www.hard-light.net/forums/index.php/topic,57390.msg1157212.html#msg1157212 |
|
2008-10-24 15:02
|
glowmap-bug.jpg (78,145 bytes) |
|
|
Attached screenshot from thread. |
|
|
This might be fixed. The latest Knightly builds should work (for the most part) with TBP again. Give the latest one a try and see if it still does it. |
|
|
Update..... Alright, suddenly it worked, and I didn't know why. I investigated, found out, and have the results here for you. Glowmaps work when the .fs2 file features the replacement info for the texture map AND the glowmap. like +old eaomega01a +new eaomega01a_Alexander +old eaomega01a-glow +new eaomega01a_Alexander-glow The new fred2open provided along latest nightly builds has glowmap selection included in the texture replacement list. Unfortunately, these entries in the .fs2 file are not available in mission files created with outdated builds of FRED2_open. That's why it never worked for me. I didn't find it out until now, because I always had the assumption the engine itself would look for the related glowmap and would't need an additional encouragement from the mission file. So, just trying a new fs2-open built didn't work, and the way this feature is implemented is a little unfortunate, coz it makes previous work obsolete. For the future ( but that's nothing for now, I can improvise for the time being ), someone can make a build that doesn't require changes to 3.4b missions to have glowmaps ingame. Thanks people for your help, your reward will be the EACW campaign ;) |
|
|
I think this can be closed since Skullar posted this awhile back: http://img136.imageshack.us/my.php?image=hermesod9.jpg |
|
|
I'll take your word for it Fubar :) |
- Anonymous
