John Dowson

That is the uninstaller. You cannot change that - it uninstalls from the locations where you installed. If you select P3Dv4, it will uninstall from the P3Dv4 location. If you select P3Dv5, it will uninstall from the P3Dv5 location. If you select both, it will uninstall from both. As I have said, a problem arises if you previously installed a single installation for both P3Dv4 and P3Dv5, but then just uninstall (or re-install) for one location, and change the installation folder. If you do this, it will uninstall the shared copy, then re-install a copy just for the version selected. So, if you previously installed a single copy for both versions, it is best to manually run the installer and uninstall for both versions. Then run the installer twice, and install for each version in a different location. It is the installation location you should choose, not the uninstall location.

Why are you giving me log extracts? If you want me to help you, please supply me with the files I have asked for.Yout FSUIPC7.ini and your FSUIPC7.log file, with the relevant logging attached. I need rto see hte full files. Not extracts. And not a 'continuation' log file.

@granathg Sorry, but I don't know what recommendation you are talking about, especially without a reference. And if it wasn't in this topic, why even mention it.... Anyway. this topic has a BAD title. I am going to close this topic now. Have you calibrated? Please see the section The Easy Step-by-Step Way to Calibrate Your Controls in the FSUIPC7 User Guide. Also, try using "Slopes". If you still can't get it to work, try searching this forum for a similar question/query - I have answered this and provided detailed instructions many times.... Finally, if you still require any further assistance, then post a new topic - or, better, post in one of the topics with the same or very similar issue. Also make sure that you are using either the latest official version (v7.1.0) or the latest beta (v7.2.0a) before you post - only the latest versions are supported. Also include/attach any relevant files, usually your FSUIPC7.ini and FSUIPC7.log files, and if a new post, give it a relevant title. P.S. Sorry to hear about your health issues. Hope that is all resolved or getting better.

So longer names work via lua but not macros? Thats interesting - thanks for reporting back. I'm not familiar with the lvar access implementation in FSUIPC4 - before my time I'm afraid (and Pete still looks after FSUIPC4).

No idea what this means, sorry.

ALL files that I request will be in your FSUIPC installation folder, unless I say otherwise. I have asked for this file many times. Have you actually read the User Guide? If not, please do so. I am not expecting you to be as knowledgeable as me in these matters, but I expect you to read my comments, and if you don't understand them ask for clarification (ie. "Sorry, I don't know what or where my FSUIPC7.ini file is - can you please explain?"). We can only progress with your issues if you read my comments and follow my advice. Please do that if you require further assistance. Lets go back to mt very first comment on your issue: Can you do that? If not, explain why and I can clarify. NB. If you cannot see the extensions of the files in your installation folder, you have windows explorer configured to "hide known file types". If this is the case, please see the Addendum in the Installation and Registration guide.

Thinking about this further, I think this is due to the fact that, as the text hasn't changed, setting the same text again won't be picked-up on the WASM as only changes to the CDA contents trigger the event to process. So, if you are setting the same text, this will not happen. I can think a couple of ways around this: - automatically zero-ing the calculator code text sent (in the CDA) after updating, and ignoring this in the WASM - add some sort of count index to the calculator code CDA structure, so that the contents of the CDA is changed even if the c.code is the same. I will investigate both options and post you and update to try in the next day or two. John

You could always put it in a separate file and 'require' it. Also, the parameter is just a 4byte (int) parameter. If your functions names are 4 characters or less, you can encode the function name as a hex sting and then use that. I've attached a simple example, in which you can assign to LuaValue with the parameters x464E31 for FN1 (46=F, 4E=N, 31=1) and x464e32 for FN2: function FN1() ipc.log("Function FN1() called!") end function FN2() ipc.log("Function FN2() called!") end local function bin2hex(s) s=string.gsub(s,"(.)",function (x) return string.format("%02X ",string.byte(x)) end) return s end -- Populate the conversion array - needs to be only done once local hex_to_char = {} for idx = 0, 255 do hex_to_char[("%02X"):format(idx)] = string.char(idx) hex_to_char[("%02x"):format(idx)] = string.char(idx) end function valueFunction(param) ipc.log("valueFunction: parameter="..param) -- Convert parameter to hex string hexString = string.format("%x",param) ipc.log("valueFunction: parameter as hex string ="..hexString) -- Convert hex string to ascII chars ascString = hexString:gsub("(..)", hex_to_char) ipc.log("valueFunction: parameter as ascII string ="..ascString) -- Call function from ascII string name _G[ascString]() end event.param("valueFunction")

If you want to save a flight, there are only two ways to do it - manually (i.e. when you say so), either using FSUIPC or the FS facilities, or by using AutoSave. ok

Why do you keep sending me useless logs? NEVER post me a continuation log. They are useless to me when investigating issues. I ALWAYS need to see a full log. And always with you latest FSUIPC7.ini file, as I have told you many times now. Also, when generating log files to investigate an issue, it is a good idea to try and remove all events that are continuously being logged (i.e. noise). To do this, use the DontLogThese ini parameter, in either your [General] or [Profile.<name>] sections. i.e. add this: DontLogThese=66065,67042

I'm not sure what could be causing this. Is FSUIPC seeing the first button press when this occurs? If you don;t know, try activating logging for Buttons & Keys as well as Events, open the log console and see what is logged when this occurs. You can paste the extract here if anything is logged and I will look into it. If nothing is logged, FSUIPC won't be seeing the initial keypress.

