Vortex225

Someone else confirmed, but you definitely need to undesignate after the last TOO 1/2 coordinates have been set via TGP. If you don't undesignate at the end, you will overwrite previous coordinates. Pickling the bombs will auto-cycle between stations but NOT between TOO 1/2; you have to cycle between TOO 1/2 manually. After all bombs are off the rail, you can use WPDSG for BDA via TGP. To make this easier, just create a WP using the MSI/waypoint sub-menu and store it in a different sequence than your navigation waypoints. You can keep waypoints separated and better organized by storing them in three different sequences. By default, waypoints are placed into SEQ1.

Just for reference, this topic has been discussed before. I'm not trying to give anyone a hard time; however, the thread may answer some of your questions. http://forums.eagle.ru/showthread.php?t=133519

I don't find this aircraft very compelling for DCS. I would rather see aircraft development resources invested in a bimodal distribution of design periods: WW2 and 1980+. Everything else is rather prosaic for me.

Thank you for the prompt reply! Is there a video that demonstrates the modification for option two?

I'm a potential owner and would be more interested with the suggested modifications - assuming they are, indeed, realistic. As an aside, I'm curious to hear from current R3 owners about their satisfaction with the product. How much of a difference does it make? Do you lose TARGET script editor functionality for the joystick? The latter is quite important to me, as I spend a non-trivial amount of time developing custom scripts for each aircraft. I would hate to lose advanced programmability/control over joystick buttons/switches.

For what it's worth, I'm a huge fan of my Crosswind MFGs. I ordered mine almost one year ago, and they have been one of the best investments in flight sim hardware that I have ever made. Milan is also quite professional and eager to answer any questions you have. His post-purchase support has been top-notch too. :thumbup:

Perhaps I'm not reading this correctly, but I would disagree quite strongly with the notion that the FPM/TVV is not useful. While it's true that a good pilot can fly their aircraft competently without one, a great pilot knows how to make the FPM one of the most important tools in their flying kit. OP: to the best of my knowledge, Russian aircraft did not have the equivalent of a FPM/TVV. It's one of the big advantages western pilots enjoyed IRT situational awareness and flight data.

http://forums.eagle.ru/showthread.php?t=133519

It would seem we've come full circle in this discussion. Thanks for the information, everyone. I'm happy to wait for the brake axes, I just wanted to know if the wait was meaningful or not.

I'm glad I asked the question, because I didn't know they were designed without toe brakes. With this knowledge, what's the best (i.e., most realistic) way to implement them with a TM HOTAS setup? How do the actual Flanker pilots activate their wheel brakes?

Apologies if this has been resolved elsewhere, but I could not find anything regarding wheel brake axes for the Su-27 PFM. Does the aircraft currently have this capability in the latest Open Beta? I really don't want to bind "w" to the toe axes of my rudder pedals for a PFM aircraft.

Awesome news! Just downloaded. :thumbup:

I've never noticed this problem with my Warthog HOTAS. The only annoyance I've ever had with it is the smoothness of the joystick response for very small control inputs - the so-called "stiction" or "sticktion" issue.

I think the OP should still consider purchasing FC3. It will financially support ED. Our simulation community may be dedicated, but it is still small. To this end, ED needs and deserves all the support it can get. You will get access to a large number of aircraft in addition to the F-15C. You never know when you might want to try one of them out. You will have access to the Su-27. Even though I'm biased towards American aircraft (Murica!), the Flanker is an amazing ride. Even if you only care for your Eagles and Hornets, learning to fly the Flanker will make it easier for you to fly against them. QED

F-15E. :thumbup:

I just watched Buzpilot's track too. While the transition was gentle (nice work), there were some things I would recommend other players avoid. First, there is nothing to be gained by keeping your landing gear up while on final approach. Instead of using your air brake, drop the gear much sooner and keep that brake retracted until transition/touchdown. Next, I don't recommend your AoA attack exceed 22 units. Above that value, your FPM will fall below your HUD (as indicated with a flashing circle). Also, it's wise to trim your aircraft to the desired AoA (i.e. 20-22 units) so you don't have to fight the pitch-balance of the aircraft on final. To this end, a properly trimmed aircraft will only require throttle work to find and maintain the glide slope vis-a-vis "power for altitude." Finally, don't worry about your speed. Focusing on AoA will take care of your speed concerns. Higher AoA will allow a lower landing speed, which is useful for heavy landings, but again 22 AoA units should be your max. Feel free to check out two of my heavy landings at Batumi here.

Be careful with that flare in the last few seconds before landing. If your AoA is near 22 units, a flare could actually cause more harm than good (i.e. the increase in drag will overwhelm the increase in lift coefficient initiated by the larger AoA). I think it's wise to consider an increase in power first, which for a constant AoA will lift your FPM in a safe and controlled manner and reduce your rate of descent, followed by a very delicate flare as you decrease power to idle. Unfortunately, these final moment during a landing are hard to master without lots of practice. Much of it depends on subjective cues you receive from your eyes regarding perceived rate of descent and your height above the ground. Many folks will recommend that you focus outside of the cockpit in the final moments before touchdown, as it's easy to get lost in your instruments during transition.

In very simple terms, the calculations required to simulate the physics of flight are more detailed and robust with the new PFM. The net effect, to get to the point, is a more authentic flight experience. In this way, the aircraft should feel more like the real thing when you're flying it.

No worries. :thumbup:

I'm certainly not claiming that one should land heavy on such a short field. Your risk assessments above are all accurate. I'm just attempting to demonstrate sound AoA landing techniques; when done properly, they allow you to make landings that would be otherwise impossible (e.g. a heavy Batumi landing). Operational risk management would, of course, discourage such attempts. However, it's fun to test one's skills in a forgiving virtual environment. IMHO, attempting things that you wouldn't or couldn't do IRL is a small but non-trivial part of what a virtual flying experience is all about. BL: Set your AoA and trim to that value. Adjust power to acquire the glide slope and place the flight path marker where you want it. Profit. :pilotfly:

Here's are two tracks of heavy landings (i.e. full fuel/weapon load) with the F-15C at Batumi. :thumbup: heavy_landing.trk heavy_landing_2.trk

Here's my Batumi landing. I did use a bit of flare on this one, but the real work is done with the throttle. While attempting to acquire the glide slope, I set my AoA at the desire value, generally 21, and then ride the throttle to make tiny corrections to the flight path marker: power for altitude. Feel free to provide feedback. :pilotfly: good_landing.trk

Some people also claim vaccinations cause problems, but this shouldn't stop you from following sound medical advice; in this case, this roughly equates to the software designed specifically by the manufacturer to fully diagnose the functionality of your device. Using Windows DM to check your Warthog HOTAS is similar to taking a Porsche to your local Sears for repairs. All this aside, it's good to hear that your device is likely in good working order. It might be worth the effort to install the open beta and see if your HOTAS is functioning properly in that client. Since it is independent from the regular version of the game, it would be helpful to see if the problem can be replicated. Failing all of this, you could always turn to the nuclear option - a full HD wipe and reinstall of the OS. It's painful, but can sometimes solve pesky problems like this. Of course, I would encourage you to exhaust all of your other options first. Good luck! Hope you can get it working again.

We're off to a great start. I understand that you think you don't need to use the TARGET software. While this is technically true when it comes to playing DCS: A-10C, the software is helpful for all sorts of reasons. For someone willing to plunk down that much cash for such high-end kit, I find it odd you choose ignore a large portion of what makes it such a robust piece of hardware. But I digress... :doh: The software allows you to diagnose the health of your HOTAS - to make sure it's actually working properly. If you don't care about that, then I can't help you.

Have you checked to verify your Warthog HOTAS is functioning properly in the TARGET software? It's easy to do with the script editor. Did everything work properly in the open beta?