Damage

Two squad mates of mine were having this same issue with OCZ SSD's... micro stutter at regular intervals. They both were running in AHCI mode. I have 2 SSD's, both running in IDE mode and my system (and A-10C) runs as smooth as silk. I offered this as a suggestion to both of my squad mates and they tried it. In both cases switching from AHCI to IDE mode solved the micro stutter issue. I know all the so called experts are going to disagree but if all else fails try switching from AHCI to IDE mode. Please don't ask me to explain it from a technical standpoint because I won't get into a debate about it. I know it may not be the best solution for everyone but it works for some configurations. I know that it yields smooth/fast/reliable performance for me and has worked for at least two other who were having performance issues.

I have a CH Pro Throttle USB. I used to have this problem too. In my case the aircraft would move forward after starting the 2nd engine. The quick on-the-fly fix was to just start the left engine, continue flipping all the switches, NAV alignment, HUD bit test, etc, then start up the right engine near the end of the procedure which would only require me to keep my toe brakes engaged for a short time before taxi. The permanent fix was to calibrate my throttle in the CH control manager. My settings in the CH software are: -DX Mode is checked - Z Axis is used for the throttle slider. -In the calibration test page my Z axis value is "0" at the top of the slider and "255" at the bottom. -Centered and Reverse options are NOT checked. -Sensitivity is "100". Dead Zone is "0". -The response curve is set to default (45 degree straight line ascending from left to right). In the DCS control options I have: Controls Tab / Axis Assign Throttle Both = Joy Z *insure all other inputs are blank for throttle Axis Tune Panel (JOY_Z) Dead Zone = 2 Saturation X and Y = 100 Curvature = 0 Slider = ON (checked) Invert = OFF User Curve = OFF These settings fixed my problem. I hope it helps you. Another possible suggestion if the above fails: If you have CH toe brakes (or other brand) try checking "reverse" for the action to engage the toe brakes. This would in effect always have the toe brakes ON, unless you pressed the toe brakes to release them. I know this sounds odd and certainly is unusual but sometimes desperate times call for desperate measures ;-)

I'd love to own a printed hard copy of the manual but I'm having a problem pulling the trigger on a manual that cost more than the program. Also the manual seems to change a little with each new patch. Has anyone printed this out with their personal printer? Did it print the whole thing with one ink cartridge? -Damage

Mk-77's would be nice. I love the smell of Napalm in the morning ;-)

Just tried this out in single player mode and it worked great! Loaded menu item F13 from the PGM list. Will test out in MP later today. UPDATE: This works in multiplayer mode too!!! Thanks

works here too.... thx!

The PGM list also has load options for F13 and F14 which I'd like to know how to access. Any know how to load F13 or F14 options?

stop, turn on ground power and shut down both engines. after engines are shut down... wait about 3 minutes. you'll notice that your aircraft will lift up (levitate) for about a minute then set back down. after that you should be good to go. you'll probably need to motor each engine prior to start to cool them down. you'll still need to ask for a re-arm and refuel. don't forget to reload data (load all).

My Norton 360 quarantined DCS.exe the first time I tried to run it. It game me a notification so I simply had to undo the quarantine and select to trust. No further issues on the subsequent launches. :thumbup:

I concur, 32 bit can work fine. On Med-High settings I get 20-35 FPS on the airbase and 35 - 60 FPS in the air. In either case the game runs smooth without stutters.

Are you saying that you can't play the SIM with Win7 - 32 bit? I'm running Win7 - 32 bit and my performance is very smooth. My settings are on Medium with Scenes and Viewing Distance on high. Search for bcdedit set increaseuserva 3072 here on the forums or google it to access extra memory There are a lot of other variables that might cause problems. What are your system specs?

I'm tired of hearing people complaining about "this is not a final version" ... and its full of bugs. Please tell me which other hardcore Sim you have used that only had one public release that was "final" with no bugs and no follow-up patches because the program was perfect at the time of release. This has yet to occur within the flight Sim community so I don't understand how people are acting so shocked and upset. How many patches were there for Falcon, IL2, LOMAC, FSX and dozens of others Sims that we've seen over the years? How many patches or hot-fixes are there for your operating system? This is a computer program so of course this is not a final version. Where are you getting this idea that this is "FINAL"? The press release is: DCS: A-10C Warthog Released! I read the whole realease statement and didn't see anything about this being FINAL. Sure there are a few bugs and I'm sure there will be a few patches in our near future. Chill out and give it more than two weeks for ED to gather the data, apply and test out the fixes. Until then try to enjoy some of the many things that do work well instead of focusing on the few things that don't... and this doesn’t only apply to flight Sims. :smilewink:

