lonewulf47

Ah, I see. This is something Urs will have to look at.

Sorry, Alain, I fail to understand what you mean. There is no need to add any weather tool. EFB2 is reading real world TAFs and METARs.

Hi Ulrich, This sounds a bit strange to me. Can you check that you use the same database AIRAC Cycle on both EFB and SimBrief?

Hi Robert, Are you aware that for MSFS you need FSUIPC V7 ? FSUIPC6 does not work for MSFS. The Freeware Version of V7 is of course sufficient.

Well, aren't we Simmers always keen on having things "as real as it gets"? That's at least my impression after having attended many FlightSim Conventions and -Exhibits. And that's exactly where EFB has been positioned. In today's simming you can't get away without actual AIRACs and thus actual valid routes. Storing routes with all procedures will thus create a lot of "inconveniences", in general referred to as loading inconsistencies or even errors. What will be the benefit of a warning due to an incompatible procedure? If it is incompatible, it just doesn't fit! And once again, full compatibility can only be achieved when ALL parties affected are using the SAME DATA. It's as aimple as that. Storing a route with all procedures attached means, that you will not be able to update your simulator data ever. Otherwise you will lose your stored routings and/or procedures. For me storing a route with all procedures attached means that I have given up any flexibility, and that's not really what makes flight simming interesting, does it?

Gentlemen, I still fail to understand why you would want to store procedures. Planning a specific route with a modern tool like SimBrief or Route Planner takes less than one minute. EFB comes into play thereafter offering full flexibility to attach every possible SID, STAR and APPROACH within shortest time. Such a completed routing is valid exactly for that moment of planning. Even next day you might encounter different weather conditions requiring different procedures. Furthermore even the basic route without procedures is only valid throughout the present AIRAC cycle. You might have realized that even MSFS is nowadays updating navigation data within each AIRAC cycle of 28 days. So, whatever you are planning, it is useless if you don't use actual AIRAC data. There will ALWAYS be a mix-up if different AIRAC cycles are used, even with the basic route. Still looking for reasonable arguments to store completed routings. I simply don't find one and believe me, after 20'000 hrs of RW flying in airline and instruction businenss IFR and VFR, my aviation background is good enough to judge that...

Indeed! As this warning is created by an internal Windows error, rebooting the PC is the remedy.

Robert, have you checked, whether the correct files are istalled in the respective AIRAC-path of EFB? See below:

Please follow the Forum Rules for all Communication and Inquiries.

Sorry, I don't have any of these Add-Ons by Paulo Ricardo. I have SBKP by LD Improvements and SBRJ by TropicalSim. Both work without problems. Anyone else?

I have it in the MSFS generic database ... and remember: EFB can only show airports that are provided by the respective Simulator!

Please see the other threads already covering this issue ! https://forum.aivlasoft.com/topic/7934-can-no-longer-get-metar-info/

See here: https://forum.aivlasoft.com/topic/7934-can-no-longer-get-metar-info/ We are working on it.

Ahmed, I take it that you have added procedures to a routing. Therefore the RSB (Routing Shortcut Bar) should be visible. Simply press the "AUTO" button and all windows are closed.

Livio, There is no such folder like "scenery", where the MSFS Add-Ons are placed. You should look for a folder "Community". All Add-On scenery (and also Add-On aircraft) are in this folder. I have no experience with a Steam installation, but available information shows an installation path: "C:\Users\<Username>\AppData\Roaming\Microsoft Flight Simulator\Packages\Community" for a Steam Installation. Thus, the path for the above installation folder should read: "C:\Users\<Username>\AppData\Roaming\Microsoft Flight Simulator\Packages". You might want to try this.