groentesoep

If the release the product to Early Adopters because they want to make sure the installer works as expected and be able to manage support requests: People that did not buy the EA version: "It is just a public beta" If they release it at once and issues with the installer arise: People that bought it: "It is just a public beta" FS Labs just can not win in this... FSLabs is a respected developer, that kept it's promises in the past. What reasonable doubt do you have to believe they wont this time?

There are non normal checklists as mentioned by Awf and pete_auau, but they are not stored locally. You'll need to open the index file in the documents folder to get a link to the non normal checklists. Same goes for the performance manual I believe.

Some very good posts in this thread. I own both, but hardly use X-Plane. Main reason being the lack of add-on planes that manage to arouse my interest. I hope the IXEG 737 and the upcoming MD80 change that. Other reason is that I am just more familiar with P3D and have invested a lot of time and money to make it look and work as it currently does. What I do really like in XP are the color reproduction and atmospheric effects (using Real Terra Haze). I can't help but feel that P3D (using FTX Global and other Orbx products) feels a bit cartoony in comparison.

Thanks for your reply. Well, it seems I just have to live with it and double check that all my controls are connected before starting a flight in P3D. BTW kudos to you for landing the plane using mouse and keyboard!

Hello, I just had to break off a flight in P3D on Vatsim, because my rudder pedals somehow disconnected. After replugging them, I lost all the controls in P3d (Saitek yoke and throttle quadrant). I'm wondering if there is a simple option to let P3D recognize the controls after they are plugged in, while the sim is already running. At the moment I'm quite annoyed. I do not have much time for simming, so when I finally have the NGX setup and everything, and than have to break off the flight because my rudder pedals somehow unplugged is really irritating. Not enough time to start the flight over again.... I'm using FSUIPC for my controls. The controllers do show up in the Windows settings, but neither P3D nor FSUIPC recognize them. Is there any way to work around this? My system is Windows 8.1, Intel 4790K and Geforce 780. Thanks in advance!

I think there is a large market gap too. But just as you I can't imagine the work that has to go in to such an add-on. I've been wondering if it is possible to make region-specific ATC-add-on's. Like a modular ATC add-on that for instance delivers ATC for Southern California or Norway. Maybe that would create the possibility to program more custom, per airport policies and phrases, which could make the whole experience more realistic. But once again I have no idea if that's even possible and how much work and cost would go in to such an endeavour.

I might have the same problem, but I need to do more testing. This occured to me for the first time yesterday. Had two flights that ended to earlie because of my system crashing and both were at night. This never happened to me before. I did install the latest Nvidia drivers recently and changed the FIBER_FRAME entry in the Prepar3d.cfg. So I will have tot test if any of these have anything to do with it. Do you use Orbx Vector?

Congratulations and a big welcome.

Ok guys, I managed to solve it after installing the previous versions of Simconnect as mentioned in the post by adi518. Afther that I installed version 1.15, version, 1,17 the P3D patch and ran the configurator. All with the use of EMT.

I haven't tried this yet. I'm going to give it a go this evening. And BTW thanks everybody for your suggestions and help.

Well, anyway it all still requires me to re-install P3D to reset all the aircraft.cfg's to default. At the moment I'm not prepared to do that. This whole Ezdok thing has already cost me more time and frustration as I want. Re-installing my whole P3D setup with all it's add-ons is going to cost me another week. I unistalled version 1.17 and tried installing v 1.15 (as administrator of course), but without any succes. After that I uninstalled everything again and installed v.15 and v1.17 and the P3d update, and did not run the EMT, but it still will not work. There is just no way I can get the Addon-menu to work. I'm still wondering though what running the Config Tool using EMT changes besides the usual additions to the aircraft.cfg files and the exe.dll, so that it messes everything up beyond repair....

Thank you for your help. I was afraid it was going to come down to this. Well, seems I have to do a full re-install of P3D then. :-s

Sorry, forgot to mention: My new pc has Windows 8.1 I do not have FSX installed. Just P3D. The migration tool was only used while running the Config Tool. But I tried removing the camera profiles that were added tot the aircraft.cfg and adding the one manually. This did not help. Or is there something else that the Config Tool is adding? If so, does this mean that I have to manually edit all my aircraft.cfg files back to their original state (whatever that may be)? Thank you for your reaction

