GeForce 8800GTX - Major indoor lag!?

**LtCmdr_Tsusai** · 01/29/2008 22:32:50

9mmfu wrote:

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.

HD3850 & XPSP2 had no lag on my end. I moved it from one machine to another, so I could use an 8800GT in my more powerful setup, and I still have no lag on the second machine. I use that machine for LE and missioning right now.

And to clarify, by "no lag", yes there is a initial spike when that building loads, but after 5-10 sec, its gone and doesn't come back, where the 8800GT of mine is a continual lag that won't die.

2nd post: http://forums.station.sony.com/mxo/..._id=36300018476

1stAnomaly

Thank you LtCmdr_Tsusai
if you could check my spec on my xfire profile and tell whether the IceQ3 3870 running on my comp wud cause any lag that wud be great!!!

ID love you and maybe pay you!

**LtCmdr_Tsusai** · 01/30/2008 14:28:06

Current MxO Rig w/ HD3850

E4500 Overclocked
Asus P5B-VM MATX MB
(2x) 1GB DDR2 800 RAM
HIS ATi 3850HD (currently overclocked because the other stuff was) http://www.newegg.com/Product/Produ...N82E16814161211
250GB SATA HDD

Previous MxO Rig w/ same 3850 (nothing was overclocked at that time)
E6750
Asus P5N-E SLI (Nvidia 650i)
(2x) 1GB DDR2 800 RAM
(2x) 80GB SATA HDD (RAID 0)

**sonofthree** · 01/31/2008 17:49:31

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?

1stAnomaly

there shud be something major done about this i know alot of people wudn't want to but im thinking of starting some sort of fund to get mxo fixed of this problem even tho im getting a IceQ3 3870!

**phi**

sonofthree wrote:

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?

I think it has something to do with hidden-face-culling (calculating which polys not to draw because they can't be seen)... if only because that was a BIG change in the way the render pipelines changed for the 8000 series cards.

I would assume its probably having to perform excessive culling calculations on the outside world, taking longer than if it just drew the polys.

1stAnomaly

*CENSORED*?

I understoood that. good.

well phi if you had more time id like to get some sort of fix on this but i know you dont. (new job on its way!!!)

Adutude · 02/07/2008 10:18:19

Alright I have an Nvidia 8800GTX and I'm having the same issue.

Runs very smooth outside, but as soon as I go inside a building I get un-playable lag, like 1 frame a second or less at times. Some of the smaller buildings get that 5-10 second lag, then they are OK, but still not as smooth as the outside world.

It also does not seem to go away after a couple of seconds.

I've got an EVGA/Nvidia 680i motherboard, 2gb of DDR2 RAM, the 8800GTX w/ 768mb of RAM and a 15,000 RPM Sata Drive and an Intel Quad core 2.66MHZ CPU.

I ran this game on 1GB of ram with an Old ATI video card when the game first came out and didn't experience lag like this.

I've installed the latest drivers from Nvidia and still no help.

Other games like Battlefield 2142, Team Fortress 2, WoW all run smooth as silk on this machine at maximum graphics settings.

Seems the rendering engine in combination with the new hardware just doesn't work with whatever code they are using inside of buildings. This appears to be a big issue, judging from the number of posts, will we get some love on this?

Vodor

I'm not so sure it's an Nvidia fault like a handful of posters seem to be angry about. Nvidia make the cards more powerful with more and different technology in them to play games which demand more power from the graphics.

Unfortunatley MXO is an old game so I don't think it'll be high on Nvidias list to fix their drivers.

I wish they would, but don't hold your breath. Where they do work with games developers to provide the best experience possible, MXO dev's probably need to do more their end and would probably be quicker.

Anyway I want this fixed as much as anyone else, I'm semi-new to MXO and can't play indoors at all because of my new 8800GT.

-vod

Adutude

I guess if they want people with newer hardware to be able to play the game. The MXO devs will need to do some work. Even if it's something that Nvidia needs to change, the MXO devs will need to drive it, reproduce it and follow up to get the fix in.

I really like the game and would play it for a bit more, but the indoor lag makes it un-playable.

**MotorZ**

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.

1stAnomaly

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

Mortas

1stAnomaly wrote:

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

I wouldnt class it as definitely ending as my Powercolor HD3870 lags indoors too

Adutude

MotorZ wrote:

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.

I'm not saying they haven't tried, I just think waiting for Micro$oft or Nvidia to fix the problem is kind of a cop out.

If it were a problem Nvidia needed to fix I would think there would be a problem throughout the whole game, it wouldn't only happen indoors. I can also go into buildings where this problem does not happen. When it does happen though, (which is in most buildings), it makes the game unplayable.

It appears that this problem happens on other video cards too, but is most prevalent on the Nvidia cards, so again blaming it on Nvidia seems like smoke and mirrors to me.

The letter about the issue from MXO came out in December, has there been any update since then, or are they just hoping this will go away?

I can tell you I won't be buying a new video card just to play MXO, I'll be taking the other option.

Vodor

MotorZ wrote:

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's not that, I've not read the entire 25 page thread but I have seen dev's post trying to resolve the issue which is appreciated by everyone.

The point is that this thread is getting on for being a year old and still no fix is an awful long time for a serious bug like this to exist, and if what the above poster says is true that they acknowledged the issue in a december newsletter then thats is fairly bad customer service response to something that has been reported many months before.

If what you call 'our' dev's know about the graphics engine then I really hope they have other dev's that do, or how did they ever produce the game in the first place?

I'm not pointing the finger at anyone here, I'm technical in my job too and I know how difficult it is to keep on top of things and sometimes you do get weeks if not months behind but over 6 months is quite embarrasing.
It's actually getting on for 10 months since reported but granted very few people had DX10 or 8800 cards or whatever is causing the issue back then so it was never isolated in a timely manner.

Dev's, It would be very much appreciated if you took some more time on this as you seem to be the only ones who can.