John Dowson

That is nothing to do with FSUIPC, and is only an informational message. Do you not see any errors, or anything relating to the FSUIPC installer? Did you check your AV? Please do that. So you don't see anything when you run the installer? The first thing that should happen is that windows UAC should ask permission to run the installer - do you see that? Anything else?

Stops when? Or are you saying that it runs the uninstaller, to uninstall the previous version, and then stops? If so, it sounds like it is crashing for some reason. Can you check both the windows Event Viewer for any crash reports (under Windows Logs -> Application), and also check any anti-virus software that could be blocking the installer. What folder are you trying to install into (or where was your previous version installed)? Have you extracted the installer from the zip file? John

What do you mean by 'offset log'? There is no such thing. There is the myOffsets.txt file, which is not a log, but a list of simvars (or a-type variables) to add to offsets. You may be able to add lvars to this, as lvars are now supported by the SimConnect SDK, but I haven't tested (or documented) this yet so I am not sure. To add lvars to offsets, you should use the [LvarOffsets] section of the ini file (see Advanced User guide). Sorry, what does this mean? Do those lvars work to control the fuel valves or not? Btw, it is a good idea to test lvars before using them, using the provided facilities (e.g. Add-ons->WASM->Set Lvar...,).

Well, they won't as you never pitch down for than 20 degrees. I released the next version of FSUIPC7 last night, so the pressure is off, and I am going to have a few days off (well, not off, but more relaxed!). But I don't really have anything else to say on this subject that I haven't already. I don't understand why your original code doesn't always display to one dp (it does here), but I am not going to worry about that. Use any of the three options - your original code, original code + conversion to 1dp, or my code. They are all pretty much the same except for the difference I have already pointed out. Cheers, John

Yes, those are the ones that I couldn't find anything for, as I said: and later: As there is nothing obvious, the next step would be to inspect the xml code to see how that works. I will take another look, but not until the weekend. John

Sure - license sent. John

License sent. John

I tried using a pre-compiled lua and get the following error: *** LUA Error: D:\FSUIPC7\Lua\soundTest2.lua: bad header in precompiled chunk This error is normally due to mismatched compiler versions, but I compiled with 5.1.4 and this is also the version that is built-in to FSUIPC7, so I am not sure what the issue is here. I will update the documentation (for the next release) to state that this is no longer possible. Regards, John

That was pitch-down - I went to the extremes to test! The maximum pitch-up I tested was around 50 degrees: Hmm, strange - I am not sure why, but the code I showed you should always restrict this to 1dp. John

I do not understand the following: 1. why do you have FLAPS_DET, FLAPS_DETENT_SET and FLAPS_UP assigned to ranges on your flaps axis? I would have though just assigning your your flaps axis to FLAPS_SET would be sufficient. 2. why are you also assigning to FLAPS_SET & FLAPS_UP in your wing sweep axis? I thought the wing sweep would be independent of the flaps 3. the ranges on your sweep controls look very strange, as well as the entering/leaving assignments, especially this one on the minimum axis value: 5=2S,B,-16384,-16384,65595,0,M3:1,0 -{ Entering=FLAPS_UP, Leaving=Macro F3_Sweep_Decr: F3_Wing_Decr }- Ok, that's interesting - could I see this explanation please? What type of variables? Can you not use these variables rather than mouse macros? Could you possibly attach a screenshot of the wing sweep and flap controls so I can see how these operate? Thanks, John

Hi Ray, I just tested this with a simple lua: function PitchDisplay(offset, pit) -- Ray's code local mypit = pit*360/(65536*65536) if mypit <= 20 then --descending mypit = math.floor(-mypit *10) / 10 else --ascending mypit = pit*360/(65536*65536) mypit = 360 - math.floor(mypit *10) / 10 end local mypit1 = tonumber(string.format("%.1f", mypit)) -- My Code local jdPit = -pit*360/(65536*65536) -- convert to degrees, also reverse sign so -ve descending/pitch down, +ve ascending/pitch up if jdPit < -180 then jdPit = 360 + jdPit end jdPit = tonumber(string.format("%.1f", math.floor(jdPit *10) / 10)) -- ensure value is to 1 decimal place displayString = "Ray's original pitch =" .. mypit .. ", Ray's 1dp pitch = " .. mypit1 .. ", my Pitch = " .. jdPit ipc.log(displayString) ipc.display(displayString) end event.offset(0x0578, "SD", "PitchDisplay") When running this I got mostly the same number printed each time, the only difference being when the pitch falls below -20: So it seems your original code displays to 1dp anyway! Cheers, John

Great - thanks for the update. John

