Jump to content
The simFlight Network Forums

John Dowson

Members
  • Posts

    12,277
  • Joined

  • Last visited

  • Days Won

    250

Everything posted by John Dowson

  1. ok, didn't know it was called that! No idea what could have caused this, but not FSUIPC.
  2. Yes, but use your profile name ([Auto,xxx] where xxx is your profile name) or if not using profiles then just [Auto]. Please read the documentation - how to auto-start luas is explained there - as well as most other functionality! John
  3. Your log shows: Why have you installed the hid/usb driver and not the com/serial driver? Please remove that and install the pfccom64.dll driver. I think you also need a registered version of FSUIPC7 - although not sure.... Do you not have a license? If not, try the trial one attached - just save it to your FSUIPC7 installation folder. Also, please only attach files after you have exited FSUIPC7, not while it is still running. John
  4. Trial licenses sent via PM. John
  5. Rather than using offset 0x07CC for the heading,, it is better to add the AUTOPILOT HEADING LOCK DIR simvar to a different offset, so that this doesn't trigger the default behavior associated with that offset. To do this, you need to use the myoffsets.txt file. Create this file (in your FSUIPC7 installation folder) if it doesn't exist, and then add the following line: 0xA000, 2, AUTOPILOT HEADING LOCK DIR, F64, degrees This will add that simvar to offset 0xA000. You can change this to another free-to-use offset if already using this one. you then need to change/update your VB code to use this offset for the heading. Then you will need a simple lua script to update the heading when this offset changes value. The script should be auto-started using your profile-specific [Auto.xxx] section, e.g. [Auto.FBW-A32NX] 1=Lua FBW-Heading The lua file (also attached) is straight-forward, and just sends the offset value using the appropriate control, when the offset value changes: FBW-Heading.lua Please try this and let me know if you have any issues. John
  6. Your comments are extremely small and difficult to read - can you please try and post them as plain text in future. Please read the documentation on how to use presets, in the Advanced User guide, in the WASM section. Presets are made available via the mobiflight events.txt file, and you can also define your own in a file called myevents.txt. They are loaded automatically and available for assignment when you select/check the Select for Preset checkbox. The events.txt file is the MF file at the time of release, so is always slightly out-of-date compared with those available on the MF HubHop site. If you want to use a newer preset, you can download the events.txt file from the MF HubHob site and use that to replace the one in your FSUIPC7 installation folder. This is all explained in the provided documentation for FSUIPC7.
  7. You have to do more than that. As i said, please read the provided documentation on how to configure FSUIPC to use the PFC driver - the PFC DLL User Guide. Once you have read that and configured correctly, if you still have problems then please show me/attach your FSUIPC7.ini file, FSUIPC7.log file and PFCcom64.ini and PFCcom64.log files. But there is no point in attaching these until you have at least read the documentation and tried to configure this yourself.
  8. Have you installed and configured the PFC serial driver for FSUIPC (available from fsuipc.com)? If not, please do that - and make sure that you have read the documentation...
  9. Can you explain what you want to achieve? As I said, you can use either the Heading Bug inc dec controls, or the custom events. You will need a lua script that uses the A32NX.FCU_HDG_SET control, via calculator code, if you want to use an offset to control the heading bug. If you can let me know exactly want you are trying to do, I will look into it, but probably tomorrow now. John
  10. What is AAU2? What weight data from FSUIPC are you using? Have you tried monitoring the weight offsets used, to see if they hold the correct data? I have checked a few of these offsets and they seem correct in the 787-10: 0x1400: PAYLOAD STATION WEIGHT:1 - 170.0 0x1420: PAYLOAD STATION NAME:1 - "Pilot" 0x1430: PAYLOAD STATION WEIGHT:2 - 170.0 0x1450: PAYLOAD STATION NAME:2 - "Co-Pilot" ... 0x30C0: TOTAL WEIGHT: - 440876.40625 0x30C8: TOTAL WEIGHT - 13702.8886714 Not sure why they would say this. Nothing has changed in FSUIPC as far as the weight data is concerned. If this occurred after an aircraft update, it will be the aircraft update that caused this. If you need further assistance, please provide more information, i.e. which offsets are being used
  11. I can only seem to change the heading with the Heading Bug Inc/Dec controls. The fast versions of these controls do not work either. Both the fast versions of these controls and writing to offset 07CC use the Heading Bug Set control - this control doesn't seem to be working in the FBW A320. However, it is probably better to use the FBW custom events (or presets). These events are provided in a file called flybywire-aircraft-a320-neo.evt located in your EventFiles subdirectory. Copy or move this file to your FSUIPC7 installation folder (i.e. up one level) to use. Once installed, you will have the following custom events that you can use for the FCU heading: A32NX.FCU_HDG_INC A32NX.FCU_HDG_DEC A32NX.FCU_HDG_SET A32NX.FCU_HDG_PUSH A32NX.FCU_HDG_PULL If you want to control the heading via offset 07CC, you would need a lua script to monitor this offset and send the value (when changed) to the sim using the A32NX.FCU_HDG_SET event, or, probably easier, using calculator code. If you want to do it this way, let me know and I can look into providing a script for you.
  12. You have additional logging activated - check and clear your Log->Custom value. Looks like logging for custom value x10 (all simconnect events) The DontLogThese ini parameter only applies to standard event logging,
  13. No, its read-only... Ok, that is strange What version of FSUIPC7 are you using? Make sure you are using the latest version, 7.3.21: 0x07CE 2 AUTOPILOT HEADING LOCK DIR:3 Responded Autopilot target heading value, as degrees*65536/360 Not sure when that was added but was quite a while ago... As I said, I am no A320 expert, but I can take a look for you tomorrow and report back. John
  14. Which version of the FBW A32NX are you using? I am no expert for the A320, but I think this can depend on the AP mode (managed or selected). If the Autopilot Heading lock is set (offset 0x07C8) then you cannot update this value. You could try offset 0x07CE (target heading), or look at the available MF presets to see what they use to control the AP heading value, and use that - either the preset directly or the lvar (or whatever the preset is using). I will update the title and maybe some other FBW users can help.
  15. No need to change the comments as they are rewritten. It is not possible that the control numbers change unless you change them. If you are editing the ini when FSUIPC is running, make sure the appropriate assignment panel is open first, and click the reload button once you have saved any changes. No problem. Cheers, John
  16. If you want full access to the facilities data, you will have to use the SimConnect SDK. I can look into providing an offset area for facilities data requests, but this would return limited data. I can look into this to see what I could provide, but it won't be until at least September now. I will make a note and get back to you when I have looked into this in more detail. John
  17. 👍😎
  18. Please see the following post: That post includes a preset for the condition lever that moves it between the 4 discrete positions on an axis. Basically the condition levers positions are controlled by the lvars L:MSATR_CONDITION1_POS and L:MSATR_CONDITION2_POS which take a value between 0 and 3, with each number representing a discrete position.
  19. License sent via PM.
  20. I have updated and released MakeRwys for P3Dv6. The Lorby Scenery Exporter has also been updated but not tested. Please report any issues, Thanks to Lorby (Oliver) for the fast update of the Scenery Exporter. Regards, John
  21. Note that I have now released v6.2.0 which includes this update.
  22. I have now updated MakeRunwys for P3Dv6. However it will also need an update of Lorby's SceneryExporter to process Add-On scenery. I will release the update version when this is available. FSUIPC6 v6.2.0, compatible with P3D versions 4. 5 & 6, has been released. John
  23. All presets are provided by the FS community driven by MobiFlight, and available from https://hubhop.mobiflight.com/presets/. I can see you have already asked the MF team about this on their discord channel, which is generally the correct place to ask about presets. John
  24. I haven't yet but will...don't think there is a P3D version check in MakeRunwys but I will test over the weekend. The bgl format should be the same.
×
×
  • 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.