[Admiral Nelson]

Welcome back.

It does complete FS2.  I will work on these shortly; I need to recalculate the RGB & luminosity values used in stars.tbl.  A possible complication is the lens flares, which aren't going to be exactly the same color as the stars themselves unless these too are all remade. I'll post the other requirements for FS1 etc, too.

[chief1983]

w00t

These things are so damn pretty, can't wait for the final 3.6.10 vps.

[IceFire]

In the mv_music.zip I just downloaded...it seems to be missing FS2_Amb_A01.ogg.  Good reason for that or just left out?  Just thought I'd bring it up.

[CP5670]

I don't think we have a high quality version of that one. If you know of one, send me a link and I'll update the VP with it. It's possible that I left one out by accident.

Note that there are a handful of cases where the music file appears to be higher quality, but it's just upsampled from the 22khz version and sounds totally identical to the old one. I don't remember the one you mentioned as being such a case though.

[IceyJones]

i have one suggestion for the improoved grafic-fx of shield hits.....imho this fx is in principle realy great, but it looks like a wall during a hit. it is not transparent.....would it be possible to increase the transparency for this effect?!

[ARSPR]

i got a problem but i dont know if it can be considered a bug or not or if this is just some random problem with my computer. Some beams like the shivan and AAA beams do not have the charge up effect or the "energy ball", for lack of a better term, during the actual firing phase. I think they are related to the MV_advancedeffect file, but having no modding experience whatsoever i cannot say for sure. a picture just to show what i mean.

DaBrain as you asked I was going to mantis it but this seems this very same issue, so I post it here although I suppose you've already found the reason.

On game startup with 3.6.9. debug I get the following errors:

• SBeamAglow.eff from Advanced Effects doesn't have their related frames. This is the cause for those missing beam glows.
• And also, 3.6.9. debug complains about BFRed (redefined in Advanced Effects beams2-wep.tbm) having more than 5 sections. Is this limit going to be pushed up in 3.6.10 builds?

I've re-run my AllxxxxShips.fs2 missions with XT1207 debug and then I've looked at the fs2_open.log. In addition to these two beam issues I've also noticed:

• AAAf and AAAh from advanced effects > beams2-wep.tbm use AAABeamAglow as muzzle. This texture is missing.
• Some beams (like SRed from the same table) use SBeamAA as the first section. This texture is also missing.

OTOH there are a lot of warnings like the following

Code: [Select]

Warning: Ignoring unrecognized subsystem fighterbay, believed to be in ship capital01.pof
And believe me when I say that there's A LOT of them.

What are they?

[Cobra]

Speaking of beamglow, I noticed one interesting thing. I actually saw the beamglow for the AAA on a Fenris, but it lasted about half a second.

[ARSPR]

Oooops I nearly forget. I had prevously mantised several issues from 1554 to 1557

Expert modeler help is specially needed in 1556. Please check it.

[Topgun]

Do you know anyone who likes making stars?   Just two systems are needed to complete FS2, and five more to complete all of FS1, Awakenings, ST:R, Cardinal Spear, Warzone and Aeos Affair.  Basically the fellow was working in descending star size order, so the main sequence stars are not completed.  Fantasy systems are excluded, as they don't have any 'proper' stars in any case.

I like making suns. I already made afew. IE red, gold and some others.

[fsphiladelphia]

It's not a problem, the color just changed.

I'm open for color suggestions though. I'm tempted to make some changes for the final release here again.

I really do like yellow ABs although they aren't canon. They look much better than old cyan ones. They look MUCH realer.

But as MediaVPs is intended to be a RETAIL enhancement, I would offer cyan as default and, in an optional vp, the yellow ones. (Although it could be some more packing work).

If MediaVPs are intended to be a retail enhancement, and the retail color sucks, then changing the color via MediaVPs seems completely legit as an enhancement goal; further, so many graphical changes have been made which distinguish FSO from Retail that, cosmetically, this is already a whole other game anyhow.  I say go with what looks best .  I mean, a simple color change doesn't really mean much re: what is or isn't canon (unless we start talking about changing the beamglows).

