[StratComm]

Yeah, whatever it's called this week.  The one that contains the defaults for things like the thrusterglows.

[Taristin]

EDIT: Ah, the power of scaling. I've got it, welded up without much trouble. Anything in particular that needs special attention?

Just a cocpit of some sort... I struggled with that. Zods are tough.

[m2258734a]

Excellent job on the Ursa.
        I do not know if this has been pointed out, but switching between OpenGL mode and D3D changes the texture of the Ursa. While in OpenGL mode, the texture is low resolution and I believe is the same texture that can be found in the media vps that was described earlier in this thread. D3D mode has the better looking texture. Is there a reason why the modes switch out the textures? Could it be because the files have not been placed within the 3.6.8 vps yet? Thanks.

[FireCrack]

Well, if it's using the defualt texture in openGL the UV mapping should be totaly incorrect because i remapped it to one big texture.

I havent seen this happening though.

[m2258734a]

Are you referring to the low res texture to be the default texture? Would you like me to provide pictures of the different textured Ursas that I am getting, because everything looks fine to me, other than one texture is clearer and more detailed than the other.

OpenGL


D3D

[FireCrack]

They are both definitley using the texture i supplied in those shots, though it does look worse in OGL

Do you have mip-mapping on?

[m2258734a]

At the time I took both screenshots, yes. I tried to enable and disable that to see if I would get better results with the OpenGL Ursa, but it didn't solve the problem. Do you know what could be the cause of these variations?

[FireCrack]

No idea, no idea at all.

[Turambar]

check the individual mipmap and texture quality settings for OGL and D3D in your graphics card control panel, perhaps somewhere theyre set differently

[SnakeEyes]

I have had problems with model textures looking worse on OGL or D3D before, due to the custom settings I provided to the card outside FSO.

[BlackDove]

Which were?

[taylor]

Part of the problem with those screenshots is the lighting difference.  That's not the only difference of course, they can just do things differently period.  And the OGL code doesn't do all of the same things that the D3D code does (most that's a good thing).  I would like to figure out why in the hell that AA doesn't work properly though since that's been bothering me for some time.  Currently just pushing the anisotropic filter up for OGL can improve quality a bit, as can using trilinear filtering.  I'm not really sure what D3D uses as a default anistropic filter setting but OGL has it off by default.

Also, OGL doesn't change the lod bias for mipmaps like D3D does so in the same view of the same ship you could be looking at a different mipmap level.  Playing with the lod bias can be sorta neat with certain effects, but D3D appears to use it more to artificially improve texture detail.  It's not really providing more detail to the map but just allows it to use a higher res map than it really needs to.  It looks good, but can hurt rendering speed a bit.  That's why I haven't put the same thing in the OGL code.  Also realize that the "3D Hardware Textures" detail slider in the game affects OGL differently than D3D at the moment.  In OGL it changes what the max mipmap level that can be used is (if an image has mipmaps), or if there are no mipmap levels it can resize the image to be a little smaller.  In D3D I'm not even sure if it does anything, and if it does it's not as complete as what the OGL code does so you may get lower detail textures in OGL because the detail slider actually works there.

[bfobar]

I can make my Ursa look either grainy like your first (OGL) pic or smooth like your second (D3D) pic by only using openGL and fiddling with my driver-level settings to globally force or deny Anti aliasing and antistropic filtering. My best guess is that somewhere you have a setting, maybe in your display adapter setup,forcing either Direct3D to always use high quality rendering, or a setting OpenGL to never use it.

I've never noticed a problem with AA other than that my graphics card can't produce an acceptable FS framerate while doing it, but I expect that with my hardware.

[m2258734a]

When I first posted on this thread, I was confused to why the Ursa was one of the few ships that tend to look fuzzy in OGL mode. The new Lucifer, as well as the Triton's cargo container had similar texture issues. After reading everyone's replies, I checked to make sure if I had any custom settings for OGL and D3D mode, but they were both at their default settings. 3D Hardware textures was also set at its maximum. So I experimented with the settings, and I discovered that increasing the quality settings of D3D enhances the quality in OGL mode. So everything looks fine now in OGL. But I wonder why only the Ursa, the Lucifer, and the TC-Tri were affected in the first place and not any other ship (wondering about the whole "D3D enhancing OGL", too, though there must be a good reason). Anyways, thanks for the help.

[StratComm]

Large maps.  The ships you are describing all have maps with at least one side 2048 pixels long, and downscaling them may be causing odd behavior.

[bfobar]

I could tell that the Ursa had a big cockpit area, but did the HTL version really need a vasudan soup kitchen? I think it's slave labor and a GTVA conspiracy.

[Cobra]

[FireCrack]

Okay, now I NEED to update the model!

[Mehrpack]

Okay, now I NEED to update the model!

hi,
?! why, thats funny.
i think its a good easteregg.
a long patrol, they need a loot of coffee *g* and anybody who tell a story to sleep well .

Mehrpack

[Mars]

Seeing that I realize the Ursa could be a lot like the B-2, it could have a toilet behind the 2 seater cockpit... but don't add that in!