carlito777

Just finished a flight from EDDL to EDDM. Overall I can say that it is a nice aircraft which still needs some work. But it is absolutely flyable. So no need for harsh criticism. Every major aircraft release has its problems. It will get there eventually. A couple of problems I had: 1. Right after takeoff I had a really hard time engaging the AP. I was climbing out with the throttle set to TOGA. Speed was increasing extremely fast and it was rocketing towards 200 knots. Maybe I just didn't pitch up sufficiently. The FD was giving all kinds of weird instructions even though I had selected Speed mode with speed set to V2+10, Nav with FMS1 as the nav source. I really had to battle her to get into a stable climb. Tried to hit the AP button a couple of times but in the beginning it just disengaged the AP automatically. Wouldn't stay on. 2. On the STAR into EDDM it just missed a turn in NAV mode. It just kept flying straight instead of doing a turn. I switched to Heading mode but it wouldn't follow the dialed heading. Had to disengange and re-engage the AP for it to work. After that the landing was uneventfully. Did nicely capture the localizer as well as the glideslope. Was fun flying her by hand the last 1000 feet. All in all, I think the CRJ has quite some potential. Visually she is great. The FMS and AP certainly needs some work. If you can't live with some small bugs here and there, then wait a couple of weeks before buying. But I'm confident they will get there. It's a nice add-on at a very fair price.

From my point of view, I think AFS2 does have some serious potential, but it still has a looooooooong way to go. In it's current state it doesn't give me anything that I can't do in another sim (system depth, weather, ...). So for now it will stay a nice "game" to play around a little and enjoy VR, but it is far from being a serious contender to P3D or XP11. But maybe that's changing in the future.

Very welcome!

Here: http://forum.aerosoft.com/index.php?/topic/33966-aerosoft-da-crj-preview/&page=344#comment-829160

AFAIK the update is coming in September. I already own Aerosoft Heathrow and am waiting for a P3Dv4 update. Aerosoft is just sooooooo slow with updates. Frankfurt is also taking ages. In the future, I will try to stay away from their products as the support is really a PITA.

It's not officially released yet. It's only release candidate 1. You have to opt in the betas to get it. Topic title is misleading, unfortunately.

Bit of an overkill to delete the prepar3d.cfg, exe.xml and dll.xml just because the sim doesn't load anymore after you installed a scenery. I would strongly advise against that as this could result in non-functioning add-ons. E.g. if you have installed a PMDG aircraft which relies on an entry in the dll.xml. If you experience crashes after installing a scenery, it is completely sufficient to delete that entry from the scenery.cfg file or disable the add-on.

It's currently at 449€ incl. the Touch controllers because of the "Summer of Rift" promotion.

Not really necessary to put AFS2 on a SSD. I have it on a (fast) HDD and it runs perfectly. Starts up very quick and no problems with texture loading. Totally different story then FSX/P3D...

It has nothing to do with Win 10 Creators Edition. I run Win 10 Creators Edition and have zero problems. Wide view has always had a slightly negative influence on fps and that is still the same. More so if you have a weak GPU.

November

Yes, I think it does. I just finished installing the new version of 777 and fired up P3Dv4. Works like a charm here. So I'm pretty sure PMDG is not to blame.

Of course, no one from LM has admitted that there is a bug in P3D. However, various people are able to reproduce CTDs after the scenerio screen when sceneries are registered using the add-on.xml method. What I did is simply install the sceneries with their installers and then rename the add-on.xml file to something like add-on.xml.off. And then I manually added the entries to scenery.cfg. This is of course only a workaround and hopefully LM will fix the problem as the new method of registering sceneries using add-on.xml is actually very good. I'm confident that we will see a fix sometime as even Mathjis Kok from Aerosoft has mentioned that there is a problem with sceneries using the add-on.xml method. If you want to confirm that you PMDG birds work and are not the source of the problem, then simply install them prior to installing any sceneries. Then they should work just fine. That rules out the PMDG planes as the culprit.

Disable all sceneries which are registered with the sim using an add-on.xml. As stated in a couple of other topics, including sceneries via the new add-on.xml method is currently buggy in P3Dv4. Only use the scenery.cfg for sceneries if you want to avoid that trouble.

