Jump to content

bhorv67

Members
  • Posts

    23
  • Joined

  • Last visited

Posts posted by bhorv67

  1. Hi, I'm using EFB v2 b133 w/P3d v5.3 hf2. Airport in question is FlyTampa KTPA.

     

    The issue is after landing at KTPA, the airport geometry is missing from the EFB client display. While the AI traffic is visible, no runways/taxiways/buildings appear. After about 5 minutes of taxiing to a gate (usually have to call a FollowMe), the airport just appears in the client display. 

    I've tried rebuilding the database but doesn't seem to help. I don't believe I have this issue with any other airport. 

    Appreciate any help, thanks 

  2. Hi - I'm using P3d v5 build 5.3.17.28160

     

    Haven't made any sim changes recently, yet the EFB client on my network setup cannot setup SIDs or Stars. 

    When I click the Dep or Arr button on the client, the pop-up appears, but I only get the very top of the box, where the Windows 'x' is, the rest of the window does not appear. 

    Restarting doesn't help.

    The EFB server appears to be running normally, no errors. The client is connecting, and the map is following the plane, but just cannot bring up the DEP or ARR window for some reason.

     

    Appreciate any help, thanks

    Brian

  3. Issue solved - I had to create a log output from the client to see the port. This detail should be available in the main gui. Would save time troubleshooting network issues.

     

    As a side note, I've never changed the port on either the client or server. So in a later release of the server, the default port from the installation must have been changed. My client had been installed some time ago and had the default port set at that time. 

  4. Hi, I've been having trouble free experience for a long time. Just did a complete system rebuild of the PC running p3d and EFB server. New install of windows and hardware. 

     

    Both the client and server are v 2.1 b119. Currently I have the server firewall turned off, client still not able to connect. 

     

    I can ping the server IP from the client command prompt, yet client doesn't connect. 

     

    Any help would be appreciated, thanks 

  5. Today I was in flight when a power failure happened, the battery backup didn't keep the system running long enough and everything shut down very unexpectedly. When the system came back on, I lost the ability for the client to connect to the server on the P3d computer. IP addresses haven't changed. Firewall settings haven't changed. The client is waiting for the Server, but never comes online. 

    The first few times I launched the server, I was getting a strange error dialog about some access violation. Something obviously is wrong. Not only is EFB affected, but I now can't run ActiveSky either in a network setup. 

    I ran some Windows diagnostic tools, but no errors were found in the ram hardware, NIC, windows file system or disk integrity. 

     

    I'll keep searching for other issues, but any help would be appreciated. Thanks 

     

  6. I've had the trial version which up until the latest update was released has been working fine. 

     

    Now at launch of the server, I get the message ' unable to locate the server, etc....'. Usually when I click 'ok', another window open to enter name/email - since the update, EFBv2 will now just quit. 

    Occasionally, it will find the server available and say ' 10 days left on the demo", but then I'm prompted with - new Airac installed, click ok to launch the DB builder - then same problem as mentioned above happens.

     

    Now I just purchased the license and would like to get out of the trial mode - I reinstalled the client from the latest server installer, but still having the same problem. 

     

    Appreciate any help. Thanks in advance

  7. 3 hours ago, Eberhard Rordorf said:

    I had the same problem and spent hours to find the solution. The problems are the stupid "admistrator rights" in windows 10 in any of the "users/user-folders".

    The very simple solution is to mak a folder directly on your hardrive (of the client computer). Mine is   C:/FlightplansEFB.  You give the rights to open this to anybody. Then you can open this folder with no problems in the network, on your main FS computer.

     

    The link for EFB in PFPX to place the flightplans goes to my desktop. So I can very quickly copy and paste it to the open flightplan folder on the client computer.

     

    Ebi

    No need to do that - you're making it more complicated than it has to be.

     

    If you can't get network sharing setup, use something like Dropbox or OneDrive. Then map the EFB route path to whatever you used. Set PFPX to save to the same folder. Done.

  8. 14 hours ago, lonewulf47 said:

    Not so odd. Please check the User Guide "Client", chapter 4 User Interface. It's called the System Menu!

    What I should have said is the power button is an odd place to put the System Menu.

     

    Guys, I love everything you've done with the update, I know I'll buy it. 

    Accessing the System Menu is just a bit unintuitive. When you look at that button (yes, without first reading the manual), you think it's just power.

    I would suggest maybe changing the button to the client icon instead of what looks like power - yes, when you roll the mouse over it, it says system menu and power. I think that would be more clear. 

     

  9. 12 hours ago, nbillo said:

    Continuing on with this topic; can anyone shed some light on my issue?

    I have my client installed and networked on my surface pro, and the client is mapped to my onedrive documents folder. (It used this automatically during the installation) I can create my flightplans using PFPX on my server laptop and export these to the mapped folder in my Onedrive\documents\aivlasoft\efb2\clients\routes folder and they go there okay. However, when I open up my FPL radio tab, I cannot see any flightplans there and the Company Routes tab is greyed out. Only the Copy/Paste tab is highlighted. The Internet tab is also greyed out. Has anybody any ideas why I cannot see my flightplans in this window?

     

    Thanks,

    Nigel

    Click on the power button at the lower left. This will bring up another window (where you can also shut down the app - very odd place to put preferences I would say). Click on Settings, then folders. Set the 'EFB Route' to your mapped path and life should be good

  10. Stand down - issue solved. 

    Server was running an older AIRAC version from the original install (1802).

     

    I was confused by checking in the client, there's a tab for Airac Dates (Util button), which it says the latest one (1807) ends in a few days. I took that to mean that's the version that was installed. Then I realized the tiny text at the bottom of the client, which was hiding off screen, so I didn't know it was there. 

     

    Nice thing is, Navigraph Data Manager recognized EFBv2, and installed 1807. Soon as I launched the server, it found the new update, and launched the DB builder. 

     

    Very cool job guys!!

     

    one quick question - I really liked the feature from V1, that displayed distance to TOD. Is that available in V2? if so, how to do I display?

     

    Thanks.

  11. In the previous version, I was able to export a flightplan from PFPX to a folder on the server computer, then have the EFB client map the remote folder to retrieve the flightplan across the network. 

     

    In V2, the instructions say to save the flightplan to the client computer - I'm having issues doing this. For some reason, I cannot setup network folder permissions to access the EFBv2 folder over the network. I realize that's not your issue, but is there a way to have the client look for flight plans in a user specified folder? I can't find a setting in the client to change the folder target. 

  12. In typical Microsoft fashion, my computer installed an update for Windows 10 build 1607. Since this update has run, the EFB DataProvider will not run. I get an 'Unhandled Exception' error at launch of the Data Provider as follows:

     

    See the end of this message for details on invoking 
    just-in-time (JIT) debugging instead of this dialog box.
     
    ************** Exception Text **************
    System.Net.Sockets.SocketException (0x80004005): Only one usage of each socket address (protocol/network address/port) is normally permitted
       at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
       at System.Net.Sockets.Socket.Bind(EndPoint localEP)
       at System.Net.Sockets.TcpListener.Start(Int32 backlog)
       at er.b(IPEndPoint A_0)
       at h5.a(h6 A_0)
       at fe.e()
       at fe.a(Object A_0, EventArgs A_1)
       at System.Windows.Forms.Timer.OnTick(EventArgs e)
       at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
     
     
    ************** Loaded Assemblies **************
    mscorlib
        Assembly Version: 4.0.0.0
        Win32 Version: 4.6.1586.0 built by: NETFXREL2
        CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
    ----------------------------------------
    AivlaSoft.Efb.DataProvider
        Assembly Version: 1.6.8.33244
        Win32 Version: 1.6.8.0
        CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/AivlaSoft.Efb.DataProvider.exe
    ----------------------------------------
    System.Windows.Forms
        Assembly Version: 4.0.0.0
        Win32 Version: 4.6.1586.0 built by: NETFXREL2
        CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    ----------------------------------------
    System
        Assembly Version: 4.0.0.0
        Win32 Version: 4.6.1586.0 built by: NETFXREL2
        CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Drawing
        Assembly Version: 4.0.0.0
        Win32 Version: 4.6.1586.0 built by: NETFXREL2
        CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    ----------------------------------------
    Castle.Windsor
        Assembly Version: 3.3.0.0
        Win32 Version: 3.3.0.2412
        CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/Castle.Windsor.DLL
    ----------------------------------------
    AivlaSoft.Efb.Common
        Assembly Version: 1.6.7.33244
        Win32 Version: 1.6.7.0
        CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/AivlaSoft.Efb.Common.DLL
    ----------------------------------------
    DevExpress.Utils.v15.1
        Assembly Version: 15.1.5.0
        Win32 Version: 15.1.5.0
        CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/DevExpress.Utils.v15.1.DLL
    ----------------------------------------
    Castle.Core
        Assembly Version: 3.3.0.0
        Win32 Version: 3.3.3.2300
        CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/Castle.Core.DLL
    ----------------------------------------
    Desaware.MachineLicense40
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.5.2
        CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/Desaware.MachineLicense40.DLL
    ----------------------------------------
    System.Core
        Assembly Version: 4.0.0.0
        Win32 Version: 4.6.1586.0 built by: NETFXREL2
        CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
    ----------------------------------------
    System.Configuration
        Assembly Version: 4.0.0.0
        Win32 Version: 4.6.1586.0 built by: NETFXREL2
        CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    ----------------------------------------
    System.Xml
        Assembly Version: 4.0.0.0
        Win32 Version: 4.6.1586.0 built by: NETFXREL2
        CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    ----------------------------------------
    DevExpress.Data.v15.1
        Assembly Version: 15.1.5.0
        Win32 Version: 15.1.5.0
        CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/DevExpress.Data.v15.1.DLL
    ----------------------------------------
    DevExpress.XtraEditors.v15.1
        Assembly Version: 15.1.5.0
        Win32 Version: 15.1.5.0
        CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/DevExpress.XtraEditors.v15.1.DLL
    ----------------------------------------
    System.Data
        Assembly Version: 4.0.0.0
        Win32 Version: 4.6.1586.0 built by: NETFXREL2
        CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
    ----------------------------------------
    DevExpress.XtraGrid.v15.1
        Assembly Version: 15.1.5.0
        Win32 Version: 15.1.5.0
        CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/DevExpress.XtraGrid.v15.1.DLL
    ----------------------------------------
    System.ComponentModel.DataAnnotations
        Assembly Version: 4.0.0.0
        Win32 Version: 4.6.1586.0
        CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.ComponentModel.DataAnnotations/v4.0_4.0.0.0__31bf3856ad364e35/System.ComponentModel.DataAnnotations.dll
    ----------------------------------------
    DevExpress.XtraBars.v15.1
        Assembly Version: 15.1.5.0
        Win32 Version: 15.1.5.0
        CodeBase: file:///C:/Program%20Files%20(x86)/AivlaSoft/EFB/DevExpress.XtraBars.v15.1.DLL
    ----------------------------------------
    UIAutomationClient
        Assembly Version: 4.0.0.0
        Win32 Version: 4.6.1586.0 built by: NETFXREL2
        CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/UIAutomationClient/v4.0_4.0.0.0__31bf3856ad364e35/UIAutomationClient.dll
    ----------------------------------------
     
    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.
     
    For example:
     
    <configuration>
        <system.windows.forms jitDebugging="true" />
    </configuration>
     
    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.
     
    Please help !
  13. I'm using the trial version of EFB and on the first run of the program, I'm getting an error from the display unit that says it cannot activate my route because /Documents/AivlaSoft/EFB/UserData/Runways.txt is missing. I followed the install instructions and not sure what went wrong here.

     

    Any help would be appreciated. Thanks.

×
×
  • Create New...