ark1320

Yes, saw my mistakes just before your post came in. I tried ipc.writeUD(0x05CC, 123245000) for standby COM1 with the C152 in MSFS but it didn't work -- Simconnect or MSFS bug I assume. Thanks, Al

Yes, the newest spacing is 8.33KHz and is mainly used in Europe. I see in FSUIPC6 for P3D4/5 there are now offsets 0C54 to 0CD0 for COMS 1/2 which are simply described as 32 bit integers. So maybe for a frequency like 123.245 MHz you can simply write the six digit number without the decimal point. I will experiment with that. In the past I have used offsets like 034E which apparently will only accept 4 digits in BCD format. Thx, Al

Are than any plans for FSUIPC7 to support the 25KHz Com spacing that many of the planes in MSFS2020 use? Thanks, Al

Ok, I understand, sorry. All above is correct. Had just wanted to point out that if I understand the log file correctly the letter keys seem to be triggering the Lua script although not programmed to do so in the FSUIPC7 ini file.

John, Thank you -- very much appreciated! Note I updated my last post above in case you didn't see the update. Al

John, Thanks for checking that -- explains a lot! Note that FSUIPC7 does see the Numpad key inputs at least when the Key Presses tab is used to program those keys in FSUIPC7. The other strange thing is that the letter keys a, b, c, d ......i are triggering the one line logging lua script showing ipcPARAM values 1 to 9 respectively even though those keys are NOT programmed in FSUIPC7. The FSUIPC7.ini file is still just: [Keys] 485=N96,8,L102:R,0 -{Num0: Press=Lua FSUIPC7ParamTest }- 487=N110,8,L102:R,10 -{Num.: Press=Lua FSUIPC7ParamTest }- 488=N97,8,L102:R,1 -{Num1: Press=Lua FSUIPC7ParamTest }- 489=N98,8,L102:R,2 -{Num2: Press=Lua FSUIPC7ParamTest }- 492=N99,8,L102:R,3 -{Num3: Press=Lua FSUIPC7ParamTest }- 493=N100,8,L102:R,4 -{Num4: Press=Lua FSUIPC7ParamTest }- 496=N101,8,L102:R,5 -{Num5: Press=Lua FSUIPC7ParamTest }- 498=N102,8,L102:R,6 -{Num6: Press=Lua FSUIPC7ParamTest }- 500=N103,8,L102:R,7 -{Num7: Press=Lua FSUIPC7ParamTest }- 502=N104,8,L102:R,8 -{Num8: Press=Lua FSUIPC7ParamTest }- 504=N105,8,L102:R,9 -{Num9: Press=Lua FSUIPC7ParamTest }- Attached is the log file for inputs a,b,c,d,e. Al FSUIPC7.log

Here is the log file for the input sequence 1, 2, 3, 4, 5. Al FSUIPC7.log

I have had No repeats checked all along as you can see from the example Key Presses window above and the FSUIPC7 ini file, but just for the Numpad digit keys. The a, b, c, d, and e keys are not programmed in FSUIPC7 for anything, so no way to check the No repeats box. Repeated the logging experiment with just Buttons and Keys selected for logging. I hope that is what you want. I pushed the a, b, c, d and e keys in sequence with a few seconds between each. I tried to be 'quick' on and off each key push. I also waited until the plane was sitting on the runway for a short while before inputting any keys. I will repeat this experiment below but use the Numpad input key sequence 1, 2, 3, 4, and 5 to get a new log file. Al FSUIPC7.log

I repeated the above test this time pushing the Numpad 1, 2, 3, 4 and 5 keys in succession. There was no FSUIPC7ParamTest.log file produced. The FSUIPC7.log is attached. When I checked the FSUIPC7.Key assignment window, the Numpad digits were assigned as shown below for the 1 key. Al FSUIPC7.log

Hi Pete, I put "return" at the end of scripts -- I gather from your comment I should not do that. The code shown was the complete script -- not a partial script. I had the 2 sec delay so the display would not immediately disappear before I could see it because the script ended. The complete FSUIPC7ParamTest.lua script was changed as you asked to this single line: ipc.log(" ipcPARAM = "..ipcPARAM) I started the sim and then FSUIPC7.exe, and pushed the A, B, C, D, and E keys in order with about a second or so between key strokes. I did not try the Numpad digit keys with this test, but then repeated the test below with those keys. The FSUIPC7.ini file is as I originally posted above. If I open the FSUIPC7 Keys window and push the A, B, C, D, and E keys, no assignments are shown for any of these keys. Attached are the FSUIPC7.log and FSUIPC7ParamTest.log files. I'll be glad to provide whatever else you need. Thanks for the help. Al FSUIPC7ParamTest.log FSUIPC7.log

