Game Development Community

Graphics screwed up?

by Stefan Beffy Moises · in Torque X 3D · 11/13/2006 (7:27 am) · 43 replies

Hey guys,
this is what I see when I fire up Tankbuster:
tork.beffy.de/uploads/pics/tankbuster.jpgGot a Geforce NX6600 with pretty recent Drivers (9.1.4.7) and DX9.0c .... any idea whats going on there?
If I play around with the movement keys I can eventually see the background, but the game isn't playable at all and the graphics screw up again after a while... :(
Page «Previous 1 2 3 Last »
#1
11/13/2006 (4:13 pm)
Did you verify that you have the XNA Framework Beta 2 installed? DirectX wont have anything to do with this as it's using XNA, not DirectX. Are you on Windows XP?
#2
11/13/2006 (6:57 pm)
I had this issue at first as well. I uninstalled my XNA framework and reinstalled it, and it seemed to go away. Still runs a bit sluggish (might be the Nvidia 5600 FX I'm running though) but I was able to play around with it.
#3
11/13/2006 (8:07 pm)
Tank Buster runs slugish on my laptop too. It has to do with the crappy GFX card I believe.
#4
11/14/2006 (5:43 am)
Yes, Win XP Home... and I've also re-installed the XNA framework... still screwed up though
#5
11/14/2006 (7:18 am)
91.47 is a very old driver. The current Nvidia driver is 93.71. Upgrade to the latest driver at Nvidia's website then try again.
#6
11/14/2006 (7:47 am)
Updated to 93.71, no change :(
#7
11/14/2006 (8:30 pm)
Stefan, no idea. I know that tank buster runs pretty slow on my dev machine too because I'm on an ati x300 and it requires a lot of over draw. Making matters worse, the ati cards seem to bog down if fences aren't used and xna has no fences. Don't think that has anything to do with your issue, though. I wonder, is that the actual airplane (with the prop on the right) blown up real big? Weird. We'll have to be sure to test on an NX6600. Anyone else have one of those?
#8
11/15/2006 (11:53 am)
I have a 6600GT at home which is the same chip, no problems there. Stefan, can you run msinfo32 and save out a copy of your configuration and email it to me? kenh@garagegames.com
#9
11/15/2006 (12:50 pm)
Also, could you run the Space Wars demo that comes with XNA and see if you get similar results
#10
11/16/2006 (12:54 am)
HI Kenneth,
hm, I can't start the Space War demo since I have no input / mouse there, so I can't click on anything :P
Splashscreen/Menu looks good though ;)
system info is on the way!
EDIT: Gotta try with the joystick later (don't have a gamepad or something atm), guess the mouse just isnt supported?
EDIT2: managed to get to the player selection screen at least by quickly hacking some code... looks good! Not sure about the real game though, couldn't get there yet with keyboard/mouse :P
#11
11/16/2006 (6:09 am)
@Stefan - That's because it's mapped to the xbox controller by default. There's a setting that you can change to make it map to the keyboard instead, I just can't remember what it is off the top of my head. If you look for it, you should be able to find it.
#12
11/16/2006 (6:42 am)
Actually, it's mapped to both, controller and keyboard, the mappings used are just weird ;) Got it to run and play now, everything looks fine there! tork.beffy.de/uploads/pics/spacewar.jpg
#13
11/16/2006 (7:18 am)
Maybe they changed it in beta2, but when I tested it in beta1, it was mapped just to the xbox controller.
#14
11/16/2006 (8:03 am)
I think in beta one there was a #Define you could change that would switch it from xbox 360 controller to keyboard.

i hate to ask this but have you tried re-installing TorqueX?
#15
11/16/2006 (8:17 am)
Just tried a re-install... no success :(
#16
11/16/2006 (8:26 am)
Have you tried hacking the .xml file to make the sprites smaller and see what the result is?
#17
11/16/2006 (2:23 pm)
Ah, good thought Pauliver. It does look like you are zoomed in big time, try modifying the xml like pauliver said.
#18
11/16/2006 (2:46 pm)
Its actually the very same error i have with Vista x64 i mentioned here. changing the scaling and positions in the xml file fixes it but i have absolutely no idea about the correct values.
#19
11/16/2006 (2:52 pm)
I think i have an idea.

Are you running a Windows that uses a different "comma" than the standard US "."

i know in germany we type 17,15 instead of 17.15 so if .NET has some localization functions that will read a 17.15 as 1715 (1.000 means one thousand in germany) it would make the scaling off.

EDIT:
I actually changed the commas from . to , and it fixed the problem for me. Stefan i saw that you are from germany as well so this might be the cause for this issue
#20
11/16/2006 (2:53 pm)
Hmmm. What version of DirectX do you have installed Stefan? It shouldn't affect it, but just out of curiosity.
Page «Previous 1 2 3 Last »