Same here. But I think it is really important to check that at some point, because from what I read on several forums, this problem does happen quite often. And only because people get ntdll errors they attribute it to completely different root causes. And I'm absolutely sure that it has to do something with the way sceneries are registered with the sim.

Good point. Indeed, the FSDT and Flightbeam installers create add-on.xmls with seperate texture and scenery entries. What could also be a problem is the total mess with the layers as I'm not sure that all add-ons are fully aware of the layers of already installed add-ons in scenery.cfg and via add-on.xmls.

The thing is that even installing add-ons which register via the scenery.cfg can trigger the CTDs. So it must not only be an add-on which registers using an add-on.xml. And as I mentioned above, it is not driven by a single add-on, because all the add-ons which started the behavior can be used without crashes if all sceneries are registered through the scenery.cfg. So using the add-on.xml method for sceneries must be buggy in the current version of P3D v4. The type of error is a ntdll crash. But this has nothing to do with drivers or whatever in this particular case. The CTDs are can be perfectly reproduced any time when certain combinations of add-ons are used. And as I said. I can use all sceneries without any problem when registering them via the scenery.cfg.

I have to adjust one of my statements: When I de-activate all sceneries add-ons which are included via the add-on xml method, then I can run Pacsim KSLC and Orbx CRM and NRM together. So this might indeed be an issue when using the add-on xml method. Another user over at the Orbx forum stated that Mathjis from Aerosoft said that there is indeed a problem with the add-on xml method. Might be a good sign if an official from Aerosoft has also discovered the problem. Let's keep fingers crossed that LM can fix that problem. For now, I will include all sceneries via the scenery.cfg file as this still seems to work.

I have the exact same problems here. Certain combinations of sceneries lead to instant CTDs right after the scenerio setup screen. And it is only a certain combination that leads to a problem. Just to give you an example: I installed Pacsim KSLC with a proper P3Dv4 installer today and got the above mentioned CTD right after the scenario setup. BUT: When I de-activate the Orbx CRM and NRM region, I can startup the sim without getting a crash (which appeared after the installation of Pacsim KSLC). When I activate the Orbx CRM and NRM regions and de-activate Pacsim KSLC then the sim also works without problems. It is only the combination of the the add-ons which doesn't work. This is completely strange and I am pretty confident that it must be a problem of P3D as the add-ons themselves work without any problem if not combined with other add-ons. Edit: The error is reproducable even without using a single add-on via the add-on xml procedure. Only using scenery.cfg produces the same error.

E.g. I can't use the Orbx Northern Rocky Mountains region when I have Earthsim Isle of Man active. I know that Earthsim sceneries have never been updated to P3Dv4, but the Isle of Man scenery works without any problems (no crashes at all), when I de-activate the Orbx NRM region. So this is clearly an incompatibility between the sceneries. Maybe it has something to do with a somewhat corrupted process when building the scenery indexes. Otherwise, I can really not explain how a UK scenery can conflict with a US scenery... But I think we are getting a bit off topic here. Maybe it is worth starting a thread in the Prepar3d forum.

Only after the latest hotfix.

Good to hear that you resolved the problem. Took me some time to find it out in my case. It is really strange. I have airports which work perfectly, when activated alone. However, in combination with other sceneries I get crashes. @tooting: I have a GTX1070.

I had a couple of ntdll errors on startup lately which were caused by conflicting sceneries. Try to disable all sceneries in scenery.cfg and also add-on sceneries and then try to start P3D. If it works then re-active scenery by scenery. This is really a mystery in P3Dv4 but if you install two sceneries which do not work together (for whatever reason), then you get instant CTDs on startup.

Has anyone had some luck to run the Isle of Man scenery with the Orbx CRM and/or NRM region installed and updated to the latest version? I'm asking because since the most recent update of the NA regions from Orbx, I get an immediate CTD after the scenario screen when I have the Isle of Man scenery activated as an add-on. Deactivating either the Isle of Man scenery and/or the CRM/NRM region solves the problem. But I can't run both at the same time.

Bryan York has finally made a (ridiculously arrogant) statement on the pricing in the FS2Crew forum: That just supports my opinion to never buy anything from them again. I don't like to support such kind of people.