John Dowson

That implies that you are not using a registered version. Re-install, and make sure you click the Register button towards the end of the installation process, after you have entered your registration details. John

No problem. Note that there is also documentation in French, but for FSUIPC4 (inly) - most (or a lot) of it should be applicable, but some things not. Available from the Downlinks -> Documentation section: John

There is a separate document for Profiles in Separate Files - this is the relevant part: Oh - and do not manually update the [LuaFiles] section - that is maintained by FSUIPC from scanning the installation folder. John

You are using UseProfiles=Files i.e. profiles in separate file. Your [Auto] section should therefore be in your FLYBYWIRE.ini file, and called [Auto] and not [Auto.FLYBYWIRE]. John

To determine where your Community folder is in a steam installation, you need to look in your MSFS UserCfg.opt file, which for steam installs is under YOUR USER ACCOUNT\AppData\Roaming\Microsoft Flight Simulator\UsrCfg.opt Look for the last line, which is your InstalledPackagesPath - the Community folder sit under there. If you are using FSUIPC7, it is also logged in your FSUIPC7.log file, at the beginning as the FS (or FS UNC) path. John

I have moved your post from the .net client dll support forum as it seems your questions are more related to FSUIPC offsets than anything to do with the .net client. To find an offset, please use the Offset status spreadsheet, included in the FSUIPC7 download zip. In that, you can find the brake left and brake right position in offsets 0x0BC4 and 0x0BC6 respectively, as well as various other offsets (e.g. 0x3416 & 0x3418 for axes input values) I don't think this is available. Check to see if held in any lvars, or if using the FBW A320, maybe ask about this on their support/discord channel.

Ok, but I've just released 7.2,8 with a few memory fixes, so you should update to that - includes an update to the WASM as well. Yes, good idea - I will do the same! Yes, looks an interesting beast, although I'm not sure when I'm going to find time to understand and fly this a/c proficiently - I get very little time for recreational flying these days... Cheers, John

No problem. There are still possible memory corruption issues in that version due to excessively long lvar names (>56 chars). I've corrected this now (currently testing) and will release a full version (including a WASM update) later today. This will be the official 7.2.8 release. There will be some issues accessing lvars/hvars with more than 56 characters, and I'm not too sure how to handle this yet, so further work will be required. I will update the Advanced User guide with details.

The Assignments tab is only available in registered versions - you are running an unregistered version. You need to re-register (using the installer) to generate your .key file. If you don't have a license, there is a time-limited trial license available at the top of this forum. Not sure what you mean by this, but you also need to register your WideFS7 license during the FSUIPC7 installation process. So, re-run the installer and don't forget to register your license at the end of the installation process, by entering your license details and pressing the Register button. John

Looks like I messed up the UB conversion in that version - please try the attached: FSUIPC7.exe

What does not work? Please provide more information, i.e. is the offset populated and you just cannot update, or is the value not even populated? And please show me your log and ini files - required for any issue really. John

Asobo CJ4 or the Working Title mod? Have you tried logging events (with console window open) to see what events are used when you start the engine manually via the UI? Have you looked at available lvars (and maybe hvars) to see if any seem relevant, and the values they hold when you start via the UI? Let me know which version of the CJ4 you are using and I can take a look later - or probably tomorrow, as I have an urgent issue I need to look into today. John

The OPs issue must be with the code, as updating the offset does send the correct control (SPEED_SLOT_INDEX_SET), and it does have an effect - when the engines are running, as the related simvar (AUTOPILOT SPEED SLOT INDEX) is updated and the new value received and populated in offset 0x0298. If it was not possible to do this due to the aircraft state, the control would still be sent but would have no affect, i.e. the AUTOPILOT SPEED SLOT INDEX simvar would not be updated and no change in value would be seen in offset 0x0298. John

Found the issue. There was a memory issue as there are some lvars in the FBW A320 that exceed the maximum configured length of 56 characters, e.g. this one has 85: A32NX_ADIRS_ADR_1_INTERNATIONAL_STANDARD_ATMOSPHERE_DELTA32NX_ADIRS_IR_1_GROUND_SPEED i have corrected one issue that this causes (and you were experiencing) in the attached version, v7.2.8b, so please try this. However, such long lvar names may cause memory issues elsewhere, as I would expect such long lvar names to be truncated to the configured value, which they are not. I will therefore look into this further. John FSUIPC7.exe

Also not that using lvars directly, you can open the door with the canopy still closed, which you can't actually do in the UI. If you wanted to replicate this behavior, you would have to use a lua script to check the lvar AIRFRAME_CanopySlider (and maybe AIRFRAME_CanopySliderTarget ) to see if the canopy is open before trying to set the lvar to open (or unlock) the door.

I don't fly VR, but those Authenkits do look interesting though, thanks for the link. Anyway, I've found the problem - I hadn't update the lvar write code to recognise the new 'F' flag, and there were some dodgy type conversions when setting using doubles/8-bytes. This has been corrected in the attached version. With this, you can control as previously advised, by adding L:AIRFRAME_DOOR to an offset (either as a float or double) and then using the Offset Float32 Set/1000 (or Offset Float64 Set/1000) control. John FSUIPC7.exe

Can you show me your FSUIPC log file please, from when this occurs.

Can you please also show me your FSUIPC7.ini as well please. Also, please check the windows event viewer to see if there is a crash event reported there, and if so please show it to me. Always with the same aircraft or different aircraft? From the Add-ons -> WASM menu? Is this repeatable? When does it crash? Is the dialog box displayed and the drop-down menu with the lvars populated? Could you activate debug level logging in the WAPI by changing the LogLevel to Debug (in your FSUIPC7.ini) and generate a new log file please. John

