fsgeek

Hi everyone, I could post this in the TrackIR forums, but I figured I'd come here first since Chaseplane has native TrackIR support. My question is rather basic: Are their any "recommended" or popular TrackIR profiles which work well in P3D? I'm at the first stages of setting up my profile and I'm slightly overwhelmed by all the options. In the meantime I'll keep tweaking until I have something I like. Cheers, Louis

rvm33, Thank you very much for this detailed and thoughtful advice. I have since fixed all of my EZDOK issues, but I will make a note of your suggestions and implement them, should I encounter problems in the future :smile: Terence, I wrote a post on the EZDOK forum which collates everything I found regarding the middle mouse button issue, which I deemed to be perinent from my limited experience. You can view that post here. Hi Robert, Thank you very much for replying to my post, despite the fact that it's (sort of) not PMDG-related! I had already looked at this post, but I only scanned it. I'm pleased that the technical issues have been aknowledged and I look forward to the update. Hopefully my current set-up continues to behave. Thank so so much for a wonderful simulation! Best regards, Louis

Hi Terrance, The issues you describe sound somewhat familiar to mine, although they could be symptomatic of something else. If it helps you to troubleshoot, I have been able to resolve my problem. The first clue was that the "EZCA 2 Config Tool.exe" shortcut which is automatically placed on the desktop no longer pointed anywhere, so at some point the file had been removed. I guessed that Windows Defender might have quarantined it, because when I first installed EZDOK I was warned by Defender that it's a virus. I added a temporary exception to all .exe files and any directory with the name "EZCA" or "EZDOK", then disabled real-time protection (perhaps dangerous, but I wanted to hit the problem with a hammer to be sure it's the firewall). Fresh install of EZDOK and QOTS II and everything works absolutely fine (minus the usual FSX nags). I ran a search in APPDATA to make sure that absolutely every file related to EZDOK was gone. I am still left with a trail of smaller problems, but they're not blockers: FSX sporadically rebuilds the config, resetting my resolution and display settings, and removing everything under [TRUSTED] so that I have to accept all the Windows UAC warnings again The middle mouse button-to-pan feature will occasionally stop working. I have to restart EZDOK and FSX to resolve this I'm sure that I won't want to go back to the default FSX camera system, but so far I'm feeling the pain of change. Just the fact that I have to window FSX to acess the config utility is annoying because, at least for me, FSX behaves very badly when switching between windowed and full screen, or when minimising and maximising. I hope this helps! Louis

Dear all, I recently purchased EZDOK to complement the fantastic QOTS II. However, things have quickly turned sour. Because FSX issues can often be a mashup of misconfigurations between multiple software, I feel that this post could belong in either a PMDG or an EZDOK forum- I'm just completely puzzled. To make things worse, FSX doesn't let me take screenshots so I'll have to describe in words what's happening. First I installed QOTS II and it worked fantastically. The next day, I installed EZDOK 2.0, as a first time user with no previous EZDOK installations. The two were like a match made in heaven. However, after a few sessions of FSX, everything suddenly stopped working. When beginning a flight with QOTS II: The view freezes Textures don't load properly (looks like a cracked copy) The framerate drops to less than 1FPS I get a very bizzarre clicking sound (like someone is flipping all the switches in the flight deck simultaneously). These sounds come out of my monitor speakers, which shouldn't even be active I can see the initialization bar at the top of the screen, but it's lagging so badly that you can see the bar being drawn line-by-line I can't access the EZDOK config tool Basically, the sim is trashed. Why am I posting this to the PMDG forum? I decided to start a flight in another PMDG aircraft (NGX) and everything worked perfectly! I then uninstalled EZDOK and QOTS II, then reinstalled QOTS II (no EZDOK this time). The result: The 747 still does not work, but all other PMDG products still work fine. I am an EZDOK n00b but I've been using PMDG products since the original 737 NG, and I've never experienced anything this bad. I apologize if this post feels misplaced. I might repost this in an EZDOK forum later. However, I would like to know what people's experience has been regarding EZDOK 2.0 and QOTS II? I feel quite alone with this problem so I'm hoping there's a solution which doesn't involve reinstalling absolutely everything, though this may have to be the case! Thanks! Louis

