When trying to lose altitude quickly one of the things I do is cut back to idle but I keep reading here to keep at least 85% RPM on the operating engine to avoid Mech reversion.
I don't think I've noticed anything unusual, how would I identify Mech reversion if it occurred?
+1
I remember very early versions had ATC bringing you in, telling you when to turn final, mentioning other aircraft in the area etc. Maybe as early as Locon or FC?
Thanks that's what I thought about the 65E, I've been using the 65F making some hits and misses, not quite sure of all the options, seems limited, but I'll try and find some good reading or video.
Does it still need buddy lasing or can it target independently?
Can someone please point me in the direction of the current info on the Maverick.
Thank you.
Couldn't you also use a MK point to calculate distance when tower instructs you to fly heading 245 for 40?
Make a MK point at that moment and you should be able to see in real time your travel distance.
I have the throttle at 65% I then press 0 or 9 the corresponding throttle then goes back a little to the off position but the moment I let go the 0 or 9 the throttle jumps back to idle and ramps up to 65%...only if I press and hold 0 or 9 till the rpm is below 30% will the throttle stay in the off position.
When closing an engine, it's necessary to press and hold 0 or 9 until the rpms drop below 30, only then can you release otherwise the engine will restart.
Is there another way to do it without having to hold down the finger lift command till <30?
When/If MK option gets implemented:
4. MK Option. Pressing the MK option button saves a mark point at the location of the aircraft
when the button was pressed. Up to nine mark points can be created. After the ninth, the
first mark point will be over-written and so forth. Not implemented at Early Access release.
(Coming later in Open Beta)
P.9
I set up a runway waypoint in flight then set 'course select' to line up to the given runway # and you're good to go.
Good old aviation nav math is what you'll need to use to figure distance travelled in a given time without having a waypoint.
Some further testing...definitely it's easy to reproduce a slow roll by asymmetric loadout which will immediately get corrected the moment you balance the loadout.
I will continue to monitor.
I'm being asked to produce a track file [.trk] but I only see saved .trk files in:
C:\\Saved Games\DCS.openbeta\Tracks\Multiplayer
I used both CV1 and 'S' and did not find a noticeable quality change outside the cockpit. What I saw inside the cockpit was a bit clearer text however with my CV1 I'm able to read pretty much the same text but only a bit less clear. What was happening was my right lens sweet spot could not be made to line up with my right eye because of the inability to physically adjust the lens position as you can with the CV1. I tried a second 'S' thinking there may be a defect with the first and had the same issue.
So I'll just have to wait for an adjustable IPD.
I checked the FCS page and no LEF stuck at 12, both left and right wings are the same.
Controller input is centered when I press ctrl-enter and is properly calibrated.
No asymmetric bombload.
both engines are at the same output.
I have a dead zone of 3.
The free flight in the Caucasus never gives me this issue and I fly it often for testing purposes.
Thanks for the follow-up and the additional info, if you think of anything else please let me know.