[Taristin]

I don't know if this is specific to my system, or if of people are having this trouble, but FS_open (Every build I've tried except for the one MT uses) will not display textures for the modded ships.

I'm using the -mod MachinaTerra command line, and everything loads up fine. The ship models are used (I know because of the boxes in mission, and the thruster glows) But the textures themselves don't load. Despite being in the same folder. I copied them to the main FS2 data folder as well, but still no dice.

The ones I'm using are primarily 1024^ maps, and I want to use a build with environment mapping so I can test the textures I'm making. Any build other than the 3.6 we have will not load the textures. There's no error messages. Just invisible meshes flying about...  

It's not only specific to the 1024^ maps, tho. Some capships have quite small maps, and are still not loaded.

I've even restarted Windows... to no avail.

Why is this happening?

My configuration is:

C:\Games\FreeSpace2\fs2_open_T-20040729.exe -spec -glow -jpgtga -d3dmipmap -phreak -ship_choice_3d -targetinfo -snd_preload -fps -env -alpha_env  -fov .39 -ambient_factor .85 -allslev -mod MachinaTerra

Duron 600
128 Mb Ram
R9600XT 256 Mb (Overclocked to 526 Mhz)
Windows 2000 SP4 (I believe... the latest one)
Direct X 8 - 1024x768x32
2 Sample AA
DX Version 9.0b
And my TXT Caps if that's needed is attached.

[Starks]

Post screenies...

*Crosses fingers*

[Taristin]

You want screenies of an empty display in the techroom? And of thrusterplumes with no ships attached?

[jdjtcagle]

[Trivial Psychic]

This wouldn't be due to improper texture formating would it?  Like using a pcx format that Freespace can't display?  That's the only thing that comes to mind.

[Scuddie]

If that were to happen, the colors would be all screwed up, but it would still render.  This happened to me when I tried making textures with PCX mode 5 instead of mode 2 (or 3?) back in the 1.2 days.  It was colorful, but hideously ugly

[Taristin]

No, the maps render perfectly in modelview and in Aurora. The game just seems to ignore them.

[karajorma]

Modelview and Aurora may use different code for loading the textures (in fact they almost certainly do).

Try converting one texture to a different format or better yet copy the pof and change the texture in Modelview to a default [V] one. That will help narrow the problems down a little.

[Gloriano]

If they are Censored Textures then  there is no proplem in them because they work for me in game.

[Taristin]

Originally posted by karajorma
Modelview and Aurora may use different code for loading the textures (in fact they almost certainly do).

Try converting one texture to a different format or better yet copy the pof and change the texture in Modelview to a default [V] one. That will help narrow the problems down a little.

well, it doesn't load the TGA versions of the shinemaps either.

[Taristin]

I did a little more detective work, and I've found that only one of the many many builds I have on my system will display the textures. it's the fs2_open_env.exe from one of Bob's preliminary attempts at environment mapping. Unfortunately, it crashes before mission.  

None of the other builds will load custom textures. The ships that use both V maps and custom maps will only have the V ones displayed, and the other parts are see-through. None of the other builds, including 3.6 will display the maps.

C'mon Coders, atleast reply that you've read this, or that you have no idea what's going on.

[taylor]

Read it.  No idea what's going on.

What directory are the new textures in?  They have to go in data/maps to be sure the game finds them.

Are they replacement textures or true maps for the models?  In the case of replacement textures it could be a load order thing being out of whack.

Do you have a something I can test with?

[Taristin]

They are in the machinaterra/data/models directory (although I had it in data maps, but that didn't help either), and are the actual maps for the vessels. Not replacements for other ships.

Am I the only one reporting something like this? Do you think perhaps it's my PC somehow?

[Scuddie]

Did you try OpenGL?  Have you tried upgrading or downgrading your Det/Cat drivers?  This is going to sound really stupid (even for a win2k machine), but have you done a cold hard-boot since then?  If you're initially not looking at a model at the beginning of a mission, then you turn to look at it, do you see tje model and watch it disappear?  Everything I said I have experienced problems with models not mapping, so I'm not just spouting random BS out of my mouth

[Taristin]

Tried OGL. Got nothing.
Cat 4.4. I don't wanna upgrde and lose the shinemapping.
I've restarted my stsyem a few times. Not actually power off, and then back on, but restarting.
The models never had the textures to begin with, they don't dissapear and then flicker on/off...

[phreak]

*nevermind*

[Taristin]

Oh.  Why can't aurora test enviroment mapping?

[Kazan]

because Aurora and PCS don't have environment mapping code, and because they wouldn't have anything to work with

I am not expirincing your issues with _any_ build

you did say you had your maps in MachinaTerra/data/models -- THAT'S THE WRONG LOCAITON

immediately put your textures in the right spot (MachinaTerra/data/maps)


(PS Unoverclock your radeon - that's useless stress on your card - with a Duron 600 surely cannot even use those extra mhz, especially considering duron600 era mobos were only like AGP2x)

[Vertigo1]

Kaz, they had 4x AGP boards for a while when durons that slow were out.  I know because I bought one with 4x AGP (Asus A7V) when the 700MHz duron came out.

[Kazan]

my radeon 9600SE runs 8X AGP

a Duron 600 even with 8x AGP isn't fast enough to benefit from OC'ing that radeon