Let me take you point by point:
-
The NG, ITT and Torque figures all based on real aircraft data, captured LIVE from the G1000 units on real flights from IRL M500 pilots flying around world, including Brazil where it is extremely hot. All the temperatures and data you see are exactly as how the IRL pilots see it on new engines with 100 to 350 TBO aprox. Although I understand you might expect some more dramatic figures, the M500 is a de-rated PT6 with 500shp power vs a TBM / PC12 which is 850shp. So the figures you seeing are spot on.. and a simple YouTube video of a M500 flying at FL270 to FL280 would have confirmed this for you.
-
Beta range is moving the blades angle in accordance with PT6 engineering manuals, it starts from 19deg to 0deg and continues progressively until you reach -5 to -8 deg.. once you hit this range the internal FADEC will release all the fuel to the engine and you would move to full REVERSE operation rather than BETA.. please ensure you are calibrating your inputs to use BETA properly, I suspect you jumping to full REVERSE at once rather than moving thru the beta range slowly. I have done all this custom in FSR500.
3.- You must serious be having some miss configuration issue, most customer blow up their engines on take off since the torque can exceed 1450lbs when you put full throttle when the max in accordance to POH is 1313 for 5 minutes.. anytime you exceed this it will blow up the engine if you have full realism settings enabled on the EFB. Check you do not have any prop pitch input hardware binds.. if you do remove them. this is due to MSFS SDK bugs and limits as I need to move the blades myself with custom simulation to achieve the best turboprop simulation on MSFS.
4.- Read the user manual the pressurization schematics are there, done exactly as how it works IRL.. M500 pressurization is based on max PSI of 5.6 and the user manual explains in full detail how it works. IRL Pilots made me code it custom 3 times until it was working exactly as the real aircraft. This is not an airliner, the pressurization is way different..
5.- Yes the sounds are recorded as per the real airplane.. check you do not have headphone noise cancelation enabled in your system, most people complain actually how loud the engine is inside the cabin, but this is how they sound I have pictures of the day we recorded the sounds from the real airplane.
6.- The lights are incredible dim on the real airplane, check videos online and you will see, the IRL pillots made me dim them until it matched what they see. I appreciate you would like them brighter, but this is how they work IRL. Here you have a IRL shoot of how the M500 night lighting looks like:
Full video:https://www.youtube.com/watch?t=219&v=pIzg0eBZPsg&feature=youtu.be
As you can see, I did the lights very realistic.. your expectation is because unfortunately many other 3rd party developers donāt even bother to investigate how to do custom lighting effects and they attach the default Asobo lighting effects, which are designed for airliners.. leaving most airplanes with lights as birght as an Airbus attached to a little plane.. but thatās now how it works IRL. The watts on the lights are very low as your generator, alternator and battery are not as big as it would be on a full 747 for example, battery life is crucial on a turboprop in order to ensure you can start the engine without a hot start.
- The GCU 476 is in a position where is very awkward to be used for the G1000, the angle just doesnāt match, you can use your own PC keyboard already on the G1000 so it makes absolutely no sense to waste resources on enabling this. the H:Events were enabled so people with a real HCU 476 hardware can use their devices and that is in place with the latest update. I am not planning to enable it fully in 3D, two reasons: I) It is in a very bad position and the G1000 supports physical keyboards already which is more optimal. II) The input events to create this are not public available on the SDK, it was done in the SR22 which is encrypted and I am unable to see an example to perform the development work.
It seems to me you are having clear issues with your hardware setup given your symptoms, once again this is not my place for support.. you lucky I saw the post so I could reply since I check this forum from time to time, if you have further problems feel free to contact me via email or discord so we can help you instead of writing this off as a bad purchase because:
A) You have issues that can be resolved with some diagnostics
and
B) Because you donāt understand the aircraft IRL system and your expectations are not being fulfilled despite that the aircraft has been made with over 5 pilots of the real thing telling me every day how things are supposed to work. Everything is explained in the 148 pages user manual and 5 video tutorials all available to you in the EFB with QR codes.
Best Regards,
Raul