Sybull

Whilst I have a Ryzen 5 5600x and 16gb of ram, I am currently running an RX580(8gb) until the GPU market calms down. I adore playing MSFS in VR using it. Yes, it not perfect, by nothing beats flying a Small GA aircraft in VR in remote places. There are some cons to doing this on my current rig: - Have to set the VR resolution at the bare minimum. This makes dials difficult to read at a glance. I avoid glass cockpits for this reason - Frame rates, whilst not high (24fps), are perfectly good enough and don't give me any motion sickness - I have to keep the AI planes etc down to a minimum to keep frame rates up. can make for a quite experience at airports Once you have tried it, despite the drawbacks, it is very difficult, in my eyes, to return to playing it in pancake mode. Definately give it a go. Don't expect to do full on flights with all the bells and whistles. Take a 152 out to iceland at sunset and just chill out. Roll on cheap 3080's !!!

Good to know you are keeping up with the the "challenges" that Asobo and Microsoft are offering . I hope this keeps your enthusiasm going to develop the software. Plenty more button switches and knobs for me to play with and so much to learn within AAO, so I will leave the cabin lighting for a while. Keep up the good work and I look forward to future updates.

Well, That worked . Turns out it was just L:CENTRE_LOWER_panel_light that needs changing and kept in the range 1-9. 👍 Applied my new found knowledge to set the Nav instrument lights. 👍 But then I tried the Cabin light. I found the Variable, saw that in increased in steps of 5 and ranged from 0-100. Applied it . I can see the variable go up and down when I twiddle the knob but the light doesn't dim/brighten in the sim. (L:LIGHTING_CABIN_0,·Number)·5·+·100·min·(>L:LIGHTING_CABIN_0,·Number) When I use the knob in the cockpit with the mouse the same variable changes and it does dim/brighten the light. I went to the Modelbehaviourdebug window and looked under the "InputEvents" tab and found 2 bindings LIGHTING_CABIN_0_inc and LIGHTING_CABIN_0_dec. Executing these in the debug window has the desired effect on the sim I assumed I could find these 2 events in AAO, but nope. I found some event that looked like it might be it and hoped I could simply pass the variable to it after increasing/decreasing it (L:LIGHTING_CABIN_0,·Number)·5·+·100·min·(>L:LIGHTING_CABIN_0,·Number)·(L:LIGHTING_CABIN_0,·Number)·(>K:CABIN_LIGHTS_POWER_SETTING_SET) That didn't work either. Any tips on where/how to find the missing piece of the puzzle ?

I am trying to use x-touch mini to increase/Decrease the panel lighting on the Just Flight PA28 Arrow 3 (3rd part addon aircraft) By using the Developer mode I can see 2 "variables" increase and decrease in the window when I rotate the panel light switch in the cockpit using the mouse. The 2 Variables are (L:Panel_light_scaler,·Number) which increases in steps of .1 (L:CENTRE_LOWER_panel_light,·Number) which increases in steps of 1 My original thought was do have a script run that increments both these variables (L:Panel_light_scaler,·Number)·.1·+·(>K:Panel_light_scaler,·Number)·(L:CENTRE_LOWER_panel_light,·Number)·1·+·(>K:CENTRE_LOWER_panel_light,·Number) Pressing TEST does seem to increase the variables as the second line shows (lets say the developer window is showing the variables at .1 and 1): 0.2 (>K:Panel_light_scaler,·Number) 2 (>K:CENTRE_LOWER_panel_light,·Number) . I am was assuming this line will send the 2 values to each variable. If there was an error in my code the 2nd line wouldn't appear I asume. I set up a Button assignment so the "KEY DOWN EVENT" calls the script and the assigned button is the rotary knob on the x-touch But nothing happens in the sim. The variables showing in the developer window don't charge either when I rotate the knob Am I on the right track or is it going to be more complicated than that ? I feel I am getting the fundamentals of the syntax wrong.

Many thanks for that. Just the sort of tip i was looking for, 👍

Currently, I am filtering then scrolling through the variables / Activities and selecting the ones that look the most likely. I then put them in the script and click on test to see if the variable value changes when i click the switch etc in the sim and re-test I do the same with the events to see if the switch moves when i test it. It is a very hit'n'miss approach, not to mention time consuming. After a while i will post something on a forum and hope I get a bite. Is there a more efficient way of approaching it ? What other methods do people try ?

Has anyone go any tips of how to get the lighting on the PA28 working through AoO and an x-touch-Mini ? With the panel lighting, i can turn the lighting on and of by clicking an encoder, but I can't adjust the brightness by twiddling the encoder. With the Cabin lighting, same story except it I turn the knob on the ceiling (using the mouse in the sim) completely off, then clicking the encoder can't turn it back on. Many thanks

Bingo ! another piece of the puzzle. Will remember this. Makes sense when having more than one engine, so more than one of everything. . Thanks for that insight. Didn't think the Units for variables was a factor but it was the only thing I could see that was different. Many thanks for the assistance. Now I feel confident in getting this to work for me I will be buying the full version.

When trying to establish what variables I need to be checking, In the script editor I put in a list of variables: (A:GENERAL·ENG·FUEL·PUMP·ON,·Bool)·(A:GENERAL·ENG·FUEL·PUMP·SWITCH,·Bool)·(A:PITOT·HEAT·SWITCH,·Enum)·(A:FLAPS·HANDLE·INDEX,·Number) Then I press TEST to see what 4 digits appear depending on what the switch state is in the sim. flicking the pitot switch changes the 3rd digit from 0 to 1. Changing the flap lever changes the 4th Digit from 0,1,2,3 but the first 2 digits always stay at 0 no matter what position the fuel pump switch is in. The one difference between the Variables is that the PITOT is an "Enum", The FLAP HANDLE is "Number" whilst the FUEL PUMP variables are "Bool" . Should I be doing something different with Bool variables ? Or am I just looking at the wrong variables ? When looking at the SDK Documentation the 2 Fuel pump Variables have a red cross in the "Settable" column. Does that mean I can't use them ? All testing is done on the Asobo C172 (G100)

Thankyou for that. I suspected it was not going to be that straight forward (but had to ask just in case it was). I totally forgot about the Developer mode. Will have a look. I might start looking in and placing questions on he JF forum to learn more about that plane's workings.

Only got myself a Behringer x-touch mini yesterday and discovered AAO last night (demo only) for MSFS. Still in the playing around phase but I am looking to buy it shortly. One issue I am having is that, given the large amount of events, how to know which one to use. Is it trial and error or is there a way of clicking on the button etc in MSFS and being able to see what event it relates to ? I am trying to set up Midi controller with the JF Piper Arrow 3 so I can access cabin and panel lights etc using it. There is a lot to learn. 😃

Phew . Good to know. Was hoping this plugin would stop me from having to consider buying propper rudder pedals for a bit....alas not. 🤣

Brilliant ! Will try that.

Since upgrading, I am finding taxing no way near as easy or accurate as with 11.0 with my G920 racing pedals. Is this due to the upgrade, or is there a setting I need to change ?

On v11.41 the default setting for the 2 Avionic switches on the Honeycomb are: 5 : Avionics On 6 : Avionics Off 7 : Do Nothing 8 : Do Nothing In this configuration the top Garmin turns on and off with switched 5 & 6, but the bottom garmin is never switched on. What do I need to set buttons 7 & 8 to ? (Worked fine in V11.00 as there was BUS1 and BUS2 options to choose).