PiedDroit

Good point, I forgot about this one:thumbup:. I thought OP had it working and his modification made it disappear.

Revert VTB_init.lua back to it's default value and only use monitor.lua, it is enough to get the job done. If you want to use a different viewport name, the correct syntax for try_find_assigned_viewport is try_find_assigned_viewport("RIGHT_MFCD","M2000_VTB") (make sur this is the only thing you change in that file)

You can also rename the whole \Saved Games\DCS folder (or DCS.openbeta or DCS.openalpha, depending of the version you're using, each DCS version has its own folder in Saved Games). DCS will re-create a new one and populate it with default values. You can still copy some of your old settings (e.g. inputs) back into this folder.

Yes, it should always be automatic. it's just not implemented yet

I support this thread's idea too! Good suggestion!

PID to PIC seem also defective, I flew on 104 today, I never managed to get a PIC lock, I would always end up losing lock not matter how I would bash the lock button... In the end the only kill I made was with Magic II (another Mirage, single hit kill BTW, not so strong). On a side note, lock button still acts as unlock, which makes it even more frustating.

I tried a couple of time agains AI today, most of the time I can't destroy them (despite many hits on the whole fuslage, not dead 6 hits), I usually set an engine on fire and they RTB. It seems the only time I destroy them is when manage I hit the wing, this area seem more fragile, otherwise centerline hits don't get good results. I didn't have the chance to test against player.

Yes I agree, leaving it (AUTO/G/D for Magics) like this is probably the best option, it can be refined later if more info is available. Regarding MAN/AUTO, fair enough, it's not on my top priority list regarding weapon management anyway (I'm fine with the answer "no, it won't be implemented"). I'd like to see the Magic/Gun/PCA HOTAS selector properly implemented (PCA setting really shouldn't be modified when using it): "gun mode" and "cannon"?

I see, no problem. There is no good answer to OP's question yet :(

Complete description is (translated): "MAN: missile release at BRM press" "AUTO: pilot authorizes shooting (by pressing BRM) but the missile is released only at the optimum point computed by the system" The big issue here is what is this "optimum point". I'd love to see something like that implemented, unfortunately I don't know what to put in there.

I know it's all wrong but it's the one control that best serves the purpose of cycling close combat weapons. Another possibility which requires multiple free buttons (or programming a sequence) is to use both keybinds, but since pressing Magic II SELECT twice will return to gun, it would only bring confusion (at least while it behaves like that), this is why I don't advise to use HOTAS Cannon SELECT at all. Unfortunately both (HOTAS Cannon SELECT and HOTAS Magic II SELECT) alter PCA setting, where they should only override it until the user deselects them.

Hello all, I have a question regarding the PPA, in the real manual it clearly states that AUTO/G/D selector only applies to S 530. Does anyone know how the system is supposed to behave when left S 530 has been shot? I understand that making AUTO/G/D also affecting Magic IIs in DCS will allow the user to decide, thus avoiding the situation where only left missiles are fired, but I'm curious to know how it was working on the real aircraft as there is no apparent way of selecting which Magic to shoot. Also, will we have "AUTO" S 530 implemented (button (3) in the figure)? It looks like a CCRP mode for S 530 (pilot presses fire button but missile is shot only when optimal condition are satisfied). Thanks, P

Not typo. In controls, "HOTAS" section, "Magic II SELECT" actually cycles between Magic IIs ang A/A gun, but this is how it is done now in DCS, the switch behaves differently IRL. In DCS this keybind will change PCA selection between K1 and MAG. According to RL manual, that HOTAS switch (on the Throttle) has 3 positions that allows selecting Magic II's and guns without changing PCA. That switch positions should be: - PCA selection (middle) - Magic II - Gun Which means that normally using the HOTAS Magic/Gun/PCA switch should not change anything on PCA selection, it just overrides the current PCA selection. For example: - if I have K2 selected on PCA, this switch should toggle between Magic II / A-A gun / A-G gun (K2 selected on PCA). - If I have S 530 selected on PCA, that switch should toggle between Magic II / A-A gun / S 530 (selected on PCA). And so on...

Sorry, couldn't resist...

I think "C" cannon is a left over from DCS default mappings. The only way I know for selecting cannons in the Mirage are: - HOTAS select magic / A-A gun - PCA select A-A(K1) / A-G(K2) gun I don't remember Mirage having other controls for gun selection (I tried to find it in real manual). I suggest not using "C". P.S.: To answer OP's initial question, you should assign Magic/Gun select on HOTAS ("Magic II SELECT" in controls) (default mapping should be "M", in HOTAS section). Use mouse and PCA to use A-G mode (K1/K2)

That's cool, it will save some neck twisting when inspecting the pylons :)

I agree it wouldn't hurt to add a tiny dot in the middle. If that can help you to picture the sight differently, rather than looking for a specific point, I try to force my eye not to focus to much on the center of the circle, I aim by enclosing the overall silhouette of the target inside the circle. The position of the aircraft silhouette inside the circle indicates me where I'm going to hit. It doesn't work very well when the target is small relatively to the reticle, but I try not to shoot from far away anyway.

Is the threshold bug fixed? Currently what makes axis tuning unusable is that the TDC will start to move only after the axis reaches 50%. TDC should move immediately, then we can add a dead zone and reduce the speed ourselves, just like it is done on A-10C. It looks like current TDC has a built in 50% deadzone which makes any tuning useless, as any attempt to reduce the speed put it in that built-in deadzone (this is what happens when others say the TDC stops moving when saturation value is changed).

Very interesting! Is it too much to ask for a video of a gun straffing run - with targets (you are allowed to replay :D)? I'm just curious how usable it is for vehicle spotting. Thanks!

If the missile loses sight of the target (because of loss of lock) then the target might slip out of its detection cone, in that case it won't be able to reacquire it. I don't think that detection area is very large. p. s. I agree in ideal condition it should reacquire

Yeah that would clog the intakes too :) That is great news I can't wait for it!

Very nice! Any chance you look at the asymetric burst limiter in the process? If you really can do whatever you want, I suggest to create also a paintball ammunition that can be used for mock up fights, with a color effect on the target :D

Interesting video! Maybe you want to fix the links, they all point to 24m54s (text is OK but hyperlinks are wrong) :D

Errrrm no that's the other way around IMO. Sport and such, they do great. But dumb stay dumb usually. [P.S.: I agree that stands true for aircraft. Better make it beautiful then add some brains in it on retrofit :D] Anyway, those photos are great :thumbup:

Reminds me of this: https://www.youtube.com/watch?v=TWx_VmfwS6g&t=18m50s