Coop

I haven't seen that one before. I am guessing there is a conflict with a different plugin you have on your machine. You can try going through those and temporarily removing them to find the culprit.

This is most likely due to a combination of two things: Flooding the engine. Prime the engine only for ~2 seconds. Anything >3 seconds can start flooding the engine which makes the starts very difficult Use less throttle. The throttle needs 1/4" of throttle on the real plane. Most X-Plane throttles have much, much less travel than the real aircraft's throttle. This might mean you need to use 1/8" or less of throttle to accurately depict the throttle setting.

It should be powered on by default. You can try the Avitab default 2D popup and turning it on there to see if that fixes it?

Yes, it is being worked on currently

@Bakerz82Do you have the Avitab plugin installed?

@RequestDeniedThe afm category will only show when the SR22 is currently loaded in-sim. If you are accessing from the main sim menu before loading the plane, X-Plane won't pick up our commands.

Something seems to be messed up with the install. Can you delete the files inside the X-Plane 11/Output/SR22 folder? This will reset the engine and physics model to new.

@Tomatl Most likely the engine is being flooded, I would recommend trying a flooded start procedure. If you check the "start with engines running" option in the X-Plane main menu, the aircraft should start with the engine running.

Right now there isn't, but it is on our list!

The ALT2 warning will show at lower RPMs as the alternator will only engage at higher speeds (unlike ALT1). I am not sure on what is going on with the oil pressure, you can go through the maintenance dialog and select the various systems to inspect (throughout he TorqueSim meeting).

They can be found here: https://afmsim.com/g5-user-guide/ (There is also an integration guide on the same site, check under the G5 tab)

Thanks for the log, the appears to be a bug within X-Plane itself.

Does this replicate if you try loading again? If so, can you share the full log.txt file?

As I mentioned above, when Librain is updated for 11.50 we will integrate it.

Hi, We have only modeled the Perspective system (as that is what shipped with the G3) with customizations over the base G1000. The numeric keypad works can perform standard GCU functions as implemented by LR. Make sure you are on X-Plane 11.50+ to have the GCU be functional. Regarding a crash, I would need to see the log.txt file to know what is going on with that.

The only active date that relates to nav-data is the Aviation DB line. I have not seen the "(null-2020" error before but will look into it. Taxiway signs will not show on synthetic vision, it will show runways and terrain only. The actual navigation system is the default X1000, so if flight planning, etc. are working, you should be fine.

Hi Cassio, The maintenance record logs will be output to the X-Plane 11/Output/SR22 folder with details on the maintenance action performed. We have it on our list to bring this in-sim as well.

Hi, We have a fix in the works for this, for some reason it looks like those manipulators were offset to the right of where they should be. You can click on these clickspots as shown below until the 1.0.1 update is out.

That sounds like something might have broken the physics <-> systems plugin interconnect. If it happens again on load, try restarting the sim and seeing if a reload fixes it.

Rain effects will come with Librain Vulcan compatibility.

Thanks

Different GPUs handle lighting differently, but yes, HDR lights in X-Plane can cause a performance dip.

The difference in altimeters is expected, as the G1000 is based on the Air Data Computer (ADC) outputs, while the standby relies solely on the pitot-static system.

Odd, thanks for the log. We will look into it.

Hi Vu, Yes the aircraft works in VR.