@ both Demarques and Appliance

 

Assuming you are running P3D from "Prepar3D.exe" and not as simuated FSX, and the exe is set to run as admin...

 

Tell your anti-virus not to monitor the "Prepar3D.exe. Malware bytes is known to cause the issue.

 

Open "fsInsider.ini", change "Debug=0" to "Debug=1" and save.

 

Immediately after the crash, locate and send a file named "fsInsider.log"

 

Thanks

 

 

Well i must say that some weird things are happening with me lol

 

Fisrt thing i did was disable the AV (windows defender)....and crash

Second reinstall MCE again, copied the ini and dll, checked the dll's in the folder...and crash

Enabled the debug=1...and crash and no fsinsider.log to be found anyware !!??

Renamed the fsinsider.dll to disable-fsinisder.dll(just to be sure there was no other thig causing the crash)...and no crash

And was about to reply to your message and renamed again to fsinsider.dll, and guess what??...no crash and MCE is working with no problems lol im sorry i have to laugh because none of this makes sence to me...

 

For now i have MCE working, and im a little scared to install any other addon!!!

 

Anyway, thank you again Gerald, your are always available to help, just please check that situation with my email, if possible.

 

Regards.

sorry i have to laugh because none of this makes sence to me

 

Neither does it to me. You've go to love computers tempers.

 

Windows defender, Security Essentials, AVG, Norton should be OK. Right now it's Malwarebyte the offender + Avast which tends to trigger false positives on "mce.exe" (even though the file is digitally signed as coming from FS++). It puts it in the vault, thus affecting the Demo for those having that AV installed.

 

By the time they realise what's going on, the number of allowed runs goes significantly down.

 

We are thinking about hiring a drone to take care of some business.....

Neither does it to me. You've go to love computers tempers.

 

Windows defender, Security Essentials, AVG, Norton should be OK. Right now it's Malwarebyte the offender + Avast which tends to trigger false positives on "mce.exe" (even though the file is digitally signed as coming from FS++). It puts it in the vault, thus affecting the Demo for those having that AV installed.

 

By the time they realise what's going on, the number of allowed runs goes significantly down.

 

We are thinking about hiring a drone to take care of some business.....

 

hahaha tell me about it Gerald computers are my life, and i've seen some pretty strange things...but they are always right.

Since you are referring, i do have malwarebytes installed, but the free version with no live scan... and even when i run the manual scan it never caught MCE!!

Yesterday i installed 2 new add ons, a scenery and a aircraft, and things stayed working well, but i didn't use the estonia migration tool, wich i believe can have some interference on this.

 

Regards

2.6.46 Version.

 

Had regular crashing. Installed the newest version. Only thing appeared to work was to change dbug=0 to debug=1.

 

The voice recognition seemed very slow to start up and thought it was a bug but it eventually started up. I'm a little unsure of the stability. What exactly would the debug=1 do because that appears to be what got it going from the crashing?