John Dowson

Why do you need to create a variable? You can just write whatever you want to a (free for general use) offset. You can write to offsets using either the provided offset controls or lua. If you want to create a variable, then create an lvar, but I do not understand why you would want to do this. 0x66C0 is an offset, not a variable. Please do not confuse the two. If you want to write 1 to the offset (or maybe toggle between 0 and 1) when a switch/button is pressed, then assign the switch/button/whatever to an offset control, such as Offset Byte Set or Offset Byte Togglebits. You can overload your assignments if needed, so the button/switch can also send other controls/perform some other function as well as changing an offset value. Please note that I am on holiday now, and will not responding further until January. Please use the provided documentation and these forums - all the information you need is there somewhere, although it can be difficult to find... John

What information? If you want the ADF information, this is already held in offsets - search the Offset status document for ADF. That will never work... The myOffsets.txt file is for adding simvars (or A-type variables) to offsets. Those are FS events/controls and do not have an associated value. John

The trial license (key file) is available to download in the very first post in this topic. However, please note that WideFS has nothing to do with multi-screens, it is for running FSUIPC client applications on a networked client PC (i.e. a different PC to the FS). You are probably thinking of WideView.

You do not have access to the assignments menu as you are using an unregistered version. PLEASE read the provided documentation, namely the INVALID KEY SECTION of the Installation and Registration guide. Just update your VC++ redistributables, as indicated, and as already reported so often that I find it very difficult to answer such questions without being derogatory...

Glad that your issues seem to be resolved. Have a great christmas as well, and best wishes for the new year, John (from Oporto!).

The 'L:' is optional - I like to use it - force of habit. Your code was failing for the other reasons I mentioned, not that. There are various quote signs - if you look at the lua documentation for the ipc.writeLvar function, you will see that the double quotes around name are right and left sloped (i.e. opening and closing double-quotes) - this is what some editors/word processors insert, but for lua code you should just use standard double-quotes. Some folks get in trouble by using the wrong double-quote, which can be difficult to spot. Please note I am now on holiday until January. John

Its normal brackets, not square ones, and you don't need the end, and be careful with the quote symbol, i.e. ipc.writeLvar ("L:C310_LEFT_FUEL_PUMP", 0)

Auto-save is known to cause issues (pauses or stutters) when using complex add-on aircraft, and as anti-virus software is getting more aggressive it seems to be affecting more aircraft. See the following post for possible solutions: Autosave is not active in the unregistered version... John

No. If its not document, you cannot do it. As I have already said, you cannot invent your own syntax and expect it to work. Please consult the documentation for such issues. Or just try it - you will see that you get an error.

Check the MSFS logging console (you need to switch to devmode) - do you see any messages there? Is anything reported in the FSUIPC7.log file (ALWAYS a good idea to attach this for any issue, as well as your FSUIPC7.ini file)? Are you using a registered/licensed copy, or unregistered? If the latter, do you still get this issue when unlicensed/not registered? Unfortunately (for you!), I am now on holiday until the new year. Please try what I have already said and let me know the results, and attach your .log and .ini files and I can take a look in the new year. John

Please don't embed new questions in quoted text - it makes it very difficult to see what you are actually saying. But you obviously do! You are already using the offset controls, which are also added by FSUIPC. There is no distinction in the drop-downs between FS-defined controls and those added by FSUIPC. Use '..+8', as 8 is 'normal', i.e. no shifts. No it is not. Please see the Advanced User manual on the definition of key controls. The 'K...' syntax is for the key you are programming, not what the key is sending. Don't invent your own syntax and expect it to be valid. Yes, that is confusing, and I am not even sure it is even valid, That syntax is for joystick buttons. I will update the manuals and remove. Please note that I am now on holiday until the new year. Any more questions will have to wait until then. John

Sorry, but I didn't/don't see a question there... Yes, by using the key press/release controls - from page 28 of the Advanced User guide: 1070 Key Press and Release (param is Keycode + Shift code (i.e. enter with + symbol, not calculate), or JsBk) 1071 Key Press/Hold (param is Keycode + Shift code( i.e. enter with + symbol, not calculate), or JsBk) 1072 Key Release (param is Keycode + Shift code (i.e. enter with + symbol, not calculate), or JsBk) Those controls should be available from the assignments drop-down menu when using standard FS controls (i.e. not presets or Input Events). John

