kamaz74

You use the keyboard, joystick or you can click them in the ezdok client. I use a preset for the main forward view, overhead and pedistal assigned to number keys 1, 2, 3 respectively. I use Shift+1, Shift+2 etc for external cameras and wing views. Works extremely well. I had track IR and wasn't a big fan. Works great in DCS for fighters but anything else isn't very well suited. Clicking things on the panel is more of a challenge with track IR since you can to be aware of your head movements to make sure you don't miss click. Also, gotta wear a thing on your head. Meh, it's definitely a powerful product but wasn't for me.

Ezdok is what I use. Works very well. Very customizable. Not intuitive to use so be ready to read the manual.

Welcome

Just build your own routes it's fun.

I would also like to needlessly remind you that first and last names are required to post on these forums. I make sure to remind as many people as I can that full names are required because it sends me on just enough of a power trip to make me feel superior to you. I am neither a moderator nor a staff member but I am more than willing to do their jobs for free because I have little to no control of anything outside of AVSim. Please also include a scan of your driver's license and/or passport for verification. Also, mail a stool sample and cut off a bit of your hair for drug testing. Rules are rules. I don't know how you could expect me to answer your very straight forward question without knowing your full name. We have standards here. Also, please dont make up a name. This is the internet and people that do that will be reported to the cyber police.

OBS

You've clearly got the credentials.

Kept it coordinated the entire time. Nice smooth flare and landing. Excellent job!

Stupid question, but have you tried calibrating them through FS? I owned two and except for a squeaky rudder axis on both, they were really great for the few years I had them. I have a Logitech 3D pro now and like it just fine. Only £40. I recommend it.

I do this as well.

Set up the same flight again and monitor your vas. The fact it ooms after 10 hours is about in line with the findings of various people in this thread: http://www.avsim.com/topic/477686-p3d-v3-fmc-memory-leak-back/ If in fact you are experiencing the radial intercept bug, you can watch your vas leak away at about 12mb every few minutes. In the mean time, can manually enter the Sid or star fix by fix to avoid a leak. Wait until you get close to your destination to program the IAP. VHHH has been the biggest culprit for me.

Good, it's a simulator, you're not supposed to crash. If you go into Realism and check "Ignore crashes and damage", does it still ctd?

Pete, customer complaints are not tolerated here. You should know better.

It's only a matter of time.

Other people have experienced this issue with zooming displays in P3D with the PMDG 777. I also think someone in the thread mentioned the NGX as well. http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=113995&sid=f9479d083742b0ed127afaedb9a9a828&start=615 There is also another issue that has been known about since November of last year and has yet to be fixed which causes a slow VAS leak eventually leading to an OOM on longer flights. Only happens in certain scenarios. http://www.avsim.com/topic/477686-p3d-v3-fmc-memory-leak-back/ On your next flight, use this to monitor the virtual size of the fsx process. https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx I just got done with a 14 hour flight from Johannesburg, SA to Seoul, SK and landed with less virtual memory usage than when I started (and I even use FTX Global, REX, ASN), so I know this to be a completely false statement. To say FSX or the ESP based P3D might never have been designed for a 5 hour flight is ignoring a decade of VATSIM users like myself completing countless ultra long-haul flights without a single connection interruption. In fact, when you keep your VAS usage below the cap and don't go nuts with addon scenery, you can fly for extremely long durations. In 2014, I flew the PMDG 777 on 4 flights totaling 52 hours without restarting the sim at all. People seem to think 4096 textures, mesh, landclass and ground textures, autogen, extremely heavy addon airports and a very detailed aircraft simulation are owed the same stability as a vanilla FSX install. Not so. Something has to give and its usually the terrain.dll or an OOM. In the cases outlined in the links above, however, the problems are clearly with the PMDG 777 so I wouldn't be so quick to place blame on the simulator itself.