Demo app strange results
by Dave Strock · in Technical Issues · 05/02/2002 (6:36 pm) · 7 replies
Hi, I just compiled the sdk on my debian:testing system. All went ok, but when I run the demo app I'm getting some really strange textures. You can see them in this screenshot from the "Scorched Earth" mission:
www.nu-frontier.com/design/screenshots/funkyterrain.png
I'm using SDL 1.2.4-1 and XFree86's version of mesa (xlibmesa3). I havn't had these types of problems with any other programs compiled against these libs. I noticed that the latest stable version of mesa is 4.0.1, so I might try that.
Anyone else have anything like this happen? Any ideas what might be causing this? Its strange because only some of the textures are not normal.
www.nu-frontier.com/design/screenshots/funkyterrain.png
I'm using SDL 1.2.4-1 and XFree86's version of mesa (xlibmesa3). I havn't had these types of problems with any other programs compiled against these libs. I noticed that the latest stable version of mesa is 4.0.1, so I might try that.
Anyone else have anything like this happen? Any ideas what might be causing this? Its strange because only some of the textures are not normal.
About the author
#2
Edit: I was just thinking about it, and it seems that the objects in dts format are the ones with correct textures. The water and the skybox look ok too. Its mainly the terrain and dif objects that are having problems I think.
05/02/2002 (8:09 pm)
Sorry, probably should have mentioned this in the first post. I have an nVidia GeForce2, and I'm using their accelerated drivers.Edit: I was just thinking about it, and it seems that the objects in dts format are the ones with correct textures. The water and the skybox look ok too. Its mainly the terrain and dif objects that are having problems I think.
#3
You are most probably using the wrong libGL.so (probably the stock one that comes with Mesa) instead of NVidia's. The thing is you can have both installed on your system, but your system will still use the Mesa one by default. You can double check this with the command glxinfo. It will tell you right at the top if you're using NVidia's libGL.so or Mesa's.
The following utility is very useful to troubleshoot an nVidia installation: nv_check.sh. It's quite useful.
Also, any Linux gamer should be aware of the Linux Gamers' FAQ which is located at www.icculus.org/lgfaq/. This should probably be added as a resource.
Anyways, this should help you fix your problem. I used to get the same problem with Tribes 2.
05/02/2002 (8:20 pm)
Hey Dave,You are most probably using the wrong libGL.so (probably the stock one that comes with Mesa) instead of NVidia's. The thing is you can have both installed on your system, but your system will still use the Mesa one by default. You can double check this with the command glxinfo. It will tell you right at the top if you're using NVidia's libGL.so or Mesa's.
The following utility is very useful to troubleshoot an nVidia installation: nv_check.sh. It's quite useful.
Also, any Linux gamer should be aware of the Linux Gamers' FAQ which is located at www.icculus.org/lgfaq/. This should probably be added as a resource.
Anyways, this should help you fix your problem. I used to get the same problem with Tribes 2.
#4
If you press ~ after the game loads and scroll up a bit in the console, you'll find information about the GL driver that was loaded.
GF2 should work...thats the same card that I have. Could possibly be old drivers, I'm using 2880, although I think Torque has worked fine since 15xx.
05/02/2002 (8:44 pm)
If Mesa's GL is really being used, I think the rendering would be very slow, if it even worked at all.If you press ~ after the game loads and scroll up a bit in the console, you'll find information about the GL driver that was loaded.
GF2 should work...thats the same card that I have. Could possibly be old drivers, I'm using 2880, although I think Torque has worked fine since 15xx.
#5
05/02/2002 (8:47 pm)
Maybe the game can't find the texture?
#6
EDIT -- I thought Mike was the one with the problem (I got confused).
Dave, did you try what I suggested. I had the exact same problem. Textures coming in all messed up. It looked a lot like your screenshot.
John, that's the weird thing. I always thought that the rendering wouldn't work at all. But it did. Mesa basically used nvidia's kernel driver (since that's loaded fine). so it runs decently, and some of the stuff gets rendered properly, but most of the stuff looked garbled.
EDIT -- I'm glad it works Dave.
05/02/2002 (11:29 pm)
Wow! Did you both miss my post?EDIT -- I thought Mike was the one with the problem (I got confused).
Dave, did you try what I suggested. I had the exact same problem. Textures coming in all messed up. It looked a lot like your screenshot.
John, that's the weird thing. I always thought that the rendering wouldn't work at all. But it did. Mesa basically used nvidia's kernel driver (since that's loaded fine). so it runs decently, and some of the stuff gets rendered properly, but most of the stuff looked garbled.
EDIT -- I'm glad it works Dave.
#7
Thanks a lot. I had this same type of problem before on a different box, except that one simply wouldn't render anything. For some reason I didn't connect the two. Anyway, I just got rid of the mesa libs and now it works fine.
Dave
05/03/2002 (9:42 am)
Hey Yacine,Thanks a lot. I had this same type of problem before on a different box, except that one simply wouldn't render anything. For some reason I didn't connect the two. Anyway, I just got rid of the mesa libs and now it works fine.
Dave
Torque Owner John Quigley