smoothchat

My solution to control all the Latécoère (6) and the “Dornier Do X” (12) engines with a 4 throttle controller. I defined the 4 lever axes in FSUIPC7 and then put the following modified script into the fsuipc7.exe folder. Create and use an MSFS controller config with the throttles removed for the Latecoere and Dornier X. Many thanks to the person who sent me the original code. Note: the script doesn’t work with the Hercules for some reason, I use SPAD.neXt for the Hercules. --===================================== -- File Throttle.lua -- Put this file to the FSUIPC folder that contains the FSUIPC.ini file -- Add the file name to the [AUTO] section of the .ini file like this -- [AUTO] -- 1=lua throttle -- or (make sure numbering is consistent if the AUTO section already has entries) -- [AUTO] -- 1=lua xyz1 -- 2=lua xyz2 -- 3=lua throttle ---------------------------------------------------------- --variable definitions local user_aircraft_type = "" -- holds name of user aircraft in sim local number_of_engines = "" -- how many engines on the current aircraft local calc_code = "" -- string to hold RPN code local combine_throttles = 0 -- 0 = no, 1 = yes local My_Aircraft_Type = 0 -- Number assigned to a recognised aircraft --this is called whenever new aircraft is loaded in the sim function aircraft_changed(offset, uat) user_aircraft_type = ipc.readSTR(0x3D00, 256) number_of_engines = ipc.readUW(0x0AEC) ipc.log("in change_aircraft_name = <"..offset.." "..user_aircraft_type..">") ipc.log("Number of engines = <"..offset.." "..number_of_engines..">") if string.find(user_aircraft_type,"Latecoere") then -- Is this a recognised aircraft My_Aircraft_Type = 1 elseif string.find(user_aircraft_type,"Dornier Do X") then My_Aircraft_Type = 2 else My_Aircraft_Type = 0 os.exit() -- Not a recognised aircraft, so stop the script. end end --this is called when Thrustlever 1 changes function throttle_lever_1(offset, value) if My_Aircraft_Type == 1 then value = ((value + 16384) / 32767.0) * 100.0 -- squeeze value to 0-100 value = value > 99.0 and 100 or value < 1.0 and 0 or value calc_code = value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:1, Percent) " .. -- throttle 1 value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:2, Percent) " -- throttle 2 ipc.execCalcCode(calc_code) elseif My_Aircraft_Type == 2 then value = ((value + 16384) / 32767.0) * 100.0 -- squeeze value to 0-100 value = value > 99.0 and 100 or value < 1.0 and 0 or value calc_code = value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:1, Percent) " .. -- throttle 1 value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:2, Percent) " .. -- throttle 2 value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:3, Percent) " -- throttle 3 ipc.execCalcCode(calc_code) end end --this is called when Thrustlever 2 changes function throttle_lever_2(offset, value) if My_Aircraft_Type == 1 then value = ((value + 16384) / 32767.0) * 100.0 -- squeeze value to 0-100 value = value > 99.0 and 100 or value < 1.0 and 0 or value calc_code = value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:3, Percent) " -- throttle 3 ipc.execCalcCode(calc_code) elseif My_Aircraft_Type == 2 then value = ((value + 16384) / 32767.0) * 100.0 -- squeeze value to 0-100 value = value > 99.0 and 100 or value < 1.0 and 0 or value calc_code = value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:4, Percent) " .. -- throttle 4 value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:5, Percent) " .. -- throttle 5 value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:6, Percent) " -- throttle 6 ipc.execCalcCode(calc_code) end end --this is called when Thrustlever 3 changes function throttle_lever_3(offset, value) if My_Aircraft_Type == 1 then value = ((value + 16384) / 32767.0) * 100.0 -- squeeze value to 0-100 value = value > 99.0 and 100 or value < 1.0 and 0 or value calc_code = value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:4, Percent) " -- throttle 4 ipc.execCalcCode(calc_code) elseif My_Aircraft_Type == 2 then value = ((value + 16384) / 32767.0) * 100.0 -- squeeze value to 0-100 value = value > 99.0 and 100 or value < 1.0 and 0 or value calc_code = value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:7, Percent) " .. -- throttle 7 value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:8, Percent) " .. -- throttle 8 value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:9, Percent) " -- throttle 9 ipc.execCalcCode(calc_code) end end --this is called when Thrustlever 4 changes function throttle_lever_4(offset, value) if My_Aircraft_Type == 1 then value = ((value + 16384) / 32767.0) * 100.0 -- squeeze value to 0-100 value = value > 99.0 and 100 or value < 1.0 and 0 or value calc_code = value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:5, Percent) " .. -- throttle 5 value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:6, Percent) " -- throttle 6 ipc.execCalcCode(calc_code) elseif My_Aircraft_Type == 2 then value = ((value + 16384) / 32767.0) * 100.0 -- squeeze value to 0-100 value = value > 99.0 and 100 or value < 1.0 and 0 or value calc_code = value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:10, Percent) " .. -- throttle 10 value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:11, Percent) " .. -- throttle 11 value .. " (>A:GENERAL ENG THROTTLE LEVER POSITION:12, Percent) " -- throttle 12 ipc.execCalcCode(calc_code) end end --callbacks event.offset (0x3D00, "STR", 64, "aircraft_changed") event.offset (0x25F0, "SW", "throttle_lever_1") event.offset (0x25F2, "SW", "throttle_lever_2") event.offset (0x25F4, "SW", "throttle_lever_3") event.offset (0x25F6, "SW", "throttle_lever_4") --=====================================

