[Cobra]

i did as you said, and it works. damn, it still looks beautiful! *sniff*

[Ulala]

Originally posted by DaBrain

Maybe loading this effect into the gfx ram before the misson starts would fix it.

Is there an easy way to do this, or will I have to wait for some code modification or some such thing? I don't know how to do much other than copy and paste files from your zips.

[DaBrain]

I've no idea how the loading works atm, but it's a code issue. I can't change anything about the loading.

Maybe it's working as I suggested, already.


@Cobra
 That's good news on the one hand, but it toally confuses me on the other hand. I thought about a DDS problem of some kind, but if a single DDS frame works, this can't be the problem...

Is the flare still there?

[taylor]

Originally posted by DaBrain
Maybe loading this effect into the gfx ram before the misson starts would fix it.

I should be already.  The models are preloaded, bitmaps marked as used in the mission, and bmpman loads them into video ram.  The only way that it won't is if there isn't enough ram to stick everything into.  If that's the case then it could either be left out initially or the ram flushed when it gets full and new images start going in.

You have to remember that more than textures go into video memory.  You've got to count API stuff and geometry data for all models too.  In a typical mission you may only be able to get about 100 meg of textures on a 128 meg card.  Using -spec, -glow and -jpgtga, most missions are already above that.  Add to that the memory wasteful options of -pcx32 (used mostly for interface graphics at this point) and -d3dmipmaps (they are generated but not used) and that's more memory down the drain.  Also, turning on AA will use about twice the memory that it would otherwise.

[Cobra]

Originally posted by DaBrain
@Cobra
 That's good news on the one hand, but it toally confuses me on the other hand. I thought about a DDS problem of some kind, but if a single DDS frame works, this can't be the problem...

Is the flare still there?

nope.

[Ulala]

Originally posted by taylor

I should be already.  The models are preloaded, bitmaps marked as used in the mission, and bmpman loads them into video ram.  The only way that it won't is if there isn't enough ram to stick everything into.  If that's the case then it could either be left out initially or the ram flushed when it gets full and new images start going in.

You have to remember that more than textures go into video memory.  You've got to count API stuff and geometry data for all models too.  In a typical mission you may only be able to get about 100 meg of textures on a 128 meg card.  Using -spec, -glow and -jpgtga, most missions are already above that.  Add to that the memory wasteful options of -pcx32 (used mostly for interface graphics at this point) and -d3dmipmaps (they are generated but not used) and that's more memory down the drain.  Also, turning on AA will use about twice the memory that it would otherwise.

Well in that case, maybe my graphics card has finally met it's match.  The effect is still great, the slowdown is uncommon and is not that bad (no worse than when I played FS2 on one of my older systems when it first came out).

[Flaser]

Originally posted by Cobra
hey, DaB, i'm getting an expanding flare instead of an expanding shockwave.
pic:

Am I the only one who thinks this could be used for the new 'souped-up' effect?

Shockwaves are big and nasty - however IMHO they need more 'UMMPH!!!'.
Starting them out with a flare like that could do the trick.

[DaBrain]

Actually, they already start with this flare...

[Cobra]

it flares, then the flare goes inward, then the actual shockwave comes blasting out.

[Ulala]

'tis p1mp

[WMCoolmon]

**** I need to get my FS2 working.

Shockwaves are paged in at the beginning of the mission. I did not go to the trouble to make sure that they were kept in memory between missions, so what should happen (barring forgetfullness on my part) is that the shockwaves needed are paged in at the start of a level, then paged out, then the process repeats.

There should be no loading shockwaves in the level. Except from virtual memory.

[BlackDove]

So when do you think you'll have all of the Blue versions DaB?

[DaBrain]

Later...

Maybe tomorrow.

[Cobra]

hey, dab, have you found a fix for the expanding flare problem yet?

[MetalDestroyer]

Yeah, I could use your stuff into my Star Wars mods :crazy:

[DaBrain]

Originally posted by Cobra
hey, dab, have you found a fix for the expanding flare problem yet?

No, but it's probably a code bug.

You should report it to Mantis. Maybe it will get fixed till 3.6.7.

[Cobra]

roger!

[StratComm]

Originally posted by DaBrain


No, but it's probably a code bug.

You should report it to Mantis. Maybe it will get fixed till 3.6.7.

You know, I was wondering (not having the time to look at this myself yet) if this "expanding flare bug" would have anything to do with the improper warp glow scaling in the initial/final moments of a subspace protal's existance.

[BlackDove]

Originally posted by DaBrain
Later...

Maybe tomorrow.

*ahem*

The Public demands it.

[DaBrain]

Done.

Blue 3d shockwave release!

Super-High-End blue download (22 MB)

High-End blue download (8 MB)

Mid-Range blue download (2 MB)

Low-End blue download (250 KB)