GeForce 8800GTX - Major indoor lag!?

I'm having an issue with my 8800 GTX. My graphics are good most of the time, but every now and again the models on weapons, characters or interactable items get buggy and look very bad. I cant quite explain what it looks like, sorta like dots.

Scolirk wrote:

I'm having an issue with my 8800 GTX. My graphics are good most of the time, but every now and again the models on weapons, characters or interactable items get buggy and look very bad. I cant quite explain what it looks like, sorta like dots.

Sounds like the texture issue on vista with the 8 series cards

Michael1 wrote:

I tried the 8600 and it was ok.

I have a 8600 GTS 512MB and it has horrible lag indoors, even with the newest patches...I guess you got lucky or something.

I wonder if it has to do with PCI express drivers instead of videodrivers?

Well that leads to a serious new point. It seems to be DirectX 10 or the new generation graphics cards way of dealing with it which doesn't bode well for peoples hopes of a fix for the subsequent series... I thought DirectX was supposed to be backwards compatible? If it is backwards compatible, then structure of the cards are preventing it... or something (note: not a tech head...)

It has really nothing to do with DX10 completely, I run a DX10.1 ATi card (HD3850) on my portable game computer, and indoors run just fine.  As for the 2600XT, beats me, you might want to driver clean your nvidia stuff off *shrug*

For those who want to go "Oh! you're running 10.1!" It doesn't matter

"The spec revision basically makes a number of things that are optional in DX10 compulsory under the new standard - such as 32-bit floating point filtering, as opposed to the 16-bit current. 4xAA is a compulsory standard to support in 10.1, whereas graphics vendors can pick and choose their anti-aliasing support currently." http://www.theinquirer.net/en/inqui...ith-101-upgrade

Remember.  DX9 in Vista is not DX9 in XP.  Different files and the like.  To even take advantage of 10.1 stuff, you have to develop the application for Vista using 10.1 API calls.

Its still just the 8 series cards & their XP driver.

Vinia wrote:

Well that leads to a serious new point. It seems to be DirectX 10 or the new generation graphics cards way of dealing with it which doesn't bode well for peoples hopes of a fix for the subsequent series... I thought DirectX was supposed to be backwards compatible? If it is backwards compatible, then structure of the cards are preventing it... or something (note: not a tech head...)

It has really nothing to do with DX10 completely, I run a DX10.1 ATi card (HD3850) on my portable game computer, and indoors run just fine.  As for the 2600XT, beats me, you might want to driver clean your nvidia stuff off *shrug*

For those who want to go "Oh! you're running 10.1!" It doesn't matter

"The spec revision basically makes a number of things that are optional in DX10 compulsory under the new standard - such as 32-bit floating point filtering, as opposed to the 16-bit current. 4xAA is a compulsory standard to support in 10.1, whereas graphics vendors can pick and choose their anti-aliasing support currently." http://www.theinquirer.net/en/inqui...ith-101-upgrade

Remember.  DX9 in Vista is not DX9 in XP.  Different files and the like.  To even take advantage of 10.1 stuff, you have to develop the application for Vista using 10.1 API calls.

Its still just the 8 series cards & their XP driver.

LtCmdr_Tsusai wrote:

Vinia wrote:

Well that leads to a serious new point. It seems to be DirectX 10 or the new generation graphics cards way of dealing with it which doesn't bode well for peoples hopes of a fix for the subsequent series... I thought DirectX was supposed to be backwards compatible? If it is backwards compatible, then structure of the cards are preventing it... or something (note: not a tech head...)

It has really nothing to do with DX10 completely, I run a DX10.1 ATi card (HD3850) on my portable game computer, and indoors run just fine.  As for the 2600XT, beats me, you might want to driver clean your nvidia stuff off *shrug*

For those who want to go "Oh! you're running 10.1!" It doesn't matter

"The spec revision basically makes a number of things that are optional in DX10 compulsory under the new standard - such as 32-bit floating point filtering, as opposed to the 16-bit current. 4xAA is a compulsory standard to support in 10.1, whereas graphics vendors can pick and choose their anti-aliasing support currently." http://www.theinquirer.net/en/inqui...ith-101-upgrade

