John Dowson

Sorry, what does this mean? What is 'hook'? If you activate it, don't you see the FSUIPC entry in your add-ons menu? Or are you saying that you can activate FSUIPC, but the next time you start P3D it is again not active? There is no "Modules" folder any more, although you can still install there if you so wish. I see that you installed FSUIPC6 in your P3D add-ons folder. It is better to just use this location for yout add-on.xml file and install FSUIPC6 in a separate location (e.g. C:\FSUIPC6 or C:\P3D Add-ons\FSUIPC6).

Try with the Rotoe Brake control first with the parameters mentioned in that post: There is also a spreedsheet (2nd comment in that link) with more control codes that may be useful.

Check the following post in the Asobo forums: https://forums.flightsimulator.com/t/thrustmaster-tca-quadrant-still-not-completely-working/309593/695 This seems to be saying that the autobrake is working in the vanilla A320 but not working correctly in the FBW mods as they are using lvars. The offset status document says offset 0x2F80 is working in the vanilla A320Neo but returns to 0 once set (i.e. is momentary). Is this not the case anymore (i.e does the document need an update for this)?

If you didn't activate it when asked, it won't ask again. Just go to the Options->Add-ons panel and activate/enable it from there. John

If you activate logging for events, can see the event being sent? if so, and its its not working, then it should be reported to MobiFlight.

Nothing! When you install a new add-on via the xml method, P3D asks you to activate the first time it is ran. Just click Yes and you are done. John

As we don't have the FSLabs A320, you are probably better of asking on the FSLabs forums. For example, this post has some parameter codes that can be used with the Rotor Brake control to control various lights: https://forums.flightsimlabs.com/index.php?/topic/10548-some-early-parameters-for-those-of-us-using-hardware-controls/ John

Can you activate logging for Buttons & Switches and Events, and produce a short log file with your aircraft loaded, press the button assigned to the macro then exit, and attach the log file together with your ini file and I'll take a look.

From the Advanced User manual: Up to 32 “AlsoManage” lines can be given, numbered 1 to 32. Your entries with numbers 33 and above will be ignored. Your FSUIPC is also out-of-date - the latest version is 5.157. John

The error is given (on line 7): [E] *** LUA Error: C:\Prepare3D v5 Add-ons\FSUIPC6\A2AB17_MixAdj_1.lua:7: attempt to call global 'adjust_mix_1' (a nil value) So its this call: adjust_mix_1 () This is calling a function before it is defined. There are also other issues with that script, such as the conditional in the adjust_mix_1() function has a dangling 'else', and variables being tested without being defined or set anywhere, and other variables being set and never used. It couldn't have ran without a hitch - the script must have changed. Do you mean the Linda main script or that script? Anyway, If using Linda, you should use their support forum. And your FSUIPC is out-of-date - the latest version is 6.0.12.

Thats fine, but you should delete the contents of the [General] section and let that get rebuilt, as many of the parameters no longer apply. You can manually remove any aircraft from profiles if you like, or remove profiles completely if you are no longer going to use them. But they do no harm. Sorry, but don't know what that file/link is you posted, but its not your FSUIPC7.ini file.

Have you installed the MobiFlight WASM module?

No, as that is for MSFS only. You say you have purchased FSUIPC5, which is for P3Dv4, so use that. I don't know Pilot2ATC, but I suspect it works with the unregistered/free version of FSUIPC anyway.

FSUIPC is only an interface to pass controls that it receives to the FS. How the FS responds is outside of our control. Yes...unfortunately. Many events sent to the sim can result in different events received, which also don't include the actual event sent. I'm not that familiar with the A320, or the MB events or this aircraft/mod, but maybe your question should be asked on the MB AS320 mod forums, if that is what you are using. Other that, I would at least need to see your FSUIPC log and ini files to comment further. John

This is about the 100th time this has been reported...please, if you have an issue, first check the documentation and then check for previous posts of the same problem before you post. The solution can be found in the provided README.txt: Not also that you should not install as admin, unless you installed MSFS as admin for some reason. Please read the provided README.txt (as the name implies!) and also the Installing and Registering FSUIPC document provided. John