I'm running Win7 Pro 32 bit. Why? I got a great deal from a colleague on the software when it first came out. :smilewink: In Beta 1, 2 and 3 I was able to run the Sim smoothly on Medium settings with no problems or stuttering and average FPS around 30. If I bumped up the settings to "High" my FPS would drop to 15-20. After installing Beta 4 I started getting crashes in certain missions that contained a large number of objects within the game. Troubleshooting revealed that I was running out of memory. Looking at the task manager, as soon as my free memory went to "0" the sim would crash. I basically had to back down to Low settings to get most missions to run. Frustrated and not happy about going through the process of installing a new operating system along with all my programs and drivers, I was almost ready to pull the trigger on a copy of Win7 64, until.... I found the bcdedit /set IncreaseUserVA 3072 solution here on the forum and gave it a try. I'm no wiz bang computer genius but from what I understand is that this frees up about 1GB of memory. http://forums.eagle.ru/showpost.php?p=1084420&postcount=8 BINGO! I could now run any mission at medium settings with no crashes. When the Official release came out I uninstalled the Beta from my disk drive and put the new install onto my SSD. I'm now running the Sim on medium settings with FPS averaging about 60 - 70 at altitude and 30-ish when I'm down in the weeds in with multiple objects and scenery or airports in near proximity. My load times from desktop to the Start menu are about 15 seconds. My load times from the start menu to the Options are about 7 seconds. Once in the Sim, everything runs really smooth with no stuttering. I've heard several reports from guys with faster system specs and 64 bit that their performance is not so great. With so many different possibilities for system configurations/specifications there are a lot of variables for sure. If I had to build a new system tomorrow I'd go with the 64 bit and 8 GB of RAM... but for now I can live comfortably with my lowly 32 bit install. :thumbup:

I've heard from a lot of guys, most with better systems than mine that they have had long Initial Load and GUI wait times and still some stuttering and low FPS in game. Everything seems to run fine on my mid level system. From desktop to start screen = 15 seconds. From start screen to options = 7 seconds. When the Official Release came out I un-installed Beta 4 from my disk drive and loaded the new release on a Solid State Drive. I wonder if this makes the difference or if I'm just lucky?

After more than 4 years of heavy use my CH Fighterstick, Pro Throttle and Pro Pedals are still working flawlessly. I know some guys say they are turned off by the plastic design, however I can attest that the plastic used is very high quality. There has been no degradation the stick or any of the buttons or other internal/external components. I would estimate that I have at least 1500 hours use on my CH gear and I am amazed that there is virtually no signs of wear on any of the three units and they work as precisely as when I first took them out of the box. The CH programming software is very powerful. If you like to write programming code you can create powerful scripts. If you are not a programmer type you can simply use basic keypress or macro recordings to map over 300 commands between the throttle and stick. In summary, the CH controllers are durable, reliable, precise and made from high quality industrial components. No mods are needed and they are less expensive than the flagship offerings from the other major HOTAS manufacturers.

I play both. Practice solo engagements offline and fly Coop missions with squad-mates online. I'd be hesitant to by a combat flight sim that I couldn't fly online.

I know there are a couple good ramp start guides already posted here but I wanted a text only checklist that could fit on my clipboard. This 2 page document works well once you are familiar with the cockpit layout and are somewhat familiar with wait times at certain stages of the procedure. Download here: http://www.mediafire.com/file/ejnda09pxxbdxhr/DCS%20A-10C%20Startup%20Checklist%20%28Beta-4%29.pdf

Make sure the EAC switch is set to ARM and Radar Altimeter switch is set to NORM. These are located on the Autopilot panel. Unless the throttle is advanced to > 25% the view of these switches will be obstructed. The ALT/HDG should hold a level path on your current heading if you are already in level flight with the aircraft properly trimmed. Hope this helps. If you find that this is happening after a cold ramp start. Be sure to wait until the INS NAV RDY is blinking at T = 4.0 (in the RMFD CDU screen) before setting the EAC switch.

Thanks for the very informative checklist. I’m creating a bullet point text only list for the start up procedure and your tutorial helped me to understand why the EAC switch would not arm until after several minutes into the flight. I was moving through the procedure to quickly and not waiting for the INS NAV RDY to blink at T = 4.0

Same thing happens here but only occasionally. Haven't been able to tie it to any specific event yet. ========================================== Beta 4, GTX 460 1GB, NVIDIA driver 260.99, Win7 Pro x32