Warthog_Farmer

Take a chill pill =p Crap... Sorry, I probably shouldn't be speaking back to the Chief Instructor:megalol: And try the F86 and its ground handling. It's can be like ice skating after you land. Definitely no sticking there =]

And I thought I was anal... :music_whistling:

Hey! From my experience it's bad news I'd think... The system isn't right for the current build of DCS. I built a AMD PC with 8350 running at 4.4GHz, 16 gig RAM, ATI HD7970 and DCS on the SSD. It would run Warthog at about 30fps tops with massive stutters (down to as low as 5fps) whenever the screen was occupied with loads of other players (i.e. on Aerobatics server online) or whenever there was all out war going on (i.e. Single player campaign). It completely ruined the experience and I put money into changing to the PC I should have built if I had done more research. Changing to an Intel i5 made a huge difference, and then a few months later switching to GeForce 780 made another big (but not quite as big as CPU swap) difference. Now I run pretty smoothly (more important to me than FPS) most of the time at High with Civ traffic, AA, Shadowing etc... even with a busy screen and cluster munitions! That said.. DCS World 2.0 (EDGE) is soon to be released and it is a total overhaul of the graphics engine. Who knows... maybe it will be a little more optimised for AMD. As it is though... I'm sorry to say I'm not sure how much boost you can get from your current rig with tweaking...

Heh. I wonder what percentage breakdown is of consumer vs developer of the DevKits. I would reckon majority consumer who saved their pennies for a glimpse of the future. The question still remains - is it physically possible to produce a detailed enough image from such a small screen?

