ARM505

Photo's of the real thing bring up a critical point (IMHO) - do you want the sim to look like a photo, or movie, or like real life? Put another way, comparing photo's of the real life things blurred rotors to the animated in-sim blurred rotors doesn't necessarily help (IMHO). Having said that, we can't animate them at 100% real speed, so blurring is the way to go - it's just that photo's don't convey how we really see the rotor disk IRL. I hope I'm making my point well enough, it's a subtle thing. For example, compare DCS's current WW2 propeller graphical effects to MSFS 2020 - the difference is night and day. Despite having generally excellent graphics, FS2020's props look like they're out of the 1990's in terms of animation, whereas DCS props look brilliant. Or even older models in DCS that don't use the WW2 prop graphics. It's along similar lines IMHO. tl;dr - real rotor disks don't look like moving photos. Edit to add: I also get what the OP is saying, which is a separate point (that the new blur effect doesn't look as good, and is more pixelated than the old blur effect) so apologies if I'm off topic.

It's set up by default as a five state dial. Which I left it as. Frankly, there are already enough buttons that it becomes confusing enough moving between different aircraft, I didn't want to further add to the confusion. Secondly, the programming interface, while very powerful, becomes a little fiddly if you're going to add 'shifted' commands (and five states of them!) as well, since it's all done 'per button'. And it's not very intuitive at all for the more advanced settings like that. Youtube will provide I'm sure, but I didn't. All I did was add buttons in the axis range for the idle cutoff. So, idle cutoff and run, that's two virtual 'buttons' per throttle axis. That was enough for me. But, one tip: The two way red switches, of which there are four, are set up oddly from the factory - they are either 'on' or 'off' by default even though they have two 'physical' inputs as you'd expect - you might want to set them up as two button controls, ie. one input per position. Something to bear in mind. Once you get used to the idea of 'physical' vs 'output' buttons, and the way the software works, it's easier to understand. And then always remember to upload it to the device once you've made the change.

This is easily solved, but involves some extra control bind work by the developer (for example, the Aft-Center toggle, Forward-Center toggle, Aft, Center, or Forward individual keybinds for the F16's Dogfight Override three way switch, to enable it to be used by people with only a two way switch available, but still be fully realistic for those with a 3 way switch) So, any button or control that's 'guarded' could have keybinds for all of the 'open guard and press button then close guard', 'open guard', 'press button', 'close guard', and/or 'toggle guard' actions (there have to admittedly be quite a few options to fully cover all combinations, but I'm sure a reasonable compromise can be done).....that would involve a little bit of extra coding from the devs, but it's doable isn't it? They have to allow decent gameplay, but also cater to cockpit builders - the control keybinds are critical for this, but at least the mechanism is clearly already available in DCS surely?

Most headtracking software can adjust the curves, so make them non-linear. In other words, normal rates for the most common forward angles so you don't have overly sensitive head tracking for normal ops, but accelerated rates passing the 90 degree virtual point. The 2nd option, and what you asked for, is to check your headtracking software for a key to toggle it off. In the Track IR software for example, to toggle it on and off the default is F9 I think. In any case, this will be in the headtracking software, not DCS.

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)