First, you posted in the FAQ sub-section, where it states NOT for support requests. I have moved your post to the main support forum. Please take care to post in the correct place in future. Not directly. However, you should be able to do this using lua, maybe using the lua socket library. To use this with FSUIPC, see Alternatively, there is also a WebSocket server for FSUIPC, which allows you to read/write data using WebSocket connections. See http://fsuipcwebsockets.paulhenty.com/. John

I'm not sure how this could be related to the AutoSave function. You could try logging events to see what events are being sent when this occurs. I'd be interested to know if other have seen this issue - I don't have the FSLabs A321. Not sure I understand this - you want to prevent (i.e. stop) autosave, but you still want to use the auro0save flights to load after a CTD? Anyway, to prevent autosave, you can disable in the usual way. There is also an FSUIPC added control that toggles the auto-save feature on//off, but only works if AutoSave is active (in your FSUIPC config/ini file). There is also a new control (latest FSUIPC6/7 betas only) that "manually" triggers and auto-save,

That lvar is defined as for Output in the MF spreadsheet, which I think means that it is for reading only and cannot be written to. Are you saying that the offset doesn't hold the correct value? Does it not show the same value as when you list the lvars? if not, what is the value when listing and what is the value in the offset?

@Nenad Bogojevic I'm not sure but I think it may be a timing issue. Can you try with an ipc.sleep call in between the two execCalcCode calls (try with 1000 initially and if that works, reduce). If that doesn't work, I will look into it. Thanks.

It is not possible to tell what is happening for screen shots. Please attach your FSUIPC7.log and FSUIPC7.init files. We ALWAYS need to see these to lookl at such issues, not screen shots - they nearly always turn out to be useless.

Thanks! Ok, thats good. For overly sensitive controls, some folks have also found that extending the range of the axis, so that you get less movement in the sim, works for them. You can do this by editing the ini. So, for example, this is my Rudder calibration entry (in the [JoystickCalibration] section, and also any [JoystickCalibration.<profile>] sections: Rudder=-16384,-650,768,16255 If I extend the max/min entries thus: Rudder=-20384,-650,768,20255 you then get less travel in the sim for that axis. The downside, of course, is that you loose the full range of the axis. Some people find this useful, but it depends on the controls and aircraft. Just FYI, something else to try if curves on their own don't give you what you need.

I'll take a look at the A320 FBW to see what works for these and let you know...may take me a day or so to get around to this though as I've a few issues to sort out first.

Are you sure that lvar exists? Just took a look at the lvars in the FBW A320, and it doesn't exist in the stable mod at least. Can you see it if you list the lvars (Add-ons->WASM->List Lvars)? These are the only A32NX_AUTOPILOT_* lvars I can see: A32NX_AUTOPILOT_APPR_MODE = 0.000000 A32NX_AUTOPILOT_FPA_SELECTED = 0.000000 A32NX_AUTOPILOT_LOC_MODE = 0.000000 A32NX_AUTOPILOT_TRACK_SELECTED:1 = 90.653481

You can zip it. That log file you posted doesn't contain anything useful. But, as I said, if assigning in MobiFlight, you need MobiFlight support, not FSUIPC support. And if assigning in FSUIPC, I need to see your FSUIPC7.ini file as well as the log. So no point in posting the log file really at the moment. As Pete has said, it just looks like you are using the heading as a signed value when it should be unsigned. That shouldn't be too difficult to trace.... And I still don't know why you said Alt+F isn't working, and there is no FSUIPC icon in your system tray.... that log file you did post shows the Alt+F hot key is registered:

Please try the attached version, v7.2.0b: FSUIPC7.exe I have only added the Light Potentiometer Set control. I will add the specific number ones (1-30) if/when requested. John

But what have you actually tried? What do you mean by 'Offset procedure'? Do you mean the new facility to add lvars to offsets? If so, that is only available in the latest 7.2.0a beta release - have you tried that? It is difficult for me to help you when you are not explaining what you have tried. Just saying 'nothing...' and 'I can't customize' doesn't help me. I need to know what you have tried, and what you see, and also see your logs and ini files (attached preferably, not selected contents pasted). And as I said, if using lvars/hvars, test them first using the facilities provided. Did you do that?

You posted your log file, but it was a continuation log file, i.e. you started a new log. I need to see the full log file, not a continuation log file. But, if you are assigning using MobiFlight, not FSUIPC, then you need MobiFlight support. If you are assigning in FSUIPC, I need also to see your FSUIPC7.ini file.

What is this? ....ok, you are using MobiFlight to access the offsets? Then you need to probably need MobiFlight support. If you are assigning in FSUIPC, we need to see your FSUIPC7.ini. The log you posted is also useless as it is a continuation log. Pease supply the full log file, and do not start a new/continuation log file. Then maybe you should ask the person who posted that video. I have no idea what 'codes' you are talking about, sorry.

The LIGHT_POTENTIOMETER_SET control/event are currently not flagged as axes controls. I can add/flag this as an axis control so that it is available in the axes assignments drop-down. Presumably this also applies to the LIGHT_POTENTIOMETER_*_SET (where * is 1,2,3..30), which I can also add. I'll post a version for you to try with this added later today.... John