Jump to content

Captain45

Members
  • Content Count

    27
  • Joined

  • Last visited

About Captain45

  • Birthday 12/08/1945

Profile Information

  • Gender
    Male
  • Location
    Hoofddorp, Netherlands
  1. Although I am more than happy with v2, there are a few things that can be improved imho. It could be my PC, but (almost) every time I click away (top right corner) the FPL popup, the whole application is minimized. No problem to click the icon in the task bar to get things back, but 'being convenient' is something else. It happens to me more than once during a flight that I want to check the DEP and/or ARR pages. That also activates the PROC popup. Many times I don't need that. I just want to check the SID or the STAR data. (my EFB runs on a networked second PC, together with Active Sky). It would be a great improvement (for me, that is and probably many others) when the PROC popup is NOT activated automaticly, but selectable. Thanks in advance. Dirk
  2. In v.1 it was not possible to delete a WPT within a STAR. So I was very happy that in v.2 I could delete such a WPT. But... when I look at the chart both lines to and from the deleted WPT are still there. So, on paper, you fly a crazy zig-zag to that WPT. (Take f.i. the VOR near KJFK that is in many STARs). In real life you will get vectors. Why on earth that VOR is the end of the STAR surprises me, but it's a fact. In the sim I would like to make my own decisions AND, when I delete a WPT, see the outcome in the chart as well. Minor issue, but nice if corrected. Cheers, Dirk
  3. Hi Oskar, I replaced the EHAM minima and the 787-8 and 787-9 profiles with the ones from contributions. I checked the logfile and all works fine now. During the flight I had serveral red notifications on the Client's status window. Seven or eight times in a flight that took over 3 hours. The Client reconnected automatically. Only when during the rebuild a WPT was passed I needed to do a DIR TO. I haven't got the slightest idea what caused it. Maybe the PC was preparing for the W10 October update that followed later. Dirk
  4. At first a 5 star compliment for v.2. It brings far more than expected and worth while waiting. Although v.2 works flawless, my yesterdays flight KIAD to EHAM with the QW787 (skipping the ocean NAT) had several server disconnects. Just for the record, I post the logfile attached. I checked if Windows Update was involved during the flight but that was not the case. Regards, Dirk clientLogfile-1.txt
  5. Hi Urs, Thanks for the reply. It is starting to become clear now. I've found more info on this link that might be usefull for others with the same question. Greetings Dirk
  6. Although I like the improvements in v.2 versus v.1, there is something that puzzles me cocerning the decision height/altItude. The manual has several pages about 'minimums' but in v.1 I was used to simply read them from the approach chart. It could be usually 50, 200 or 500 for DH. Easy. If v.1 could determine what the value must be for a specific approach based on the AIRAC Data, it must be possible for v.2 as well. If someone can shine a simple light on 'how to determine' this value I would be very gratefull. Oh. and I know I can simple add the field elevation to the DH to get the DA. Thanks in advamce. Dirk
  7. As a long term user of v1 I thought I give v2 a try for the Demo first. Installation of the server went well except of the weatherfile because AS is on the other computer and I had not yet made a share. But I installed the Client on the other PC OK and with the Server already running on PC1, the client came alive on PC2 with world weather. (No P3Dv4 active yet) To access the weatherfile from PC1 I ran into some firewall issues so I had to restart both PC's. But.... when I start the server I get the popup telling me to open port 13 which was not needed the first time. So I opened port 13 for outgoing TCP traffic and tried again. Same outcome: a popup that tells me to open port 13 (which is open already) I'm stuck and the days left are lower and lower. Would be nice to have a look at v2. Dirk
  8. For those users that run into the same problem: There was indeed a problem in the bgl file. Hervé Sors has corrected it and the problem will disappear as from the 1803 update. For those who can't wait I'll attach the correct bgl file in the 'Use alternate airport files' status. Copy it in the appropriate directory and let the DataProvider run an update. Cheers, Dirk APX50100.BGL
  9. Thanks Urs, I suspected something like this. I'll inform Hervé Sors about this. Thanks for sorting it out. Cheers, Dirk
  10. OK. I checked it out. Under Aiport Information after the double click it comes with: D:\P3Dv4\Scenery\0601\scenery\APX50100.bgl This is exactly the same file that Sors's ILS Inspector uses. On the Landing Aids Tab it shows the wrong info that I posted about before. I'll attach the file. This is really a weird thing. Dirk APX50100.bgl
  11. Sorry. A typical RTFM issue on my side. I'll get back to you after dinner.
  12. Hi Urs, Well..., I checked the manual and in there is tells me what file is used. But when I check my DisplayUnit's Airport Information it is blank on that spot. I checked it with another airport and that gives the same story: nothing! Could this have sometimg to do with the fact that my DisplayUnit is on a networked PC? Dirk
  13. Yes I did. Several times after each Navigraph and Sors's updates. My guess is, that the DataProvider somehow reads the old file with the P3D default NavData. For restoring purposes Sors's programs rename the APX50100.bgl that contains the default stuff into APX50100.bgl.p3dini with a new active file APX50100.bgl (as I can see on the file date/time stamp). But that happens with a great number of files in the ..\Scenery directories. Maybe it is just an index thing. But since I have no clue on how the DataProvider gathers data I'm just guessing. I'll put the question also on Hervé Sors's forum.See what comes up. Dirk
  14. When I load Stock airport (P3Dv4) ENTO in the Display Unit 1.16.15942 for an Approach RWY18 it shows: Loc. SFJ 110,95 358 (RWY 178) and that is the frequency and course (BC) of ILS/DME 36. And...., when I check an Approach RWY36 there is no ILS approach, just a VOR/DME and a RNAV. I used the ILS/Runway Inspector (Hervé Sors) and found in the default APX50100.bgl: ILS/DME 36 SFJ 110.95 ILS/DME 18 TRP 108.30 The same info is stored exactly the same in the AIRAC Data files I wonder how AivlaSoft EFB can come up with the wrong info. It looks as if AivlaSoftEFB is using very old default data. Ignoring what's in AIRAC and what has been updated to Navigraph 1802 (by Hervé Sors' World NavAids package. Dirk
×
×
  • Create New...