ARM505

All I heard was.........'the missile knows where it is....

You're not the only one to have an issue with this, so here's another thread on pretty much the same subject, but.....it's a complicated request, because on the one hand some improvement *might* be possible, but how much should the entire cockpit be 'adjusted' from reality to compensate for the problem with current gen VR technology and its known shortcomings displaying very fine detail? The Mirage has one of the most difficult to read HUD's in the game, even in normal 2D - the nature of that generation of HUD? My advice remains the same: bind the zoom key/s to your stick and just zoom in when needed.

Yes, I use the controls software to do things the sim can't as well, as you say - I thought that might be a bit much for the OP, but actually brings up a valid point, specifically that another persons control bindings also won't work properly if they have done things as you said (buttons to axes, commands to press and release etc.) and they just copy the control .lua over, as there will be bound commands that simply do not exist on his setup.

To add to what was already said, DCS has (by far!) the best key and axis binding setup in a sim, IMHO. MS FS2020, IL2 BoX, the other IL2.....they're all MUCH less flexible and less intuitive. DCS even breaks it down to 'Stick' and 'Throttle' options, once you've bound the obvious axes, just open up those tabs and bind what would be on the stick and throttle in reality. Then you can expand on that as you learn the module. Plus, to refamiliarise yourself with a module after a break, you just open up the control setup, and start pressing buttons - it immediately shows you what that button does. And it's so much quicker to remember if you made the setup yourself, plus you can be consistant across modules. The only disaster comes when some screw up somewhere, or more likely a change, deletes ALL your bindings, for every module. That's a pain. And I've yet to figure out how to save ALL of them at once. I've been simming since the days of the ZX Spectrum (lol, if Flight and 'Fighter pilot' could be said to be 'simming') and trying to use other peoples control bindings is just painful.

I Why would it give a launch warning? Am I missing something on how this missile works? It's a SARH missile isn't it? Edit: never mind, read the other thread, apparently there would be no launch warnings. So, not 'awful', but 'correct as is'?

Ah, ok, I didn't have my rudder trim move. Just the rudder flapping from side to side. Will check when I fly it again.

I wouldn't call it 'trim' as it's not really ending up moving one way or the other and staying there, but the rudder is definitely twitching from side to side, yes. It's like the yaw damper is on steroids, and is constantly trying to compensate for the slightest yaw, even caused by tiny little bumps on the ground.

Seconded, thanks Fearsome-13! I put two screenshots up in the screenshots thread, it's a beauty.

The wobbles are gone, it seems to fly like it should now. I'm nowhere near smart enough to test for book speeds etc, but it's also slower at sea level, back to a more plausible level. No more speed records.... Also, BOKKE! (SAAF paintscheme now has correct Sprinbok emblem, colours, insignia placement etc - good job!)

Much better. It's always going to be dark, being black of course, but everything stands out as much as one would expect. Good job.

This isn't a TGP issue of course, no need to mention that really, but the issue is the 'granularity' of the trim. Sometimes, even with the shortest blip of the trim hat, you'll end up rolling either one way or the other. Sims have always suffered from this compared to real aircraft, which are almost always easier to trim in reality. It's the mathematical quandary of never being able to zero out 0.0002 roll input which still has results in a sim, unlike reality where things seek equilibrium more readily it seems. Plus the instant trim rate compared to real aircraft (electrically controlled trim being 'on' or 'off', which in the sim means 'instantly at full rate', unlike reality). What ED should probably have, in all electrically actuated trim, is a slight 'ramp up' time at the beginning, where the trim system gets up to speed (slow as the full speed might be). This would allow for very fine electrical trim inputs by short blips (like reality).

Well, the sentence is unclear in that case - why mention the pitch damper switch position, which would logically not do yaw damping in that case? Hence me highlighting that part of the sentence.

That's literally exactly what he's saying. "....that prevents yaw dampening to activate regardless of the yaw/anti-slip or pitch dampers switches position." The systems are off regardless of switch position.

I'm not sure if it's related, but the aircraft is now mildly unstable when flying with the autopilot engaged - there are mild roll, pitch, and yaw oscillations with heading and ALT hold mode on. I don't remember it doing that before the patch?

The first time I tried, it didn't update. I then went into the special menu, checked that the option was checked, unchecked and rechecked it, then tried again, this time turning the battery on first (cold and dark start both times) - then it did. No idea what changed, but the battery was on the second time around, I didn't test further.

