Search the Community

I have a question for all of you regarding moving the eyepoint in the virtual cockpit. As most of you probably know, you can translate the eyepoint left/right, and up/down with the arrow keys. You can also define a key combo to translate the eyepoint forward/backwards - I use Right-Alt Up/Down. But I have observed something: In all but one of the OEM Asobo aircraft, the eyepoint can't be moved outside of the interior of the aircraft (on some planes, this is limited to just the cockpit). The one exception is the Zlin Shock Ultra: the eyepoint can be moved as far away from the plane as you want, even hundreds of feet if you are patient enough to press that arrow key long enough (moving the eyepoint is very slow). I have a few Non-Asobo planes installed, that are probably imports from FSX: the DG-808 glider, the Airbus H-135 helicopter, a C-47, the P-51 Racer, and on all of these, the eyepoint can also be moved to any position, and is not restricted to just the interior of the aircraft. It seems to me that there is probably a setting in some config file that is controlling this restriction on the eyepoint translation range, but I have tried comparing all of the config files for the Zlin Shock Ultra to several other planes, and I have not been able to find this setting. Do any of you know how to turn off the eyepoint translate range restriction? Thanks! Laura-Ann Charlot Sacramento, CA

Hi there, I just installed the 777 for p3d v4, but the tilt or pitch, whatever I should call it, of the forward viewpoint in the default captain seat vc seems pitched too high compared to the one in v3 for some reason. Can I change it so it looks down a bit more by default? I forgot how, and I can't seem to find any threads that explain how to do it. When I go into the aircraft.cfg I don't see a camera definition for the captain seat, so I'm not sure which one to edit. Thanks for all of your hard work over there, John

Hello everyone. I used to fly with the default eyepoint until today. A few days ago when reading the 777’s Introduction manual, I noticed some tricks proposed there for camera adjusting, but I just didn’t pay much attention. Today, however, while performing a mid-range flight, I decided to try said tricks out. Obviously, since it’s something new it looks weird to me, especially when landing, due to the fact that I have to totally move the camera up and leave my instruments behind when trying to visually line-up with the runway (that’s the way it’s supposed to be eh?). Also, when on the ground, if I focus on the instruments I can roughly see a few meters of horizon ahead, not the entire field as I used to. However, I want your opinion (especially PMDG guys, real 777 pilots, and people who has flown the plane in the real deal simulator). For me it looks like the eyepoint was a little high, but I can’t really tell a thing since I’ve never been in the real plane, let alone its cockpit. Does my setup look realistic? I have a 19’’ Samsung monitor (8:5), resolution is 1440x900 and WideViewAspect=True. Introduction manual doesn't tell anything about moving the camera forward or backwards, which I don't know if it could also have an impact in the view's realism (logically it also should). Some pictures attached (all of them in the 777-300ER): 1. 0.8 zoom, focused on the instruments (part of the horizon also visible though): 2. View of both the yoke and the checklist holder as shown in the Introduction manual, although both don't match perfectly: 3. Again focused on the instruments, this time with a zoom of 0.9: 4. Focused on the horizon: 5. Camera tilted to the right, to have a reference of its height compared to the first officer's seat: 6. Yoke and captain's seat, looking well centered in the screen: 7. These last two now on the ground, with a zoom of 1.0: 8. And the horizon: One issue that became more evident after trying this, and worsened by the 777-300ER's length, is the with which camera drifts off-position even with a slight movement of the plane. It's really annoying and distracting to be constantly trying to move it back to where it should be. I'm seriously considering to purchase EZCA when I have some money. According to what I've read in other posts it seems to be really worth it when it comes to customizing views and assigning a specific camera location to a defined button. Thanks in advance!

Hi friends 😀 One of the best design features of X-Plane 11 is its excellent default view & eyepoint-movement controls. In a matter of minutes you can set up custom views and bind them to hotkeys from virtually anywhere inside or outside the airplane. Its also very simple to adjust the current view - just use the arrow keys. Example. Setting up a left wingview in a Boeing 737-800 in X-Plane 11 1. Use arrow keys to move backward through the flightdeck door to the passenger cabin. Keeping SHIFT pressed speeds up movement 2. Arrive at the window and use small taps of arrow keys to transition in the XYZ axis & mouse to adjust view direction. 3. Press CTRL + NUMPAD 4 Its done. Now to get to your left wingview from the Captains seat just tap NUMPAD 4 and you're smoothly and rapidly taken there. Press the same key to go back to the flightdeck. Numpad keys can be used to set up other views too. Perhaps you want NUMPAD 5 to look up at the overhead? Anyway, you get the idea. Does FS2020 have a similar system? The eyepoint view controls in FSX were so clunky.

747 fsx I purchased the 747fsx 8i addon For some reason my vc is not working, I cant get into the cockpit Seems like when the plane got longer my position stayed the same as the old version so now it thinks the captain is sitting in the passenger cabin I cant seem to get into the vc cockpit. The eyepoint places me in the cabin . I try to move into the cabin via the + button but it does not work My 747fsx was working perfectly prior to the install Any ideas? By the way the 3d cockpit is working perfectly Thoughts?? Peter VC view position is behind the cockpit Please read the manual included with the aircraft (page 8 specifically) which addresses this issue Sorry should have looked in the knowledge base first,. seems it is a know issue in the manual Thank you Peter