Loadhaul

Alright, thanks.

Just completed a flight with some strange behavior, I believe it was unrelated to the IRS as it decided to fix it self later in the flight. I was able to replicate this issue twice on two different occasions, both were however with the -700. I departed PHNL 08R without a SID as it was an assigned heading departure and SIDS were not being used, In the CDU it looked 08R DCT to my first waypoint. PHNL DCT DATBE DCT RAGDE DCT WOSLU DCT XI PLCH After being vectored out of PHNL I needed to fly direct to my first waypoint which was fine until the aircraft started weaving around and drifted left of the magenta line in which required me to use HDG intervention. The plane got worse and worse and started to oscillate; after flying the active waypoint it was then fine. I thought this was reported a while back that if you flew DCT to a waypoint after departure sometimes the aircraft would drift off track; thence if you flew a SID it was perfectly fine. I fly mostly in Australia; our departure routings are very frequently routed by assigned heading, e.g. YBCS, YPPH, and YBTL just to name a few. This has never happened before during the countless times I have done this... I got the POS REF page up on the FMS just for a reference in the screenshot. As I mentioned earlier the plane was perfect after reaching the first waypoint. https://imgur.com/a/HGyqLAG

Thanks for the in depth reply. Just sorted it out the original issue by setting the GPS position in POS page 2 before the IRS's completed their alignment process and they all matched up! After a flight for almost 4 hours there were some differences as expected, but were sorted out by doing a fast re-alignment when stationary. IRS's > NAV > ALIGN > NAV

Hi During alignment of the IRS the GPS on the ground from the default PMDG cold and dark panel state there seems to be changing values of the GPS data whilst the plane is not moving, additionally once the IRS's have aligned there is a disagree between IRS L and IRS R. FCOM VOL 2 (11.20.5) illustrates the procedure of this process. Once sufficient DC power is supplied I switch both IRS gyros from off to nav. I verify that white align indication is displayed and not flashing. I then monitor the time taken for them to align which is on the realistic setting, as stated in VOL 2 (11.20.5) I enter the reference airport in the FMC and go to POS REF page 2. On page 2 both GPS indications are displayed; in my case they disagree, but even more odd to me they change, though the aircraft is not moving during the IRS alignment process. Once I select GPS L for example and insert it into the prompts on the previous page, GPS L on page 2 changes coordinates from the ones I entered. Not to mention GPS L disagrees with GPS R, this is before the IRS has completed alignment. After the IRS alignment is complete IRS L and IRS R disagree on the IRS display selector knob and on POS page 2. From my understanding these positions will update ONLY when the aircraft is in motion and not stationary. During flight I have large navigation inaccuracies related to what ever I'm doing wrong here. I tested using a pre-aligned panel state and noticed there is no disagree/deviation between either IRS. I'm certainly no new user of the 737, been flying this aircraft for about 2 years now and have obviously done this correctly then, but I must be missing something here since I haven't flown it for a while, or i'm just noticing something that is normal... Here's an example of how these coordinates change over approximately a 30 second interval, keep note the aircraft is not moving. GPS L - S27 23.5 E153 07.3 GPS R - S27 23.6 E153 07.4 After about 30 seconds - 1 min GPS L - S27 23.6 E153 07.4 GPS R - S27 23.7 E153 07.4 GPS L - S27 23.6 E153 07.3 GPS R - S27 23.6 E153 07.4 Is it normal to see these coordinates change and disagree whilst the aircraft is not moving? I understand there might be some disagree under some circumstances but during flight the IRS disagree is enough to cause navigation errors. Thanks, Mitchell.

Well I'm coming to clues that it wasn't the T777's fault as by looking at old flights done on the same route as you described the format isn't like that, instead those waypoints used a (NXXWXXX) format.