What version of FSUIPC are you running? The latest version is 7.4.1, so if not using that please update and try again. There was an issue with FSUIPC flooding the MSFS console/log after an MSFS update around a year ago, which could cause stuttering, but this was soon resolved. The latest FSUIPC should not cause any stuttering, and is perfectly compatible with Spad.Next and other add-ons. John

A32NX_PARK_BRAKE_LEVER_POS is an lvar, not a simvar. You need need to use the Adding Lvars to Offsets facility, described on page 46 of the Advanced User guide, not the myOffsets.txt file which is for simvars (or A-type variables) only. John

Yes. The easiest way to assign an axis to control an lvar value is to use a preset. See the following post where a preset is used to control an lvar for the throttle (in the Duckworks mod of the DC3): John

I am sorry Ray but I have no idea. Try asking on the P3D forums and include that AppHang event. There is a post on P3D appHang with v5, but it doesn't say much: https://www.avsim.com/forums/topic/602354-p3d-v52-freeze-application-hang/ Always worth updating your graphics card drivers, if you have not done so already... John

License sent.

It will be generated the first time you run that version.

Bvars are input events (as far as I am aware - or closely related). The latest release of FSUIPC7, 7.4.0, enables direct assignment to Input Events. Other than that, there is no direct access to B-type variables, and you cannot use them via calculator code. You can alter the xml files to allow b-var control via lvars, But I think that it would be better to look at the available Input Events before you consider this. There is a post somewhere where I showed how to do this. John

I have no idea how to do that. For windows defender, there should be logs/events for all activity in the windows event viewer - see https://learn.microsoft.com/en-us/microsoft-365/security/defender-endpoint/troubleshoot-microsoft-defender-antivirus?view=o365-worldwide This should tell you when a scan was started, finished, etc. Maybe next time you get a pause, cross-check with the events there, which should then tell you if this could be related to windows defender activity. Of course, if you use any other anti-virus software, you would need to check where that logs its activity.

Please see my previous response. You evidently do not understand the difference between the left and right hand sides of the axes assignment panel. You need to assign your axes on the left hand side, selecting Send Preset to FS, NOT on the right-hand side, which is for sending button assignments when entering/leaving ranges. These two things are completely different. Please see the provided documentation. And for ANY issues, please post here: That is the initial post, with solutions, for this issue. Post there if you have any further issues. I am also now locking this topic. John

Can you not log anti-virus protection behavior? That would give you more insight, if you think that this is the cause of such pauses/freezes. In a previous life, I used to investigate/trouble-shoot such problems for business apps, and the issue was invariably caused either by the OS not being tuned for its purpose, or from large-scale garbage collection. But this was in my unix / java days. Windows internals are more of a mystery to me that I would rather not enter into more detail than needed.... 😉

I am sorry you feel that way. I just don't understand why you would want to contact Hi-Fi when you have no information that your issue is at all related to AS. But do as you want.

Why are you creating a new post, rather than posting in the existing post for this issue? But why? Do you understand the difference between the left-hand side and the right-hand side of the axes assignment dialog? The left-hand side is where you assign to your axis, i.e. to send controls based upon the position of your axis lever which uses the value associated to the axis lever position. The right-hand side is to send specific controls when the axis lever enters or leaves a specific range (this side to send button controls) , but the value of the axis lever position is not used. Please at least read the provided documentation if you do not understand the UI, it is explained there.... What you need to do is to use the presets as given in the other post, and assign to the axis using the left-hand side of the axes assignment dialog, selecting Send Preset to FS. I am closing/locking this now. Please use the original thread for any more questions using these presets:

But why report to Damian/Hi-Fi as it could be nothing to do with AS? As a developer. it is very annoying when people keep pointing the finger at your software as the culprit for some strange issue that is not at all related to the software that you provide. I get this all the time, and it is very frustrating as well as being quite time consuming. My suspicion is that it is either windows or P3D, but with these types of issues it is incredibly difficult to determine the cause, and quite often they disappear as easily as they appear. I has an issue last year that caused my flight sim PC to pause for several minutes, and then my system was auto-rebooted, with no logs or errors reported anywhere. This lasted for 6 months without resolution. I don't have this problem anymore, but I suspect it was a GC card/driver issue.