Leaderboard

Thx a lot guys! I just found the culript, by deactivating the running plugins, one by one. It was OpenVFR´s Iceberg plugin... I always used this plugin, as it also offers a nice fix for the water in XP. But with XP 11.50 b11, it seems to cause some problems. However, the fault wasn´t at your end! ;-) Thx again for this great addon! And yeah, Coop! Good to be back in the saddle (cockpit), again... ;-)

Hey Mik! Good to see you again. Not sure what this could be, the advice from Ulrich a post up would be my first recommendation. Besides that, can you provide the log.txt file too if it still shows with our plugin?

@Mik75 try loading up the islander and then deactivating the islander plugin via the plugin manager. if the window doesn't go away, it's not an issue with our plane. if it does go away when our plugin is inactive, we'll have to look into it.

Just to close out the topic on a high note - made the flight with the G5 from Key West FL to Grand Bahamas (MYGF). Great flight - all systems seemed to be functioning great and although the first landing was a bit scary not knowing what to expect, I followed the check list and made a smooth landing. Grats on a great plane and look forward to continued development.

Yes, that is them.

Never mind, I just came across your ticket. Furthermore, contrary to what you stated here, you did not wait more than the 3 day timeline. You were found to be using aircraft from an account that does not belong to you. Until you purchase those products, we will not be assisting in this matter.

Hi Cameron and Coop, Thanks. I got it working now. The load manager appears on the left side. It's a great airplane and glad to have it fully functional again. With a screen resolution of 3840X2160 that tab is really small. Thanks again for your assistance.

So, @Goran_M the first flight without AI plguins was definitely more stable, even the vertical navigation was more accurate. I will keep it like this for some time, I will keep you updated if I encounter anything 'weird' Thank you!

I see what is happening: The waypoint you are flying to was getting BYPASSED (means the plane could not fly over it because of the turn radius) - and appearantly this was by more than 2.5NM lateral distance, so the waypoint never sequenced (got deleted). The plane is - however - following the magenta track, it does not "know" that it missed the point. The cure for this is to fly "direct to" the point you are actually flying to - in this case ANC. Then the flightplan is "in sequence" again and the plane will behave normally. To avoid this happening in the first place, make sure that you have no "bypass" points in your route - often the speed of the plane is too big in that case, or the waypoints are at too acute of an angle. Cheers, Jan

Thank you very much! Upgrading MS Visual C++ library helped a lot (read as: resolved the issue). M20R G1000 with SVT

lol. Yes, the circuit breakers are simulated.

Jan is right, we have not touched the AP or VNAV code at all since 1.21, so if something is worse, we need to know exactly what it is that "makes it worse". Debugging is quite tough business, not so much the fix, but the amount of diligence it takes to quantify what the issue is and put it into words. Good VNAV starts with good routes to make calculations from, and that is where we currently are as of this instant, fixing the STAR / APP route building code as these procedures are selected...since they are clearly resulting in 'funny routes' where VNAV calculations make no sense. That '470' bug is a pain for all of us and I'm super sorry about that one, but its fixed for the upcoming update and we are also now trying as many route editing combinations as we reasonbly can to test the robustness of entries. We will have an update in relatively short order with several fixes for sure and I for one, will be interested in seeing how the FMS handles "in air edits on descent" for all the situations folks will try that we did not get to. VNAV complaints are heavily biased toward the descent calcs and revisiting my code, its not hard to see why....which is a good thing...as it paints a clearer path for repairing the code. We are now working on FMS code and VNAV with priority, so any patience / feedback as these updates come out will be appreciated and help us improve. Bug reports regarding VNAV after this next update will be quite valuable as we are focused on that work at this time. -tkyler

Glad your sorted.... Anthony

We had internal discussions about this and decided to move the white text to our console message box ONLY when an error occurs in sim. You can download the updated plugin which removes the white text from the upper left here: