Jump to content

sprowse

Members
  • Posts

    13
  • Joined

  • Last visited

Posts posted by sprowse

  1. 2 hours ago, aivlasoft said:

    Hi Steve,

    thanks for your good words on EFB.

    In MSFS many things have changed. There is no *.air file anymore. Instead of the name of the *.air file it should be the ICAO type designator. Currently the ICAO page 8643 seems to be unavailable due to a technical issue but most probably the code is M20R. But to be honest, I don't know whether this Carenado aircraft will provide the ICAO code properly. I don't like to advise "just try it" but for this I simply don't know another way.

    Thanks guys for all the help, I've now tried a few variations of m20p, m20r, m20p ovation etc but to date no joy.  Anyhow I've asked Carenado what code they used.

    Thanks again 

  2. I must add my thanks for making the EFB compatible for MSFS, I’m totally lost, literally, without it.  I do have one question: I’m try to make a profile for Carenado Mooney Ovation (M20R), I know how to add profiles, but in this case I cannot find the necessary *.air file.  Clearly not a big issue, but any guidance would be very much appreciate.  Once again thanks so much for your continued support for our community and for your brilliant EFB.

     

    Steve Prowse

  3. 15 hours ago, lonewulf47 said:

    Steve,

    If a route is saved in the EFB v1/v2 native format (.efbr) it may contain any kind of waypoints. If one of them is not part of the actual AIRAC cycle, the routing waypoints will be prefixed by an asterisk (*) but will load anyway. In the uplink function only routes compatible to the actual AIRAC dataset  (not necessarily the newest) are allowed. In your case you might need to create a new routing manually and save it in the native .efb format. Then you will be able to load it any time and it will also show up in the company routing directory. 

     

    Oskar

    I've just purchased v2 and have started to rebuild the .PLN routes into .EFBR routes using v1 then I'm saving them into the v2 client route folder.  All seems to work just fine.  If any Concorde vpilots are using v2 you can export .efbr files in .pln format into a folder so that CPC can read them.  

    I really do appreciate all the work and effort that has clearly gone into, my most used addon, every flight really.  Thank you one and all!

     

    Steve 

  4. Congratulation Urs and team...the new version looks fantastic!  I'm using the uplink feature with some of my old Concorde routes.  The problem I am having is that many of the routes do not use recognised/current fixes, eg some are simply called FIX1, FIX2 etc with their  associated co ordinates.  The problem is EFB v2 does not seem to be able to process them, in the way v1 did and hence is unable to upload the route.  My question is; I'm I doing something wrong, or is v2 unable to read a route using fixes that are not in the current Nav data base.  

     

    Many thanks

     

    Steve

  5. Sorry to report but I've just tried your latest version with P3D v4 + hotfix one.  The result being I'm getting no airports found by the display unit, the nag box says airport not available in FSX.  I do have FSX, installed on the same partition P3D,  and it is working as usual brilliantly with you excellent software,  spec win10.  

     

    all the best

     

    Panic over reinstall of EFB did the trick.....all working Purrrrrfik now :-D 

  6. If anyone wants to try a new version - 1.6.3 - then please go and download from here.... http://www.aivlasoft.com/Vbg19PxC6xmYJm3Z04OaMKg2GR/AivlaSoft.Efb.Setup_v1.6.3.exe.zip

     

    There are some changed DP settings, and a new PDF viewer control....

     

    If any of the new changes "break" former good changes please let us know....

     

    Regards,

    All installed and all seems well with this update (using upgrade W10 and FSX gold).  PDF viewer btw is much better.

     

    Thanks for all your efforts, Urs and travis.

     

    Steve 

  7. Hi Steve,

     

    you're right, on my machine wasn't a copy of Adobe Reader DC.

     

    I have downloaded the latest version from here: https://get.adobe.com/reader/otherversions/ with the following options:

    attachicon.gifAdobeReaderDCDownload.png

     

    Then I restarted the computer, started the DisplayUnit and loaded a pdf-document. No problems so far, the browser control showed the document properly.

     

    Maybe you try to update the Adobe Reader DC to the same version?

     

     

     

    Well I've just got the latest W10 update installed and the PDF problem seems to have been rectified...many thanks Urs.

  8. Hi Steve,

     

    thanks for the report. When I try to reproduce it on a Win10 computer then a message box appears which asks whether I want to download or to open the pdf-file. From my point of view this is the default message box from Internet Explorer when clicking on a pdf link. After selecting "open", the IE browser window opens and shows the pdf-file content. Can you confirm that this is more or less the same behavior on your computer?

    What you have reported above happens if Adobe reader DC is not installed.  If however it is installed the pdf page opens but is blank after a few seconds the DU will stop working.  Below, is the generated error report:

     
    Log Name:      Application
    Source:        Application Error
    Date:          9/13/2015 7:10:36 PM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      ADMIN
    Description:
    Faulting application name: AivlaSoft.Efb.DisplayUnit.exe, version: 1.6.2.0, time stamp: 0x55f2da5b
    Faulting module name: AcroPDFImpl.dll_unloaded, version: 15.7.20033.2203, time stamp: 0x5507d6f6
    Exception code: 0xc0000005
    Fault offset: 0x00030b84
    Faulting process id: 0x1c90
    Faulting application start time: 0x01d0ee14bd7a0bec
    Faulting application path: C:\AivlaSoft\AivlaSoft.Efb.DisplayUnit.exe
    Faulting module path: AcroPDFImpl.dll
    Report Id: f478077e-a6e2-4e68-abc5-10951b8a2b8a
    Faulting package full name: 
    Faulting package-relative application ID: 
    Event Xml:
    <Event xmlns=
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-09-13T11:10:36.000000000Z" />
        <EventRecordID>6254</EventRecordID>
        <Channel>Application</Channel>
        <Computer>ADMIN</Computer>
        <Security />
      </System>
      <EventData>
        <Data>AivlaSoft.Efb.DisplayUnit.exe</Data>
        <Data>1.6.2.0</Data>
        <Data>55f2da5b</Data>
        <Data>AcroPDFImpl.dll_unloaded</Data>
        <Data>15.7.20033.2203</Data>
        <Data>5507d6f6</Data>
        <Data>c0000005</Data>
        <Data>00030b84</Data>
        <Data>1c90</Data>
        <Data>01d0ee14bd7a0bec</Data>
        <Data>C:\AivlaSoft\AivlaSoft.Efb.DisplayUnit.exe</Data>
        <Data>AcroPDFImpl.dll</Data>
        <Data>f478077e-a6e2-4e68-abc5-10951b8a2b8a</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

     

    Hope this helps

     

    Steve

  9. Hi all,

     

    this is the download link of the latest public beta version 1.6.2. Please report any anomalies herein. Thanks.

     

    http://www.aivlasoft.com/DPYZHbwca65FnjabRYHbf0pL8/AivlaSoft.Efb.Setup_v1.6.2.exe.zip

    Cannot read/open PDF files that are stored the user's library using the DU...Modules....Library.   Using Adobe DC latest version, installed on root drive. Operating system W10 home edition,  all current updates installed. Other than this issue everything seems to OK.

     

    Steve  

  10.  

    I wonder if I can have a refund now as I only had use of this for a couple of months and as the Consumer Act says"NOT FIT FOR PURPOSE"

     

    Good point Caal:

     

    Specifications

    EFB version 1.5 (and higher) supports the following two simulators:

    • Microsoft Flight Simulator FSX, ServicePack 2 or Acceleration Package or 'Gold Edition'
    • Lockheed Martin Prepar3D, Version 2.0 (and higher)

    Further requirements:

    • Microsoft .NET-Framework 3.5 SP1, or higher
    • Network Interface Card (NIC)
    • Internet: to install either a personal license or a demo license your computer must be connected to the Internet (see also next paragraph "Internet connection").
    • Memory: at least 1 GB for a separate DisplayUnit. If all components (including FSX/P3D2) are running on a single computer, then at least 2GB are required
    • Harddisk: 50MB available space
    • CPU: best performance with Dual- or Quad-Core processors i5 or i7, at least "P4 3.0 GHz"
    • Screen resolution: 1280 x 1024 pixels

     

     

     

    Above is the spec for the current version of EFB....note no OS is mentioned and moreover  the DOTNET  requirement is for 3.5 or higher....and there is no requirement for a clean install.  I also note that one of the guys that actually did a clean install now finds EFB does not function.  

     

    All the best

     

    Steve

  11. So Aivalsoft's EFB will only run on a clean install of windows 10 as per this post, which follows, from the "support team"

     

    'Posted Yesterday, 05:15 PM

    Development of version 1.x has been stopped more than one and a half year ago (Jan 2014). Nobody was talking about Win10 then.

     

    Only version 2.0 of EFB (which is still under development) will run on Win10 (better say, on .NET framework 4.5). EFB 1.x requires .NET 3.5.1 which obviously is not available after an upgrade to Win10 but it will be installed by Win10 as soon as a program is demanding for it. But only if the operating system has been installed from scratch (not via upgrade). See here: http://aivlasoft.ipb...ge-2#entry11307

     

    The cause for the problem is not EFB, the cause is the upgrade feature of the Win10 installation which obviously does not the same than a clean installation of Win10. After a clean installation of Win10 no problems have been experienced so far with EFB 1.5.1.'

     

    Amazing to say the least...I've, installed, on my Desktop so many other types of flightsim software some much older than EFB, and they all run perfectly on windows 10!  Just how old is FSX now?  It RUNS!   Yes against all the odds.... I think it even runs better!!!! I think Urs you should put a note on the frontpage, if you're brave enough, of the website saying that EFB does not run on windows 10, only if you've upgraded though. If you want EFB to work you'll have to start from a clean HD you know what I'm talking about give yourself a week of work plus just getting your flightsim just as you like just so you can install EFB.  Yeah right!!!!  How many times have I read from developers ' no it not our software its your machines its your setup yeah yeah blah blah....I'm very disappointed Urs I expected more from you.  Still never mind I'm back to using FS commander which like all my other flightsim software runs just fine on W10.  Oh I guess when EFB version 2 does eventually appear we'll all have to pay for the upgrade; yes? Now there a surprise but I guess it is a full rewrite and it is W10 compatible; here's one of your long time customer who'll not be buying it any of it!

     

    Best regards

     

    Steve Prowse  

     

    PS I've been supporting you since July/August2010

  12. I agree Mike. Come on guys lets find a simple fix to save your customers from a lot of hassle

    Very strange that the one app I thought would not cause any  trouble with the windows 10 upgrade is indeed the only  app that doesn't work!   Moreover the only help we are getting here is; use a clean install only,  well it is too late for that for me and rolling back is not an option....so my question is; are you trying to sort out some sort of fix or what?

     

    Steve Prowse    

×
×
  • Create New...