Peekstra

I'd love to get it working as the video's look very impressive and I've now got a GTX 970. FSX isn't installed anymore so I can't look there how the scenery needs to be configured in my case. Regarding the support something did go wrong on their end because I sent a message 10 days later after the first one how things were going along and didn't receive a reply. I'm not angry with them because I know it's a very small company trying to to do their best but it shouldn't happen when you run a ticket system. Hmmm... it seems that I have to start mailing them again as the first contact was at the end of august. EDIT: I just fired up the ESI installer and noticed that they're working on the P3D installation to be directly supported. Maybe I'll just enjoy the Europe LC and the Milviz Beechcraft 350 first until it's fixed.

Well, I never got Isle of Man to work and didn't receive a reply from support. Guess I'll give it another try in the next couple of weeks as they mention that you should retry contacting support (if you don't receive a reply within 72hours). Native P3D installer support would really be appreciated!

When starting P3D I got an automatic update message from objectflow, very nice!

Why is it recommended to revert to the pre-hotfix build of 2.2? The LM download page states that the 2.3 update should be compatible to both versions...? Prepar3D® v2.2 to v2.3 Academic Patch – Only use if you have version 2.2.10437.0 or 2.2.10438.0 installed!

I haven't used cloud shadows yet due to performance issues. However, in the screenshot in #254 it seems that the shadows don't properly cover the airport runways and taxiways. It can be seen on some parts but most of the time they seem to be cut off were the tarmac starts. Is this new to V2.3 or due to some of the settings being tested?

Is there any news about the release date now it's almost august?

Hi Tom, I also got the error a couple of times with a perfectly clean re-installed Prepar3d so for me, the problem seems to be in P3D. But the error can probably be triggered by addons as well. At the moment I have all my addons installed again (no ASN), and I've not seen it in the last three flights. But maybe that's because they were a bit shorter. If only the error could be reliably reproduced... Peekstra.

Hi Jim, thanks for your reply. To be 100% sure I've already gone down the uninstall everything route, cleaning everything up, disable UAC and AV. So I already came to the conclusion that the fault must be in P3D itself. I've made a detailed post at the P3D forum and hopefully they'll be able to pick it up, reproduce it and implement a fix. I urge everyone who has the same problem to report it there as well (after doing the disabling stuff to diagnose it). It's great to have an opportunity to directly inform the developers so let's use it! best regards.

I don't think that the actual DLLs can be corrupted by installing third party addons because they're digitally signed and automatically repaired by the system. However, it might be that a specific P3D bug might be triggered by a different version of the (in my case) msvcr100.dll file. The fileversion, which can be found under the explorer properties - details tab is 10.0.40219.325. You can also look this up in the eventviewer at the time when P3D crashed. It lists the actually used version. The filedate of the msvcr100.dll file in my system32 folder is from 2011 so it doesn't seem to have be replaced with a different version. This should be the used version in my case because the P3D folder doesn't containt the file. So if someone could look this info up we can check if we're running the same version, or not. I also ran the command sfc.exe /verifyonly to check for any errors in my dll's and other system files. All files were verified to be 100% OK and no repairs were necessary. thanks!

That's a good solution! :smile: Thanks for the quick info.

Just to make sure: I currently don't have an OpusFSX license and if I buy that now I'll have to buy an upgrade to use the (soon to be released?) FSI? thanks!

I just did a flight from EHAM to EDDI and Prepar3d didn't crash. So the FACT - FAUP route might be triggering the problem for me.

I guess that the only option left is to report in the Prepar3d forums and hope that a developer will be able to reproduce it.

Just a quick followup: I removed everything and did a basic install without any addons. Flying a built-in plane from FACT to FAUP and after more than an hour the error popped up again when I got close to FAUP. So it turns out that it isn't caused by any addon but probably directly related to a problem with the sim itself.

Same problem here, with only these addons installed: - Piper Cheyenne X (not working) - Real Air Turbine Duke v1.2 - REX 4 - Textures - Demo install of ASN NEXT BETA for Prepar3d (not activated yet) I'm currently uninstalling everything including my AV scanner to do a full clean install. Hopefully, it will be gone. Debugging will be very time consuming, the error can take up to two hours to occur. <_<