jasonboche

Sorry for a reply to an older thread but I had this same issue and there is a fix for the engine start bug. You need the file B767at.gau from Level-D. Look at the following forum thread: http://www.leveldsim.com/forums/test-acceleration-engine-start-fix_topic23089.html?KW=B767at%2Egau

I'd say this one has been answered if the mods want to mark it as such.

Thank you for the pointers. With the help of the forum, I think I've got it sorted. Problem occurred 100% of the time for me with 3 777-300 flights, with or without using FSInn, FS Real Time, etc. When I upgraded to SP1 and installed the 777-300, I used the OC to remove all 777 and NGX liveries, cleaned house basically. However what remained was a customized saved panel state which loads by default for the 777 each time I started which I documented for re-installs: PMDG 777-200LR jason startup profile Start at default config, then... SOUNDS: Play in exit view yes, Device Speakers Resettable siren yes Fuel Short range 18.7% 59,993 lbs. Center fuel pumps off Payload 67.9% Beacon lights on Logo Lights on APU on Stdby/TCAS off A/T off Parking brake on COM1 122.8, ensure L VHF MIC on Ground connections wheel chocks 2 plugs pwr plugs connected air cond. connected So when I launched FSX tonight, I went straight to my default home airport, loaded the 777-300. No other plug-ins that I normally run. Programmed a quick flight plan so that I could bring up PROGress. The problem was immediately evident where basically progress time stamps in Zulu were about 4 hours behind what it should have been. Without relaunching FSX, I then used the FMC to load the default 777 startup config which ships with the 777. Then programmed a quick flight plan so that I could bring up PROGress. The problem was immediately gone and the SID waypoints were correct based on the current known time on the chronometer. I went so far as to load FS Real Time and modify the Zulu offset by -12 hours. Both the chronometer and the PROGress times snapped instantly to their correct times. Long story short, it was a modified default saved panel state that was loading with the aircraft as PMDG pointed at. Thank you everyone. This was the only issue I've seen thus far. Quality aircraft as per usual from PMDG. Jas Afer the above fix, when I perform your steps, nothing happens which I presume is correct now. POS INIT 4L currently shows the correct UTC time.

Not yet but after this event flight in to Boston I'm definitely going to start some trial and error with FSRealTime. I don't think the issue is FSInn (hasn't caused an issue in years) but one never knows.

For the benefit of those having the issue, disclosure on some of the software in use: FSX w/ SP2 FS Real Time (time sync utility for sim) FSInn client for VATSIM

I think you're right, my bad. Was trying to connect the two for coverage purposes. Perhaps a mod can delete my initial reply.

It is occurring again after a reboot. Has not occurred with the 777-200 (pre SP1) or the NGX. http://boche.net/dropbox/2014-07-19_14-13-49.jpg HW details: Processor 3rd gen Intel Core i7 3770k (Ivy Bridge) Processor Cores4 Processor Speed3.5GHz OC to 4.2GHz RAM16GB Video Board ManufacturerMSI Video Board ModelGeForce GTX 660 Ti Video Memory2GB 192-bit GDDR5 Mother BoardASUS Hard DrivesDual SSDs and 4TB SATA MonitorDell 24" LCD Operating SystemWindows 7 64-bit YokeSaitek ProFlight You're right and I did apologize earlier for being terse & I've sent a PM to 777. This is the PMDG support forum and I hope somebody is getting paid around here. I know what GMT/zulu and offsets are but I fail to understand what that has to do with this issue. The chronometer and ETA should both be on the same page (Zulu). Unless you're highlighting a known bug with ASUS motherboards. Again, haven't seen it using PMDG products for 3 years.

I've simplified the image because you either don't understand or you don't listen and you're derailing this thread. Please accept my apologies as I know you're trying to help.

Cross post http://forum.avsim.net/topic/446896-eta-time-in-progress-page/

No. FMC ETA progress and Chonometer in the aircraft don't jive with each other. Both should both be Zulu. Forget about what time it is on my PC or where I'm at geographically. Current Zulu time flying over the state of Washington is 1618z and the FMC says I should arrive in Minneapolis 966 miles away at 1438z.

Currently occurring in the 777-300 (777-200 and SP1 also installed)

Yep. Came here looking for a resolution to the same issue. Hope I didn't miss anything embarrassing but I've been flying NGX and 777 for close to 3 years. Screenshot: http://boche.net/dropbox/2014-07-19_11-21-23.jpg

VPA481, Popcorn Manager, do you need an apprentice?

I've had the NGX for a few years. Wonderful bird. One thing that puzzles me though is an event which happened tonight and has also happened a just a few times in the past. Starting the engines on pushback, #2 fires, #1 looks like it's spooling up but it never finishes. N1 stays at 19.9. N2 58.3. FF .65. Oil Temp -1, VIB 0.0. I can advance the throttle to 53.3 N1 and the right side #2 engine spools up but the left stays static at all of these numbers and is dysfunctional. Screenshot here with throttle at 53.3 N1 - you can see the left side basically not responding: http://boche.net/dropbox/2014-2-20_21-51-23-102.jpg Resetting the aircraft to DEFAULT via the FMC doesn't fix the problem, the #1 engine still fails. The only way to correct is to exit FSX and reload then everything is fine. Is this a bug or a real type of engine failure? Aircraft failures should be disabled but it's possible I missed a setting somewhere. I was trying to get out of Minneapolis tonight on VATSIM and I tried to relight #1 multiple times using both cross bleed and APU methods with no success. I also shut down #2 and tried to start #1 first via APU. No success. Dead engine. Anyway, it doesn't happen a lot, I was just curious what the problem could be since my expectation was failures are disabled. Thank you, Jas

PMDG Technical Writer has to be the most depressing job of them all