Hey guys, I hope someone can help me with getting Ezdok to work. One my old pc it used to work under Windows 7 and P3D v2.2. Recently I upgraded to a new pc and installed P3D v2.3, but I can not get Ezdok to work. I already read a lot of topics on this on several forums, but to no avail. I installed Ezdok 1.5, the 1.7 update and installed the P3D version of EZCA.exe. When starting P3D the EZCA will start and the icon will show in my taskbar. But when I click on it, the window will not open. The EZCA menu is also missing from the P3D addon menu. My exe.xml looks like this <?xml version="1.0" encoding="windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>exe.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>EZdok camera addon</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\Program Files (x86)\EZCA\EZCA.exe</Path> </Launch.Addon> <Launch.Addon> <Name>Couatl</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>fsdreamteam\couatl\couatl.exe</Path> <CommandLine>--mode=prepar3dv2</CommandLine> </Launch.Addon> </SimBase.Document> My dll.xml looks like this: <?xml version="1.0"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>Addon Manager</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>bglmanx.dll</Path> </Launch.Addon> <Launch.Addon> <Name>ObjectFlow</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>D:\Prepar3D\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow.dll</Path> </Launch.Addon> <Launch.Addon> <Name>VistaMare Core</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>VistaMare\ViMaCoreX.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Migration Tool Plugin</Name> <Path>MigTool.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>as_connect</Name> <Disabled>False</Disabled> <Path>as_srv\as_btstrp.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG HUD interface</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> <Launch.Addon> <Name>IvAp</Name> <Disabled>False</Disabled> <Path>D:\IVAO\IvAp v2\ivap_fsx_bootstrap.dll</Path> <Commandline /> </Launch.Addon> <Launch.Addon> <Name>PMDG Interface</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDG_Interface.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>RAASPRO</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>.\RAASPRO\RAASPRO.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>Flight Recorder</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Aerosoft\Flight Recorder\AS-FlightRecorder.dll</Path> </Launch.Addon> </SimBase.Document> The following is added to my aircraft.cfg's: [CameraDefinition.201] Title=EZdok Aircraft Universal camera Guid={D8D67955-2E9B-4e75-9D8B-8EFFBBFAC65B} Description=Universal camera for EZdok cam utility Origin=Center SnapPbhAdjust=Swivel SnapPbhReturn=FALSE PanPbhAdjust=Swivel PanPbhReturn=FALSE Track=None ShowAxis=FALSE AllowZoom=TRUE InitialZoom=0.40 ShowWeather=Yes InitialXyz=0,0,0 InitialPbh=10, 0, 0 XyzAdjust=TRUE Category=Aircraft MomentumEffect=FALSE ClipMode=Minimum HotKeySelect=4 I used Opus recently, but just don't like it as much as Ezca and it refuses to work with the Airbux X 318/319. That's why I really would like Ezdok to work. Anybody got any tips or ideas? Thanks in advance

