softreset

Is there any factoring in of the measured winds by the FD? Also what is the expected "capture" time of the FD to the intended LNAV path? Using this example, if the pilot perfectly centers the the crosshairs how would (or rather, should) it take to close the .54 nm deviation?

Yes, that's my "minimums landing" view that's my default in-flight view. I have 8 VC views in total, all at the zoom factor (.59 zoom). I cannot access the BARO or MINS knob in that view. I rarely use the HUD, if I can't visually land from 2500' AGL I'll ride the AP down to minimums. With that view engaged, the expectation is that I switch to that view when I'm fully configured so the only thing is the A/T switch or the IAS dial. I don't use the hidden TOGA clickspot as I have it mapped to my throttle.

I agree with Kyle that it's something with your current zoom. There's no specific setting to tweak, that's the miracle of EZDOK, you can configure it however YOU want. For example, that's what mine looks like:

Heh, I saw this thread title and I immediately thought: Someone is using ProATC/X. Yeah with the recent 1.8.5 update (which has now been replaced by 1.8.7, is when I first started experiencing it too. Walter's recommendations are spot on, both have worked for me. I've found that there's a small window of time after DEL comes back and you have to lock in the transponder code. I've had good luck when I'm recording things to immediately input the transponder code. If I can get it to match what the application expects within 30 seconds of me finishing my scripted read back, I don't get the ping. I've also noticed that the audible warnings are automatically suppressed when I get switched over to TWR. Asssuming I have the correct code entered.

Hi Kevin, thanks for your response. I should have clarified my original post. I was dissatisfied with EZDOK, uninstalled it and then had VC issues. So I did a clean install (off a pre-EZDOK) FSX installation. That's when the default zoom issue started appearing. After continuing to fool around with it, it would appear that my default saved flight (a fully powered off Trike) had a VC zoom of .30 and all other aircraft were pulling that value. By changing it to .68 (what I wanted) and saving it as the default flight and then reloading the sim now the aircraft starts with the .68 zoom value. I suspect, although, unconfirmed that the hard coded .cfg values assume no default flight.

I recently purchased EZDOK and after fiddling with it and trying a couple of presets, I realize that I'm just not ready right now to spend a couple of hours in-game but not actually flying. I've done a clean install of my FSX directory as the built-in restore functionality was still creating weird preset camera issues. The default VC zoom is .30 and I'd like to get to between .65 and .70 Here's what I've done and/or attempted to do: In my Users\my_username\AppData\Roaming\Microsoft\FSX directory I have set the fsx.cfg file to contain the following - WideViewAspect=True There are three individual camera files that I've determined exist: Users\AppData\Roaming\Microsoft\FSX\Cameras.cfg InstallDirectory\FSX\cameras.cfg InstallDirectory\FSX\SimObjects\Airplanes\PMDG 737-800NGX WL\cameras.cfg That's the model I'm flying, I acknowledge that each variant has a cameras.cfg file I've tried adjusting the Initial Zoom under the [CameraDefinition.002] / Title = Virtual Cockpit from the default of 1.0 to a different value. I've tried = 0.5 & 0.6 & 0.4 on all three camera.cfg files and the -800 NGX WL always loads with 0.3 zoom scale. What am I missing here? It's referencing something that I'm clearly not adjusting. Thanks!

Second this. I try to have the transponder set before I finish my read back of it. I've yet to be nagged if I do it right away.

http://www.avsim.com/topic/483995-losing-clickspots/

I'll let someone else call out the first/last name on the forums, please. But regarding your question - http://support.precisionmanuals.com/kb/a109/weather-radar-troubleshooting.aspx Found on Google in 4.8 seconds.

The best luck I've had with the default ATC is V/S @ 2300-2600 FPM to 10,000 feet (from cruise) and then FL CH at 220-240 until I'm 30 NM out and then I'll start slowing things down for approach. At least that's with the default FSX ATC. Otherwise they'll be barking at me to expedite descent or I'll hit the FAP waaaaaaay too high or too fast. I've used Pro ATC/X which is pretty solid, uses real-world STAR/SID but it's still not perfect with approaches.

By that logic, wouldn't it make sense to add your vote into one of the existing topics? That way rather than having someone try to evaluate 40 threads of 1-3 comments they can just see one big thread with a lot of comments/views. It makes it easier to gather the data point.

Gotcha. I've never loaded a save flight (based on reading in this forum that it had the potential to introduce oddities with panel states). If I decide to do back-to-back flights, I'll go so far as to completely restart the computer and just re-select everything manually. I always launch the game with the NGX though (it's not the default plane). So I'll try your approach of loading the scenery and then the plane. In the interest of thoroughness, I'm going to try a clean install on a different computer next week and document all my findings for the official PMDG support ticket. Everything was fine for a while, so I know it's not a definitive issue with their product, something is causing it to occur on my end. Even if that means it's the program and not something I'm actually doing.

Nick, what do you mean "starting fresh" every flight?

This issue just started happening with me over the weekend, what start was degenerative, has now made the aircraft completely unusable in the VC environment. I had installed FS2Crew (button, SOP2) and it worked for the first two flights. The tutorial flight and the next one of my choosing. On the third flight it would show up once in a while. I do not use EZDOK and I use views between 1.00 and .70 zoom. All three flights, I never left the default captain view. My zoom never exceeded 1.0 and never went further back than .70 I removed FS2Crew and the did three flights, the first two had no issues, the third had intermittent issues that by the time I reached TOD had total loss of VC button interaction. I found that if I minimized the application, upon resuming it, I could click one thing. Didn't matter what it was, but I got one action. If I minimized/maximized, I'd get one each time. I also found going into the options menu also gave me one action. I do not have the game "pause" on menu interaction. Last night, on plane launch I had no click spots. I reloaded the Long state (what I've been using) and that didn't fix it. Switched to C&D, same problem. Short, also same problem. I do not have the NGX as the default aircraft. Reloading the plane does not fix the issue. This morning, I backed everything up and did a total, 100% clean install. Not just of the NGX and FSX but of Windows 10. I reinstalled the following and only the following after fully patching Windows 10: - Steam - Flight Simulator X - PMDG NGX (just the 800/900 base, not the 6/7 xpac) - FSUIPC (free version) - Ran all three Sim Connect files from the SDK folders - (Restarted for good measure) Launched FSX. Changed from the Glider to the PMDG 800, loaded up a no weather, middle of the day time at my KSMF airport (no add-on scenery, no ACAD files, nothing). Completed a successful, problem free flight from KSMF to KLAX. Quit the application, restarted the computer, made the return leg from KLAX to KSMF and just before CZQ started to experience intermittent click spot issues, by the time I passed TURLOC I had lost MCP functionality but radios worked. Passing ELKOE, I had lost all VC interaction capabilities. Quit everything, restarted. Created a new KLAX departure flight and by the time I hit the runway, full VC interaction was lost again. Some additional information on my hardware: - No external monitors - 1920x1080 resolution - Wired USB mouse, wired USB keyboard - HOTAS X thrustmaster System is fully patched/updated, no other add-ons besides the PMDG NGX and FSUIPC. As of an hour ago, the plane is 100% unreliable in a "natural" state. I've got 200 hours on it over the last 3 months and it was perfectly fine until this past week (with no new add-ons). All panel states have 100% loss of VC functionality within 20 minutes of launch, sometimes less, sometimes right away. Recap: - Started to occur - Installed FS2crew (which made it worse), removed it - Still occurred, then got worse - Total clean install of environment, no add-ons, still occurring - Now is unusable Side note: After "moving on" I installed some other payware aircraft (Aerosoft, A2A) and all four planes function without issue in the VC environment. I'm heading out of town tonight on business for a week but when I get back I'll file a formal ticket with PMDG, but just wanted to get my experience documented here as well.

Excellent. Registered and have been browsing. Thanks for the great tip. They're absolutely all there (a little tricky to navigate) but it's all good. Thanks for the tip. I'll check out Skydemon as well!

All, I've learned to heavily rely on AirNav & Skyvector for all my US planning. But I'm interested in joining a European based VA and I'm not finding a similar online resource. I pay for monthly Navigraph updates but do not currently pay for their charts service. What would be the best approach here? Free is always preferred but I have no problem paying for charts from a reliable source. Jepp is out of budget, though. Thanks!

What is VAS - http://support.precisionmanuals.com/kb/a108/vas-management-stopping-out-of-memory-oom-errors.aspx

Man... I wish I could modify the subject line of my original topic. Nonetheless, a lot of great stuff.

It's 100% about the 'neat' factor for me. So I apologize if I've poked the bear on a sensitive topic. Honestly, considering how so many VA sites seem to emphasize that, I just assumed it was... a thing. I think Nick has done a pretty good job of encompassing my feelings about it. My entire life/profession revolves around metrics and performance calculators (I manage a large call center that does 5000+ inbound calls a day) so for me, the tool is about having a sort of "report card" at the conclusion of my experience. I don't treat it like a leader board in a video game, per say (although it's clear there are many places that do) but it's a nice tool to have in the already plethora of add-ons out there. Honestly, if there was an add-on that evaluated me on every stage of the flight, I'd run it. I'd love to have a tool that tells me: "You're too slow on the approach, you took long to do X." Certainly not barking at me during my play time but a sort of post-game wrap up. I have very little doubt that I routinely arrive at my FAF too slow or that my flare isn't smooth. I also struggle to maintain a smooth taxi speed and frequently find myself having to constantly adjust my throttle. Once I get that confidence up, I then move onto the next thing. So rather than taking control of the plane at 500 feet above the runway I can then take control at 750 or 1000. Or maybe I try to hand fly the LOOP8 SID out of LAX to the letter versus immediately engaging the AP and avoid what would be a total disaster on the initial turn (I always seem to overshoot it). Heck, that's part of the reason I haven't flown on VATSIM yet (and I want to real bad). Because I don't want to "screw it up." I want to ensure near mastery level of basic flight mechanics and be able to reproduce them almost subconsciously. Anyway, long enough, here. Again, apologies if I poked the bear and derailed the subject.

Nick, http://bobbyallen.me/landing-rate-monitor/ That's the one I've seen, but there's definitely a lot of other ones. At a minimum you'll need FSUIPC (http://www.schiratti.com/dowson.html) The VA I've joined has all of the "stuff" built-into a GUI. It's pretty cool, actually.

Honestly, I prefer the "exhaustive data" approach. I'd rather watch a 2 hour long YouTube video that floods me with data than have to watch a dozen, 10-15 minute videos and try to piece together information. Not to mention, without fail each of those videos are done a little bit differently. Oh I'm a 350+ (but sub 600) ft/min T/D guy, all day. It's fun to let the plan auto land at <100 but I jokingly call myself the "tooth fairy" because I'm collecting loose ones at the conclusion of the flight. Yeah the SWA virtual I fly with broadcasts it the moment you land on the ACARS plugin and there's always ribbing on anything above 350. One of these days I'm going to set it down like a meteorite and see what they say.

My pleasure. Yeah, you've got a lot of videos and they're all pretty long. So saying: "In that one video where you did the thing" is about unhelpful as possible. It was a very helpful video, in addition to the tutorials. Yeah... I've just reached the threshold with add-ons where my computer is no longer happy. A sub 200 ft/min touchdown at 9-14 FPS isn't really a thing. Thanks again.

So I've now done 5 trips on the original route in question and definitely using SPD INTV has helped considerably when necessary. The last 3 trips were 100% speed brake free. One last question I had and we can button this up. I'm 280/12000 and I need to slow to 250/10000 at an upcoming step on my trip. Do I descend to 10k and then slow or slow and then descend to 10,000? Or is weather/wind specific (the answer would depend on conditions). Kyle... in watching your supplemental tutorial v2 (around the 1 hr, 28 min) mark you're descending to 6,000 and then give yourself instruction to slow to 220. But you don't slow until you reach 6k versus enroute to 6k. Is that typically the way it's done? Get to the target height and then slow? I know that's how the FMC calculates it, typically (the decel point right before the target waypoint).

Thank you both for your detailed and thorough responses. It's all starting to make a lot of sense. I appreciate it and you've given me some great 'take home' advice to use on my next flight.

Yeah, I'm in the same boat. Most of my time flying is after the wife goes to bed and we're in a small place as well. I'm very confident she won't be onboard with me chatting it up. I've been enjoying simbrief.com for planning but I too have gone from jumping into the cockpit and actually planning stuff out. It's probably the reason I'll never graduate to anything larger than the 737. I don't have that much time. :smile: