Weta43 Posted August 10, 2021 Posted August 10, 2021 Do the cockpit arguments not work the triggers for the Su-25 ? I've previously used them to trigger actions on other aircraft, and I checked they work on the Ka-50 before posting, but they don't seem to for the Su-25... Anyone else noticed this ? Cheers.
Rudel_chw Posted August 10, 2021 Posted August 10, 2021 Yes, they need a clickable cockpit to work, so the FC3-level modules do not work well with them .. what specific argument are you using? For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
Weta43 Posted August 10, 2021 Author Posted August 10, 2021 17 & 14, to catch the engine spooling up Cheers.
Rudel_chw Posted August 10, 2021 Posted August 10, 2021 2 hours ago, Weta43 said: 17 & 14, to catch the engine spooling up You could use an alternative way to check for the engines spooling up, by checking the RPM parameters .. for the Su-25 they are: BASE_SENSOR_LEFT_ENGINE_RPM BASE_SENSOR_RIGHT_ENGINE_RPM Their values go from 0 to 100 % RPM. I'm attaching a sample mission, for you to try. Su-25A - Test Parameters (by Rudel_chw).miz For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
Weta43 Posted August 11, 2021 Author Posted August 11, 2021 Cheers, I'll give that a go. It's a bit off that the CAs don't work in FC3 - the fact that they're not clickable doesn't change their use as animation arguments. Cheers.
Recommended Posts