Jump to content
The simFlight Network Forums

John Dowson

Members
  • Posts

    13,453
  • Joined

  • Last visited

  • Days Won

    278

John Dowson last won the day on August 14

John Dowson had the most liked content!

Profile Information

  • Gender
    Male
  • Location
    Spain

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

John Dowson's Achievements

Grand Master

Grand Master (14/14)

  • Well Followed Rare
  • Reacting Well Rare
  • Conversation Starter Rare
  • Very Popular Rare
  • Dedicated Rare

Recent Badges

614

Reputation

  1. Even better: if ipc.getLvarId("L:Lear_LDG_Weight") == nil then ipc.createLvar("L:Lear_LDG_Weight",10361) while (ipc.getLvarId("L:Lear_LDG_Weight") == nil) do ipc.sleep(50) end end ipc.execCalcCode(" (A:TOTAL WEIGHT, pounds) (>L:Lear_LDG_Weight) ") -- get current total weight ipc.sleep(200) ldg_wt = ipc.readLvar("L:Lear_LDG_Weight") ldg_wt = math.floor(ldg_wt + 0.5)
  2. I don't have the fenix, but if you engage vnav by pressing the altitude button, you could try the preset FNX320_FCU_ALTITUDE_KNOB_PUSH. See https://hubhop.mobiflight.com/presets/?vendor=FenixSim&aircraft=A320 for a list of the available presets for the Fenix - all MobiFlight presets are available for assignment in FSUIPC. You can also see these by using the Find Preset button in the assignments panel, after checking Select for Preset:
  3. What part? And what part don't you understand? In which panel? as I said, you cannot change this in the axis panel. In button & key assignments, you can assign a button to either a profile or not, and should be able to check/uncheck the profile-specific checkbox accordingly. If this is not clear, please provide more information - what arte you trying to do? Which panels are you using - axis, button or key assignments?
  4. For PMDG aircraft, you can use the provided custom controls. See For the NG3, the custom controls are: #define EVT_MCP_VNAV_SWITCH (THIRD_PARTY_EVENT_ID_MIN + 386) #define EVT_MCP_LNAV_SWITCH (THIRD_PARTY_EVENT_ID_MIN + 397) You can also use FSUIPC's logging facilities to determine what is being used: set logging for Events, open the logging console and see what is logged when you press the switch in the virtual cockpit. This will be a custom control using the Rotor Brake control, which is an alternative method of using PMDG custom controls, also described here: (N.B. when logging events in many add-on aircraft you will see many events being continually logged - you should ignore such events using the DontLogThese ini parameter) For the Fenix, you can also use logging to determine what is being used. If no events are logged, try listing the available lvars (Add-ons ->WASM->List Lvars) to see if any look applicable.
  5. There are a few things that could be improved in the script: 1. You only need to create the lvar once, do you should handle this if the script is being called multiple times. 2. If you create an lvar using ipc.creatLvar, you don't need to reload the WASM afterwards - this is done automatically. As for the timing issue, lvar values are, by default, updated and send out from the WASM at a frequency of 6Hz, so roughly every 166ms.Therefore a delay of 100ms is not going to be enough most of the time, although this depends on the timings. Taking into account the time needed to send and process the request, you would need a delay of 200ms to make sure the new value had been received. if you want faster updates, you can set the WASM ini parameter LvarUpdateFrequency to VisualFrame. if ipc.getLvarId("L:Lear_LDG_Weight") == nil then ipc.createLvar("L:Lear_LDG_Weight",10361) ipc.sleep(600) end ipc.execCalcCode(" (A:TOTAL WEIGHT, pounds) (>L:Lear_LDG_Weight) ") -- get current total weight ipc.sleep(200) ldg_wt = ipc.readLvar("L:Lear_LDG_Weight") ldg_wt = math.floor(ldg_wt + 0.5)
  6. Thanks for this - I will move it to the User Contributions section. Also note that another way to use the mode switch to have different assignments to the same button/switch depending on the mode switch positiin is to use compound assignments. You need to manually edit the FSUIPC7.ini file to do this, and the method is documented in the Advanced User guide. However, this is only applicable to button (and key) assignments, not for axis assignments. John
  7. Your license information is available in your SimMarket account. John
  8. Yes, you need a radar.bmp file for any of this to work. This was provided by ActiveSky, but that functionality isnt available for MSFS. Once you have the radar.bmp file then sharing/displaying shouldnt be a problem. But I do not know how you can generate such a file with MSFS. Note I am on holiday now until September. John
  9. You just add it to your ini and it akways applies. But dont switch it off (i.e.set to yes), try setting it to Enum first. This will still monitor, but using a different method.
  10. Just caught me in time... Currently lua is the only possible way to do this. I will look into allowing 2 parameters for events at some point, but I have a few more urgent things that I need to do before I can look into this. Note I am now on holiday until September, although I will be checking for support issues occasionally. John
  11. Please also note that I am now on holiday until September, although I will check for support issues occasionally. I am now out-of-contact until Monday though. John
  12. As with all other users who report this, your key validates just fine. I will pm you a key file and try this. Save the key file to your FSUIPC installation folder, then re-run the installer and validate the key by clicking the Register button at the end of the installation process, If it validates, then the only possible reason that you are unable to register is that you did not enter the details correctly. If it does not validate, and you have installed the required VC++ redistibutables, then it can only be your anti-virus software blocking the validation - please check that.. Can you PLEASE respond once you have done this. I would like to understand why so many people are having this issue so that I can update the documentation accordingly, but nobody is responding. John
  13. Do NOT manually edit the [LuaFiles] section. This section is maintained by FSUIPC. Your script is never running, so the offset will not get updated. Before you write the axis value to an offset, check if you can use either offset 0x3416 / 0x3418. If you just want notification that the brakes are being used, you could also try the 'brake being used' flag in offset 0x32F9. So check these offsets first. If none of those offsets are working, then maybe consider using a lua script. If those offsets don't work and you want help with a lua script for this, it would help me if you could provide a log, with logging set as previously advised. Note that I am now on holiday until September, but I should have time to look at this again on Monday if you need help with a lua script (so please provide the log file before then). John
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.