Hi. Regularly I fly pacific routes in the 777, this is certainly not the first time on this route either. I did a reinstall of the 777 last week by uninstalling just the prompts from my PC, then installing it again later. (Not sure if this is the correct way to do it). I then updated my Navdata to 1809 and all that stuff... Keep in mind all parts in the flight plane are entered manually by myself. KLAX > 24L > SUMMR1 > FICKY as the departure, then I enter an airway. I understand that lat/long way points must utilize the legs page and not RTE. However when I enter my first one in, N2655W13021 I receive an 'invalid entry' error. This is for the entire set of waypoints on this flight, so essentially I had to cancel it. Is there anything i'm doing incorrectly here that is obvious? I also wanted to know if it is suggested to delete files related to the PMDG 777 in the sim and what not as well as uninstalling it for a cleaner install which could've caused a mess up here, and yes the product has been updated. I intend on trying to install it again and see if it resolves itself there; however I doubt it will. If anyone could try there 777 with the route, by manually entering these waypoints please let me know what the result was. Flight Plane (Simbrief depicts the waypoints differently to PMDG, i.e, 2655N13021W is N2655W13021 with the PMDG 777.): KLAX/YBBN SUMMR1 FICKY B581 WEDES DCT 2655N13021W 2432N13350W 1838N13946W 1603N14252W 1114N14913W 0911N15238W 0518N15937W 0329N16312W 0012S17019W 0412S17711W 0500S17826W 0620S17930E 0816S17600E 1148S16846E 1416S16539E 1713S16250E 2107S15934E DCT HARVS Q21 SAVER DCT AMITY DCT Regards, Mitchell G.

That's strange, my navigraph is up to date and It publishes 113.60.

Hi, sorry. Perhaps it doesn't use a DME, however I expect that as it's a VOR arrival, anyway. I'm not sure what you mean by the plane still in go around. I bounced back up off the runway and pushed TO/GA, I flew LNAV, then held at 4000FT. After that I went and popped in the same arrival and arm the hold exit. I then reset the MCP altitude and engage VNAV, it doesn't give me an altitude deviation, so I'm assuming it's not engaged properly. I appreciate your help, are you able to link me where I can get information on the mode the aircraft was in, as you said it may be in go around mode. Thanks.

Hello. I just did a flight in the 737-700 from NFFN to AGGH, the descent went fine with VNAV on and followed the profile perfectly as assumed. I flew the over head VOR arrival into AGGH 06, it went fine with vnav following everything. However I needed 6.0 DME to reference a turn, I tuned both nav selectors to 113.60 which was the frequency I needed. I switched to see the VOR 1 + 2 on the the displays, they didn't show a distance. I encountered extremely bad turbulence on the approach and performed a missed approach, I entered the published hold at 4000FT. I armed hold exit and flew the approach again, the fms had calculated all the altitudes and speeds for me, so I engage vnav to follow them, however when I reach a waypoint vnav stays at 4000FT, yes I selected 2300FT for it to descend. I went around again and soon after flew more of a visual approach. Thanks, Mitch.

Hello. Recently I've been having a menu bar come up at the top of my screen. It depicts as a bluish color and runs across the whole entire top screen, it's not the P3D menu bar. Does anyone know how I can stop it from popping up, it's quite annoying, I can't interact with it either.

The issue seems to of not been present when I did a test flight from YSSY to YMML, going into darkness. Does the PMDG 777 track the local time of the nearest airport?

What's really strange is when I test it by loading in somewhere and speeding up the time it works perfectly. The lights turn on at night and switch off in the daylight like they should. However when I do a real flight they don't turn on or off.

Unable to upload images. It's essentially all the lights do not turn on like they should, when you turn the master bright switch up it stays very dim (the middle button is pressed in). If you switch the dome light on and then off, they all switch on like they should. However when it becomes daylight again the lights stay on and don't dim properly which looks awful.

These are my settings, I didn't change any thing here so no luck. I have cast and receive on for interior and external vehicle. The quality is medium and draw distance is ultra.

I'm using stock P3D with no shaders or tweaks apart from its own settings, I'll have a look.