September 2, 20214 yr 27 minutes ago, RALF9636 said: Exp version Developed for DEV Version! I have internally already fixed it (there are more changes from DEV to EXP), but I wait some time as I do not want to support two versions. You can change the variables in the scrips yourself: A32NX_EFIS_L_ND_RANGE A32NX_EFIS_L_ND_MODE Guenter Steiner -------------------------------------------------------------------------------------- Betatester for: A2A, LORBY, FSR-Pillow Tester --------------------------------------------------------------------------------------
September 2, 20214 yr 25 minutes ago, guenseli said: Developed for DEV Version! I know. I wasn't complaining. 😉 25 minutes ago, guenseli said: I have internally already fixed it (there are more changes from DEV to EXP), but I wait some time as I do not want to support two versions. Yes, it's definitely a moving target. Give it time to mature. 25 minutes ago, guenseli said: You can change the variables in the scrips yourself: A32NX_EFIS_L_ND_RANGE A32NX_EFIS_L_ND_MODE I'm really a total noob in this regard. So far it was: Write event K: 0-A320 AP-RNG dec Now I changed it to: Write event K: 0-A32NX_EFIS_L_ND_RANGE dec. It still doesn't work, so I must have got this wrong obviously. How do you find out how these variables are called? Is there a list somewhere?
September 2, 20214 yr And thx again @guenseli for the great effort and work. I just played around a bit today but this will change my sim experience forever.
September 2, 20214 yr 24 minutes ago, RALF9636 said: Write event K: 0-A320 AP-RNG dec Now I changed it to: Write event K: 0-A32NX_EFIS_L_ND_RANGE dec. No no no 😉 Change it back, please. Then open AAO --> Scripting -> RPN Scripts editor (new window opens) Left, unfold A320 AP --> double click on RNG dec There you see some code. Don't know the "old" (DEV) code as I'm on EXP as I said, but the new code is now: (L:A32NX_EFIS_L_ND_RANGE,·Number)·1·>=·if{·(L:A32NX_EFIS_L_ND_RANGE,·Number)·1·-·(>L:A32NX_EFIS_L_ND_RANGE,·Number)·} RNG inc is: (L:A32NX_EFIS_L_ND_RANGE,·Number)·4·<=·if{·(L:A32NX_EFIS_L_ND_RANGE,·Number)·1·+·(>L:A32NX_EFIS_L_ND_RANGE,·Number)·} NAV Mode dec is: (L:A32NX_EFIS_L_ND_MODE,·Number)·1·>=·if{·(L:A32NX_EFIS_L_ND_MODE,·Number)·1·-·(>L:A32NX_EFIS_L_ND_MODE,·Number)·} NAV Mode inc is: (L:A32NX_EFIS_L_ND_MODE,·Number)·3·<=·if{·(L:A32NX_EFIS_L_ND_MODE,·Number)·1·+·(>L:A32NX_EFIS_L_ND_MODE,·Number)·} Insert this stp by step and press "UPDATE" to save after every insertion the script. Then, the SD functios should work also with EXP How I do find the variables? You have to crawl through all that code inside the FBW mod (or other addons). Of course I use Notepad++ to search, but it is a very time consuming detective work. Some addon developers provide some variables, but mostly I have to search and gather them step by step. Guenter Steiner -------------------------------------------------------------------------------------- Betatester for: A2A, LORBY, FSR-Pillow Tester --------------------------------------------------------------------------------------
September 2, 20214 yr 13 minutes ago, guenseli said: No no no 😉 🙂 Now I start to understand the concept... 13 minutes ago, guenseli said: ... Then, the SD functios should work also with EXP Confirmed! 13 minutes ago, guenseli said: How I do find the variables? You have to crawl through all that code inside the FBW mod (or other addons). Of course I use Notepad++ to search, but it is a very time consuming detective work. Some addon developers provide some variables, but mostly I have to search and gather them step by step. That increases my appreciation for your contribution even more. Thanks a lot! Btw I do miss AP2 and the right side LS (which are needed for autoland to work as far as I am aware)... 😉
September 3, 20214 yr On 9/1/2021 at 9:22 PM, Fielder said: AAO knows which aircraft you are currently flying in MSFS. so MSFS has to be running everytime I want to change a setting in AAO? AMD 7800X3D, Windows 11, Gigabyte X670 AORUS Elite AX Motherboard, 64GB DDR5 G.SKILL Trident Z5 NEO RGB (AMD Expo), RTX 4090, Samsung 980 PRO M.2 NVMe SSD 2 TB PCIe 4.0, Samsung 980 PRO M.2 NVMe SSD 1 TB PCIe 4.0, 4K resolution 50" TV @60Hz, VR: Pimax Crystal Light + HP Reverb G2 @ 90 Hz, Honeycomb Bravo Throttle Quadrant, be quiet 1000W PSU, Noctua NH-U12S chromax.black air cooler. 60-130 fps. no CPU overclocking. very nice.
September 3, 20214 yr Author No MSFS does not have to be running to change things in AAO. But if it is then you can instantly test the changes. The other advantage of AAO knowing which plane you are in, is that the profile for that particular plane loads automatically and you can test the change instantly. Of course you could make a profile for each plane in MSFS without using AAO. But you would have to change to the options screen to load the right profile. AAO changes profiles as soon as you change planes. Using AAO, most of the assignments for a given plane will the same as for other planes. But you could have any changes you want for that plane in the profile too. Faster or slower trim, a different response curve on the major flight AXIS. Or an assignment to turn on overhead dome lights instead of panel lights (if your plane does not have a panel light (a light behind the gauges), such as the default 152 uses a dome light instead of a panel light. So you can have the same keyboard key that turns on the correct main illumination in every plane. You only have to remember one keyboard key to work the main lights in every plane. Edited September 3, 20214 yr by Fielder 5800X3D, RTX4070, 600 Watt, one or two 1440p 32" screens, 64 GB RAM, 4 TB PCle 3 NVMe, Warthog throttle, VKB NXT EVO stick, Honeycomb Alpha yoke, CH quad, 3 Logitech panels, 2 StreamDecks, Desktop Aviator Trim Panel. Crystal Light VR.
Archived
This topic is now archived and is closed to further replies.