They didn't get replaced. You specify the [Auto] section. FSUIPC writes the [LuaFiles] section with the .lua files it finds in your installation folder. If wasn't obvious that it should have been 1=Lua HidDemo and not !1=HidDemo.lua then I don't know what to say....perhaps I should give up providing user manuals...😞 This script has been available for many years and should work without too much trouble really...You should check the vid and pid are set correctly, and you can set the logging flag (in the script itself) as well as activating logging for lua plugins (from FSUIPC) so that you can see if it is running or not and perhaps what the error is. But as you have already stated that you will not be purchasing a license, and this functionality requires a license - and I am also very busy, I don't think there is much point assisting you with this any further, sorry. John

There are no hot keys in FSUIPC7, apart from the hot key to display/hide FSUIPC7 itself. Offset 0x0C1A was previously reported as working (as its marked in green in the offset spreedsheet) but I've just taken a look and it doesn't seem correct. I can see the value change occasionally, but it jumps back to 0, but sometimes shows other values (32, 64, 128). There are also no controls exposed via simconnect to control the sim rate, although there are some MSFS controls to increase and decrease (as well as set the sim rate). You can assign these to keys (in MSFS) and then assign buttons to these key presses in FSUIPC. However, there is no control to return to normal speed, and it difficult to know when you are at normal speed without that offset working! Here are some Asobo references to the issue, where another tool for this is mentioned that you could try: https://forums.flightsimulator.com/t/bug-changes-in-simulation-rate-are-not-displayed/8698 https://forums.flightsimulator.com/t/simulations-rate/351296/10 I will look into offset 0x0C1A to see what is happening with this, but this will take a while. I'm concentrating on providing lvar access at the moment, and am making a note of such issues and will look into them once I've released a beta of the WASM lvar access module. John

Yes, I know, thanks. I provide manuals so that I don't continually have to answer these type of questions... Your ini file has this: + The Advanced User Guide says: So, isn't it obvious that your ini's [Auto] section should be: [Auto] 1=Lua HidDemo ?

This value doesn't change until you click the Set button. Its the In / Out values that change, and then you use the Set button to set the (max in this case) in value. If the In/Out values aren't changing, make sure you have assigned Direct to FSUIPC Calibration and the flaps axis.

Hi Daniel, ok, thanks for the detailed explanation. I'll definitely look into this when I have more time. Regards, John

Why wouldn't you if nothing has changed? What message? When? Did you download the exe I posted above and try that? Please do. I have also PM'ed you a key file. drop that into the same folder as your FSUIPC7.exe. You don't need to. If you want to use anything there, documentation is provided (from that link I also posted). Your screenshots above show MANY errors.I think there must be something pretty seriously wrong with your system and should consider reinstalling Windows. Do you have any anti-virus software running (apart from Windows Defender)? If so, maybe try temporarily disabling.

You can either add them to your existing event files or create a new one for them. Note the max limit of 256 events per file. And there is also an issue with the current release v7.0.4 (and earlier) in that only one event file can be used, so if using multiple event files you need to download the latest version I attached where the event files were posted. I'll release this as v7.0.5 when I get time.

It is currently not possible to use the FSUIPC auto-save files as there are currently issues with saving and loading flight files via simconnect (which FSUIPC uses), although this is possible directly from MSFS. We are waiting for this to be addressed by Asobo. John

Yes, and you have to add it to the [Auto] section of the FSUIPC7.ini file. This is explained in the step-by-step guide for the Alpha and Bravo scripts, or see the section Automatic running of Macros or Lua programs in the Advanced User Guide. John

Yes, we are aware of it. There are issues when calibrating for PMDG aircraft in FSUIPC due to priority levels of the axis controls being sent. However, you can still assign in FSUIPC but assign to the FS control and not direct to FSUIPC calibration. However, this may be depend on the axis (e.g. throttle vs aileron/elevator). Best to just try and see what works for you. If you assign to FSUIPC calibration and calibrate, but you then suffer from a jittery axis, then this is usually a sign that different values are being received (due to the priority level issue mentioned) and you should switch back to 'Send yo FS' and not calibrate. Ok, then just leave it as it is! Then can't (or shouldn't) happen. Next time it happens, post again with your FSUIPC log and ini files and I'll take a look. Would be better if, once it occurred, you could activate logging for buttons & switches and events, and press the button again to generate the log entries (you can do this without closing the FS or FSUIPC). Then close the sim and post your log and ini files. John