The only thing with Simbrief.com is (correct me if I'm wrong) that you still need to get the routes from an outside source, while PFPX can generate it's own routes. To the OP: I've used FSBuild in the past and am using PFPX now. To me PFPX is hands down the best option. Even though it has more functionality it's way more user friendly than FSBuild. PFPX is also still actively developed, which, I believe, is not the case for FSBuild. PFPX has a lot of "auto"-options. Which can make planning a flight a proces of pushing a few buttons. Topcat can be a nice additions but is not necessary to use PFPX. Topcat is purely used for calculating you take-off and landing performance numbers.

I'm sorry you don't get any reaction to your posts. Nobody probably knows how to solve this or what's going on. I know I don't. Good luck with finding your sollution.

A couple of months ago my FSX-PC crashed and I had to do a full re-install. This was just after the release of P3D v 2.2, so I decided to take the plunge. I decided to not do a dual install because somehow that seemed "cleaner" to me, and I'm afraid of the conflicts running P3D and FSX alongside may cause. But maybe one day I will re-install FSX again. I ran FSX in DX10 and did not suffer many OOM's. Mostly because I used the SceneryConfigEditor and do not fly many long haul flights. So besides some quirks here and there, FSX wasn't all that bad for me (though I must admit that I banned a lot of the FSX-negativity to the back of my brain ;-)). Till now P3D has been a pleasant surprise. It means that I have to give up on somethings, like the NGX and the 777. On the other hand I can still fly the Q400, AXE and MD-11. Aerosoft airports are working, but have trouble with the lighting (except the newer ones). FSDT and FlyTampa are working great for me. The performance with P3D is a lot better for me than with FSX. I can even have road traffic on now, without watching to a Powerpoint. I have the feeling that the ground scenery is more detailed/dense. All of this without tweaking settings and such. I miss flying the NGX and 777, but not yet enough to make the switch back. The fact that not all add-ons are working in P3D, also has a positive effect on me. I can be really happy when a add-on that I already had for years becomes P3D compatible. Without trying to sound to cliche: it really lets me enjoy and appreciate the stuff that I have...

I can confirm this. Downloaded them yesterday and there are indeed triple installers.

That solved it, thanks! I set the scenery complexity from sparse to normal and all the buildings magically reappeared. Your help is much appreciated!

First of all, let me start off by saying that I know that these scenery's are not supported for P3D v2. At some of my add on scenery's there are no buildings visible, while the surrounding photo scenery is clearly visible when looking top-down. Does anybody have a clue what could be causing this? It is occuring with Aerosoft Approaching Innsbruck (installed using EMT and at the top of my Scenery Library). The buildings do not show and there are no runway markings visible. I know LOWI is not P3D compatible, but I have read of people succesfully using it... It's also occuring with some airport of the Airport of Norway scenery. I believe these are supposed to be compatible with P3D now, but not all the airports are working. Bergen (ENBR) is working for instance, while Kirkenes (ENKR) is only showing very washed out ground scenery when looking from above, but no buildings at all. I know some of you people here can come with sollutions to problems that I could never think of, so maybe you can give me some suggestions? Thanks in advance!

Well, that's exactly what I said. The Q400 is not as complex in that area as the NGX or 777 is and does not allow you to turn on the autopilot and autothrottle and sit back and "enjoy" the ride. Because of that I believe it is a good option for the "in-betweeners".

Almost every airplane can be flown without using the FMC. The 737 NGX still has basic navigation radio's and course selectors (in the 777 you will have to use the FMC to set these, but only one page of it). The point I'm trying to make is: do you have to use the FMC to fly the 737? No. You can still do basic VOR-VOR navigation or even fly a DCT from one airfield to the other. For me however, part of the fun is setting up the plane and the FMC and try to mimic (what I percieve to be) real world operations. If you want to learn how to work with an FMC, might I also suggest the following Youtube channel: https://www.youtube.com/user/FSXpilot767

I concur that the NGX-tutorial is great if you want to start learning FMC's. For a less complex FMC, I would recommend the Majestic Q400. Which does not require you to fiddle with performance data and cost-indices, but mostly focuses on the navigation part.... On the other hand, but I think you will regard this as a positive, the Q400 does not allow you to engage the AP after T/O at 400 AGL and disengage the AP after the aircraft has autolanded itself. The VNAV is not as sophisticated as on the 737 of 777 and there is no autothrottle in the Q400.

Well, my upload to the Avsim library got rejected, because I did not add any installation instructions. While this probably is the rule and they might even have a good reason for having this rule, I just do not see the logic behind adding installation instructions to a PDF-file. So i got annoyed, and did not make any more efforts. Maybe later...

Thank you for al the kind words guys! I appreciate it. Thank you for your comments. I uploaded a new version with some of the changes you proposed. I added different checklist captions with the "TO THE LINE"- part and added a reminder for the V-speeds and the acceleration altitude. The other items I did not add, because as I and mr. York said before these checklists are ment to be an addition to the manual, not a replacement. For me it would be contradictory withe the whole "condensed"-idea behind this file. However, I decided to upload the original MS Excel file, so you can edit it to your own liking. It can be found here: https://dl.dropboxusercontent.com/u/20624964/q400flows.xlsx