Yes - I removed the 7.4.13 beta version when I released it officially, so now downloadable from the usual places. There seemed to be 2 issues with the 7.4.12 version: - WASM crashing after long flight. Not 100% sure on this but it seems that some add-ons are continually creating lvars which, due to the way lvars are pushed out from the FSUIPC WASM to its clients (including FSUIPC) caused some resource issue and the WASM to crash. - start-up and connection issues due to a combination of switching the auto-start method to using the MSFS.bat file and the auto-tuning functionality running when MSFS is updating, causing long start-up times and too many re-connection attempts/. Both issues have been addressed in the new version. You don't have to add that to the ini for the time being, but if you get any connection/start-up issues, then please add this TestOptions to your ini. That option provides extra logging as to why things are started or not during initial connection to MSFS. John

Ah, looks like your lua add-on is using the HotKey offsets starting at 0x3210. So your issue may be that keys are not being received from MSFS, which a few people have reported with version 7.4.12. Update to 7.4.13 and try with that version. If you still get an issue, it is most probably due to start-up issues. Please activate logging for Buttons & Keys, and show me your FSUIPC7.log and FSUIPC7.ini files from a session when you got the issue. John

Why are you posting those files? I am not going to look at them. If you want them debugged, contact the provider. I will only check if FSUIPC7 is working correctly, if you provide the files I need.

Ok, good. And sorry - I had done most of the work for you but looks like I forgot to attach your FSUIPC7.ini in my last post. Sorry about that. There are other profile sections that need cleaning. I have also just released 7.4.13, so please download and use this. Correct the remaining profile sections to use substrings, then add the following parameters in the [General] section to force an auto-tune: StartUpTuningActive=Yes John

I never said that this would fix your issue - you just need to be on the latest version for me to investigate. And, as I said, I need to see your logs if you want me to look into this. And I have just released 7.4.13 - please update to this version, the only supported version., and try again. If it doesn't work. show me your FSUIPC7.log file. The log file will be in your FSUIPC7 installation folder. If you do not know where that is, use the FSUIPC7 File -> Open Installation Folder option. If you still cannot see the file, you will have the Windows Explorer options set to Hide extensions of known file types. Remove that option.

I have just released 7.4.13 - can you please install this version and see if that solves your issue. If not, I need to see your files: FSUIPC7.log, FSUIPC7.ini, FSUIPC_WASM.log. Please exit FSUIPC7 before attaching the FSUIPC7 logs, and only attach the FSUIPC_WASM.log after exiting MSFS. John

Sure, I will PM you one. Sorry, but I will not send you one as it looks like you have been using the trial license since November 1st 2022: If you want to continue using FSUIPC7's licensed functionality. please purchase a license. John

I have also just released 7.4.13 - please update before requesting any more support.

If you just remove that, it will brake. You have to correct it. But, you say this is working. If your original code WAS working (which I doubt), then just converting mypit to have 1 decimal place should not change anything, except to display the value with 1 d.p. But you saiy this didn't work. Ok.

No. LINDA is no longer supported by the developer. I have never used LINDA and just haven't got the time to look into it and support it, sorry. Especially for VRI devices, which I also know very little about. How do you know when it controls COM and when it controls NAV? If you want a button/switch (including rotary buttons) to send different controls, then you need something else that this depends on, e.g. another button or maybe an offset. Lets assume you are using another button or switch, so when this switch is down/off, the rotary controls NAV, and when up/on, it controls COM. So, on the rotary, you would assign the left/righ buttons to decr/incr both NAV and COM. Then you would add a compound button condition to those assignments, so that the assignment triggered would depend on the state of your other button/switch. See the section on Compound Button Conditions in the Advanced User guide, page 22.

I have replied there and locked that post. Read my reply there, correct those issues, and tell me what your problem is here...DO NOT START YET ANOTHER THREAD ON THIS SAME ISSUE.

That is strange...maybe I should have checked this in P3d (I checked in MSFS as that is what I had running). I can't see how your code can work because of this: if mypit <= 20 then --descending Why is 19 descending, -19 descending, but 21 ascending? Maybe try something like this: -Display Pitch Angle... pit=ipc.readUD(0x0578) -- 0=level, –ve=pitchup, +ve=pitch down mypit = -pit*360/(65536*65536) -- convert to degrees, also reverse sign so -ve descending/pitch down, +ve ascending/pitch up if mypit < -180 then mypit = 360 + mypit end mypit = tonumber(string.format("%.1f", math.floor(mypit *10) / 10)) -- ensure value is to 1 decimal place I can fire-up P3D to check there but not today... John

@DaveSCUSA Please explain what issues you are having with assignments to this aircraft here, but at least please try what I have already advised you to use, i.e. input events. And as I have said, the last time I looked at this aircraft I could not find anything to control the fuel cut-off triggers (bottom of throttle). I can take another look, when time permits, but I doubt I will find anything unless there has been an aircraft update. Apart from these, which you have to trigger manually in the VC, there should not be an issue starting this aircraft. John