PiedDroit

I usually push it around 100kts. I think IRL they don't let drop by itself as it might damage the front gear.

Not at all! I'm most interested by those too. See mattebubben's post above, I agree with all his points.

I recommend reading this thread (you can start at the end to see what's being worked on). Giving a percentage is difficult to estimate, a common joke in the software development world is saying that 80% of the dev is done in 20% of the time and the 20% remaining accounts for 80% of the time :D

I'm not a specialist but I think you get the idea. Whatever term that means others must ask you before using a name in specific context. See Vincent90's answer ;)

As I already wrote, it allows tracking, so yes, better target positioning and therefore better firing solutions. That is not only ground mapping, that is ground mapping with good enough resolution to distinguish objects on ground and figure out their exact position. I.e. they lock on an object that is fixed in space where M-2000 only knows distance to designator. In addition to that, their computer probably handles wind layers to provide even better accuracy.

The name itself is copyrighted where the image is not I think. The aircraft itself is not a high fidelity copy, there's a lot of guesswork, most of the material is taken from public domain. You will see many occurences of a very detailed item but the name has been changed because the rightful owner can prevent you to use it, but can't prevent you to use the image of it.

That works for the "Murage" (Nevada), but I think he's refering to the aircraft here.

They do indeed, they can map the ground with good resolution and "see" targets, thus allowing tracking, where TAS mode on the M-2000C will only compute range to whatever is under the piper.

I understood that too. From a user point of view, even if the contact is still in radar's memory, it moves out of the view. This is a good visual hint that contact is lost. no square on HUD (or at impossible place) => time to unlock

Try firing them like normal missiles?

Don't worry, it will quickly become second nature to press the unlock button as soon as the contact is lost ;)

Hello, manual can be found on your local DCS install folder: \DCS World\Mods\aircraft\M-2000C\Doc\DCS M-2000C Flight Manual EN.pdf I personaly prefer that they hold putting online the manual as it is not finished and it frees time for more bug squashing ;) BTW, here is a small track (for 1.5.3 release), one of my attempts to AA refuel (first tracks were corrupted because of the use of airbrake, I replayed this one at x2 speed and no problem). You can check the amplitude of movements of the FPM and energy carets, it's really small and controlled. It's not perfect yet but I'm happy of the result so for far, as westr said, keep trying it will come eventually. There is one long gulp at the beginning, 2 quick contacts in the middle (I retreat and retry because of bad position) then one last gulp at the end. I think I'm too close to the tanker and that's why I disconnect in the middle, hard to tell... Edit: go back to normal speed before the end of the first contact, until first separation finishes, as the track glitches during the disconnect, don't worry it doesn't last long :music_whistling: M-2000C refuel 9.trk

Thanks for the config file. To answer your question, yes, you can have a one size fits all. Just put all your viewports in there. The only condition is that the names of different viewports don't collide. For this reason I suggested Zeus67 to use try_find_assigned_viewport("VTB","RIGHT_MFCD") instead of just try_find_assigned_viewport("RIGHT_MFCD") in VTB_init.lua (it will look first for viewport "VTB" and if not found, will use viewport "RIGHT_MFCD").

Can you share how you fixed the issue? This kind of info is always valuable :thumbup: I don't know how to export the RWR sorry

SERVAL is RWR, so M-2000C has it and it should be able to detect missile launch under certain conditions (not talking about IR).

I see what you mean, deceleration using high AoA. I'll read a bit a more on that because I'm really curious about why they suddenly boast about the AoA / first shot etc, when this was a known feature of this A/C, from the start.

I find very funny they bring back this old debate (about trading your speed for one good shot) :noexpression: You could read similar discussions about F-22 and the thrust vectoring, SU-27 and it's famous Cobra. And about rapid deceleration being an advantage? :huh: Other A/C have airbrakes instead.

This will extremely useful :thumbup:

That might sound stupid, but did you try the same shortcut a second time?

Cool, thanks! BTW I managed to do the full transfer several times (with 5-10 contacts :music_whistling:) but it's getting better, I even managed to make it once in one gulp on last attempt (5th of the day, arms aching). I tried to make a track but everytime the replay is corrupted :( To other learners, what really made it work for me is the FPM and the energy carets. When going for contact with the basket, make sure the A/C is on the tanker's path (i.e. not drifting left or right), with FPM on the horizon and small speed difference (2-3 knots, i.e. walking speed). Anything outside those parameters will make it difficult to maintain contact (catching the basket is only half of the job). Focus on keeping the FPM on the horizon, use FPM and energy carets to make very small adjustements in altitude, bank and speed. To help maintaining contact, find a visual reference that will help you maintain good position (e.g. keep the tanker's engine on a certain portion of the basket) - but don't forget the focus should be on the FPM. Curve are 0, HOTAS WH, feet off the rudder. I also put the FBW gains in CHARGES (STORES) mode, to get a less snappy plane. P.S.: One thing I *think* is modelled is that the drag of the basket is transferred to your aircraft and takes away the extra few knots you had in excess. So don't back away the throttle immediately after connection. Happy refuels!

Yes. it goes off screen only because the VTB is too small to display the full 120° pie-shaped coverage. If you switch to B-scope you'll be able to see the full 120° Note that if you're using one of the smaller coverage modes, you wiil be able to make the radar sweep go off screen again by steering the radar azimuth to the left or to the right (but it will still be limited by the 120° coverage).

you can mitigate the tanker speed problem by forcing it to cruise and orbit faster. Overall speed should be much faster than with A-10C (this will fix your alarm issue)

I will try again with 0 curve to see if I get less over correction then :thumbup:. I was using 10 at the moment without much luck. Like FSKRipper, I'm quite interested to know xxJohnxx's setup for the tanker.

Hi there, as a future VR user (and one time DCS/DK2 user), I support the idea of zoom in VR! :thumbup: I brought this a couple of time in the VR discussions on this forum too. It does support full 6DOF movement, just like the TrackIR. The problem is not only about reading gauges, it's more about seeing things on the outside world.

What is your method for getting VTB on secondary screen? This has changed recently, you should now let core files (VTB*.lua) untouched and instead add a RIGHT_MFCD viewport in your monitor lua.