What do you mean by 'stops' - does it crash? Can you list lvars? Can you at least show me your FSUIPC7.log file, from when this occurs. You may need to enable some logging, but show me your log file first. John

Ok, good - that is what I suspected. I will amend the Advanced User guide to mention this if using profiles in separate files, as its not clear. Yes, as do us all! There isn't much documentation on lvars, and FSUIPC is aircraft agnostic, so it handles all lvars equally (internally) as 8-byte (64-bit words (doubles). I'm afraid it is always up to the user to know what the actual type is, and use the appropriate functions when reading/writing or using in offsets. John

I am confused by your FSUIPC7.ini. You have included a separate profile ini, which is used when you are using profiles in separate files. However, you are not actually using profiles in separate files - you have: UseProfiles=Yes and not UseProfiles=Files So I think that maybe the lvars-to-offsets is working, but not your assignments to that offset. Having said that, there may be an issue with using the LvarOffset ini section when using profiles in separate files. I haven't checked/tested this yet. It may work, I'm not sure, but I don't think it will automatically transfer the LvarOffsets.<profile> section to your separate ini file. So, first, change to using UserProfiles=Files (if that is what you are using) and see if it works then. If not, manually copy your [LvarOffsets.FLYBYWIRE] FSUIPC7.ini section to your FLYBYWIRE.ini and rename to just [LvarOffsets]. I'll also check this here, as I hadn't considered the profiles-in-separate-files option when I implemented this. John

I'm sorry, but what do you mean? What functions? These are lvars - do you know what they are and how to use them? I am assuming you know what I am talking about. If not, I suggest you read up on what they are, and consult the FSUIPC user guide + advanced user guide on how to use them. Me neither. But that offset is in the range reserved for PMDG, so it is in no way applicable to the A320. I really cannot help you if you are not trying what I am recommending. Have you tried listing the lvar values and changing them to see what effect they have? You can do this via the Add-ons->WASM menu. You need to do that first, to see what works for what you want to achieve, and once that is done you can then think about setting up button or key assignments (or maybe lua scripts) to achieve the same. The A320 is a complicated beast. Try the FBW discord forum (https://discord.com/channels/738864299392630914/750095266937438258) for questions on the FBW A320, and also the MobiFlight webapp they have for the FBW A320 - in the links I have posted, twice! I can help you to get things working via FSUIPC if you know what actual works in the aircraft (lvars/hvars/calculatot code/MF presets), but I cannot possibly support all functions for all the various add-ons/mods. You have to do some of the work. John

Hi Andre. I've bought the Spitfire now and will take a look at this later this afternoon or evening (a bit busy at the moment on non-MSFS stuff....). I went to the Reginald Mitchell C.P. School in Butt Lane (Kidsgrove), where R.J. Mitchell was born, the designer of the Spitfire. I was born in Clough Hall (Kidsgrove), about a mile away. I've been thinking of getting a Spitfire for a while, although I don't usually fly combat aircraft... I'll ley you know what I find. Cheers, John

Hi Andre, Hmm, sounds very strange - I don't understand, for example, how the Toggle action can work but the Set not, as this should result in exactly the same code being executed in the WASM. This seems to contradict what you said earlier: I'll take a look to see what is happening. I don't have the a/c you are using, but I should be able to trace what is happening with any lvar, so I'll do that first. I may need you to activate Debug logging in both the WASM and WAPI and show me your logs (and FSUIPC7.ini) if I don't find anything this way, but lets see what I find first... While I'm doing this, maybe try adding the lvar as a 8byte (double) number, by using: and the Offset Float64 Set/1000 control. I'll try and look at this this afternoon, but may take a while... John

What do you mean by 'commands' - they are lvars. Did you try listing lvars to see what is available? And then try setting//changing them? Also, those lvars are for the Asobo A320, which is the a/c you initially said you were using. the FBW A320 is a different aircraft and will have different lvars. Anyway, just took a look om the FBW A320 (latest dev version) , and those lvars are available, as well as the following APU related ones: A32NX_APU_AUTOEXITING_RESET A32NX_APU_AUTOEXITING_TEST_ON A32NX_APU_AUTOEXITING_TEST_OK XMLVAR_Momentary_PUSH_OVHD_ELEC_APUGEN_Pressed A32NX_OVHD_PNEU_APU_BLEED_PB_IS_ON A32NX_OVHD_PNEU_APU_BLEED_PB_HAS_FAULT A32NX_OVHD_APU_MASTER_SW_PB_IS_ON A32NX_OVHD_APU_MASTER_SW_PB_HAS_FAULT A32NX_OVHD_APU_START_PB_IS_ON A32NX_OVHD_APU_START_PB_IS_AVAILABLE XMLVAR_APU_StarterKnob_Pos A32NX_APU_N APU_BLEED_PRESSURE ... Try activating the functions you want to program in the UI, and see which lvars are affected. Then try updating the lvars to see if they can be used to achieve the same. If so, you can then assign either using the lvars-to-offsets functionality with one of the offset controls (to change the offset value and thus update the lvar), or an lvar macro, or a lua script (needed if more complex calculator code is involved). Also, as I said, if using the FBW A320, check the MobiFlight preset list (https://hubhop.mobiflight.com/#/list) and see which lvars/hvars/calcularot code they are using and try to emulate that (or install the MF WASM module and use the presets via FSUIPC event files). You should also ask on the FBW forums as they will know more about the specifics of the FBW A320, Please report back how you get on. John