Remember.  DX9 in Vista is not DX9 in XP.  Different files and the like.  To even take advantage of 10.1 stuff, you have to develop the application for Vista using 10.1 API calls.

Its still just the 8 series cards & their XP driver.

Are you running Vista or XP SP2 Tsusai? As I ran a preliminary test with a HD3850 on XPSP2 and experienced some of the same issues as with the 8xxx series Nvidia cards.

ok devs...what changes between inside and outside when it comes to rendering rules?

Are "outside" walls different from "inside" walls?
When an area is "indoors" does it attempt to render/load all textures/polygons "in" the "indoor" area.


Obviously there is something...different about inside areas when compared to outside ones. I don't mean to sound harsh, but its pretty obvious this is where the rendering engine is having an issue. Not with DX10 cards as a whole or even with the 8800 series as a whole. The bug only shows up under specific conditions and is thus most likely inside the code and not inside the drivers?

Well im getting a Radeon IceQ3 3870 so its all ending for me!

You guys are looking at it as if the Devs haven't done anything with this. A lot of dev time has been wasted trying to find a setting that could get MxO to work with the 8000 series. Unfortunately, none of our devs know anything about the graphics engines, and are not trained to know how to fix it either. They've exhausted all possibilities on their end, and we have to hope Nvidia can find something on theirs.

You guys are looking at it as if the Devs haven't done anything with this. A lot of dev time has been wasted trying to find a setting that could get MxO to work with the 8000 series. Unfortunately, none of our devs know anything about the graphics engines, and are not trained to know how to fix it either. They've exhausted all possibilities on their end, and we have to hope Nvidia can find something on theirs.

Just tried this, no effect.

Hope springs eternal. I've just received word from a beta tester in my faction that the new Vista update will eliminate all known graphical issues with MxO, that has to do with the 8800's. I've seen screenshots for confirmation while he was running Vista, and it looks to be legit. I'll find a few and post them if I can.

You guys are looking at it as if the Devs haven't done anything with this. A lot of dev time has been wasted trying to find a setting that could get MxO to work with the 8000 series. Unfortunately, none of our devs know anything about the graphics engines, and are not trained to know how to fix it either. They've exhausted all possibilities on their end, and we have to hope Nvidia can find something on theirs.

... it sounds too good to be true. 

Now they naive people cant see passed the two immediate parts of the chain and they have to blame someone instead of getting off their arse's and doing something to change it like im doing (getting the Radeon 3870 which has no problem and is kickarse).

So, I bought this brand new computer, and it is my naivitivity that I didnt look up every possible game forum to check whether my 8800 is supported or not ? And, to make things better, you really expect us (including me in this case) to throw this, again, brand new 8800 in the bin and get another..oh yes, brand new card?

Reality Check?

I'm having no problems whatsoever with other games, so please explain to me again why I should get off my arse and get a new graphics card for one single, not too new game ?

It's sometimes easy to lay blame, sometimes not. Here, I cant really say who's to blame but for certain not the player-base.

*CENSORED* STRAIGHT 9mmFU



i know this is hard to fix! But what everybody is trying to say in there own twisted ways is that:

The problem exists and we want a fix SOE shud be doing all they can to fix this and if it means paying you devs more or contacting nVidia or telling Microsoft to get off their arses! and the same goes for every company out there its a triad of companies not putting in the effort they promise/should and then falling on the devs shoulders. Now they naive people cant see passed the two immediate parts of the chain and they have to blame someone instead of getting off their arse's and doing something to change it like im doing (getting the Radeon 3870 which has no problem and is kickarse).

I respect the devs for what they are doing especially rarebit who has given mxo and this issue a good bash and keeps our game interesting. I dont like SOE's view of this game as a little cash flow on the side. But i thank them for not shutting it down a while ago. I dont like Windows not putting there best into a product that they claimed to be the best OS in a long time! and nVidia not living up to there name of making mxo they way it meant to be played! So it is alot of problems and people not living up to their names and everyone getting ancy at a problem thats not going away soon!

Dial it back a few notches folks.

As it is I think I am going to clean up this thread for non relavent posts.