Hi all,
Just to clarify a few things that have been mentioned in this thread.
The VOR "spirals" issues isn't something we have ever been able to replicate, but I have personally seen a very small number of users reporting similar issues. As mentioned above, making sure the Working Title GNS530 is fully up to date should solve the issue. As much of a chore as it can be to keep everything up to date, we would recommend always keeping any GPS mods fully up to date to minimise any chances of issues appearing. It's probably the number one cause of autopilot issues we get through our support channels across multiple aircraft.
The autopilot roll oscillations are a known issue when no GPS is selected (weather radar visible). We do have a solution for this that is currently in testing, but we need some time to ensure the fix works across all possible scenarios. As soon as we are confident in the fix, we will push a new update out for the F28 Professional. The difficulty we face with the F28 (and our PA28 range) is when the Working Title GNS530 is selected, it tries to take control of and override all of our autopilot code, so we have to effectively code the aircraft systems and flight model so that it works with multiple autopilot systems, which gets very complicated very quickly! One last-minute improvement to the Autopilot behavior with the Working Title GNS530 selected has likely caused this knock-on effect with the basic Autopilot functions which went unnoticed ahead of the v0.1.2 release. As a short-term solution, you shouldn't have any roll oscillations when the Working Title GNS530 is selected on the EFB.
If anyone is experiencing any issues with State Saving in v0.1.2, if you can contact Just Flight support we should be able to provide a fix for that: https://www.justflight.com/support
Mark - Just Flight