Protection failure. Please reinstall product or contact support.
-
@Martyn said in Protection failure. Please reinstall product or contact support.:
Thanks for all the information on this. The more information we have, the better chance we have of tracking down the cause(s). Always a challenge when it's working fine for us!
Can anyone encountering the issue please confirm exactly which version of P3D v4 or v5 is being used, which OS and which install location (Add-ons or P3D directory), and whether P3D is being run in admin mode.
I'm using:
-
P3D v5.1 HF1 (5.1.12.26829)
-
Windows 10 Pro Version 20H2 (Build 19042.630)
-
Both install locations tried
-
Sim is set to run as administrator through compatibility settings (FSLabs Configurator overrides any setting for this)
-
-
Seeing the error from time to time but switching even between liveries working fine to get it going:
P3D v5.1 HF1 Windows 10 Pro Version 2002 Addon Folder Sim is set to run as administrator
Cheer
Thorsten -
Thanks all. This remains our top priority and was a bit of a mystery given that this product uses exactly the same systems as all our products for many years.
It'd be great if you could try a few tests for me - http://tiny.cc/spr5tz
In turn, move each of those test gauges into \SimObjects\Airplanes\JF_146-100\panel, overwriting the existing file, and then load P3D to see if there is any change to the issue.
Also, if you don't already do so, please try right clicking and running P3D in admin mode even if the properties are set to run in admin mode.
-
P3D V5.1 HF1
Win 2004
Sim is set to run as AdminstratorInstalled to Addon folder
1.1 update - protection failure
Test A - protection failure
Test B - protection failure
Test C - protection failureEven tried it by right clicking -> run as admin which doesn't matter but for sake of request I did it anyways.
Reinstalled to Sim folder
1.1 update - protection failure
Test A - protection failure
Test B - protection failure
Test C - protection failureEven tried it by right clicking -> run as admin which doesn't matter but for sake of request I did it anyways.
Loading default plane then the 146 results in alarms that won't shut up.
Kind of bums me out since I got it for my Birthday.
-
@Martyn said in Protection failure. Please reinstall product or contact support.:
Are you able to provide me with a recording of the alarms that can be heard?
I'm seeing two things.
If I load BAe first, then load Raptor, then load back to BAe I get this weird alarm.
Video URL: https://imgur.com/a/5Y9FkWf
If I load Raptor first, then BAe, I get no alarm but I am getting what I think is the engine starting sound constantly repeating. It's happening even in cold/dark.
Video URL: https://imgur.com/a/Fkm4L2o
-
Thanks for the videos!
Please move this version of the gauge into \SimObjects\Airplanes\JF_146-100\panel, overwriting the existing file, load P3D to see if there is any change to the issue and then send me the JF_146.cfg file from within the %AppData%\JustFlight\JF_146\P3D\ folder (either PM me the results or send to martyn@justflight.com).
-
@Martyn It seems to be many different alarm sounds depending on which plane you try. Different sound for 146-100 and different sound for the 146-200, often even different alarm, crashing sounds for different liveries. And when I try to reload the sounds from your drop down menu the alarm sounds double. The only way to stop it is when I disable the sounds from your dropdown menu but I then lose all the custom sounds ie: switch click sounds. Hope this helps.
-
@Martyn said in Protection failure. Please reinstall product or contact support.:
Thanks for the videos!
Please move this version of the gauge into \SimObjects\Airplanes\JF_146-100\panel, overwriting the existing file, load P3D to see if there is any change to the issue and then send me the JF_146.cfg file from within the %AppData%\JustFlight\JF_146\P3D\ folder (either PM me the results or send to martyn@justflight.com).
Sending you the CFG via email -- same issue; getting protection error.
I did this with the 1.1 update file above but not any of the test gauge files.
However, loading Raptor then into BAe seems to fix the weird sound with constant engine startup.