About Oculus... Hey folks, Been thinking a lot recently about the Oculus and DCS. I had a shot of Dk1 quite a while back now and wasnt immediately quite as amazed as I was expecting to be. Mostly due to the crummy resolution and partly because the first couple of minutes turned my stomach; but the more I played though the more I lost track of the poor resolution and got into it. Anyway... DK2 is out and I haven't tried it - but the word on the street is the resolution still isn't good enough to read your gauges and switchgear without leaning in. Edit: for some reason my original post didn't include the most important paragraph: With Crescent Bay on the horizon I will be first in line to buy it IF someone can convince me that it's possible to get a detailed enough image out of such a small screen. I understand they are rumoured to be 1440 screens... But I just can't see how the pixels can be so small and accurate that my eyes (no glasses/contact lenses needed) will be able to make out the instruments... Otherwise I'll probably be looking at superwide monitors and TIR5 (I have TIR4 at the mo but it's on its last legs) Thanks for reading and I look forward to your replies!

Every power saving option in BIOS is disabled and I am running a single GPU so I am not sure that ULPS would help me in particular - others with Crossfire may benefit as far as I understand. Your quote from AMD is fair but - let's be honest - how many apps have you run that haven't specifically stated 'Windows ____ compatible'. For something that will irreversibly corrupt some windows components it should have a big red flashing sticker before you hit 'download'... or better yet a quick OS check and prevent you from running it with a small explanation. I agree with finding the cause. Tomorrow I will have a good rummage around the files and see if the Jsmoke equivelent files are in there... I just hope they haven't been put into another file that's inaccessible for someone like me ^_^ I'll be back!

At the risk of derailing this thread completely I believe that bug affects EzDock which I don't use =p My problems seem to lie with even a vanilla copy of FSX and the 13.4 and 13.8 drivers. 13.1 seem stable so far

If you don't mind booting up FSX with 13.8 and buzzing around for a bit that'd be great. See if you can recreate or if it really is just me... It starts screwing up for me randomly but I seem to be able to 'encourage' it by forcing terrain textures to reload. Either by accelerating time, slewing fast or cycling around the tower views. Otherwise it will just happen when flying around. Almost guaranteed to happen within 20 minutes. Fwiw I normally fly the PMDG737 and use some ORBX scenery but its happens on a completely clean FSX install too so it isn't addon problems.

Believe me I've tried. It's odd that 13.1 is so stable compared to 13.4/.8 with no tweaking at all. On my last install of Windows I put on 13.4 to see if it would help out with DCS. It was a little bit better (possibly) so I left it installed and forgot about it. A week passes and I boot up FSX with my nice shiny new TM Warthog and I get hit with the above issues. I spend a couple of weeks trying to change settings, tweak my hardware, reinstalling FSX multiple times trying to solve the issue.... to no avail. Then I remembered I had updated the drivers... I tried rolling back and it failed. This is when I picked up the AMD tool I warn people about. I downloaded it (it did say "For use with Windows 7" but never mentioned "NOT for use for Windows 8") and ran it. This screwed my Windows install and forced a reformat/reinstall session. So that takes us to the present day. It seems 13.4 and afterwards for me cause the above issues in FSX. The surprising thing is that it only seems to be me getting these problems nowadays. I was worried about a bad chip somewhere in my rig but it's only these complex sims that ever show it any problems. I can chill out on max settings stressing the same chips in new games with no issues. So 13.1 it is for the foreseeable future. I'll live with my issues and pray EDGE will be my savior I guess =\

13.8 report: Runs better but only marginally so... There is still a noticeable hit. It screws FSX over though just as 13.4. This is stolen from someone suffering the same problem: Going back to 13.1 to give FSX a good blast with it. Might be the happiest medium I can get.... SkateZilla, just checking out your signature... You got your 8350 to 5.1GHz!? May I ask what temperature you run at under load with the H100 attached? I was considering doing something similar since both FSX and seemingly DCS are CPU heavy and they are one of the main reasons I came back to PC gaming.

Drivers wise I realised its 13.4 I had that were completely unusable in FSX. I tried 13.1 just there and they were a little better (I think) in DCS and didn't seem to throw up the errors in FSX. Downloading 13.8 right now. There does seem to be a lot of excitement around these drivers so here's hoping it's the holy grail! I doubt it... but I'll give them a fair crack. I'll report back with my findings, and thanks to everyone contributing to this thread. Ps. Do we think "EDGE" may offer any improvements to these performance issues or is it all about scenery?

No sir, 2012 drivers. 12.11 isn't listed anymore on ATI website (even under the previous versions) but the actual installer does say BETA. The only reason I went back is because the latest version causes mega scenery glitches in FSX. 12.11 Beta must have been the latest available when I built my rig last December... There are no later drivers with the exception of 13.1 which is the problematic build.

Hey again folks. CBUs and MLRS are not present. It is literally the first mission of the campaign where you either have to drop a bridge, provide CAS or take out a group of artillery. I dread to think how the MLRS will affect me when I get to that stage. I upped my OC to 4.6GHz on the CPU but when I look at the monitor it never really seems maxxed out and the temperature comes up a little higher than I am used to - but not melting hot. The reduction in frames seems to be sustained when looking in the direction of the battle. As I ingress it is fairly shoddy, try and hit the target and then depending on how I egress the frame rate could shoot back up again. As I make a turn back to the target area it will start to drop in performance again. I have noticed a lot has been said about the smoke in previous versions of this sim, and the JSmoke edit doesn't seem to be relevant on this patch anymore. Could anyone shed light on how I can "remove" the smoke in this version and see if it is down to my system getting stuck on this? I forgot the mention my graphics drivers (CCC 12.11) are slightly out of date due to FSX going crazy with the latest incarnation. As a result of a failed rollback attempt using the ATI Driver Removal tool (NEVER use this tool with Windows 8 - it ruins your OS!) I am sitting on a fresh install of Win 8.

Hey guys thanks for the immediate replies! I am just taking the 'hog up and orbiting to the north and cycling through all the units to figure out what is causing the hit. I was watching at Apache up close and personal who was hovering way out against a ridge and sending in hellfires about once a minute. I set up the camera so that it was just the Apache and scenery - nothing else. It was sitting at 65FPS solid as a rock. Then at missile launch it drops to ~30fps. Now that is just one rocket causing that... Good idea on checking the log at the end I will be doing that for the next while I guess... Mirrors are off in response to your questions. I forgot they were there to be honest with you and have been off the entire install. Kuky - it isn't necessarily on approach to target. I can be on the ground at Batumi and just looking in the direction of the war then it will hit me to the same extent.

ATI / Windows 8 Users: This will be the first thing you read if you are reading this so take note! Do NOT use the AMD Catalyst Uninstall Utility on Windows 8. It is not clearly marked on the website but multiple reports (me included) that it cocks up some Windows files. I confirmed that something happened to mine by checking "Power Settings" in Control Panel and it just wasn't there anymore. So I don't know what it corrupts but having Windows running in limp mode meant nothing except re-format and re-install for me. You have been warned. -----------Original Post-------------- Hey. I have done quite a bit of reading on these forums about performance issues and I'm led to believe my CPU isn't ideal. However most folk manage to have it run regardless with the occasional blip (CBU burst etc) My setup is: ASUS Crosshair V Formula Z AMD 8350 at 4.3GHz aircooled and stable (In DCS max temp. is between 40-45) 16GB Corsair Vengeance at 1866 ATI 7970 HD 3GB Windows 8 64bit If I fly around with not a lot happening my frame rate does jump around but it's not noticeable unless you watch the FPS counter. Generally never dips below 30-40. However, as soon as I boot up the campaign first mission and approach the target I get FPS hits down to 10fps and noticeable stutters. The MFDs are set at 512 and don't seem to be the issue as there is no FPS hit when booting up the TGP without all the ground action. I got fed up of this spiking I tried to run it off my SSD instead of HD. No difference. I tried running everything at LOW settings instead of mostly max... Again no difference. It's frustrating as hell that when I get into what this game is made to do it is so sluggish it borders becoming unplayable. Also, if I play through and then return to Batumi and so much as look in the general direction of the battle the FPS issue returns. This is where I get confused. Surely if it was a physics/calculations problem with all the projectiles from artillery/tanks/missiles then it would drop the FPS as soon as the AI started engaging each other until one side had won the fight? I'm assuming the fight doesn't "pause" whilst we are looking away from it. It doesn't seem to happen on departure from Batumi however - possibly because the fight hadn't got going yet... This is making me think it actually has something to do with the smoke (either gunsmoke, rocket trails or burning wreckage smoke) which I would then put down to the GPU? It was the same on 1.2.2 as the current 1.2.5. What can I do to alleviate this problem? Any ideas folks?