[blowfish]

I am getting a really weird issue with glowmaps.  On standard ships, they look fine, but ever since I installed these new VPs, standard textures on user made ships look like they have no glowmaps (they look like retail textures).  This problem disappears when I use the 3.6.8 zeta MV_Textures VP.

Also - The new Shivan beam effects look great, but they sometimes look kind of odd (see screenshot).

[attachment deleted by ninja]

[DrewToby]

Regarding the secord part of Blowfish's post above:

Uh, the hell? The Ravanas I run into don't fire anything near that cool looking. I'm getting this straight beam of red light, nothing fancy at all, and it does a massive amount of damage.

Actually, now that I think of it, all the Shivan ships seem to have the same game-breakingly-powerful, solid-red beams...even the Lilith. I just finished watching the Keeper in Blue Planet (with a pilot that worked with the previous VPs) get cut down by a single Lilith on medium. The thing fired maybe...four or five times, or so, and the Keeper went down. The beam was about as wide as the Lilith's body.

I'll go back in-game and see if I can get a snap of it...seems only to have happened to my Shivans. Never had anything weird happen before this, too.

EDIT: Also, just to be sure...these VPs are compatible with everything that worked with the previous batch, right? Like BP.

[DaBrain]

I am getting a really weird issue with glowmaps.  On standard ships, they look fine, but ever since I installed these new VPs, standard textures on user made ships look like they have no glowmaps (they look like retail textures).  This problem disappears when I use the 3.6.8 zeta MV_Textures VP.

Also - The new Shivan beam effects look great, but they sometimes look kind of odd (see screenshot).

That can only happen if you didn't delete/remove the mv_models.vp.

[DaBrain]

Regarding the secord part of Blowfish's post above:

Uh, the hell? The Ravanas I run into don't fire anything near that cool looking. I'm getting this straight beam of red light, nothing fancy at all, and it does a massive amount of damage.

Actually, now that I think of it, all the Shivan ships seem to have the same game-breakingly-powerful, solid-red beams...even the Lilith. I just finished watching the Keeper in Blue Planet (with a pilot that worked with the previous VPs) get cut down by a single Lilith on medium. The thing fired maybe...four or five times, or so, and the Keeper went down. The beam was about as wide as the Lilith's body.

I'll go back in-game and see if I can get a snap of it...seems only to have happened to my Shivans. Never had anything weird happen before this, too.

EDIT: Also, just to be sure...these VPs are compatible with everything that worked with the previous batch, right? Like BP.

I didn't change any weapon stats in the tables. If the weapons are stronger or weaker, something else is most likely interfering, which probably also explains why the correct effects do not show up.

Please download the readme and follow the instructions step by step.


The compability with mods is yet to be tested. I also noted that there migth be problems with some mods, although only problems of graphical nature. (Also in the readme)

[blowfish]

I am getting a really weird issue with glowmaps.  On standard ships, they look fine, but ever since I installed these new VPs, standard textures on user made ships look like they have no glowmaps (they look like retail textures).  This problem disappears when I use the 3.6.8 zeta MV_Textures VP.

Also - The new Shivan beam effects look great, but they sometimes look kind of odd (see screenshot).

That can only happen if you didn't delete/remove the mv_models.vp.

But I did remove mv_models.vp.

[DaBrain]

The models in the MV_Assets.vp all use renamed textures. Pretty much none of them can even use the maps included in the mv_textures.vp.

Make sure you don't have a mv_models.vp in the root directoy either. Also look for the z_pack.vp.


Check your MV_Assets.vp. Maybe the file is corrupt and doesn't work.

[DaBrain]

In "Their Finest Hour" it appers there are some beam-free issues

Has that one been in Mantis before?

[blowfish]

 

The models in the MV_Assets.vp all use renamed textures. Pretty much none of them can even use the maps included in the mv_textures.vp.

Make sure you don't have a mv_models.vp in the root directoy either. Also look for the z_pack.vp.


Check your MV_Assets.vp. Maybe the file is corrupt and doesn't work.

Well, that would explain why no user-made ships look correct ... if all of the textures are renamed (all the HTL models work fine).

So is it safe to use mv_textures with mv_assets, or will that mess something up?

[DrewToby]

I didn't change any weapon stats in the tables. If the weapons are stronger or weaker, something else is most likely interfering, which probably also explains why the correct effects do not show up.

Please download the readme and follow the instructions step by step.


The compability with mods is yet to be tested. I also noted that there migth be problems with some mods, although only problems of graphical nature. (Also in the readme)

Yeah, it's not a problem in the installation. That was my first thought. It actually seems to just be the beam itself: just tested it, and found that the ships are using the HRed beam. That explains the monstrous damage, though I thought they had a different look to them. Here's an image of the beam itself.



Is that the correct effect for the HRed? Solid red, no white core? Seems a little odd, compared to the others, which I stared at long enough to fly into, unfortunately. Did the same with most of the normal-mapped ships.

I know you've heard it before, but you guys (Upgrade Project, et al) are absolutely amazing. @_@

[Talon 1024]

Hey people.  I've really loved this release of the MediaVP 3.6.10 Beta.  The missile engine glows really make it look a lot more realistic.  I was just wondering if you could do something similar for ship thrusters too.

[DaBrain]

Well, that would explain why no user-made ships look correct ... if all of the textures are renamed (all the HTL models work fine).

So is it safe to use mv_textures with mv_assets, or will that mess something up?

