Coop
-
Posts
1,667 -
Joined
-
Last visited
-
Days Won
64
Content Type
Profiles
Forums
Latest X-Plane & Community News
Events
Downloads
Store
Everything posted by Coop
-
We haven't pushed an update yet, but to fix it you can make a minor manual mod for the time being: Open DA40NG.acf in a plaintext / code editor, on both lines 26684 and 26685, change the value from 1.000000000 to 0.000000000 -
Turning down the "Environmental" sound slider in X-Plane settings will help for now. We have it adjusted for the next update which is in the final testing stages.
-
Nothing to share on it at the moment.
-
For retail, it isn't currently planned. For our Pro & ATD users, we do have a solution available.
-
Not at this time. X-Plane 12 doesn't make weather information available to draw weather cells on the mp.
-
It sounds like the engine state file may have corrupted during that crash. You can reset the state by deleting the State and Record files in X-Plane 11/Output/SR22
-
I see what looks like a click spot in your screenshot attached (it is slightly offset from the main circle, but can be seen behind the center of the knob. Which aircraft integration is this?
-
With X-Plane 12, glass sometimes doesn't show clearly with low rendering settings
-
Braking action is largely controlled by how you've calibrated your brake pedals. The braking force will be proportional to the pedals if calibrated properly.
-
Yes, you need to enable the option for the GPS DTK to be automatically set. This setting needs to be set in Plane Maker for the aircraft being used, Systems -> Auto Adjust CDI to GPS DTK.
-
Press the center of the right knob if the cursor isn't showing, when on a selection, you can use the inner knob to adjust the value for the brightness, the outer knob will scroll through the list.
-
Check this thread, I believe it is related to this issue:
-
This is an issue with X-Plane, certain graphics cards, and the SVS system. Keeping SVS disabled is the only option for now.
-
Xplane Failures on TorqueSim SR22 don't seem to be working
Coop replied to MMK's topic in G1000 SR22 Series
User-triggerable failures are only part of our Pro licenses (the maintenance and wear-based failures are still part of the retail version). -
The data sources for the G500 are not adjustable. We do read from the X-Plane datarefs largely, so for certain datarefs, if they are write-adjustable by X-Plane, theoretically you could override them and then what you set there could show, but that isn't something we officially support.
-
Our X-Plane 12 products require the latest MacOS version, Ventura (13.x).
-
If you are trying to use the version of the Islander with the G5s integrated into the virtual panel, there is a separate aircraft file to load, that is labeled (G5) in the X-Plane aircraft selection interface. If you don't see that option, try re-running the Islander installer.
-
Currently all X-A products need to run on Rosetta mode w/ Apple Silicon due to the Gizmo plugin from X-A that handles product activation.
-
Dual cue isn't currently a feature we simulate.
-
This isn't a feature that is simulated by the X-Plane X1000, which handles all of the navigation for our G1000. At this time, LR does not provide any mechanism whatsoever for us to modify their navigational behavior in the X1000.
-
We have a pending bug that has been filed with Laminar Research on this, it is a bug on their end.
-
I would not recommend changing that setting, as it can cause significant issues with the autopilot response tuning. If it isn't causing you other issues, you can keep it, but just something to be aware of.
-
Reality XP GNS 430 Issue in Torquesim SR22TN Entegra
Coop replied to mattwlkr1's topic in Entegra SR22 Series
Those settings appear correct. I'd recommend making sure you are on the latest RXP GNS version. If it continues, can you send a video of what you are seeing? -
Sensitivity of your hardware trim wheel isn't something we have control over. I'd recommend checking your calibration and seeing if X-Plane provides any options, but I'm not familiar with that in particular.
-
In g500.cfg for the aircraft where you installed the G500, change the "v_config_*" values to the KIAS speeds for that aircraft. The V-markers and airspeed ranges will adjust as appropriate based on the entries there.