I've been having some really strange behavior with a Lau script in FSUIPC7 that I have used for a long time successfully in FSX and P3D. The script is supposed to call different functions based on ipcPARAM values, but is not working correctly. So I finally decided to write a tiny ipcPARAM test script to see if I could figure out what is going on. Here's the script which simply reports the ipcPARAM value if finds. -- FSUIPCParamTest.Lua Test if ipcPARAM value is being read correctly ipc.writeSTR(0x3380, " ipcPARAM = "..ipcPARAM); ipc.writeSW(0x32FA, 2); ipc.sleep (2000) return The relevant portion of the FSUIPC7 ini file looks like this: 485=N96,8,L102:R,0 -{Num0: Press=Lua FSUIPC7ParamTest }- 487=110,8,L102:R,10 -{Num.: Press=Lua FSUIPC7ParamTest }- 488=N97,8,L102:R,1 -{Num1: Press=Lua FSUIPC7ParamTest }- 489=N98,8,L102:R,2 -{Num2: Press=Lua FSUIPC7ParamTest }- 492=N99,8,L102:R,3 -{Num3: Press=Lua FSUIPC7ParamTest }- 493=N100,8,L102:R,4 -{Num4: Press=Lua FSUIPC7ParamTest }- 496=N101,8,L102:R,5 -{Num5: Press=Lua FSUIPC7ParamTest }- 498=N102,8,L102:R,6 -{Num6: Press=Lua FSUIPC7ParamTest }- 500=N103,8,L102:R,7 -{Num7: Press=Lua FSUIPC7ParamTest }- 502=N104,8,L102:R,8 -{Num8: Press=Lua FSUIPC7ParamTest }- 504=N105,8,L102:R,9 -{Num9: Press=Lua FSUIPC7ParamTest }- This script should simply display the numbers 0 to 10 based on pushing the Numpad digits 0 to 9 and the period key. But when I run the script, nothing happens when I push the digit keys or period key on the numpad (which I checked is on), but if I push at the A key, ipcPARAM = 1 is displayed, if I push the B key, ipcPARAM = 2 is displayed, and so on with the I key displaying ipcPARAM = 9. Note you may have to push a key a few times to 'start' the display, as shown below for when the A key is pushed: This happens even if I remove all other FSUIPC7 Lua scripts. I know there are major problems with the SimConnect text display functions, but that aside, I don't understand why pushing the letter keys A, B, ....I triggers the script in the first place, but pushing the Numpad digits does nothing? Can SimConnect problems distort the value of ipcPARAM being 'read' by the script? Thanks for any ideas, Al

OK, I understand now -- thanks. It seems that if you make a change to a Lua script, you have to exit and restart FSUIPC7 for the change to take effect. Does that seem correct, for now at least? Have you had any reports on problems with the ipc.set() and ipc.get() functions, and with ipcPARAM values not being correctly recognized? I'm just trying to sort thru things that are not working. Also the ipc.ask() function does not seem to work which I have often used to get user input such as a desired airspeed or frequency. Is there another way to do this currently? Thanks, Al

