[Silent Warrior]

So there I was, playing JAD2 without a care in the world, and suddenly I noticed that some meshes stopped being rendered. Their glowpoints were still there, though - you really should see the Ares this way, looks just like a christmas-tree. Since these meshes were all fighters (Lokis, I believe), missiles was enough to work around this little problem.
But then I fired up Desperation ch. 2. Some four missions in, I found that neither the Rakshasa, Aeshma, Basilisk, Lilith/Cain, even the Demon, and just about every terran fighter/bomber except the Perseus wouldn't render. Just two missions earlier, though, the Demon rendered just fine. I haven't checked today, though, it might just be a random wossname. In the mission at hand, though, I had to whack mainly Cains and Rakskhasas -> unplayable. Thoughts?
I think I exited FS2 and started it again, and the problem remained. If I did indeed exit and restart. I didn't reboot.

Specs:
P4 2.0A Ghz running at 2.1 GHz
512 Mb RDRAM
Radeon 9700 Pro 128 Mb, running that HDR-shader the community refined a good while ago (Omega 5.12)
Windows XP Home SP2
SoundBlaster Live! Platinum 5.1 (LOVE that LiveDrive!), latest and halfway ancient drivers
Saitek X45

FS2:
Recent CVS-exes, preferring P4.
3.6.8 beta Media-VPs
Video: OpenGL 1024x768x32
Sound: EAX
Speech: Disabled, except for techroom

Commandline: C:\Games\FreeSpace2\fs2_open_r-P420051222.exe -spec -glow -jpgtga -mipmap -nomotiondebris -2d_poof -cache_bitmaps -img2dds -targetinfo -ship_choice_3d -3dwarp -warp_flash -snd_preload  -ambient_factor 70 -mod Desperation Right gorgeous, I tells j00! Framerates 20-60, some sort of mega-stutter/monster-slowdown when something big explodes or when flak gets dense, though, but very much playable.

[Edit] Downloading latest exes and I just read about the 3.6.8 MVP-updates. To be bagged. But do keep thinking about this.

[Edit 2] Hm... It still happens, but not on the first mission played... And with the new beta-MVPs, I get monster-slowdowns when beams are fired. Don't wanna play one mission, exit, restart, play another mission, exit, restart etc...

[CaptJosh]

When that happens, it's usually time to restart the game if not your computer. I ran into this while playing a version of Sol: A History where I specially modded the tables so that they would work on SCP. As far as I can tell, it's a memory leak issue. One thing that might help is turning off -cache_bitmaps. bmpman bitmap caching is known to cause some memory issues. Something about it not unloading the cached bitmaps from memory, so you run out of memory for stuff. I ran into this playing the FS2 main campaign on earlier builds when caching bitmaps was the default behavior of the SCP and I would get stuck repeating a mission because I screwed up in one way or another. On each progressive load, the mission ran slower and had more jitter, particularly when beam fire came into play. You also might want to kill that -mipmap switch, come to think of it.

[Silent Warrior]

Buggrit... Will do. Memory-leaks r teh suck...

[Mr_Maniac]

Maybe you could try to deactivate -img2dds?
I had that problem, that Ships get transparent with -img2dds under Windows/OpenGL (works fine under Linux )...
Maybe a miscalculation of the Alpha-Channel?

Oh... And those Monster-Slowdowns: It's most propably the adveffects.vp.
I don't have slowdowns with beams, I have them with the Ultra-High-Res-Shockwave
But that's not too bad... So I leave it in because I like it High-Res (and the rest of the game runs great)

[taylor]

I recently noticed a problem with missing ship textures when playing Derelict.  It was always on the same ships, missing the same textures (not all of them, just some), in the same mission, and was certainly not because of a memory leak or anything.  I made an OpenGL change or two after that so it may be fixed now, I haven't checked since.  This may not be anything related to the original thread problem though, but it is similar.  If the current CVS build fixes it then it could have been the problem.

I had that problem, that Ships get transparent with -img2dds under Windows/OpenGL (works fine under Linux )...
Maybe a miscalculation of the Alpha-Channel?

It messes up under OS X too unless I do some freaky byte-swaps.  All data is presented as BGR order rather than RGB and I think it's having issues with that during compression.  I haven't figured out how to deal with that yet though.  OS X has the byte-swaps but those aren't set up for Windows to use.  There are some OGL hints I can use but haven't really had a chance to test them yet.