No, you got it wrong. The texturenames in the models have been renamed, as well as the textures. So using the mv_textures should practially do nothing. It has textures in it, no model is looking for. You might only mess the tables a bit by adding it.

So I suppose your Assets VP isn't working correct.

Is that the correct effect for the HRed? Solid red, no white core?

No it looks broken. Actually no beam effect looks like that.

But again, if the ships have beams they shouldn't have, or the beams do more damage than they should do, there are most likely other VPs, or tbls interfering. Make sure your FS2 directory is clean. Also look into the data folder. There really shouldn't be any tables in there.

Hey people.  I've really loved this release of the MediaVP 3.6.10 Beta.  The missile engine glows really make it look a lot more realistic.  I was just wondering if you could do something similar for ship thrusters too.

Thanks. Finally somebody wrote something about that.
The flares for the missiles where actually an idea for SoL, but I was able to expand that by making use of the mipmaps. So the flares fade in.

I'd love to see that for the fighters, but it would be quite a bit of work and I won't do it, but it is possible.

[Ghost]

Didn't run any missions, just looked through the tech room. Good job, Devs!

[blowfish]

Yeah, it's not a problem in the installation. That was my first thought. It actually seems to just be the beam itself: just tested it, and found that the ships are using the HRed beam. That explains the monstrous damage, though I thought they had a different look to them. Here's an image of the beam itself.

Is that the correct effect for the HRed? Solid red, no white core? Seems a little odd, compared to the others, which I stared at long enough to fly into, unfortunately. Did the same with most of the normal-mapped ships.

If that is BluePlanet (which I think it is), then those Ravanas are supposed to be using HReds instead of LReds in that mission.  Don't know what's wrong with those beams though ... the HRed looks OK to me (aside from having no beamglow).  I think that the issue you are experiencing occurs when one of the beam textures defined in the table can't be found anywhere, though I have no idea why this would happen.

No, you got it wrong. The texturenames in the models have been renamed, as well as the textures. So using the mv_textures should practially do nothing. It has textures in it, no model is looking for. You might only mess the tables a bit by adding it.

So I suppose your Assets VP isn't working correct.

But won't user-made ships still be looking for those textures?  Or are those textures supposed to be in mv_assets too?

[DaBrain]

If that is BluePlanet (which I think it is), then those Ravanas are supposed to be using HReds instead of LReds in that mission.  Don't know what's wrong with those beams though ... the HRed looks OK to me (aside from having no beamglow).  I think that the issue you are experiencing occurs when one of the beam textures defined in the table can't be found anywhere, though I have no idea why this would happen.

Well, maybe Blueplanet is requesting beam textures from an older MediaVP, which don't exist anymore. I don't know.

The first thing I'd try, is use FS2 without any mods and see if that helps.

But won't user-made ships still be looking for those textures?

Yes, that's why I wrote that into the readme.

[Zacam]

So, uh, why does MV_Effects\models (with the exception of shockwave.pof) have redundant POFs as contained in MV_Assets\models? I can determine a difference with some, but not all.

(by differences, I mean OTHER than texture renaming.)

Also, mv_shockwave-shp and mv_shockwave-wep are identical between MV_Effects and MV_AdvEffects.

*EDit: Corrected myself before I embarassed myself.

[blowfish]

Hmm ... the HTL Dis seems to have some holes in its texture, possibly maps that didn't get renamed?  Also the HTL TAC 1 (I never thought there would actually be one) seems to have too little mass - I can knock it around with Subachs and Tempests, and it has a seizure when it blows up.

[FT-Hunter]

I will place a mirror up as soon as i get these files.

[Zacam]

blowfish: The mass value is attributed, but the CENTER of mass is not, according to PCS2.

The moment of inertia values are radically different as well.

**Edit: Changing the moment of inertia values in ModelView32 corrected it for me. I was going to edit in PCS2, but upon saving, the file size doubled for no reason what so ever (that I could determine). Which sucked, because I had to hex edit the pof to rename debris-2 to debris02.

Also, I noticed that while I fixed the thrusters positions on the Ravana, I forgot that the model lacked collision. From the thread ARSPR linked to (The topic for the Ravana) a RAR was attached which had both fixed thrusters and collision.

Capital2S-01.7z is an updated copy of that model.
MD5: 8A870A7DF59FB45A1F46D0366AE14370

And the fixed Cargo Container:
Cargo03.7z
MD5: 8F800B8E7E7B08C0733EAC3AC0F2F196

DaBrain: You might want to clear out your cache folder. I've found of blueplanet cache files in MV_Assets. I also have of cache files being generated INSPITE of them existing in MV_Assets: AstB01, AstB02, AstB03, Belial, CMeasure01, spacehunk and naturally, Capital2S-01 and Cargo03. Adding the updated ones into MV_Assets does not generate new ones.

[ARSPR]

So, uh, why does MV_Effects\models (with the exception of shockwave.pof) have redundant POFs as contained in MV_Assets\models? I can determine a difference with some, but not all.

(by differences, I mean OTHER than texture renaming.)

Also, mv_shockwave-shp and mv_shockwave-wep are identical between MV_Effects and MV_AdvEffects.

*EDit: Corrected myself before I embarassed myself.

Yeap, there are a lot of useless models in mv_effects. They're never going to be loaded if assets is present.

OTOH Zacam is right. If as a installation rule you post that mv_adveffects needs mv_effects, then you can delete the redundant shockwave definition tables from mv_adveffects.

[Darklord42]

Thanks for the small fixes Zacam I didn't see those.  I was just about to mention the crazy cargo container when it took damage spinning in all directions.