New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
missions created in DCS 2.7+ occasionally render AN/ASN-41 navigation computer inoperable #344
Comments
|
having trouble reproducing, a mission file would be most helpful, we've let hawkmoon know |
Hi I have several mission with this issue. How Can I share it? Thanks |
the issue tracker can accept attachments -- just drag and drop or paste them in. |
Thanks callmepartario, please would you tell me where is the issue tracker ? I am trying to attach the miz file here |
you are posting on the issue tracker right now. you're there. just drag the mission file into these posts you're making. |
for example. In my case, the navigation system is inactive and cannot be programmed either. You can hear the adjustment "clips" but the indicators remain at 0 and the system is inoperative. It only works editing missions already created in 2.6 If you need more missions, information, etc ... about this error, I will be happy to share them with everyone. thanks for your effort |
fixed in 2.1.1! |
Describe the bug
Newly created missions in 2.7's mission editor render the navigation computer inoperable.
If you load a mission created in 2.6, loading it in 2.7 has everything working just fine.
Additionally re-saving it to 2.7's mission format (including making cloud changes) does not appear to cause this breakage (in the develop branch, the quick-start missions are all updated and are not showing this behavior).
Thanks to SPINEG, HawkMoon and others in the discord for helping reproduce a few things here. Any additional testing or reproduction would still be welcome!
Software Information (please complete the following information):
The text was updated successfully, but these errors were encountered: