Search the Community

After downloading a 3rd party airport I'd like to take a look around it and its adjacent scenery. Before, with P3D I would start at the new airport's location, then close the planes' cockpit view, and switch to Slew. Use F3 to gain a 100 feet or so AGL, then use the flight stick to move about and investigate anything of interest. Note that I'd programmed the flight stick's axis commands from P3D's Controls - slew mode page. Can I set up MFS to do something similar? I've programmed the keyboard slew commands, but that's insufficient because (a) I haven't found a way to remove the aircraft from the scene; and (b) the keypad moves the scene too far and too quickly left/right, forward/back, and without a means to change heading. So can the Drone Camera be used to accomplish the same purpose? All I've been able to find in forums and on YouTube is advice to buy an x-box controller to manage the drone camera's motion, which I have no idea how to set up or use. Is there another way to accomplish what was so easy to do in FSX/P3D, without more hardware? (I'm using a Thrustmaster "Airbus" flight stick.)

Hey guys & Chase Plane developer I really need your help, before latest version v0.1.170 released, I got smooth camera moving around using mouse & keyboard.... but after latest version was released I got stuttering and lagging when moving my camera using mouse. When I move my camera using keyboard, its okay & still smooth........but, when I try to move using mouse by holding scroll wheel, it stuttering & lagging ...really annoying. is it because of my CPU usage memory 3 excessive use? or my settings? need your help.

Hi guys, I've been struggling with this strange issue for some time now and couldn't really find any solution online. Here's what happens to me: on numerous occasions when I start a flight my hat switch wouldn't respond, it appears to be completely blocked. Then if I switch to outside view everything starts to go crazy - camera performs a weird backspin and rotates endlessly, engines of any airplane (doesn't matter default or addon) spool all the way up and that's it for me - all I can do is to shut down fsx. The only way I can somehow manage to have it under control is to restart the system and run ezca configuration tool. This happens every time I select a new aircraft, but also every now and then with no particular reason. Apart from it, the whole problem appears to have nothing to do with my system specs, as currently I'm using windows 10 and FSX:SE, with clean vanilla installation of many addons, including EZCA 1.18, but I was familiar with the issue when I used Acceleration and Win7 before... Has anybody of you encountered this weird bug? I'd appreciate any help. Best regards.

Hi.. How can I put the camera somewhere on the ground and it will just stay there.. viewing only the part I fixed it on. I tried so many types available and they keep on disappoint me. All are following the aircraft,, I don't want the camera to follow the aircraft. I used to have an add-on in fs9, but it no longer works with fsx. I want to place the camera just like in this video: So many thanks, captains. Regards, Raptor22

Hello! I have a Problem with my EZdok. When I fly in FSX, it creates Errors in the Windows-Error-History, eg: || Name der fehlerhaften Anwendung: EZCA.exe, Version: 1.1.8.7, Zeitstempel: 0x2a425e19 Name des fehlerhaften Moduls: unknown, Version: 0.0.0.0, Zeitstempel: 0x00000000 Ausnahmecode: 0xc0000005 Fehleroffset: 0xf1550000 ID des fehlerhaften Prozesses: 0x3324 Startzeit der fehlerhaften Anwendung: 0x01d17575009d6d87 Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\EZCA\EZCA\EZCA.exe Pfad des fehlerhaften Moduls: unknown Berichtskennung: ceb0d003-1dad-4b2e-94da-a2edd75f3b5e Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: ""BLANK IN REPORT"" || About 20 errors after that, my FSX crashed with this Error: || Name der fehlerhaften Anwendung: fsx.exe, Version: 10.0.61637.0, Zeitstempel: 0x46fadb14 Name des fehlerhaften Moduls: FMGS.DLL, Version: 1.2.7.82, Zeitstempel: 0x552db3f3 Ausnahmecode: 0xc0000005 Fehleroffset: 0x00036b03 ID des fehlerhaften Prozesses: 0x1c34 Startzeit der fehlerhaften Anwendung: 0x01d175689b9979bb Pfad der fehlerhaften Anwendung: E:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Pfad des fehlerhaften Moduls: E:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Aerosoft Airbus A318_A319 Base\Panel_Fallback\DLLs\FMGS.DLL Berichtskennung: 4606c439-c0dd-480b-8786-bc9da976922c Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: ""BLANK IN REPORT"" || I reinstalled Version 1.18.7 of ezdok and tried it again. Now, my FSX didnt crash but it still creates EZCA.exe Errors in the history! Every time it does that, my FSX freezes for about 0,5 sec. I am using Windows 10 x64, EZDOK, FSX etc. started as administrator. If you need any more information, please ask me because I really want to fix this error! I hope you can help me, RollingMountain.

Hello, Guys! I don't know whether it's an appropriate forum for this. I'm using FS Recoder. I want that in saved file, when I play my recorded file, I should see it in every Angle what I want. Suppose, I want a specific place (probably call Spot Camera or not). I've stand in the end of runway and watching the plane to take off, so plane should come and go over me instead of I go with the plane. How can I do this? Next, If I want to set my own Tower Camera, how to set t? Suppose Default camera of FSX was at right side of Runway and I want to make another tower camera which should be at the left side of runway how can I do this? I've seen some videos but couldn't understand. Please help me here. Regards, AP

A few years ago, user Javiz posted a way to place cameras on the airstrips without having to install programs like Chaseplane or EZdok. (https://www.avsim.com/forums/topic/403991-how-to-make-a-plane-spotting-view/) It works very well on P3d and FSX, but the camera's speed is very slow. Does anyone know how to change this camera speed? Thanks

So i did a landing comparison of the FSL320 vs. the FF320. A sidestick camera is included in both videos. Conditions are relatively the same during both landings. Variable winds /w light turbulence. I made more adjustments than needed to show the differences in response and feel. Enjoy P.S. I don't intend starting a war over which is better. FSLA320: https://youtu.be/x36g0o73SKI FF320: https://youtu.be/DM7whpazKkA

X-Camera, from Stick and Rudder Studios a is an enhanced camera system for X-Plane 9 and 10 that lets you define multiple view categories and multiple views within those categories that are associated with specific aircraft. Take a look at this short tutorial on YouTube. Download from these two locations: X-Plane.org StickandRudderStudios.com Features TrackIR Each view can enable or disable the TrackIR input. If the view is out the cockpit window having TrackIR enabled is desirable. However, if the view is a close-up of an instrument panel then having TrackIR disabled is probably the better choice since the view will be stable making it easy to click on cockpit controls with the mouse. We also support LinuxTrack on Linux and Mac systems. HeadShake If the HeadShake plugin from SimCoders is installed then the view can accept input from HeadShake. Similar to the TrackIR feature you will likely want this enabled for certain views but disabled for views on instrument panel close-ups where a stable camera makes it easier to use a mouse to control cockpit knobs and switches. The HeadShake plugin must be at version 1.3 or higher for the integration to work. Smooth Transition When this option is enabled the camera with smoothly transition from one view to another over approximately half a second. When the option is off the view will transition immediately. Views can be controlled in a number of ways •Each view can be positioned by using keyboard keys or a control panel •The camera’s X, Y, Z, Heading, and Pitch can all be adjusted for each view •Views can be assigned to a HotKey or JoyStick button for easy selection •A HotKey or JoyStick button can be used to navigate to next or previous views •The views for a specific aircraft can be saved to a CSV file for easy editing Walk Mode Any view’s camera can be placed in Walk Mode. While in this mode the camera can be walked or floated around using keyboard input. If you ever played the video game asteroid that is what walk mode is like. The mode is particularly useful for pre-flight inspections of your aircraft. You can create a external view and after selecting that view you can “Walk” the camera around checking out your landing gear, props, etc. Linear Transitions and Auto Advance Linear transitions allows you to define a transition between two adjacent cameras in category. This capability, in conjunction with the auto advance feature, allows you define fairly sophisticated animations that can be used for automated Pre-flight inspections, scenery viewing, and cool transitions affects that can be used when creating flight videos. All the transitions in our YouTube video were done with X-Camera. What's New in Version 1.0 1.0 Added support for LinuxTrack. Read the LinuxTrack section of this manual for more detail Added support for 8 way hat switch panning Added middle mouse button simulation for easier mouse look operation on Linux and Mac Added enhanced transitions that allow you to create very cool affects for making flight movies. Also added license key support for these more advanced features. Added command to restore a camera to its original position Added roll support for TrackIR, LinuxTrack, and HeadShake. X-Camera now supports a full 6 DOF with these three options. Fixed a problem where X-Camera was not able to save settings for each aircraft if there was more than one .ACF file in the aircraft directory.

I don't know if it is P3DV2 related but i don't had it in FSX and as far as i can remeber don't had it in P3D 1.4. Creating a new Camera View is only possible for Virtual Cockpit. When i Switch to "Aircraft" the P3D Camera don't Switch to external and stays in VC. That happens with all planes and even activate/deactivate camera funktion (to rewrite the camera in aircraft.cfg) in OpusFSX don't help. Does anyone have the same Problem ? Greez

Okay guys, I thought I will make an official thread for those of us who are confused about the view system in FSX. I know it can get very confusing, especially for someone new to FSX. It certainly did for me. I'm just now getting the hang of it and would like to share some helpful tips or useful information for others on here. Please forgive me if this information is already on here, but I thought it'd be nice to have 1 thread that covers everything. Ok, let's start. First off, many of you who play FSX are most likely not using the built-in view system and are using a 3rd party addon called EZCA better know as EZDok Camera Addon. You're going to be likely using one or the other and not both simultaneously as this will cause a lot of strange behaviour and conflicts. If you have this addon install, notice that when you start up, that *MOST* of your planes will have a default zoom of 0.40. This can be changed for each aircraft. The files are all located in: C:\Users\{your_username}\AppData\Roaming\EZCA\db\ (you will have to configure your settings to allow you to see hidden files and folders. Each aircraft has its own configuration file and it is stored here. There are 3 folders in here for the 3 distinctive views: aircraft, virtual cockpit, and world. To edit your default view for a particular aircraft, go to that folder. If you want to edit the default virtual cockpit view, then go there and look for your plane's name and load the file up with a text editor. Notepad will do. To change the default zoom level, look for an entry called Zoom=xx, it should be right under [CAMERA]. I believe the a Zoom=26 will get you a 0.30 zoom level when playing. That is the lowest you can go. Once you made your changes, just save the file, and it will pretty much be instantly refreshed when you switch to another view and switch back, you will see your new zoom level! Another thing to look out for is, have you ever encountered a problem with non-clickable buttons when under cockpit view for a certain aircraft? Well the problem with that is, your zoom level is too far back. To fix this, just enter 'EDIT' mode in EZCA and move that view forward until you can click the buttons. I had to find this out the hard way. For those of you who are using an xbox 360 controller with the wireless receiver. Make sure you have the controller turned on before starting FSX. I notice that if you turn it on afterwards, EZCA won't recognize the controller. I was struggling a lot in the beginning with all these views and zoom levels, and now I have a better understanding. Hopefully this information will help others out there. Feel free to contribute to this thread. I will post more helpful stuff as soon as I learn more.

Hi, I am experiencing jumpy/stuttering camera movements. They appear to hit a regular "clock tick" intervals. So every 1 second of so, the camera appears to stop and then immediately start moving again. This happens when using the middle mouse look, and when switching between presets. Has anyone else had an issue similar to this? I searched the forum but couldn't find anything about this kind of problem. I do not think it is FPS related as it happens at all performance levels. I am using the PMDG 737 in P3D v4 Thanks in advance for any help that can be offered.

I have a lot of hours invested in setting EZDok up with camera angles and positions for certain of my aircraft. Those of us that use EZDok and don't use TrackIR really depend on (and enjoy) these views/cameras in FSX...I really like using them for screenshots and Fraps videos etc. I have always thought we should share the EZDok Camera Sets files we make, but a search of the File Library only turns up 4 entries. So I was reading this thread: http://forum.avsim.net/topic/377664-how-does-ezdok-compare-to-active-camera/ ...and noticing how many people make their own EZDok camera sets for scratch..Yes, I'm sure most of us start with a similar aircraft and we Export the EZDok Camera Set File from the Camera Studio app, then we open it in the new aircraft and we click cameras and hit '2' on the numeric keypad and we edit each camera to our exact liking by moving the mouse and rolling the mouse wheel etc. Probably we rename them. I know once I have my cameras kind of the way I want them, I always export a file to a folder I call X\:EZDock Camera Sets I do that not so much to share the file later, as I don't know that I am particularly good or thorough at setting these up, but EZDok has a way of sometimes starting up and not loading any cameras for a certain variant of your aircraft and this way I can just go get my cameras if I have named them well. Anyway.....not a new concept...certainly one of the reasons I bought the Captain's Training for the PMDG 737-NGX from Angle of Attack was to get the excellent and exhaustive EZDok Camera Set for that aircraft (obviously that licensed set from AOA is NOT one we would share in the manner I am suggesting for our own homegrown sets). My suggestion is that we EZDok users start Exporting our camera sets and uploading them to the library or elsewhere. I don't know what section of the Library would be right, but I do know we want to name them carefully. If I make a set for my L39 I might call it "VRS FA-18 #2 06012012.ecs" for the F-18 Superbug. For the L39 it might be "L-39 Albatross Std GPS 060912B.ecs" and another might be "L-39 Albatross Garmin 430 GPS 06102012A #1".ecs. You get the idea....if I map the GPS to the '5' button I'd want it to take me to the Garmin if it's aboard. I'm sure there is more to it, and we'd always have to customize the files we pull down some. For example I have a Saitek X52 stick and yoke. The stick has (2) hat switches- I leave one at default usually. But when I travel I take a Logitech stick with (1) hat switch and on my laptop I set the EZDok camera settings so they are only invoked when the trigger is pulled....so 'up' with no trigger is pan up, but 'up' with the trigger pulled takes you to "Pilot Eyes" camera position. Anyway- let me know what you think...perhaps it's as easy as attaching .ECS files to individual posts in this thread with good naming. But I do think we should all stop re-inventing the wheel (customize the wheel, make cool covers, yes, but re-invent not so much). Phil

I was browsing around to a freeware camera like Walk and Follow or EZ DOK, and came across the "EZ Walk" camera, which apparently is freeware. However, I can't find a working link to it. Does anybody have one?Thanks,boeing247

Hello all, i want to know how can i show and fix a fsx camera on lower du. thank you.

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!

Hey folks ! I just wanna find out whether the spot view camera distance in Prepar3d platform is as easily adjustable as in FS2004 or it behaves the same awful way as in FSX. Thanks for any replies !

I know camera view is not a new topic but I have not found the answer I am looking for yet. I know you can configure camera views for FSX but I cannot work out the setting to get what I want. In "Tail" I get exactly what I want except the camera is too close. I want to be away from the plane not on top of the tail. But the behavior of this view is good because the plane moves exactly to your joystick. In "Fixed Spot" view I get the distance from the rear of the plan that I want but the behavior of the camera is off the planet. If I turn my joystick the plane pivots and the scenery does not follow the plane. I do not see the point of this weird behavior. So "Tail" gives me the camera behavior, and "Fixed Spot" gives me the distance from the rear of the plane. Can someone please tell me the setting to get what I am looking for. You should note that MS Flight does not have this problem. When you view the plane from the rear you can set your distance and the plane follows the joystick. This is what one would expect. So MS Flight has it right while FSX has a mental "Fixed Spot" that does not track the joystick movement from the rear but keeps pivoting the plane, putting it on weird angles and constantly change the perspective so you keep have to adjust the view to the rear of the plane manually. Why such a nutty behavior? Its enough to drive you mad. Please help.

Hi, I've edited my camera.cfg file to add some new fixed cameras. I have put shortcuts to them and they work fine. I would like to add a few more but in the FSX config I can only assign shortcuts to cameras 5-9. Is there anyway to add more?

Hello everyone, Since my X-Plane 11 installation seems to be broken since trying the 11.11r2 build (I get 15fps max on every render setting and can't run the sim in real time), I decided to ignore my inadequate experiences with Prepar3D and give it another shot. I started it up and loaded the default Baron 58 and to that point everything seemed to be working fine. But when I wanted to look down to my throttle panel, I noticed an issue I hadn't had before. When looking down, both using the hat switches on the joystick and using space + mouse, the view tilted to the right. So instead of looking down, the left side of the camera went down, but the right side stayed the same, creating a very weird view for my eyes. Something else I noticed was that when I zoomed out to below 0.70 zoom, the view started to look very weird, almost as if what I was seeing was a camera pointed at a computer screen at a 40 to 60 degree angle. It's hard to explain, but anyway I'm not sure if the exact problem matters. All I need is a generic fix for weird camera angles and incorrect panning of the camera when looking up or down. Does anyone know how to fix some general camera/view glitches or how this specific issue can be resolved? Thanks in advance, midazz1

I have installed P3D 2.5 and the EZDOK 1.18 beta, but when I go to click the middle mouse button the view doesn't change. This is also the same when I go to try and edit a view - as none of the defined keys do anything. What is the problem here? (Screenshots of what is currently configured below): Any help is greatly appreciated

I found a pdf of the manual for Dovetails Flight School and was reading through it. I never bought Flight School but am curious what Flight Sim World might have to offer. In noticed that Flight School retained the old, clunky FSX camera system. In comparison, X-plane's camera system is a wonder to behold. I haven't seen any comment on this (maybe I've missed it), but I would urge Dovetail to upgrade their camera system to XP's standards, It is so much better than what FSX came with. (I've never used prepar3d, but would be horrified if the same old system is still in use there too.)

Why can’t I go through the cabin with the cockpit view on all aircraft? I tried to navigate with the arrow keys through the cockpit, this works for any aircraft. In the TBM 930 I can navigate more then only through the cockpit - I can navigate completely through the cabin. In other aircrafts the camera stops immediately when I try to leave the “cockpit area”. I understand that it is not possible with aircraft without a modelled cabin view. What I do not understand: Why can't I navigate to the cabin and backseats with the Beechcraft King Air, Diamond DA62, Beechcraft Baron, and so on although the cabin view is simulated?! What I mean (in TBM 930 this is possible!):

i want this exact same view saved as one of my custom cameras. But it doesn't seem to work. This is one of the default views under the showcase camera. Does anyone know how I can get this exact view to save as a custom one?

Hi everyone, I have set up my number pad bound to the internal camera views. So for example: Num 8 = Look straight ahead Num 7 = Look forward left 45 degrees Num 4 = Look left 90 degrees (left wing) ...and so on. After the latest Hotfix an odd issue has surfaced. The Numpad 4,7,8,5 INTERNAL views now show EXTERNAL views. It is only those 4 keys affected. The rest of the numpad works as intended showing internal views. Try as I might I cannot get those 4 keys to save to internal view. I have checked the menu, checked the key bindings and everything is in order. It was working perfectly even after WU6 , its the Hotfix that did this. These pics will make it clear. Would anyone know of a fix? Thank you. Numpad 8 (Look straight ahead) BEFORE hotfix 🙂 Numpad 8 (Look straight ahead) AFTER hotfix ☹️ ________________________________________________________________________________________ Numpad 7 (Look forward left 45 degrees) BEFORE hotfix 🙂 Numpad 7 (Look forward left 45 degrees) AFTER hotfix ☹️ ________________________________________________________________________________________ Numpad 4 (Look left 90 degrees) BEFORE hotfix 🙂 Numpad 4 (Look left) AFTER hotfix ☹️