crap_landing_dave

Perfect! Working. Needed to update and RTFM.

Thanks Lorby for all your help on this, and for a quite superb product. I have it doing all sorts to maximise my hardware on various aircraft. Got one question for you. When you posted the condition lever bvars, did you also successfully find you could write to them? I'm using the map lvars to bvars method and have the correct inputs going into my local lvar. I can also 'sync lvar with bvar get' and can see my lvar changing correctly between 0,1,2,3 when I move the condition levers by hand. What is not working though is me writing to the Bvars. Any common mistakes there? I'm doing this in mapping settings, activate profiles, then restart the sim for each test. Hook is enabled. LVar: (L:AAO_Fuel_Condition_Lever, Number) - this is working, I can move my axis and see this updating correctly. BVar get: (B:ENGINE_FUEL_Lever_Mixture_1) BVar set: (L:AAO_Fuel_Condition_Lever, Number) (>B:ENGINE_FUEL_Lever_Mixture_1_Set)

@Chapstick once you've collected the Lvars then you find them when you go looking for, for example, a key down event. There are a group of events called "Local simulator variables"

Thanks for this. Having only recently moved to MSFS I've got to do some reading on BVars, but that technique of looking into the developer menu is another one I can chuck into my things to try.

Hi, love this product more every time I use it. Was very pleasantly surprised how well this could watch for (and avoid spam on, awesome feature) events for the 737, and I've had just as much luck with the 310 today, mostly thanks to the ability to gather all LVars (really great feature again this one). Of the ones I care about to map to my Warthog, I found all of the ones below. Most are very obvious apart from the ones in square brackets so you can easily dig them out using Scripting>Read LVars from sim, then waiting a bit until they are recorded, and then you can find them under "Local simulator variables": Seat belts, no smoking, Landing Lights, Turnoff, Taxi, Beacon, TCAS ["A310-tcas_mode_pedestal' set to 0,1,2,3], chrono ET ["A300_CHRONO_ET_STATUS"], AP disconnect ["A310_AP_DISCONNECT_BUTTON] The one I haven't had any luck with is strobes. I can only find two variables and I can change them with my hardware switches, but they don't cause the Strobe switch to move. Anyone got to the bottom of it?

I rolled back to a previous acronis backup of Windows from a few days before the update, and changed the group policy to prevent updating. That was ignored, obviously, and left me back at square 1. Ended up instead restoring just the d3d9.dll in system32\ from the pre-update version, and it's working fine.

Just a +1 here on lower frames and occasional blurry textures after 2+ hours of flight. Didn't see any obvious problems with VFR A2A Cherokee, but with the performance heavy jets in my case. The issues I've had are gone after reverting to 4.4, so I'm hanging on for the hotfix.

Thanks for this config. Very helpful to just get something close when you install an AAL livery with apparently no other settings to make it run like one.

This looks interesting to me. I love the effects I'm getting out of most of the presets I've tried, but I find it a bit hard to navigate around unfamiliar airports at night due to (no doubt realistic) darkness levels. Was there a fix for this? Matt if you prefer the email route I can easily do that.

Actually he said it was at least 5 figures. I don't think he'll be booking any holidays in St. Lucia today or any time soon. For me, it's a simple case of not having the time to get the display looking great myself. I downloaded PTA tweaks and a config file posted on his twitch channel some months ago in P3Dv3, and my enjoyment of flying went up easily 10-15% just based on the aesthetics I now have. I'm prepared to pay for that to continue in v4, and some may not. You can choose whether you're in or out. For the poster who asked about entering the activation every time on startup. I have the same issue. Hopefully that can get sorted soon.

Wow, thanks for this. I had all kinds of buttons programmed and redoing the ini would have been a nightmare. Opened the old .ini, changed "FixControlAccel=No" and all is well.

Thanks. This does look like the exact same issue. I'm not sure if I want to go through the solution steps every time. Just thinking out loud here but presumably there's a way to find out exactly what command gets executed for those Airbus lights. If I can get those I can enter them in FSUIpC.ini where I have a shift mode working properly with a memory offset.

Hi, I'm really impressed with the Linda tools. I only installed yesterday and have found it has perfect access to all the things I couldn't find on the airbus easily through FSUIPC. I'm using P3D 2.5, FSUIPC 4.944a, Linda 2.6.4 and the Airbus module 4.3 v2 Here's my issue. I assign buttons according to a 3-position mode switch on the Cessna yoke which is recognized as button 23, 24, 25 UNSHIFTED: Button 23: Unshifted Button 24: Shifted 1 Button 25: Shifted 2 1: Button 23: Unshifted Button 24: Shifted 1 Button 25: Shifted 2 2: Button 23: Unshifted Button 24: Shifted 1 Button 25: Shifted 2 I have no repeats and no release settings On a chosen button I have these settings for my modes as a test of external lights: Unshifted, button 16 = Landing Lights toggle Shifted 1, button 16 = Beacon Toggle Shifted 2, button 16 = Taxi Light Toggle If I restart the Lua engine in unshifted mode(button 23) and hit button 16, the landing lights work OK. If I move to mode 1, I get this in the console window, and the beacon lights work as expected: LUA.0: SHIFT MODE = 0 LUA.0: local shift 1 LUA.0: SHIFT LIM 06A30BD30 Mode = 1 I then proceed to move to mode 2, and I get this in the console window: LUA.0: SHIFT MODE = 1 LUA.0: local shift 2 LUA.0: SHIFT LIM 06A30BD30 Mode = 2 However button 16 still activates the beacon lights (taxi lights expected) Rocking the switch back to Mode 1 again gives me this: LUA.0: local shift 1 LUA.0: SHIFT LIM 06A30BD30 Mode = 1 LUA.0: SHIFT MODE = 2 Beacons still active here (correct) and finally back to unshifted gives: LUA.0: local shift 0 LUA.0: SHIFT LIM 06A30BD30 Mode = 0 LUA.0: SHIFT MODE = 1 and beacons again (landing lights expected) So unshifted seems to work initially, but as soon as I move to mode 1, I can't seem to get out of it. Can you see where I might be going wrong? Sorry for the long post. I was hoping as much info as possible would help.

And me. Just wanted to affirm and offer thanks for the solution.

Just one more +1 to the officially posted solution here. One thing I did without issue was first back up my FSUIPC.ini file, then carry out the instructions. Once the weather radar displayed fine (it did first time with the fresh FSUIPC install), I restored the backed up FSUIPC.ini file and got all my mapped controls back as well.