jasonboche

Where do we assign a key for SODE?

stephenbgs I just realized maybe you and I are seeing the same behavior. SODE works for me but I have to navigate the menus to actually select the gate I'm sitting at. For instance, when I launch SODE, I see 2 menu options. The first option I believe is to select the stand I'm at. The second option says "No triggerable objects found within 6.5nm/12km..." I believe maybe what you're saying is that SODE isn't automatically detecting the gate you're at. If that's the case, I have the same thing. I have to choose the gate first, then I can operate it. It's kind of a pain to scroll thru the list to find the right gate.

Thank you for the reply Dave - that was helpful. I did some looking around when I got home from work and noticed that in the P3D sound settings (I'm still very new to P3D), it was mapped to the Default device. I remember from my long FSX tenure I had to force this from the Default device to the Speakers (Realtek yadda yadda). All good now :) Thanks again.

I have a new installation of the PMDG 777-200 on P3D v4 (no Hotfix 1 yet). I fly on VATSIM so in the FMC I have the PMDG aircraft audio going to my desktop speakers, and only vPilot audio goes to my headset. The first few flights were wonderful using the Delta livery. This morning I started a flight using the Aeroflot livery and upon taxi and takeoff, I couldn't hear the engines spooling up but I heard plenty of other aircraft noise coming from my external speakers (things rattling, tires thumping over the gaps in the concrete, etc.) I put on my headset and sure enough the engine noise was being split to the headset. I verified in the FMC that the sound output was supposed to be my external desktop speakers. At this point I'm wondering if the Aeroflot livery is causing this or maybe I just need to reboot my computer. Afterall it is Windows. I haven't gone back to check if the Delta livery is still working properly. Thank you, Jas

OOC Did you install P3D v4 Hotfix 1?

I ran into the issue where TAB +S (default for SODE) stopped working when I'm in the PMDG 777 but it's still easily accessible from the pulldown menu. I think when the OP is saying is that he can access the menu but SODE is acting as if there are no aircraft doors near the jetway such that the jetway isn't going to activate.

This is among the best and most helpful posts I've ever read. Thank you rsrandazzo.

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

Excellent! I will look for it on AVSIM!

It was an excellent event - thank you for organizing FedEx. ACARS assigned 100% load. Got out of Memphis on time. Great controlling in Memphis and Dubai. FSX didn't crash. No holds for me. Landed with a lot of fuel as a result. DAL641 KMEM-OMDB - my album

There are 4 approach plates for DESDI. 2 for each rwy direction. You can follow the links from Vatsim.net to the Inited Arab Emitates Vatsim site to grab the plates.