collegeroad Posted June 4, 2017 Share Posted June 4, 2017 Hi, Sorry for posting another EUENG issue I have tried without ORBX at all and all works fine, tried EUENG with default settings and took off after 2 minutes sim crashed, tried with maxed settings the CPU was at 100% could not do anything so hard reset (With and Without add on airports made no difference) something is an issue with EUENG and needs general peole like us to test, beta tester are good and all but sometimes needs a general public to test as well. Ps Never had this Issue in Prepar3d V3 Please dont remove but no doubt will be. PC Spec: i7 6700k OC 4.6 EK KIT 280 custom watercooling Asus Z270F Motherboard Vengeance DDR4 3200OC 16gb Gefroce GTX1080ti Founders Edition 525gb M.2 OS Windows 10 Pro 1tb SSD for Prepar3d V4 Link to comment Share on other sites More sharing options...
Nick Cooper Posted June 4, 2017 Share Posted June 4, 2017 Hello, If you are conducting a test, can you please state what simulator you use what settings you are using the location of the error the nature of the error the aircraft you were using which external software was active the specifications of your PC. Otherwise, your report has nothing in it which might enable anyone to help you with the problem. Link to comment Share on other sites More sharing options...
collegeroad Posted June 4, 2017 Author Share Posted June 4, 2017 what simulator you use Prepar3d V4 Academic what settings you are using Defualt Prepar3d V4 Settings the location of the error BEX64 (sim1.dll), Faulting process ID: 0x207c the nature of the error Have No Idea just know it EUENG as in the US no issues at all the aircraft you were using Default Raptor in Prepar3d which external software was active Active Sky 16 tried without made no difference the specifications of your PC. i7 6700k OC 4.6 EK KIT 280 custom watercooling Asus Z270F Motherboard Vengeance DDR4 3200OC 16gb Gefroce GTX1080ti Founders Edition 525gb M.2 OS Windows 10 Pro 1tb SSD for Prepar3d V4 Link to comment Share on other sites More sharing options...
Nick Cooper Posted June 4, 2017 Share Posted June 4, 2017 Thanks. The location of the error: I meant where were you in England? Then I can go there and see if I also experience the error that you are attributing to the software. The nature of the error: BEX64 (sim1.dll), Faulting process ID: 0x207c I can only ask Google, same as you. Link to comment Share on other sites More sharing options...
collegeroad Posted June 5, 2017 Author Share Posted June 5, 2017 Was taking off from Default Gatwick Airport, seems strange that if I remove EUENG from the scenery library all is well but once it is activated again Prepar3d crashes again Link to comment Share on other sites More sharing options...
Fizzelle Posted June 5, 2017 Share Posted June 5, 2017 3 hours ago, collegeroad said: Was taking off from Default Gatwick Airport, seems strange that if I remove EUENG from the scenery library all is well but once it is activated again Prepar3d crashes again Just thought I would try and replicate your scenario. I had a good flip all around the Gatwick area and no problems to report. For reference I am using FTX Global Base, FTX HD Trees, OpenLC Europe, OpenLC North America, updated ORBX Libraries and all the UK sceneries (except NI). The only time P3D4 has crashed to desktop was when I loaded in an old P3D3 flight plan created by Plan-G. Otherwise it's as stable as anything! Link to comment Share on other sites More sharing options...
collegeroad Posted June 5, 2017 Author Share Posted June 5, 2017 I Uninstalled/Reinstalled EUENG yesterday and I have activated all the UK Regions and OpenLC areas and took off today and all seems fine but I will monitor it over this week with things and see if it replicates itself again Link to comment Share on other sites More sharing options...
Richard Lincoln Posted June 6, 2017 Share Posted June 6, 2017 Hi, Thanks for reporting back. Glad all is working well now Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.