Vortex225

I see. Well, I've entered a turn many times where my speed was high enough to induce a black out without exceeding the aircraft's AoA limit. In these cases, the airbrake is very useful. It's a valid point though. Thanks for the info!

I have found Gerry Abbott's videos to be very helpful during my training missions. Here is a pertinent CDU tutorial: ExcessiveHeadspace has a great JDAM tutorial that demonstrates how to use flight plans for combat situations. CDU offsets are very important too. Here is a training video from Tigerpwrr: http://youtu.be/lZYhfO9-Elk As always, check the ED Wiki for more information: http://en.wiki.eagle.ru/wiki/DCS:_A-10C_Training_Supplements http://en.wiki.eagle.ru/wiki/DCS_A-10C_Guides,_Tutorials_and_Reference_Documents

I may not understand your meaning correctly, but the controller scheme works just fine. I've tested it several times. I should add that the rear scheme requires the SPDB function to be of type "hold" in the TARGET software. Also, this scheme is specific to the TM Warthog HOTAS. I don't know how one would configure other sticks for similar functionality.

Just a quick follow-up. While I could not determine a scheme that would provide incremental control, I did reverse engineer a concept I read about on these forums some time ago. Specifically, it is possible to use the three modes of the speed brake slider to provide "hold" and "toggle" functionality. First, bind the SPDM control to Airbrake Off. Next, bind the SPDB to Airbrake On. Finally, bind SPDF to Airbrake On. With this configuration, sliding the speed brake slider to the rear will engage the airbrake only while the slider is held in the back position. Once the slider is released, the airbrake will retract automatically. Conversely, when the slider is moved forward, the airbrake will toggle in the engaged position and remain extended until the slider is manually moved into the center (SPDM) position. The rear scheme is perfect for hard or break turns where the airbrake is only needed for a few seconds. The Forward scheme is great if you need airbrake to remain engaged for any significant length of time. It's not perfect, but it will do nicely for now.

Gents, Has anyone managed to implement an incremental speed brake solution for the aircraft in FC3? I have a TM Warthog, and I'd like to control the speed brakes with more precision than a simple binary on/off option (i.e. like the A-10C currently does). Any suggestions?

Since we're a relatively small niche community, I would venture to say that most of us would gratefully open our wallets (or purses) for the modules mentioned in the video. This is especially true for the F/A-18C, Su-27SM, F-15C, and FW-190. Perhaps ED could use Kickstarter to get more financial support for each of these modules, and provide frequent project updates to those who give generously. Heck, I would probably kick in almost 100 USD for each of those modules for early alpha access, insider updates, and the ability to provide feedback.

"I'm starting to think I may never fly this plane." Absolutely hilarious. Great find! :thumbup:

Speculating about the next DCS module(s) is like guessing your holiday gifts; it's entertaining and helps to enhance the drama, but it's all but impossible to draw any real conclusions. Another comparison? Since I'm a new dad, I suppose it would be like speculating about the gender of your unborn child. "Look how low she's carrying that baby; that means it will be a boy!" :thumbup:

I would also love to get a copy of the mission file. Great concept!

I did not care for my G940 and ended up donating it to a friend. The HOTAS Warthog is a much better solution.

I've had this error as well when attempting to force my VHF AM radio to start with 131.00 tuned-in at mission start (i.e. ATC for Batumi). To solve it, I simply supplied the box with valid UHF frequencies instead (in my case, I selected 251). Unfortunately, I never did figure out how to configure my A-10C to start with VHF AM 131.00 dialed-in.

I have two GTX 590s in quad-SLI configuration and I can report that it does work. However, SLI for DCS is not officially supported by Nvidia drivers. That is, it must be "forced" with the appropriate alternate frame rendering mode (AFR2). As an aside, I can't imagine your frame rates are great with only one GPU supporting three monitors. My two 590s have their hands full with my single 30" monitor (2560x1600). Better SLI support would improve performance, but this is unlikely to happen in the near future (if at all). Hope this helps.

The irony here is deep. Your objection to this perspective is also political in nature. This doesn't mean your points aren't valid. If the facts support your claims, then they should be evaluated on their own terms.

Congrats! Do yourself a favor and pickup some clamps for your HOTAS Warthog. If you're using a traditional desk, they can transform your configuration. http://www.joyloc.com/ SimHQ Review: http://www.simhq.com/_technology3/technology_188a.html

Two (i.e. v2), please. :thumbup:

You can always add your user-generated waypoints (or markpoints) to a custom flight plan. This will allow you to view the navigation lines connecting your waypoints and avoid cycling through all of the airfields and other miscellaneous waypoints loaded into the CDU at mission start. As an example, I always create a custom flight plan when I'm landing. When I contact ATC with an inbound call, they provide a range and bearing from your current location. I place an overhead markpoint as soon as this occurs, and create an offset waypoint from this markpoint using the ATC bearing and range data. I then look-up the waypoint number of the desired airfield and add it with my custom offset waypoint to a new flight plan. This provides me with a nice navigation line along the glide slope to the runway and removes all of the superfluous waypoints from your HUD (i.e. when cycling with the UFC rocker). Hope this helps!

First, I would only pay for a model that enhanced flyable aircraft. Next, I would definitely pay if the new external models came with improved 6-DOF cockpits (e.g. F-15C from FC3). My priorities: 1) Su-27 2) Mig-29 Ultimately, DCS needs at least one fixed-wing fighter with clickable cockpits (i.e. study sim quality) for each coalition. When A-10C detail has been devoted to the Su-27 and F-15C (as an example), we will have a truly amazing game.

I haven't noticed any problems with TWS, and I've used 120Cs several times in this mode recently. I'll do some tests later today to see if I can generate any inconsistencies.

Fish has some videos on the CDU. What specifically do you need help with? Entering waypoints? Managing markpoints? Creating flight plans from waypoints? Bullseye offsets? Have you tried the wiki? Check the Aircraft Systems/CDU Tutorials. http://www.youtube.com/watch?v=H9nhxcd_s6A There are numerous YouTube hits for "DCS A-10C CDU"

As 159th_Viper hinted, you definitely have some room for improvement. Also, have you tried the new 3GO skin from HungaroJET? Combatace's Su-33 Model 1.3? Here are some recent screens from my machine. All settings on high. 2560x1600.

You have to wait until your navigation system has completed the alignment procedure. In the image below (from Arclight over at Subsim), click OSB 9 once T = 4.0 0.8. Once this is done, you can enable EGI, EAC, and RDR ALTM. http://www.subsim.com/radioroom/showthread.php?t=179884 http://forums.eagle.ru/showpost.php?p=1184047&postcount=2

I don't know if others feel the same way, but I took that last sentence rather poorly. Equating FC2/3 with any Microsoft sim is inappropriate, IMHO. :doh:

I couldn't have said it better myself. The latest patch addressed my FPS issues and renewed my ability to enjoy the sim. To help support the company, I've added the P-51 and CA modules to my digital library. I will scoop up FC3 as soon as it drops too. Well done, ED! :thumbup:

I'm experiencing the same FPS drops as described above. 1.2.0 ran very well with all settings on "High" at 2560x1440. After 1.2.1, I noticed a non-trivial performance penalty when viewing the aft cockpit area and when flying near cities (e.g. Batumi). Considering I have a SSD and 2x GTX 590s (i.e. four total GPUs running in quad-SLI), I highly doubt my hardware is the culprit. Thankfully, ED appears to be aware of the issue and is pursuing a solution.

Thanks for the prompt reply! I'm happy to provide system specifics or software settings if desired.