Hi guys, Are any of you using AES with 747 v3, and if so, do you have a good .cfg that you could share? Cheers! Louis

Hi everyone, Today I bought the Thrustmaster Warthog and so far I'm really loving it! The only thing that's bothering me is that the throttles in the NGX are very jittery when I bring the throttle very close to the idle position (I'm not using the cut-off detent). I added a dead zone at the idle point through the TARGET software but this doesn't help. I disabled the left throttle entirely and kept both throttles locked together and the problem still persists. Even at higher thrust settings this problem can occur. I've noticed that the throttle has a small amount of "give" in either direction before it starts to slide properly, so I'm wondering if this could be the cause of the problem. I appreciate that it's very difficult to troubleshoot these sorts of problems from afar, but I'm wondering if other Warthog/NGX owners have had similar issues and if so, what did you do to fix/workaround the problem? Thanks in advance, Louis

Problem solved, thanks Oliver. For those with the same problem, change your mapping from C:\...\FSX to C:\...\FSX\PMDG (or whatever drive you're installed into). No need to go all the way to \PMDG\NAVDATA. Regards,

Hi all, For the first time ever I decided to update my nav database. I downloaded the Navigraph FMS Data Manager and paid for the latest cycle (1401). In the manager (attached) it tells me that all PMDG products are updated to this cycle. However, when I start a flight in the 777-200LRX I still get the "NAV DATA OUT OF DATE" message, with a cycle number of 13somethingsomething. In my FSX folder in the Navdata folder, all the text files are showing the latest 1401 cycle as the current database. The NAVDATA folder in the PMDG folder is indicating the older version. How do I fix this issue, considering that the data manager is telling me that PMDG is already up to date? Thanks very much!

Thanks for all the useful information, Mike. Makes me want servo-driven throttles ;-) Louis

Thanks for the reply, Fabo. In the real T7 can the throttle levers always override the A/T or only in hold modes? I ask because I want my PMDG 777 to be as realistic as possible and there are three options: Never Always Only in hold mode Thanks,

Hi everyone, I noticed recently that I was able to manually override the throttles with my Saitek X52 Pro at any point during the flight, even when VNAV of FLCH are engaged. This really annoys me so I realised that I could change this in the simulation options. My question is the following: In the real T7, can pilots manually override the A/T by pushing the throttle levers while VNAV or FLCH are engaged, or is this just an in-sim option? Regards, Louis Vallance

Someone with more knowledge than me can confirm or deny this, but I believe that below 2,500ft the systems check to see if you're in landing config. Since gear up and flap 15 below 2,500ft isn't a landing config the system has to assume you're in a CFIT (controlled flight into terrain) and set off the terrain warning.

When starting from C&D you need to manually switch on your COM radio by selecting on COM1 or COM2 on the centre pedestal. Good luck!

Thanks Kyle, that clears it! Yep, both VNAV and LNAV were armed prior to CMD B being engaged.

Hi everyone, Something interesting happened to me when flying a Thomson 737-800 to Skiathos. The outside air temperature before take-off was 30C which didn't make me think twice. A couple of seconds after pressing TO/GA I got a master caution. I couldn't see the message from my side so I assumed it was the door lock glitch. However, the light remained on. It was an "Air cond" caution and the bleed trip off light was illuminated on the overhead panel, along with a cabin zone temp warning for the aft cabin. The temperature for the aft cabin was at 31C even though the temperature control was set to auto. I decided to set CMD B so that I could take a closer look without having to worry about crashing the plane, only the A/P immediately tripped onto CWS P mode and VNAV also tripped with LNAV remaining on. The aircraft continued to accelerate towards 300 KIAS even though the A/T was engaged and 154 KIAS was set on the IAS/Mach window of the MCP. My question is: What caused the air con caution? Also, could the issue with the A/P be related? I had the FMS properly programmed with SID information entered along with everything else necessary to use the A/P fully. Thanks, Louis Vallance