RayProudfoot

EFB works fine with v5.2. 👍

@MikeOdy, I've been running EFB v1 and v2 for years on a network. It runs perfectly. The only thing you need to be aware of is the recommended minimum resolution for the Client software. I don't recall it but a 1920*1080 screen should be okay. The higher resolution and bigger the screen the better it looks.

Hi gents. I'm resurrecting this topic as I've spent some time integrating Rwy 12/30 into the existing AFCAD that has Rwy 17/35. I've cleaned up a few faults and my AFCAD is attached. It's been created for P3Dv5 but may also work with v4. Locate ORBX\FTX_AU\FTXAA_YSCB\Scenery, rename ORBX_YSCB_APX_1.BGL and ORBX_ZSCB_APX.BGL and drop the attached BGL into the same folder. As well as introducing Rwy 12/30 it also solves the problem of the EFB map changing to a different airport name when taxiing to Rwy 35. I haven't replicated all the GA parking spots mainly because even using AIG Ai there simply isn't the traffic to justify the extra work. Oskar, it looks okay to me but as always I'm happy for you to check things out. YSCB_ADEP5_RAY.bgl

Indeed.

That went straight over my head. 🤣 I’ll test tomorrow with a suitable setting. I’m sure the label in the flight plan window said nm, not minutes. I’ll check tomorrow.

Oskar, 10 minute distance??? I thought it was a nautical mile distance. That might explain the problem. If you look at my request at the top I asked for a sound xx miles before ToD, not xx minutes.

I'm sorry Oskar but it's definitely not playing the wav at 10 before ToD. I manually adjusted the distance and tried it several times but no joy. Strangely it did play on passing one waypoint but that was well before ToD and didn't play at the next waypoint. I run the Client on a separate PC. Might that be an issue? Other sounds play okay though.

Thanks Oskar. Yes, default sound is doorbell - less of a heart attack than others - and Vertical Profile selected. I'll try again and report back.

Hi Urs, Thanks for adding my request to the latest release. I'm not hearing the sound played when 10nm from ToD. I have "Allow sounds to be played" checked and in the lower-right of the flight plan window I assume Play Sound ticked with 10 entered is the distance before ToD. But no doorbell wav is audible. Have I missed something?

Thank you Urs, much appreciated. 👍

Hi Urs, any chance you could add a new sound event? x miles before ToD? An audible alarm say 10nm before ToD would be helpful, thanks. x would either be configurable or a set distance. Up to you if you feel like doing it.

Hi Urs, Thanks for explaining why this flight time calculation cannot be changed without massive amounts of work. I'll have to defer lunch when flying Concorde since it's not really possible to leave it unattended for such a period. Thanks for tweaking the ISA Dev display. 👍

Hi Urs, I hope you had a happy and safe Christmas and my best for 2021. I flew Concorde yesterday and paused the flight whilst I had lunch. Looking at the log after landing the flight time included the 25 min break I took. According to your post it should have been fixed. On a slightly different topic I notice the ISA deviation isn't shown against OAT on the info column to the right when the deviation is between -4 and +4. Whilst that may not matter for sub-sonic aircraft the air temperature makes a big difference to the efficiency of Concorde's engines. Could you show the deviation irrespective of its value please?

Hi Ron, I filed a plan from KBDL to KBOS. Cruise at 13,000ft. STAR was ROBUC3 into 27. A few miles from ORW I changed it to JFUND2 for the same runway. When I updated it in EFB I had changed to HDG mode. I could see the plan updated over to the right. A couple of miles later and still before ORW (which was the active waypoint) I reverted to ROBUC3. The active waypoint was changed to ROBUC but I hadn't passed ORW. Still in HDG mode. So I carried on to ORW and just before reaching it switched back to NAV mode. The aircraft turned left towards ROBUC. Things seem okay. I think I will use your technique of switching to NAV mode before any changes to the plan. It allows me to keep control. Strange how I've had the problem of sections of my arrival being removed. I'll keep an eye on it but for now I have a procedure that works. Many thanks.

That’s very good of you Ron, thanks. That’s my job for tomorrow.

Thanks Ron. I’ve settled down for the evening but I can try one of your plans tomorrow morning. Can you provide the waypoints prior to the STAR please? And you switched to HDG mode, made the change and then back to NAV mode?

Hi Ron. It works with simple plans but falls apart when a arrival procedure is chosen and executed in EFB. The active waypoint in the DA62 changes to the final waypoint before the destination airport. The previously active one and all subsequent ones just disappear from the plan. I need to try this in HDG mode and see what happens. Strange because all EFB is doing is updating the P3D flight plan. But something about it is not liked by the DA62 G1000.

Hi Ron, I tried a short flight from GCLA to GCTS. Here's the routing. More or less a straight line until the TFS VOR. ARACO DCT GANTA DCT BAMEL DCT TFS With the autopilot in NAV mode and inbound to GANTA I selected Direct To BAMEL in EFB and it worked perfectly. Did the same in HDG mode and switching back to NAV mode it was also fine. I need to load a more complex plan with a change of STAR and see what happens then. But for now, I have your suggested settings which are working, thanks.

@rwilson881, thanks for reporting back Ron. I wonder if a different sim is the reason you haven’t had the problem. It seems unlikely as the code in the Vertx DA62 should be the same for all sims. It’s with all plans when I’m required to make a change to the plan usually because of a different STAR. I’m still learning the techniques with the DA62 so maybe as I get more familiar I’ll feel more in control. I’ll try your method and see how I get on.

The developers had already provided an update. It’s available on SimMarket with the base product. Great service! 👍

@rwilson881, thanks, much appreciated.

Thanks for that Oskar. Probably best the user doesn’t get swamped with warnings. I’ll write to the developer and ask for new runway markings. I’ll also use PFPX as my reference as it’s updated by each AIRAC cycle.

Hi Oskar, Fair enough but on checking PFPX (fed from my Navigraph sub) it shows 04/22 so that's good enough for me. Still confused why EFB didn't flag a conflict with the AFCAD it's using for LDZA which clearly shows 05/23.

Hi Oskar, Do you have a link to that site so I have a suitable reference? So maybe it’s a very recent change as all the other software has 05/23.

Just an update to this. I had a bare-bones scenery install when I said P3D was showing 04/22. The scenery itself is 05/23 confirmed by the actual runway markings and confirmed as 05/23 when I run P3D with all scenery enabled. So it's just EFB showing it as 04/22. Odd because when this sort of mismatch happens EFB usually doesn't show the SID/STAR data but it still does.