Why am I stuttering with 100 FPS?

[MarkyMark]

I'm out of eggnog! :(

 

MarkyMark, I cannot see any big problem within your DxDiag.

However, you are using "Standard IDE";

 

 

I've found that the "VEN_1002&DEV_439C" and "VEN_1002&DEV_4390" to belong to either something called "AMD SATA Controller(Native IDE Mode)" or "ATI Xpress200 SATA/chipset". Is this correct?

 

I would expect that the performance of your computer may improve if you install the drivers - instead of relying on the standard Windows 7 builtin drivers.

You may have to go search your mainboard vendors site to find the drivers. :)

 

Panzer, I think you may be right. I was downloading something in the background and I pretty much couldn't even take off it was so choppy (never mind that I keep getting blown out of the sky by tank shells....I'm going to blame that on windows 7 as well). Previously, I could download and multitask like crazy and never get a slowdown.

 

It's an Asus M4A78 pro motherboard. Not to be too sarcastic, but I find getting drivers for my asus stuff...painful...due to the broken Engrish. Apparently this motherboard is "Rock solid and heart touching". :music_whistling: Anyways I'm off to look for these drivers..I'll report back.

 

edit: also interesting is that the "standard dual channel PCI IDE controller" is listed as having a driver from Microsoft dated 2006?

Edited December 30, 2009 by MarkyMark

[MarkyMark]

Well I updated my drivers as best I could, but I think what might have done it was creating a static swap file around 10gigs (setting both upper and lower limits to equal).

 

I swear I may have had this problem before and I'm probably crazy but it seems like the more you play the game the faster it gets. Is there a temp or swap file that gets built up the more you play? I did get out of the georgian oil war campaign and went in to the next one so perhaps it's a campaign problem as well.

 

I did lock up in the cockpit 4 times until I quit the game and re-entered and then was able to continue on. And I had one incident where my kills weren't being shown after missions. Previously I had some issues with games that were installed in to the "pogram files (x86)" folder instead of the usual "program files" folder. That was in vista 64 bit. So maybe the directory is causing an issue as well, I'm not sure but overall it's much better now.

[MarkyMark]

Update:

 

Ok, I was just about to lose it. After saying things were better I went and tried the "Battle" mission and it was crawling again....the SHKVAL would skip about 50ft as I slewed across.

 

So I uninstalled, downloaded the 1.01c patch, and reinstalled to the regular "Program Files" directory. It runs perfectly now. Better than it did before in XP or Vista.

 

So, it's likely 1 of 3 things.

 

1)The directory really does matter.

2)The patch changed things (I was at 1.01a before so it shouldn't make a difference).

3) Some setting had changed after I installed the first version of BS (A driver update, or something else) and the game had a configuration set for an old set of drivers. I highly doubt this could be it.

 

Can the install directory really make a difference?

 

The other issues with other games I have seen with the "Program Files (x86)" is that often, shortcuts would not appear on the desktop after something was installed there.

 

So really I have no idea but I did just try it out in the "battle" mission (the busiest action I have seen) it works GREAT.

 

Thanks for the help.

[Panzertard]

Good to hear that you had time to investigate it and find a workaround, Mark. :)

 

The directroy shouldn't make that much difference, both of the "Program Files(x86)" and the "Program Files" should have the same permissions.

Permission problems normally manifests themselves as;

- Cannot launch / run the game / script errors / crash before fully loaded.

 

What you've seen is somewhat outside that scope.

But every Windows system is unique - nobody has the same factors when they start a new application.

 

The patch A to C should have fixed some shortcut / uninstall issues, not the things you have seen.

 

And then you mention the "other applications tend to not place shortcut on the desktop when using Program Files(x86)".

 

All these bits of information - together with the previous posts I would consider that;

- you are seeing some minor permission / registry issues - maybe it's possible to repair these, maybe not. I have no advice for you on such procedures, CCleaner is a "nogo" place for me - I normally use the builtin tools or reinstall Windows when such things happen.

- you are seeing some minor Filesystem issues. Can be repaired with CHKDSK C: /F and likewise for D:

 

I'm a bit puzzled over the standar dirver being a driver from 2006 as well, I havent looked into that. It may be that the standard drivers were created back in 2006, who knows. :)

 

One question comes to mind though;

- How you upgrade from a previous OS into Windows 7? Did you "reformat" C:?

- Or was it a Windows 7 over Vista upgrade?

This might be a factor, altough it shouldn't keep any of the drivers regardless of what you did. But a few pieces of software may remain and play along with the other factors.

[MarkyMark]

It was a clean install, not an upgrade. However, the drive was not formatted, I kept my old files in the window.old directory.

 

Perhaps it was a fluke, a corrupt file on install, which was fixed upon reinstall. I'm not sure. As I said before, I also had 4 cockpit lock-ups in a row, which never happened to me before.

 

Minor things were happening too, such as locking up on a tank, in clear view, with a perfect shot, and missing by 20ft in front or behind it...sort of felt like "lag" from the BF2 days frankly.

 

But it's all good now except my first mission kills didn't get recorded again heh. And I kicked butt too. :( lol

[MarkyMark]

One last item of note.

 

In my previous install, the cockpit graphic for the waypoint keypad (on the right) and the laser panel (on the left side) were both gray, with no texture...no scratches or anything, just a flat gray. Not the keys themselves but the flat panel they mount to. I had really paid it no attention but anything that can help pinpoint the problem in future might be helpful for someone else.