Couple of weird issues with 2.12 Patch 1

[Blammo]

LA-5 texture externally looks weird.  The lettering and other elements are not matching up with the plane body.  Possible this is something with my install, but every other plane looks correct.

Offline, when you do a mission and then go back to the back, all of the NME GVs/Planes are gone and don't return until you quit and rejoin.

GV engine sounds seem louder.  This is specifically true with the Jeep.  May just be me, but I have them turned down really low and yet when I drive a jeep around it seem very loud compared to all other GVs.  Maybe this is just modeled differently because it is open are, but thought I would bring it up.

When looking at planes in the hangar and switching between planes each on has to refresh as if loading the texture for the first time (I describe it that way because on my old system I used to have textures set not to pre-load and it would behave that same way).  You change from one plane to the next and you see the model for a moment with no skin.  It then fills in and in a couple fo seconds is correct.

[Blammo]

Last night I deleted my cache and renamed the video8.cfg.  I let the cache get rebuilt and I am still seeing the same thing.  What it looks like is that the skin is not properly oriented to the model.

Anyone else seen this?

Also notice that there is a stutter in my frame rate each time something is rendered for the first time.  For instance, if I shoot at the drone B-24 and a langing gear falls off, when it first falls away, there is a stutter.  If I cause the thing to burst into flames, there is a stutter.

This was not there prior to this upgrade.  It may have something to do with what I am seeing in the hangar as well.

[Pyro]

Can you post a screenshot?

[Krusty]

I get the same thing on the La5. You can see the full profile of an la5, but shrunk and placed in a wierd place. It's all mis-mapped or something.


I haven't noticed the hangar display issue, though, but I did notice a bit more stuttering.

I've got an E6420, 2GB DDR2 dual channel, PCIe Ge7600 GTS 256MB, running 1280x1024, 512 texture res, preload textures, preload skins, hardware vertex enabled (I think that's it, I've got the box below "preload" checked), all GV/gun effects enabled, sliders at max.

[Kermit de frog]

With Patch 1

I and everyone around me noticed stuttering all their end at the same time.  we were flying together for over an hour or two and then bam, in a few minutes, we were hit with stuttering every 30sec or so.  Seemed to stutter when we were firing, or lookin around.  Maybe sametime was due to we all were fighting at same time so naturally the stutter comes when fighting.

I wrote this poorly, but I'm in a hurry, sorry.

[Hamltnblue]

Could be the extra bandwidth of hundreds of people downloading the updates and patches as well as the fresh download of textures which happens after the update.

[Blammo]

With Patch 1

I and everyone around me noticed stuttering all their end at the same time.  we were flying together for over an hour or two and then bam, in a few minutes, we were hit with stuttering every 30sec or so.  Seemed to stutter when we were firing, or lookin around.  Maybe sametime was due to we all were fighting at same time so naturally the stutter comes when fighting.

I wrote this poorly, but I'm in a hurry, sorry.

That is very similar to me...everytime I fired or looked at new things, etc.

I went online and when I try to select either LA, I get an invalid skin ID error.  So, I deleted the skins and went offline to download them...They are not availabe on the skins page.  Were the skins removed?

For the stuttering, did not see it immediately online (like I did offline), but every now and then I would get a little hiccup.

Intel Quad Core 2.66, 2 GB RAM, 8800 GTC SSC w/ 640 MB RAM

[Blammo]

OK, figured out the LA5 issue.  Every plane that got updated now no longer matches the skins so anything bu the default skin will not work.

Still not understand the stuttering, but it got me killed.  Then, after flying a while it stopped.  I think because by that point every texture had finally actually loaded.  Could be wrong, but it jsut doesn't seem like the the textures are actually in memory.  Either that or they are taking a lot longer to render in this release.