oskrypuch

Very good, thanks. * Orest

Any chance to see one, a Nexrad layer in the EFB map display? That is the one thing that I find is really missing, that I need to look elsewhere for. * Orest

FIXED. Thanks.

Thanks! Will test that shortly, looks like the fix. * Orest

After arrival, when taxiing at Toronto Pearson (CYYZ), I intermittently lose the view of the airport complex, although any online aircraft still remain in the same relative positions. This has happened more than once. Using P3D v5, PMDG 738, FlyTampa Toronto scenery. When this happens, the CYYZ - Toronto/Pearson title changes to ZYYZ - China (ignore), I don't believe ZYYZ is actually a valid ICAO airport code, although Z--- is normally China. Zooming in or out or trying to change the view, and come back to it, doesn't make a difference. An odd bug?? * Orest

The PMDG operations app will detect and solve this issue (for all) by adding/changing a registry value. Pathname length restriction (260 chars) affects their livery saves as well. You can do it yourself as well, just google around. For Home you have to edit the registry, for Pro you can change a group policy. You must be relatively up to date with the OS. * Orest

Thanks! * Orest

Delete, and rebuild your Aivlasoft database(s). * Orest

I keep meaning to ask (x years!), been passively trying to figure it out, didn't notice it described in the docs, what is the meaning of the single letter beside the airport code, usually a set color, here an M in blue in the top left ... I'm thinking it relates to the phase of flight, but "M"? * Orest

OK, thanks. * Orest

OK, so question, what is the level of functioning to be expected for the G3000, for example with the TBM in 2020, SU11? If I load the TBM with a flight plan, it doesn't appear to propogate to Aivlasoft. And, if I create a flight plan in Aivlasoft, it does not appear in 2020. So, there doesn't appear to be any sync at all. The TBM profile is recognized, the forward flightplan tick boxes are ticked, and it has recognized 2020 as the sim running. This is with the Aivlasoft version just updated tonight. Curiously I had to run the database builder (for both 2020 & P3D), as there were no databases existing any more, not sure why. Maybe that happens for some updates. The rebuild found the sims, and recreated the databases. Is that expected with the latest Aivlasoft update? * Orest

Much appreciated. * Orest

Presume you mean ... Unfortunately there is now work around yet. OK, thanks. * Orest

So, SU11 is out, and there seems to be some changes the flight plan internal formats. Any chance that actually HELPS work around this issue? My interest is in being able to control the flight plan and any enroute plan changes, directly from the Aivlasoft EFB, like I can for small GA aircraft in P3D. The UI in 2020 for the GPS units is virtually unusable, with the arcane mouse twitching needed. * Orest

Could you consider ADDING the SQUAWK code to the STATUS block. Should be simple to do, and there is lots of room, as below. Or perhaps in the ATC Ribbon, under Auto Scroll. Handy to have for quick reference. * Orest

Other than plead with the developer, or at least seek clarification. It could even be something as simple as a format change. WorkingTitle is pretty responsive. * Orest

So that would obviously affect the addition of a DCT waypoint change, as that generates a "present position" custom waypoint. But, it may be even more than that, I didn't think that the flightplan transferred at all into MSFS, if using the 1000. Will double check that, it may be something along the lines of above. Thanks for looking at this. * Orest

I normally run P3D, and have been runnning the EFB for years with great success. Just recently looking at MSFS2020, more for small GA. Installed the Steam version, running fine. I scanned MSFS with the Aivlasoft database builder, have FSUIPC7 installed (and recognized as running), and YES I have the option ticked in the G36 profile that I'm running in 2020, so as to forward the flight plan. EFB runs, shows the location as usual, everything else works, except the flight plan forwarding to MSFS, is not happening. I am running the just released SU10 version of 2020 (Steam). What am I doing wrong? * Orest

Looks like you've fixed this already, thanks. * Orest

Actually, that doesn't help. We forward the flight plan from our dispatch, rather than (necessarily) the Pilot ID that is used to log in to VATSIM. But, given that I'm the primary developer, I can certainly amend that! * Orest

Well, my pleasure to be of help, and look forward to the fix. If I can import from SimBrief now, it may be academic. Will check that out. * Orest

Having the flight number matching your VATSIM filed number, prevents the ghost showing when TFC is enabled in the client view. There used to be a way to set a default for your flight number when inputting the flightplan, minor issue of course, just need to put it in manually. Just installed into a new computer, and can't seem to find that setting. Is it still there? * Orest

Perfect, thanks! Any projection on when the next update might be? I guess it will pop up. * Orest

First of all, thanks for the great app! Not sure how often you update the data in the ATC ribbon strip, but if you scan for INFO x in the text that you would show in the "i" link, that is a pretty reliable way of catching the ATIS sequence designator. If that could be continually shown on the square info graphic in the ATC Ribbon, that would be great. Let's you know when to have another look. Something like the graphic below, showing Info K. Thank you for considering it. * Orest

I would echo the same. An example, TOR_CTR is currently 125.775. Setting 125.77 on a radio will implicitly add the .005, to give 125.775. However, the Aivlasoft EFB does not do that in the convenient quick-click it provides on the Radio panel page. Making this even more confusing, VATSIM does NOT append that same .005 in its frequency lists, which is why the EFB picks that up. With the switch away from voice rooms, in favor of using the actual dialed in frequency, in this instance setting 125.770 will no longer work. What you need to do is round the value to the nearest 0.025, correct to three digits, until VATSIM catches up with this in their frequency list. If they start simulating the new .0083 spacing, that would be another level of complexity. Of course manually typing in 1 2 5 . 7 7 5 works fine in the EFB as well. * Orest