[Bobboau]

if you're useing the 3.6 exe, try this my newer builds have been useing a totaly diferent method for drawing backgrounds. so maybe this will be fixed (though I doubt it)

[Tolwyn]

hmm... the plaet is in non standard reolution of 1200*1200

[Bobboau]

that could quite posably be causeing problems try resizeing it to 1024^2, though the game should be resizeing it already, but it could be resizeing it to 2048^2, wich might be too big for your card.

[Tolwyn]

I will give it a try... I wanted to resize them anyway, in order to save some cpu time

[Flipside]

Hmmmmmmmm... I got this on some of my skyboxes for a while, I think I sent an Email through the tester list. I just checked and yes, it is still happening, at first I thought it was an odd polygon and was my doing, but I've checked the skybox on a much earlier build and it seems fine.
I'll post screenshots and try to identify the first build that did this tonight

[Tolwyn]

hmm... and there is no easy way to resize planets and keep alpha chanel. I will have to rerender them

[ShadowDrakken]

just curious, but why do you need a 1200x1200 planet when the game only runs at 1024x768 anyway? isn't it just a waste to have a texture that large?

[Tolwyn]

because.... maybe I want a large scaled planet?

[gevatter Lars]

I haven't read everything above...only thats about planets and other stuff.
Well I got the bug out with activating something called "-d3d_bad_tsys"

With this activ I can see the planets..looking nice and it runs without problems.

[Lightspeed]

Originally posted by ShadowDrakken
just curious, but why do you need a 1200x1200 planet when the game only runs at 1024x768 anyway? isn't it just a waste to have a texture that large?

1200x1200 is stupid anyway. Either make it 1024x1024 and save 12 (TWELVE!) megabytes of texture space, or go ahead and add enough detail so it's worth the 2048x2048 pixels.

[Flaser]

Futhermore to actually answer you question ShadowDrakken - it's because the maps are projected onto the models - so when you're flying next to a destroyer only a portion of the map is visible.

For background elements, the same issue is present when the mission designer tries to simulate a planet very close.

[Tolwyn]

Originally posted by Flaser
For background elements, the same issue is present when the mission designer tries to simulate a planet very close.

exactly... but still... even a latge texture map still looks like crap if you need to simulate a very close planet. A use of a model is a waste of ressourcesand therefore I am in a bind

[Bobboau]

useing a model would be even worse, from a quality stand point

[Tolwyn]

Originally posted by Bobboau
useing a model would be even worse, from a quality stand point

exactly... but, use of a 2048 map is also a waste of ressources. I also fear that the game will run only on high end systems in this case

[Lightspeed]

Holy ***, i'm experiencing a similar problem now, too.

This seems to be down to some code problems

However, it doesnt happen with any backgrounds, but explosion / beam images. Sometimes, when an explosion ANI starts, or a beam graphic (beam as well as beamglow) are started they are white rectangles - but switch back to the intended graphic about 1 second later.

There seems to be something wrong with the way textures are loaded mid-mission.

Also, I had another worrying bug. You might remember the vanishing textures thingy.... Well, I played some missions in a row again - and suddenly it crashed me out during mission loading saying 'Error parsing briefing_icons.tbl - Missing Briefing icon', and crashed my whole system (so I had to do a hardware reset).

After that, I restarted the game, and it loaded up fine.

So - there seems to be something screwing up so FS2 doesn't find the files anymore (this could also lead to the invisible texture thingy), and there also seems to be something wrong with loading textures in a mission (see white squares problem).

[Tolwyn]

same goes for FRED... at least on my system: stars are in the effects folder, but FREd reports them as missing

[Starman01]

There seems to be really a problem with loading background-files.
But I had this even before 3.6. I think I have this since the march-builds.

Sometimes after loading a mission, your FPS will drop dramatically
(from normal 90 FPS to about 20 when facing some backgrounds).

Exiting the game, and restarting it (reload of mission does not work)
solves the problem, than I will have the 90 FPS again, by the same
backgrounds).

Those new sun-files will drop down the Framerate from 100 to 50,
even in an empty mission . Not fully sure who made, either
Lightspeed or Tolwyn).

However, I haven't encountered the problem with these white squares
yet.(I'm using a GF4 TI 4200)

[Bobboau]

RT just found a bug in his textur management system, this might be the cause of it.

[Tolwyn]

I made 'em... they are TGAs in 512*512 resolution.

[Bobboau]

use the comand line -d3d_bad_tsys and see if this has any effect