Coop

Yup! We recommend the experimental flight model.

Regarding the G1000, do you have any physical hardware that has an avionics switch that is turned off? Something is causing the X-Plane G1000 to not turn on. With the menu, there is a weird glitch it seems with windowed mode if the window are resized after loading the plane (where the default menu position can be off screen) the bottom edge of the window is draggable, so you can move it around using that.

We are using the same system as the TBM, so that would be the shared reasoning. I believe VNAV altitudes need to be assigned for the pathways to be visible, but I am not positive on that.

We just started this page: https://torquesim.atlassian.net/servicedesk/customer/portal/1/topic/a7a12d04-db0f-4347-9a15-b232956f57b1/article/421724195 and we will try to keep it up to date as we receive bug reports. Besides that, this forum is the main bug reporting forum. We will be working on the rest of the manipulators to get them working ideally in VR!

Is the starter cranking, but it just won't turn over? This can happen (rather easily) if the engine was flooded. The IO-550 is very finicky with getting the right fuel in to prime, too much and it won't go easily. Prime it for a second or two (three max). Then boost pump on, throttle to 1/4", mixture rich and crank the starter. This process works like a charm for me.

Thanks for letting me know - we are glad you are flying now. Hopefully we will have a fix for this pesky bug really soon!!

Just looks like a missing Microsoft Visual C++ redistributable, you can update those following our guide here: https://torquesim.atlassian.net/servicedesk/customer/portal/1/topic/a7a12d04-db0f-4347-9a15-b232956f57b1/article/128188431

Hi Chris, This was just a small oversight as 1.1.1 changed nearly nothing in the main plugin (it was mainly texturing/other changes) - you can verify you have 1.1.1 by the file Version.txt in the main Islander folder.

With a crash like that, might be wise to hit the "Replace" button and get a new airframe. You can also go through and run the inspections along the right side of the screen, the inspections will find any broken bits in those subsystems and replace/repair.

It can be a bit fiddly, I will look into it on our side and forward to the SVS developer if I can't figure out what is going on. For testing purposes, what was the flight plan you entered?

Hey! There is a pesky bug we are dealing with. Can you make sure to try the following steps: Load into the X-Plane default C172 In the plugin menu, go to Gizmo -> Windows -> X-Aviation Licensing Hit the reload license button on the window that pops up. Make sure that the SR22 is now displayed in the list of aircraft. Load the SR22 If that doesn't work, please send the log.txt again after that happens! We are looking into the root cause of the issue with the highest priority right now.

@OuterMarker Are you able to figure out what button presses were able to take you to the broken state? Let me know if you can replicate. We are looking into this as well. Pressing and holding the CLR button for a second or two should restore you to default state, let me know if that doesn't work.

The door can be opened in flight, but it will only go out a few inches cause of the airspeed (based on what the airspeed is, it will get pressed pretty hard to the fuselage). We will be adding this in with the next update

While this is partly X-Plane, its also partly purposely applied (though we will be toning down this effect a bit). In real life, the G1000s get serious glare when the sun hits it at certain angles, what you are seeing is the washed out screens from the sunlight.

Can you try these vrconfig files? It should be improved in many ways (not perfect yet) Let me know what it does/doesn't fix for you! SR22TN_vrconfig.txt SR22_vrconfig.txt

Oh that's interesting, taking a look into that.

@clecorougeAre you on X-Plane 11.50b15? This issue seems like it might be caused by the old 2D broken pipelines that were fixed with b16. If you are on b16, please upload your log.txt so we can see if anything is going wrong there.

Here is a temporary improvement for the VR config, we will be integrating this + more in the 1.0.1 update. Engine start, again, the main thing is to not flood the engine, the IO-550 is very (very very very) sensitive to flooding which makes it very difficult to start. Give it a second or two (3 max) of priming, then throttle to 1/4 inch, fuel pump to boost, mixture rich, and it starts like a charm (nearly) every time. SR22_vrconfig.txt SR22TN_vrconfig.txt

The weight displayed in the aircraft window includes the base airframe weight + the supplements added to the aircraft (in our case, Oxygen, FIKI, and Air conditioning). That makes the X-Plane weight. The additional difference is the weight of the oil on board and TKS fluid. I've noted the request for passenger and luggage weight - we will look into adding that!

You can edit the liveryConfig.cfg file in the livery of your choosing until we get the bug fixed. Just make sure to save the file, then open up the SR22 menu and the tail # field will be populated with what was in the tailNum value of the file.

This appears to be an obscure unicode bug with the keyboard handler, we are looking into it; the "-" key on the number pad should work just fine.

Let me know what you find, we are still digging into this from all fronts on our end as well.

Hi, yes it does. It should be enabled by default, but if it isn't it can be enabled though the PFD: "PFD -> SYN VIS -> PATHWAY"

Can you upload your log.txt file?

We will be adding a GUI flag to make it clear as this was poorly documented, when you run the inspection, the system outputs a custom generated maintenance report. This is viewable in X-Plane 11/SR22/logbook and each inspection will show a report showing what was performed!