OLD CROW

Don't worry too much about that fact.... Several people want pilots with a bushy moustache... I think that makes things easier to modelers.... . Of course I'm not serious...about the moustaches...

One simple solution to mask on/off in cockpit would be Oxigen pass switch ON/mask ON.... O2 switch OFF/ mask OFF. "As easy as" that.

Indeed, but there's a modeled pilot face template in every single skin we use ingame, default or custom ones. So it seems in any moment of the creative process anyone thought in showing pilot's face.

"Kinda" F/A-18C ACLS test

Puedes simular que las tropas embarcan haciendo que estas desaparezcan cerca del helicóptero con un trigger, zonas de trigger, puede que alguna bandera y la opción "desactivar grupo" en el punto A y luego hacer algo similar y "activar grupo" en el punto B y todo eso que te ahorras en scripts y otras historias que no sabes si en la siguiente actualización funcionen bien y si la misión es para compartir pues le ahorras a los demás el buscar el script, instalarlo,etc, etc.... Además creo que visualmente en ningún módulo, oficial o no, se ven las tropas embarcadas.... pues eso. El único que sabrá el truco es el mago.

Now motivation enough you got to do it little padawan

I haven't watch the film yet. I'm too busy editing missions, recording gameplays and editing vids that I literally have no free time for Mavericks ;))))

I've noticed that, at least, in the caucasus dogfight vs. Su-27 and in the Syria vs. F-15 and vs. 2x F-16 instant action missions the AFCS Roll switch is in OFF position once you spawn in air and it needs to be switched on manually before entering the fight.

Collective lever Pull up/ push down changes the AOA (angle of attack) of your collective (ALL) rotor Blades(chopper's wings) throughout a complete rotor spin. That all blades AOA change means more/ less lift. On the other hand we have the cyclic where the lever/stick only changes the AOA of the blades in the exact point of the cycle you are pushing/pulling the stick (like the ailerons in an aircraft for the rolling). 100% sure you can find out other better tech explanations, but you need to understand what they move and the reasson for that move.

Luckily for all of us we have sims like this to be as seriously fun as we want or funnily serious as we can to emulate whatever your level of reality.

I never said P I said Mustang. The only who wrongly used P-51D has been who tittled the vid I posted. Just for laughs....Would it be same kind of comentaries if I dared to use MIG-28 instead of F-5?

And owns. He owns the Mustang shown in the film

Then the answer to your question to CASE III in RVR CAVOK conditions in nowadays DCS is NO cause is the SC ATC who dictates the recovery case depending of the weather forecast conditions, at least from what I know.

You can push the CASE III conditions just changing the weather with the presets OVERCAST+ RAIN, also changing wind intensity etc,...would work fine to your pourposes, also you're going to practise almost "IRL" conditions where CASE III is aplied. I remind you those types of recovery are based in Visual Rules so you can perform a case II-III at 12 o'clock mid day if you can't see anything beyond your A/C nose.

Thanks mate I will bear all your inputs in mind. 2 hours later: problem solved!!! The problem is when you couple the A/P (CPL button) in the time gap from the ATC couple and the left DDI ACL RDY announcement. If you couple both almost at the same time A/C becomes a mustang horse (uncontrolled nose up/down also rude banking left/right), but when you couple ATC at (aprox.) 140 IAS wait patiently til ACL RDY tilt in DDI and then press the CPL button and the A/C goes into glideslope and on speed AOA in a really smooth way. I tried a couple of times and it worked fine.

I've just downloaded latest beta release a couple hours ago. I tested twice my own CASE III with the new hotfix and these are the results: Before hotfix I drank the soup a couple miles before reaching the carrier, so the autopilot put the plane below the glideslope path, now 100% times the autopilot is putting the A/C over the glideslope path so I got to uncouple it and do manually all the corrections for not overshooting the carrier. Also the autothrottle and the autopilot are very rude in the initial corrections for the AOA and the glideslope. I attached the video also the miz file. I still guessing there's a delay is the AI logical processes for "lower" CPU's. PG_SC_TEST_ACLS.miz

Maybe it could be useful or maybe not cause it is based in first release. Good luck.

Nope it was not my intention also I checked twice AP was really Coupled. From my own research at home seems there's something wrong when you try to modify the carrier parameters in the default mission CASE III recovery. I've tried today to make a new mission from scratch with no other AI than the autopilot and ZERO issues and wire 3 with strong wind. Now I think this is like religion, computering or doing the Indiana Jones: It's a leap of faith: whatever one day doesn't work next works fine, just cause you do it from scratch. But I got to say that making a clean and clear mission from others AI controlled units is far away from being a definetly solution. Thanks anyway. I also attached the mssion if someone is interested in it. PG_SC_TEST_ACLS.miz

Well.... it's only my guess but We all have came here with a similar issue, so I own a 6 years old PC with an intel I5 at 3.2 GHz CPU, so after several attempts to do Case III and 100% cases I finished in drinking the soap due a CPL couple/uncouple issues my guess is: Could it be related with CPU loggic processes bottle necks? I talk about CPU cause I got same issues when I call the ball with the Hornet and with the Tomcat in the Super Carrier and the LSO always say "Wave off" by omission I always call the ball even I am visually in the right path and glideslope for wire 2-3. Thanks for advance. The mission I've used all times is the default F/A-18C Case III recovery in the Persian Gulf Map adding to the carrier the Link 4 and the ACLS options in the mission editor. All times the autopilot kept the speed vector below the glideslope bar (as shown in the video).