John, I don't understand your comment that Lvars don't (won't) exist in MSFS. My understanding is a developer can use XML coding if so desired, and so I'd expect Lvars would exist in that case. And also there is the legacy mode for porting over existing a/c, with some modifications I would assume, that would have Lvars. Or is my understanding incorrect? I do realize Gauges written in C++ and compiled into Wasm are different and won't have Lvars. I will certainly pass on any non-working offsets or controls not currently listed as such in your spreadsheet. Al

I am having a lot of trouble getting Lua scripts that I've used for a long time in previous sims working in MSFS, and would be interested to hear how it is going for other Lua script users. I've written some very simple test scripts, but have not had much luck with those either -- they work sometimes, but not other times. Getting messages to display does not seem to work well either. So I'm just curious what others are finding which will be a clue to help me determine if "I'm the problem", or if it is perhaps related to the current state of the sim. I typically use Lua scripts to do things like set courses and headings, altitudes, radio frequencies, to operate the autopilot, etc. So far with MSFS I've just been trying to set a Nav frequency without much luck. Thanks, Al

John, Pete, -- thanks so much for your continued outstanding support!! Al

I'm in the middle of trying to get some of my Lua scripts working in MSFS. It looks initially to me that with FSUIPC7 you kept the same offset address/parameter associations as with previous versions of FSUIPC. Is that a pretty good assumption in most cases? Also, I was looking at the color code you provided with the offset spreadsheet for FSUIPC7 ( thank you for that! ), but noticed some offsets are not color coded at all, just gray -- what does the gray mean? Thanks, Al

I did that, and simply put my modules folder in that FSUIPC7 folder. I forgot to ask above, is there a particular version(s) of Simconnect that need to be run for FSUIPC7, or does that all happen 'automatically'? And if you are running Lua scripts automatically under [Auto, does it make any difference with FSUIPC7 if the sim or FSUIPC7 is started first? Thanks, Al

So I assume there is no longer a need for a modules folder per se, or if we want to use one for uniformity with previous FSUIPC installs, we should put FSUIPC7.exe, FSUIPC7.ini, FSUIPC7.key, and any Lua scripts, etc all in the modules folder and that should work. Al

The attached RptMoveAircraft script is a variation of the above NpCmove Aircraft script in that when activated it asks if you want to Repeat(Rpt, i.e., reuse) the previous move settings. If you answer NO, then the script will ask for the same parameters as the above script. If you answer YES, then the script will immediately reuse your previous move parameters and move the aircraft accordingly. This is convenient for repetitive operations, such as when you want to reposition the aircraft after each landing when practicing approaches. The move parameters are saved in a csv file. The first time you run the script you must answer "NO" and enter parameters so an initial csv file is created. After the aircraft moves you may need to move the throttle, etc., slightly so the sim knows those settings. RptMoveAircraft.zip

Looks like others are having similar problems with SimConnect displays in P3Dv5: https://www.prepar3d.com/forum/viewtopic.php?f=6312&t=138871 Al

If your request was by email, after four weeks I'd try sending another email just in case the first one got 'lost' somehow. 😉 Al

I have updated the autothrottle lua scripts to work with Mach# as well as IAS in knots. Each autothrottle script defaults to airspeed values in Knots below its crossover altitude, and in Mach# above its crossover altitude. The crossover altitude for the TurboJet and CRJ scripts is currently set at about 29000ft. For the TurboProp and C441 scripts it is set at about 24000, and at about 22000 for the MU2 script (crossover altitudes can be changed with a text editor). When a script is activated you will see When climbing or descending through the crossover altitude the autothrottle automatically switches to Mach# or Knots, respectively. In addition, a key or button can be setup through FSUIPC to manually switch the autothrottle back and forth between knots and Mach# at any time.The corresponding A/T target speed displays when the script is running looks like this AutoThrot3C441.lua AutoThrot3CRJ.lua AutoThrot3MU2.lua AutoThrot3TrbJet.lua AutoThrot3TrbPrp.lua SetUp Autothrottle Lua Scripts.docx

Thanks Thomas. I still haven't figured out a way to reliably trigger the problem. Al

I agree the P3Dv5 menu flickering issue has gone away with HF2. That flickering was quite slow -- maybe seconds between "flicks". The flicking I'm talking about here is quite fast -- maybe 5 times/sec -- makes it hard to read the display. However, it doesn't seem to always happen. If I can determine how to make it happen reliably I'll send you a script to try. Thanks very much for the offer to help! Al

I have a Lua script that runs in a continuous loop and displays various flight parameters in a simconnect message window using ipc.display() as shown below . The flight data display is updated about every two seconds. This script runs fine in P3Dv4.5HF3 with a nice steady display. However, when using the same script In P3Dv5 (with or without the Hot Fixes) after a few minutes the simconnect message window display begins to flicker at a high rate, and stopping and restarting the script does not stop the flickering display. I use FSUIPC6 for both sims with the latest version of Win10 Pro. I realize this is likely not a FSUIPC problem, but am posting here to see if any other FSUIPC Lua script users have come across a similar display issue with P3D5 and might have some insight into the cause. Thanks, Al