Coop

Hi Andrew, The autopop function is triggered by the RSG plugin calling for it, so while positions and etc. can be saved the automatic popouts are only triggered with RSG hardware. The standard commands for popouts (see in the X-Plane command browser, under the "afm" prefix, can be bound to either hardware keys, or you can trigger those commands from a script if desired.

Thanks for the log.txt. I've got a fix for this that should address it in the 1.0.1 update (should release in the next few days, we are wrapping it up now). If it continues there, do let me know. On the DA40NG operations, something to note with the fuel system is it is highly unique. I'd recommend checking out a DA40NG POH (there is one here) to learn more on the operations, but on this specifically, the fuel selector doesn't pick L/R/Off like most, it is Normal/Emergency/Off. For cooling a bunch of fuel is passed to the engine, and a majority is pumped back, through a line in the right tank, into the left tank. In Normal mode, fuel will pump from the left and the behavior is traditional. In Emergency mode, fuel will pump from the right, but the excess still goes into the left tank, causing fuel to inadvertently transfer. The preferred method of operation is to stay in normal mode, and then use the Fuel Transfer switch on the panel to get fuel from the right to the left tank when an imbalance is spotted.

Hi Herbert, I see that repetitive nuisance log message in there, but that shouldn't be the cause (I've fixed it for the next update to not repeat that). I'm unfortunately not seeing anything in the log.txt to help. Are you able to replicate this?

Hi Aglos, Regarding SVS, it does not. We may add it in the future, but right now that system isn't the most stable for X-Plane 12. Regarding Maintenance, that is not featured but mainly due to the differences between the SR22. SR22s are common for owner-operator situations, as such maintenance is a huge part of the ownership experience. With the DA40NG, this aircraft is more designed to mimic the typical experience found with that aircraft -- rentals and flight training. We focused on the components that are most relevant for those situations.

Hi, From the log, it appears you are loading the default Laminar Research SR22 and not ours, the TorqueSim SR22.

I've got those logged and will be looked into. Thanks for the report!

Press the right side knob to get the cursor to show, then rotate the outer knob to highlight the Pressure section. Once there, use the inner knob to change the value. When HPA is selected, click "ENT" to set it.

In order to debug what is going on, we will need 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 libacfutils fix shows promise as a stable workaround. We'll be deploying updates for our products with that implemented soon, targeting early June.

I'm guessing X-Plane isn't set to Rosetta mode so as Pils mentioned, Gizmo wouldn't be running to activate the aircraft.

We can't replicate this on our side, but if you can load a default airplane first, then switch to the SR22, that is a fix that seems to work for some other airplanes that have seen this issue.

I believe the difference here is the wing generation. The G3 had the "G5" wing for the latter part of the production which has the increased fuel capacity. We've modeled the newer wing.

Engine sounds are improved in the coming 2.0.1 update. Are the audio panel lights not working on the 3D cockpit and/or the RSG hardware?

Regarding the crash in X-Plane 12, it appears it's the bug with SVS we are seeing with some platforms with X-Plane 12 and Mac drivers. Disabling SVS will fix the issue, we have instructions in the v2.0.0 release notes here: Regarding the installation errors, the path seems to be an abnormal location for the X-Plane install. X-Plane typically works best when installed in a non-protected folder, such as Desktop or Documents.

Yes, same thing.

The cover should be in the copilot pocket. Clicking on it should return the cover. The aircraft is persistent, so make sure to place the covers and tiedowns at the end of your previous flight, while also make sure to not select the option in X-Plane to start with the engine running.

Something appears to be conflicting when we spool up a second thread to handle the configuration file asynchronously. I'm guessing that something else on the machine is preventing this from happening. Given that this is an isolated issue, I'd recommend checking: Make sure there isn't some overly active antivirus on your machine killing the process upon writing to disk Temporarily remove all of your 3rd party plugins in Global Plugins (of course, keep Gizmo to activate the aircraft) to see if one of those is causing a conflict.

There are two main potential sources of the issue and it depends on the symptom. Is the propeller turning over, it just doesn't seem to ignite, or is the propeller not spinning when running the starter? If the propeller is turning: Verify the fuel selector is to L or R, and that the tanks have fuel Prime the engine for max. 2-3 seconds before starting (full throttle, full mixture, then prime for 2 seconds or so. Too long can flood the engine. Pull back throttle, Set the fuel pump to boost Set throttle to 1/4 inch, in the virtual model. If you have a hardware throttle, this is going to be much less than 1/4", as nearly all sim throttles have significantly less throw than the real SR throttles. Engage the starter. If it doesn't turn over within a few seconds, slowly oscillate the throttle up and down a bit. If the propeller is not turning: In the SR20 -> Aircraft window, charge the batteries Perform maintenance via the maintenance tab of the same window. You can also via the same menu change the starter type. You may have more luck with one over the other.

Hi G. From the log file, it appears that the main systems file does not exist on the system. I'm guessing some overactive antivirus on the machine flagged it false-positive and deleted it.

In order to debug what is going on, we will need 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?

Odd, I'm glad it is working now. Not sure what happened previously from the prior logs.

The plugins between the two aircraft, so the crash would result from the different settings. I'll see if we can figure out what is going on with the flickering though.

Got both reports logged, thanks! T-1879, T-1880 to keep an eye out in future release notes.

Popouts can be opened from the RXP GTN menu under plugins. Regarding the glide slope, the airplane will just follow what the GTN sends to the HSI. What was the HSI showing for the glideslope indicator?

From the logs, I'm seeing SVS still enabled, disable it by setting "svs" to 0. If disabling that doesn't help, try also setting "disable_mtuploader" to 1 as well in settings.cfg. The settings.cfg file to change is located at: X:\X-Plane-12/Aircraft/X-Aviation/SR22 Series/TorqueSim SR22/plugins/sr_systems/settings/settings.cfg