G21pilot Posted yesterday at 05:23 PM Posted yesterday at 05:23 PM (edited) Hey, First off thank you for a great immersive experience. I've come back to this campaign after a while and it's really awesome to fly realistic missions with comms. In my last two missions I've had odd wingman behavior where they fly off in another direction and won't rejoin if the normal commands are used. This coincided with the last update (and post hotfix). In the first case Gravity turned and flew an opposite track between wpt 2 and 3. I eventually got her to rejoin but when asked to refuel she just flew behind the tanker (close enough to refuel but didn't). We pushed for our anchor point, but her jet had flaps half and probe out the whole time. I'm not sure if this is a bug or a simulated failure. The probe and flaps stayed out for the mission, and she wasn't in the f10 menu to attack targets as expected. She wouldn't hit the tanker on the way back to the boat and flamed out after a bolter and crashed. The next one Shadow flew off into Iranian airspace at low level after attacking the convoy and was shot down. Again, he wouldn't respond to any comms to rejoin, rtb, etc. Results were mission failed. I really do feel for mission designers as it seems that building a mission that works is kind of black magic but keeping it going through ED updates is an entirely other thing. Hope this input helps. Sorry, I don't have track or tacview files. Goose Edited yesterday at 05:24 PM by G21pilot
Solution G21pilot Posted 21 hours ago Author Solution Posted 21 hours ago OK, It was VIACOMM. I had removed all my other mods but forgot about this one until I re-read the help pin. FYI I did not have to change the hooks or lua; just not launch it. :) 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now