Forums » Bugs
new warthog
The new warthog/centurion models are completely white in my install and cant be changed
win 7 64bit intel i5 Ge force 210
win 7 64bit intel i5 Ge force 210
my god, that video card is ancient - have you tried switching to OpenGL? I'm almost suprised it runs VO. The later ship models require some shaders or things that may not be present on the old-as-crap card; see wikipedia:
Nvidia officially announced and released the retail version of the previously OEM only GeForce 210 (GT218 GPU) and GeForce GT 220 (GT216 GPU) on October 12, 2009. 2009 mate. geez.
Nvidia officially announced and released the retail version of the previously OEM only GeForce 210 (GT218 GPU) and GeForce GT 220 (GT216 GPU) on October 12, 2009. 2009 mate. geez.
The fallbacks for the DirectX 9 driver must not be working right, we'll have to take a look.
Make sure you're using the latest drivers for your GPU, as well.
(Note, the linked drivers are for 210 desktop, and not the 210M notebook GPU, be sure of which one you have).
Make sure you're using the latest drivers for your GPU, as well.
(Note, the linked drivers are for 210 desktop, and not the 210M notebook GPU, be sure of which one you have).
thanks Inc ill try the new drivers
Luxen yes I have a 2009 PC we arnt all well off techno geeks
I only need it for email youtube etc and it works fine for that
Luxen yes I have a 2009 PC we arnt all well off techno geeks
I only need it for email youtube etc and it works fine for that
I don't know if its related but every time I log in I get the msg
Warning using default obb for meshname: 'debris_plated_metal_01'
I updated the drivers for the GPU but no change
It is only the hog/centurian that are white the centaur/vulture are fine
Warning using default obb for meshname: 'debris_plated_metal_01'
I updated the drivers for the GPU but no change
It is only the hog/centurian that are white the centaur/vulture are fine
Nah that is not related, I think everyone who logs in gets that message. It is possibly wrongly using the dx11 driver as the card does support 10.1 with MS 4.1 support, but really with that card you should be using the Dx9 driver.
No driver updates will fix it, your card does not support Dx11, change to the Dx9 driver. If you are using the Dx9 driver then try OpenGL. If none of the above work tme for a new card, you really cannot expect a software company to support old crap hardware just because you are not a techno geek.
Oh and it might not just be because it is an old card, it was crap when it came out too. Honestly, newer updates will break support for older hardware, and there comes a time in every long-lasting softwares life when it no longer works properly on older hardware (VO does not run on my Pentium 3 with a 3DFX card anymore!). Saying "we are not all well off techno geeks" is a stupid bloody answer, you can get a waaaay better GFX card for like $80 (cheaper if you go second hand).
No driver updates will fix it, your card does not support Dx11, change to the Dx9 driver. If you are using the Dx9 driver then try OpenGL. If none of the above work tme for a new card, you really cannot expect a software company to support old crap hardware just because you are not a techno geek.
Oh and it might not just be because it is an old card, it was crap when it came out too. Honestly, newer updates will break support for older hardware, and there comes a time in every long-lasting softwares life when it no longer works properly on older hardware (VO does not run on my Pentium 3 with a 3DFX card anymore!). Saying "we are not all well off techno geeks" is a stupid bloody answer, you can get a waaaay better GFX card for like $80 (cheaper if you go second hand).
Yoda, what the hell? Your objective comments are inaccurate, and your subjective comments are quite disagreeable. That does not belong on Bugs.
The guy has a legitimate problem with an officially-supported hardware configuration. We still support Windows 7 and DX9/10 cards. In fact, when we re-did the new assets to use modern DX11 compression like BC7, we explicitly wrote new runtime-compression techniques to allow these "too-modern" assets to still work on older hardware, which is almost certainly what Drevent is experiencing (we tested it, but I'm guessing we missed some combination).
No driver updates will fix it, your card does not support Dx11, change to the Dx9 driver.
I explicitly asked him to update drivers because shader-compiler problems are common driver issues, and if his drivers were particularly old, it might have presented a false-issue on what looked like a fallback problem. But, if he's upgraded, I'm 90% certain the issue is on our side.
Also, he cannot use the DX11 driver, it has a hard requirement of DX11.0-spec hardware, so it automatically falls back to the DX9 driver if that is not detected.. which is good, as the DX9 driver is much faster and better suited to older GPUs.
The GeForce 210 is old and pretty slow, but it's still a discrete DX10.1 Tesla core, and should be able to run the game for a little while yet (albeit getting slower as the content gets more intensive).
There's no reason to blast the guy for not-upgrading.. a lot of people don't know how, or have the time or money, and the bug he's reporting is likely legitimate and probably impacts everyone on the DX9 driver (including vast numbers of integrated GPUs and laptops), so frankly, I would like to fix it.
Drevent: We'll take a look and see if we can reproduce the issue. If we can, we'll fix the fallback problem. If we can't.. it may be something specific to your setup that we can't easily address.
The guy has a legitimate problem with an officially-supported hardware configuration. We still support Windows 7 and DX9/10 cards. In fact, when we re-did the new assets to use modern DX11 compression like BC7, we explicitly wrote new runtime-compression techniques to allow these "too-modern" assets to still work on older hardware, which is almost certainly what Drevent is experiencing (we tested it, but I'm guessing we missed some combination).
No driver updates will fix it, your card does not support Dx11, change to the Dx9 driver.
I explicitly asked him to update drivers because shader-compiler problems are common driver issues, and if his drivers were particularly old, it might have presented a false-issue on what looked like a fallback problem. But, if he's upgraded, I'm 90% certain the issue is on our side.
Also, he cannot use the DX11 driver, it has a hard requirement of DX11.0-spec hardware, so it automatically falls back to the DX9 driver if that is not detected.. which is good, as the DX9 driver is much faster and better suited to older GPUs.
The GeForce 210 is old and pretty slow, but it's still a discrete DX10.1 Tesla core, and should be able to run the game for a little while yet (albeit getting slower as the content gets more intensive).
There's no reason to blast the guy for not-upgrading.. a lot of people don't know how, or have the time or money, and the bug he's reporting is likely legitimate and probably impacts everyone on the DX9 driver (including vast numbers of integrated GPUs and laptops), so frankly, I would like to fix it.
Drevent: We'll take a look and see if we can reproduce the issue. If we can, we'll fix the fallback problem. If we can't.. it may be something specific to your setup that we can't easily address.
I got a new card so no longer a problem for me but maybe for others