Coop

Can you to send us a copy of the X-Plane log.txt file? You can find a guide to get this file here: How to find the X-Plane log.txt file?

The in-sim popups will show centered around the mouse cursor. If you have RealSimGear hardware, the RSG plugin should communicate with the G500 to auto-pop-out to the hardware automatically.

Correct, no stability augmentation should be used.

Something you can try, in the aircraft -> plugins/sr_systems/settings/settings.cfg, you can set disable_mtuploader to 1.

From the looks of it, the OpenGL layer while running in Vulkan is not functional with that GPU driver. You can try without Vulkan enabled and see if that fixes things, but that is an unsupported hardware arrangement on our side, so there isn't anything we can do.

CG stands for center of gravity

In the real aircraft, you'd make sure there is resistance to pushing the brake pedals. In this, just test the brakes by immediately using the brakes (testing both wheels independently) after first rolling before you get going too fast.

Most likely something is triggering the warning/caution during X-Plane start.

There wouldn't be a default aircraft type you can select for this -- the airframe is based off the Impulse 100, but this is highly modified with many times more performance (and fuel flow). Closest aircraft in SimBrief would probably be a TBM?

It is on the list to look into still, hopefully should be soon, we've had some other projects that have taken priority recently.

Yes, the G1000 is using the X-Plane G1000 with modifications with has its differences. We are looking into options to do a P+ system down the road, if we find suitable options, we will look into doing G6 options.

Hi Lennard, The G5 just follows the main X-Plane heading bug, so the default X-Plane heading commands should work. In X-Plane configuration they are under Navigation & Radios -> Autopilot -> "Autopilot heading up" and "Autopilot heading down"

Regarding the ELT, it would be in the virtual 3D cockpit to turn it off, I don't believe there are hardware switches for it with their setup. Regarding the engine, I'm not sure what would have caused that, but good the overhaul worked.

Regarding the alarm, does it sound like the standard G1000 warning bell, or does it sound like an ELT siren. If it is the ELT siren, you can turn off the ELT switch located near the circuit breaker panel in the pilot's footwell. Regarding starting the SR22, there are a few important guidelines for starting the engine successfully: Don't flood the engine. 2-3 seconds of priming is plenty When starting, keep the throttle at 1/4". If it doesn't start, slowly oscillate lower and higher until the engine properly starts If the engine doesn't turn-over properly, the plane's battery could be dead -- it can be recharged from the SR22 menu -> Toggle Aircraft Window -> Recharge Batteries.

There is not

Which distro of Linux?

Thank you for the kind words, I'm glad you enjoy our aircraft! We don't have SR22T plans at the moment, but maybe in the future.

We don't use the X-Plane engine model whatsoever, we are setting the override flags with X-Plane so we provide the engine forces out to X-Plane. From my understanding, X-Plane still runs the underlying default engine model in the background (that doesn't do anything with the rest of the aircraft) and what you are seeing here is whether the default engine model run. If OneAir has any other dataref that can be set for the engine status, I can look into that, but if all they are looking at is a non-writable dataref there isn't anything we can realistically do that wouldn't add a whole level of complexity to the product.

That dataref isn't writable by us, only X-Plane so there isn't anything we can do about that, that isn't a circuitous workaround. Is this in regards to a third party add-on reading this dataref?

We really don't understand what you think the issue is here. I am not seeing anything wrong from the screenshots you sent and I do not understand what you are saying. I'm happy to help sort the issue, I just truly don't understand what you are saying.

I really am not understanding what is going on. You would need to go into FPL to enter the flight plan. The G1000 flight managment system is part of X-Plane (see their manual here: https://x-plane.com/manuals/G1000_Manual.pdf), not the SR20 itself.

The flight plan doesn't sync with anything, you'll need to input it manually. If you are trying to go from YVR, you can hit the Direct To button, enter YVR, then hit ENT to go there from your present position.

Oh my, that explains a lot! These settings are significantly higher than they should be for your computer's spec. Some settings to change: Texture Quality. Try lowering down a notch or two (or three). Right now X-Plane is trying to load around 10 GB of textures into VRAM (much beyond what your graphics card has) so lots of texturing paging would be going on, slowing everything down significantly. World objects at high: If your CPU is a bottle neck, lowering this a notch should improve things Visual effects. If the GPU is still the bottle neck, lowering this a notch would help

I am not sure I understand what you mean, can you send a screenshot showing what you are referring to? Regarding Vancouver, the airport ICAO code is CYVR but the collocated VOR-DME's code is YVR. The G1000 navigation system is a part of the X-Plane simulator and handled by Laminar Research, we just load it in from X-Plane. It is not a 1:1 representation of the real G1000 units.

Clearly the sim is extremely bottlenecked. The combination of graphic settings + scenery + other plugins is beyond what your computer can handle. Anything below 20fps with the sim will start to breakdown the X-Plane physics model and you'll run at slower than real-speed. If you can upload a screenshot of the full X-Plane graphics settings I can take a look.