Just for info, from the manual: "The starter pushbutton shouldn't be pressed for more than 2 seconds to avoid damaging the electric starter and should never be pushed when the engine is turning, at the risk of destroying the starter system."

I had the same attitude (will not install mods, other than SRS), but all it took was unzipping the mod to the mods folder. I was just wondering if simply creating the 'aircraft' folder in the mods folder solved the problem, or something similar. I could of course experiment, but I'm being lazy Especially as it should be fixed soon.

I also installed the A4 mod, which corrects the F1 sound - I wonder how little actually has to be done to correct the issue, until the OB patch at least, which is probably going to be released soon? I literally just unzipped the A4 to the /saved games/DCS/mods folder, and checked to see that it showed up as an icon when DCS started, that's it. I never used the A4 at all. The Atar is then restored to all it's glory. I wonder if you just need to make an 'aircraft' folder under the mods folder?

I'm not commenting on the realism, or what it's supposed to be, only that when this happens you must shut it down completely and follow the relight procedure. This is the only way I've got it to behave properly again. My 2c, my opinion, never flown a Mirage IRL - if this were to happen to engines I know, reducing thrust until the abnormal behaviour stops would be sufficient. Once normal airflow through the engine has been restored, it should behave normally again, assuming there was no previous damage. I'm not sure what is supposed to be happening here. I'd assumed a compressor stall as well, but it should be correctable by reducing thrust IMHO (again, I'm not an expert with the Atar)

Well, thanks for the feedback, good luck!

Is there any quick fix for this? Some .cfg file or something to edit? I'd love to have my F1 sounds back... I did the sound.log check, yes, also filled with Su27 and Su25 engine sounds. Such an odd bug.

I always thought it was odd to have to push the stick button when engaging the A/P - that's not like any autopilot I've ever heard of or used.....we'd need the original French manual to see if it's a 'lost in translation' thing. Pilots would definitely remember whether they had to push the stick button in, it's odd. I'd remember that.

If the controls were designed to be immediately accessible, and fall readily to hand (like the examples quoted above), and didn't require multiple movements to actuate, then there is absolutely no reason not to bind them to your HOTAS from a realism point of view, as the same speed of response and functionality is then reached. Having a real cockpit around you is a MASSIVE advantage, even with non-HOTAS cockpits. People forget how small fighter cockpits are, almost every single control is nearly immediately reachable, often only by feel, or at worst with the briefest glance. I've sat in a Mirage F1, it's a small space. Every button is almost immediately to hand. Sure, you may have to glance down, but it's a millisecond. And the controls around the throttle are basically a few cm from your fingers. Compare that to glancing down (with no peripheral vision, unlike reality), waggling your mouse around to find the cursor, getting onto the hotspot while holding your TrackIR still.....there is IMHO zero realism lost when binding controls to your HOTAS that weren't there in reality (even things like gear or flaps). This is a similar conversation to the Mosquito gear lever retraction (applies to the MiG21 as well for example) - in reality, moving the safety gate out the way is very easy with one hand, and one action, in the sim it's much more difficult. You could argue that some controls wouldn't be reachable under high G load, etc etc, but in the vast majority of situations the real cockpit, even in non-HOTAS setups are still easier to use. IMHO. Having sat in quite a few cockpits, wishing I was flying them! FW190, Spitfire, Mustang, Yak 3, Me262, Mirage F1, MB339, Me109 (tiny!) AT6 (Harvard to us) and countless civilian aircraft.....the same with airliners in sims (which I've spent thousands of hours in in reality). I know it's totally unrealistic to have MCP controls on your HOTAS in MSFS, but in reality reaching up and twiddling the heading bug is incredibly easy compared to mousing over it in a sim. There are known combat situations where pilots end up heads down when they shouldn't have to be - for example, quoting from the interview with the wingman of the South African Mirage F1 pilot, on the merge with MiG21s, they were so close that they could see the opposing pilots had their heads down for some reason, quite odd given that they were at the merge - apparently, the MiG pilots were finding their external tank release control to drop their tanks. All the Mirage pilots saw were objects separating from the MiGs, and that their heads were down. After the war, it became apparent exactly what they were doing (they conversed via intermediaries), and why their heads were down (they had to hunt for the jettison controls in the MiG). So, perhaps leave out more complicated controls like emergency jettison, sure, absolutely. It would be realistic to have to hunt for *those* type of multi-function, rarely used controls. tl;dr - IMHO, you are hampering yourself unrealistically by not binding almost anything you need to your HOTAS.