Pete Dowson

Sounds like pre-calibrated flap positions. How many poisitions does it say on the calibration display? You supplied a Log, unfortunately with no helpful logging enabled, and no INI file so we can see your settings. Please do so. Also a log with axis logging enabled. Only move the flaps axis to avoid generating a very large log file. ZIP it in any case if it is too big. Also check if it is different when assigned to the normal FS control Axis Flaps Set. Pete

You haven't attached your METAR string, so I can't even look at it. You certainly didn't need to post the standard SimConnect documentation of the format! Don't you think we've got access to that in any case? Are you positioned at the weather station you are setting? If so, wait for it to change. If not then the weather is interpolated between the station you set and those around you. And will still take time to change. If you are setting global weather you need to set Global mode (same weather everywhere) to use it. That's done by a different NWI call documented in the NWI text document. Many weather programs using SimConnect were only ever fully successful using global weather. It gets complicated otherwise. Pete

The virtual buttons are part of the joystick scanning (real & virtual buttons are scanned each time). And assignments to the virtual buttons need registration in any case. So i don't know how you'd use the virtual buttons offsets: except from a program -- two programs, probably. One to set the button bits, the other to read them. So it would be the same, really, as using any user offsets. Pete

It shouldn't involve any "programming". at least no more than assigning things in MSFS itself could be called "programming". You simply need to know which control operates the Autopilot on and off. According to the list of MSFS controls those are called "Autopilot on" and "Autopilot off". Try those. If they don't work then that aircraft is doing its own thing and someone with that aircraft will probably need to help. BTW, do you know how to program an autopilot when you've enabled it? The term "programming" can legitimately be applied to the computer called the autopilot. 🙂 Pete

I just wanted it to check that it can actually install, because it too needs to find the correct folders. I'll have a look to see if there's any logging I can add to find out why is fails. But first, please can you look into the Windows Event Viewer -- Windows Logs - Applications, to see if there are any entries referring to MakeRwys.exe. If there are any please post details here. Also please confirm that you are running MakeRwys "as administrator". Best to change the EXE file properties to make it run as administrator in any case (right click - Properties - Compatibility). And tell me if you use any of the command line options. I can't get to look at this till tomorrow (Monday) afternoon in any case. Pete

I installed and tested yesterday's MSFS update, and the WASM loading problem is fixed. Everything works fine again. Pete

You can use the solution used by everyone before the 128 button versions of FSUIPC6 and FSUIPC7 were released -- the Lua plug-in "HIDdemo" provided for you in the Lua example plugins. You have to edit it to suit your needs. See the other threads on the Honeycomb devices. Pete

There’s no separate paid and free FSUIPC versions. The difference is in the registration. As far as I remember, Linda makes use of Lua plug-ins to FSUIPC. If so then it will need you to purchase a registration for FSUIPC. Really you would get proper knowledgeable answers from the LINDA site. Pete

I've now updated MSFS to version 1.15.8 and MakeRunways is still okay. Pete

What did the popup say? I have MSFS updated to WU4, and MakeRunways 5.126 works fine here. My MSFS is from the MS Store like yours. Is there another update yet, to fix WU4's WASM problem? The start of my Runways.txt file reads like this: Looking for: "C:\Users\Pete\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\content.xml" ---- okay, Content list loaded Now looking for: "C:\Users\Pete\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt" Checking: "C:\Users\Pete\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\" Found MSFS official scenery in: "C:\Users\Pete\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\" Loading language pack from: "C:\Users\Pete\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\fs-base\en-US.locPak" Loading materials list from: "C:\Users\Pete\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\fs-base-material-lib\MaterialLibs\Base_MaterialLib\Library.xml" Found MSFS community scenery in: "C:\Users\Pete\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\" Reading MSFS scenery: On another PC I have the files in E:\Wpsystems, but otherwise the paths correspond. Where are those files are on your system? Well, obviously MakeRunways hasn't changed. Does FSUIPC7 install and connect okay? Pete

Okay, tested. The latest version here does as you say, returning 255 for the release of buttons 132-227. I'll work on fixing that today. Pete

The problem before it was fixed was with the POV buttons, 32-39. The regular buttons are 0-31. The extra buttons now added are 132-227. Where did you get 6.0.14c? What link? Anyway, I'll test it here today with the very latest build. Pete

1. Make sure that you have FSUIPC set to use ‘Joy Letters’. There’s a chapter about this in the User Manual. 2. Make a backup copy of all the data files in the FSUIPC installation folder. That’s the folder containing the FSUIPC.EXE file. In fact, easiest just to backup the folder. You’d still need to rerun the (latest) installer at the time, but first restore your backup folder. The installer will do the rest when you choose that folder for installation. Pete

I just read such files as simple text files, and use the Lua string library to search for the keywords I'm interested in. The standard Lua string library contains all of the functions you'll need. I'm afraid I've never investigated operating XML files with an XML editor or handler. Pete

I'm not sure you've done anything wrong. Here's the [JoyName] sections: NEW: [JoyNames] AutoAssignLetters=No 0=X56 H.O.T.A.S. Stick 0.GUID={3B5C1710-9C80-11EB-800A-444553540000} 1=X56 H.O.T.A.S. Throttle 1.GUID={3B5CDA60-9C80-11EB-8014-444553540000} OLD: [JoyNames] AutoAssignLetters=Yes 0=X56 H.O.T.A.S. Stick 0.GUID={6467EC70-9C3A-11EA-8005-444553540000} 1=X56 H.O.T.A.S. Throttle 1.GUID={646888B0-9C3A-11EA-8008-444553540000} A=X56 H.O.T.A.S. Stick A.GUID={6467EC70-9C3A-11EA-8005-444553540000} B=X56 H.O.T.A.S. Throttle B.GUID={646888B0-9C3A-11EA-8008-444553540000} So, with only two clearly identified devices, and conveniently with the same ID numbers as before (only the GUIDs have changed), it is easy (you could have worked this out yourself from the chapter on Jot Letters in the User Guide): Here's the NEW section with the changes you need highlighted: [JoyNames] AutoAssignLetters=Yes 0=X56 H.O.T.A.S. Stick 0.GUID={3B5C1710-9C80-11EB-800A-444553540000} 1=X56 H.O.T.A.S. Throttle 1.GUID={3B5CDA60-9C80-11EB-8014-444553540000} A=X56 H.O.T.A.S. Stick A.GUID={3B5C1710-9C80-11EB-800A-444553540000} B=X56 H.O.T.A.S. Throttle B.GUID={3B5CDA60-9C80-11EB-8014-444553540000} That's it. Pete

Asobo seems to have broken the WASM module facility. https://forums.flightsimulator.com/t/standalone-wasm-modules-crash-the-simulator-after-latest-1-15-7-0-update/390552/4 https://forums.flightsimulator.com/t/wasm-module-connection-broken-after-wu4/390841 We're stuck until this is fixed I'm afraid. Pete

I'm afraid ASOBO have broken LVar access with the WU4 update yesterday. https://forums.flightsimulator.com/t/wasm-module-connection-broken-after-wu4/390841 https://forums.flightsimulator.com/t/standalone-wasm-modules-crash-the-simulator-after-latest-1-15-7-0-update/390552/4 Pete

Yes, it's confirmed as a bug in the MSFS update: https://forums.flightsimulator.com/t/standalone-wasm-modules-crash-the-simulator-after-latest-1-15-7-0-update/390552/4 https://forums.flightsimulator.com/t/wasm-module-connection-broken-after-wu4/390841 Pete

glad it is sorted, but: Those lines correspond to the "Map to 4 Mixtures" and "Map to 4 Prop Pitches" options on Page 2 of the Calibrations. That page is concerned with assignments made to the generic "Mixture" and "PropPitch" controls, whereas not only do you not have any such assignments, you have two specific Engine 1 & 2 assignments in any case, and so don't even need any mapping except possibly for 3 or 4 engined props. The calibrations for the 4 mixtures and 4 props were therefore conflicted with trying to copy non-existent generic axis assignments as well as dealing with local specific assignments. I would be interested to know why you set those mappings up in the first place. These mix ups really have not been reported before, even though this system has been the same for some 20+ years! Pete

There is no "core plug-in". Is your Arduino a COM-port connection? If so just read and write data for it using the COM library. Look it up in the FSUIPC Lua library document. You have to write a corresponding program for your Arduino to. So you just invent your own serial port conversation with it. I know very little indeed about Arduino.s , and an Engineer friend did the work involved in installing the little bit of associated hardware which operates by start switch magnets. And that in turn is handled by ProSim. I suggest you ask in a cockpit building forum, or maybe one for Arduino users. They'd be a lot more help than I. We can help understand anything you ask about the COM library, but mostly it is simply "Open port ... and a write data ... read data loop". Since you write the software for both ends of the wire, it is all completely up to you. Pete

But have you installed them? You definitely said your FSX was the original. Perhaps you could post your FSUIPC4.LOG file so I can see what is happening. You'll find it in the FSX Modules folder. It would also be useful if you found the Windows crash details for FSX.EXE in the Windows Event Viewer. You also said: If this was the case, why have you not reported it before? How long have you been using an old FSUIPC4 user? FSX dates back to 2005 (the original one ,at least), and once the updaters were released FSUIPC has been a very stable and well trusted addition. Considering this I'm thinking your installation of FSX might be cottupted. Haven't you considered reinstalling it afresh, plus the updates of course? Pete

So I don't understand the question. If you mean the Lua interprester built into FSYUPC or WideClient, then that is also where the provided libraries are -- within FSUIPC. If Air Manager incorporates its own Lua interpreter and library, no. You might be able to convert from one to the other but I really can't see how they can be shared. Ah, you mean sharing data, not sharing code and functions. Yes, you could obviously share any data stored externally to the Lua facilities in things like like LVars (stored in the current sim's data area), or FSUIPC offsets, if Air Manager interfaced at all with FSUIPC, would do. Or failing that a file. I use a simple Lua plug-in using the COM library in FSUIPC's Lua to read and write data to an Arduino. i've never used any other Arduino interfacing software. But my use of Arduino was done some time ago. Currently I only use one with an add-on board to operate the magnets on my 737 starter switches. Pete

You need to update your FSX! There are lots of bugs in SimConnect in the original edition. There were two updates to fix things. They are still available: https://flyawaysimulation.com/downloads/files/1950/microsoft-flight-simulator-x-service-pack-1/ https://flyawaysimulation.com/downloads/files/2796/flight-simulator-x-service-pack-2/ Pete

There's a chapter about it in the FSUIPC User Guide. Take a look. I just meant that if you'd disconnected them already, when you reconnect them use the same sockets. And, yes, USB sockets! Pete

The reverse function definitely reverses the direction of the axis changes. It operates in the same way on all axes with the option set. Did you re-calibrate each one after setting REV? You need to do so. And of course make sure the same controls aren't also assigned in P3D. they could be interfering if so. Pete