[MP-Ryan]

Whoa.

I just got a chance to test these when I fired up Dunkerque.

Now, I don't have GLSL support enabled (no shader 3 support on this vieo card) so perhaps that may be contributing to the issues, but I am having major LOD issues.  The Arcadia, Manticore, Orion, Argo... everything but the GTF fighters look like absolute garbage.

In other words - this takes it back to worse-than-retail quality if you don't have shader 3 support.  Is normal mapping entirely replacing the old high-resolution ships?

I'll post a screenshot momentarily.

[MP-Ryan]

Apologize for the darkness, apparently the 1028 Xt build doesn't preserve gamma settings when it takes screenshots.

http://members.shaw.ca/jillianandryan/files/freespace/screen0002.tga

At any rate - have the normal maps entirely replaced the his-res textures on the non-HTL ships?

[Herra Tohtori]

I prefer to use -no_set_gamma with FS2_Open, I got the overall colour settings so good that I don't really want FS2_Open to use any different settings.

That, and if your desktop gammaa/colour profile is a customized one, the screenies will not look like they appear in-game.

[chief1983]

Ryan, did you double-check the in game graphics options that your model detail option is set to full?  If so, possibly try a new pilot, maybe your old one got corrupted?  That's all I can think of.  Normal maps aren't replacing any models, only enhancing them.  Be sure to check with no mods too, and possibly look in the tech room or the F3 menu just in case.

[MP-Ryan]

The settings have not been touched.  The only difference is the enabled mod - 3.6.10 versus 3.6.8

Identical settings.  First image is 3.6.10, second is the old 3.6.8.  Here's what an Argo looks like.  Again, the gamma setting in FSO is not preserved in screenshots so they're dark.

http://members.shaw.ca/jillianandryan/files/freespace/screen0004.tga

http://members.shaw.ca/jillianandryan/files/freespace/screen0005.tga

I'm going to grab a capture of an Orion now.  It's really noticeable there.

[MP-Ryan]

Here's the Orion.  Again, the only change between the two screenshots is which mediavp set is in use.  First one is 3.6.10, second is 3.6.8.  Oh, and this is done with a totally new pilot, just to be sure there are no issues there.

http://members.shaw.ca/jillianandryan/files/freespace/screen0005.tga
http://members.shaw.ca/jillianandryan/files/freespace/screen0006.tga

Might I suggest one of you try disabling GLSL support with the 3.6.10 MVPs and see if you get the same issues?

[Cobra]

Stop using TGA >.<

[MP-Ryan]

Stop using TGA >.<

I'm lazy and just posting straight from my screenshots folder

[IceFire]

I don't think we have a high quality version of that one. If you know of one, send me a link and I'll update the VP with it. It's possible that I left one out by accident.

Note that there are a handful of cases where the music file appears to be higher quality, but it's just upsampled from the 22khz version and sounds totally identical to the old one. I don't remember the one you mentioned as being such a case though.

Got it...seems to be a few others "missing" as well but if they aren't present in high quality format then obviously thats a good reason for not including.

[Sparky]

i got a problem but i dont know if it can be considered a bug or not or if this is just some random problem with my computer. Some beams like the shivan and AAA beams do not have the charge up effect or the "energy ball", for lack of a better term, during the actual firing phase. I think they are related to the MV_advancedeffect file, but having no modding experience whatsoever i cannot say for sure. a picture just to show what i mean.

DaBrain as you asked I was going to mantis it but this seems this very same issue, so I post it here although I suppose you've already found the reason.

On game startup with 3.6.9. debug I get the following errors:

• SBeamAglow.eff from Advanced Effects doesn't have their related frames. This is the cause for those missing beam glows.
• And also, 3.6.9. debug complains about BFRed (redefined in Advanced Effects beams2-wep.tbm) having more than 5 sections. Is this limit going to be pushed up in 3.6.10 builds?

I love the new mediavps... but I dunno how to fix this either. I get the no beam glows only for the shivans...