PeterDowson

Yes, but I don't like anything other than scenery on the projected screen outside my cockpit windows! Spoils the illusion! Regards Pete

So it is true, that updating EFB always needs an uninstall first? I think that needs to be changed -- or at minimum emphasised in the README for the update packages. It was certainly not a necessity before SP4 as I pointed out. As it is I am happy enough with SP3 until, probably, Version 2 comes along. Regards Pete

Synthesized simply means "made" or "created". So the ASE synthesized weather is not only what has been downloaded, but it has been processed for FSX, made into the right form. This is why it sounded more correct. I really don't know where you get "wibbly-wobbly" from. Anyway that more describes "jelly", not weather nor cheese. Pete

Right. I did try that and it was fine. I didn't find it in the manual -- though I see in another post that it appears in a picture. That actually explains why I didn't find it -- I have the manual, like all my FS App documentation, on my iPad, and searched the text for details of the relevant file and where to find it. Perhaps you could include it in the text at some stage, please? Searches don't work on pictures I'm afraid. Regards Pete

I'm a bit reluctant to do that now it works again. I did NOT "apply all the service packs" before installing SP4. I installed them as I saw them, since I first got EFB. Today, having been running with SP3 okay for weeks, I saw SP4 and applied that. This produced the failure I described. If everyone needs to do a complete uninstall and reinstall each time an SP comes out you should certainly state that in the notes, or, better, find a way of applying SPs which don't need such drastic measures. I'll stay with what I have, up to SP3, until something is resolved. i read what the changes were and they don't seem to affect my usage in any case. I just thought you should know. Regards Pete

After a successful flight today using EFB updated as far as SP3 -- successful other than the ASE weather data problem reported separately -- I noticed that SP4 had been released. I thought I'd better keep up to date, so I've just installed it. Now the Data provider just won't load. It displays: Could not load file or assembly 'Desaware Machine License20' and a load of versioning stuff plus: at j3.a (string A_0) at ib.a (String A_0) at wj,g () at wj.h () at wj.l () I couldn't do anything with it. So, I tried to uninstall SP4 (only), but lost the lot, so I've now reinstalled 1.3.1, SP1, SP2, SP3 and my latest NavData (in that order), and I've got a working EFB again, up to SP3 level. Looks like SP4 needs something in addition to what it seems to provide? Should I wait for SP5, or maybe Version 2 is near? Regards Pete

I was allowing EFB to get its METAR data from FSX, but realised that because I'm using ASE in DWC mode, this would be wrong except close to the weather station requested. So I changed it to point to the ASE weather files. There seemed to be two it accepted when browsing for the path: current_wx_snapshot.txt current_synthesized_wx.txt I looked at both and they seemed to be pretty similar, so I chose the latter. However, when asking for the METAR for LIPZ, the display part of EFB said it wasn't a recognised format. I'm using ASE with the latest update, SP3. what am I doing wrong? I tried to attach a ZIP of the weather file, but even Zipped it is too big (304kb, max allowed only 256?) Regards Pete

Aha! Found out what was happening ... I'd told the Provider part to rebuild its data. When it had finished it had put up its prompt waiting for me to "ok" it to restart. By that time I was in the midst of setting up other things and getting FSX loaded, so I didn't see it! Allowed that to restart, then restarted the Display program on the client PC, and all is now well. Maybe it does highlight some minor weakness somewhere though. I do hope Version 2 is coming on well. I can't wait to have the FSX installed plan autoload into the EFB -- the only hassle I have with the 10" touchscreen is selecting the correct plan type and the specific plan. Fiddly with big fingers! Regards Pete

I was trying to start a flight from LSZH to LIPZ, and selected the FS9 style PLN file okay (attached). But upon activating it just hung forever displaying "Loading data for LSZH". The main buttons still responded, but when pressing Route Setup again there was a crash report -- though I could carry on and still wait forever for the LSZH data. I attach the crash report details too (screen grabs). But the main problem is it hanging getting airport data. If I close the program down and restart it, it goes direct to the hang loading LSZH data. What can I do about this? Is there any more data you need? I am using the recently released FSDreamTeam's ZurichX version 2. Regards Pete [flightplan] title=FStarRC: LSZH to LIPZ description=Zurich to Tessera at FL330. Generated by FliteStar via FStarRC (c) Pete Dowson type=IFR cruising_altitude=33000 departure_name=Zurich departure_id=LSZH, N47* 27.04', E8* 33.06', +001407.00 destination_name=Tessera destination_id=LIPZ, N45* 30.03', E12* 21.01', +000007.00 waypoint.0=LSZH, A, N47* 27.04', E8* 33.06', +001407.00, waypoint.1=2.1DM, I, N47* 27.03', E8* 35.08', +002500.00, waypoint.2=95TO2, I, N47* 27.02', E8* 38.02', +003600.00, waypoint.3=ZH502, I, N47* 27.09', E8* 46.00', +007200.00, waypoint.4=ALBIX, I, N47* 15.00', E8* 33.09', +017600.00, waypoint.5=RONAG, I, N46* 46.08', E10* 15.05', +033000.00, waypoint.6=LIDT, I, N46* 1.04', E11* 7.05', +033000.00, waypoint.7=Xrstr, I, N45* 46.02', E11* 28.58', +023949.00, waypoint.8=VIC, V, N45* 38.02', E11* 40.06', +019800.00, waypoint.9=PZ504, I, N45* 12.07', E11* 58.08', +009500.00, waypoint.10=PZ503, I, N45* 14.07', E11* 54.04', +008200.00, waypoint.11=PZ504, I, N45* 12.07', E11* 58.08', +006900.00, waypoint.12=LAREN, I, N45* 16.07', E12* 3.07', +005000.00, waypoint.13=LATUS, I, N45* 22.02', E12* 10.07', +002400.00, waypoint.14=LARTI, I, N45* 25.08', E12* 15.05', +001100.00, waypoint.15=LIPZ, A, N45* 30.03', E12* 21.01', +000007.00, [attachment=2]ScreenHunter_01 Aug. 31 11.22.jpg[/attachment][attachment=1]ScreenHunter_02 Aug. 31 11.23.jpg[/attachment][attachment=0]ScreenHunter_03 Aug. 31 11.23.jpg[/attachment]

Just the once so far, but I've not had time to start up the cockpit again yet. That'll be tomorrow. For all I know it is everytime from now on, in which case it would presumably indicate some corruption, or it may just go away. Isn't that just always the way, until you get enough info? I hoped the crash data was enough. looks like a trivial thing, a Key missing someplace? Maybe the cfg or ini file? Seems a lot of these managed languages like C# and VB make a crash on the slightest pretext which in C would just return an error number and allow the program to do a proper report or recovery. I'll let you know if it happens again. Just didn't want to lose the data, so it's yours now . Regards Pete

First crash I've had in the Aiviasoft EFB. I am running the display on a networked PC, on a 10" touchscreen. I'd loaded a route and activated it, then continued setting up my cockpit ready for taxi and takeoff. Next time I looked at the display, it had crashed with the message shown below. (I took several pix with the data scrolled a little each time so you got it all). Not sure what happened. It never has before. Best Regards Pete