Hehe, Thanks Bjoern, It's just a couple of lines from the Formation script which I published on the X-Plane forum. Thank you for prompting my memory. I have discovered that I had since enabled another script which conflicts with mine. FYI My script is here ..... https://forums.x-plane.org/index.php?/files/file/50534-formation-flying-flywithlua-script-update-see-notes/ When I acquire the AI planes and create a formation so I can fly my plane with them (as a wingman), I push the 1st AI plane's heading into my plane's autopilot heading so it will turn and fly the same heading as the formation (which is led by the 1st AI plane). Example of what happens. The aircraft heading changes to match the AI plane. cheers

I wrote a FlyWithLUA script long ago that would set the heading bug using code similar to below .... ------------------------------------------ dataref("gPlaneAPHeading", "sim/cockpit/autopilot/heading", "writable") -- defined earlier on in the script gPlaneAPHeading = 90 -- set the AutoPilot heading ------------------------------------------ but, with no change to the code this no longer works, yet I can set the dataref via the dataref editor plugin. Does anyone have a suggestion of what I need to change to get this working again? It appears to no longer be writable My searches have turned up nothing. Thanks.

I have blocked the exe in the firewall (using Binisoft Firewall Control) , so it doesn't update, but the other ports remain open. A trouble free workaround for the moment.

Yes, thanks Mark. Cheers!

Same here. Please provide a way to reinstall the earlier version and not have it auto update.

I have the opposite issue. I want to keep the older version of AviaServer (and prevent it from updating). It took me weeks to get my home cockpit working with all my hardware. I will be keeping the older version of the 737 for quite some time. Is there a way to prevent the auto update of AviaServer from occuring?

Anyone got an idea how they get 737's from Renton USA to Australia? What routes do they use? I'm trying to realistically replicate the flights required to fly the new PMDG 737 from it's birthplace to Australia and Simbrief says the 737 doesn't have the range to fly the Pacific, even with a Fiji or Vanuatu stop over.

I can happily populate the CDU on the x320nx and get the option to request IFR from Clearance, but if I do the same in the Salty747, I don't get the option. Is anyone aware of a step in the Salty that I must complete before the Clearance option is activated? or is there no link between the FMC and ATC at the moment?

I found this happening at predictable locations after I updated my nVidia drivers. So I rolled back to 472.12 only to find the problem still there. So I rolled back to a week old system backup (which had the 472.12 drivers) and the problem is gone. In my case, something about the driver install is changing something that introduces this pause. Only solution at present is NOT to update the drivers.

The profiles are stored in "Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\SystemAppData\wgs\000901FDF6A0322A_00000000000000000000000069F80140" (last folder name may be different) ---- re:recovery of lost profiles When I moved from the alpha to the release, I was able to transfer all my controllers over by doing the following.... The same process can apply to lost (or accidentally deleted) profiles. 1. In FS2020, create a new empty profile for the particular controller and exit the sim. 2. Go to the profile folder (as above) and search through the sub folders until you find the file just created that relates to your controller 3. Using a text editor like notepad++, copy the contents of the old profile (from a backup) into the newly created profile file, replacing what was there. You may want to update the "Friendly name" text. 4. Run FS2020. The newly altered profile will be uploaded to the cloud. Assuming you have a backup, you can recover a profile that was deleted this way. Note: Every time a profile is created or altered, a new GUID based folder is created, so you cant just copy an old profile into the profiles folder. You have to create / cut and paste (at least that's how it was the last time I did it) Of course, the better ongoing solution is to have your OS on a small partition so you can backup regularly, and ensure that the FS2020 data folders (eg: Community and Official folder) are on a non OS drive, so if you lose the configs, you can just rollback your OS partition which will restore the FS2020 main runtime and profiles to the last backup state. Missing profiles will be re-synced to the cloud.

I think we should all report it to zendesk. The more reports the better. I have found that reducing the size of the game window helps, as does the ASW30 solution (for rift users)

I'd report it to the Zendesk. They got onto it pretty quickly the last time the gaming services "broke" things. I would also disable all auto updates so i have control over what gets updated. If it happens to me, I will just roll back to one of my regular "C" drive backups. I have deliberately set up my OS on a small partition to make backups small and manageable.

The P51 from FSX Acceleration ports across very well, including instruments.

This sums it up. Solid Bridge Explanation You would think that Asobo would have at least addressed the bridges along the "showcase" route before its release.