Jump to content
The simFlight Network Forums

John Dowson

Members
  • Posts

    13,293
  • Joined

  • Last visited

  • Days Won

    271

Everything posted by John Dowson

  1. I understand what is happening, what I am saying is that it is impossible for FSUIPC7 to start another copy of itself (unless you specifically ask it to via the [Programs] section of the ini file). Something else is starting another copy, maybe MSFS, maybe another add-on, I just do not know. What happens if you remove the start of FSUIPC7 from your EXE.xml - is it still started or are no copies started? Try that. If FSUIPC7 isn't started, add it back and see if that fixes things. Other than that, I cannot really help. This has nothing to do with FSUIPC7 itself. If two copies are started via the EE.xml (that previous test I mention should tell you this), then maybe ask on the Asobo forums. John
  2. Do you understand the difference between the left and right hand side of the axis assignment panel? Have you read the user guide on axis assignment? If not, start from there. You are highlighting the dec preset FNX32_DISPLAY_BRIGHTNESS_L_ND_WX_DEC. It makes no sense assigning an axis to a dec control, certainly not on the actual axis (left-hand side of the axis assignment panel), and also usually not on entering/leaving an axis range (right-hand side of the axis assignment panel). Looking at the calc. code for that preset: (L:A_DISPLAY_BRIGHTNESS_CI_OUTER) 0.05 - 0 max (>L:A_DISPLAY_BRIGHTNESS_CI_OUTER) This is taking the value of an lvar, subtracting 0.05 from the value, then setting this as the new value. i.e. it is decrementing the lvar L:A_DISPLAY_BRIGHTNESS_CI_OUTER by 0.05. You can define your own preset to control the lvar value with an axis. There are several ways to do this, the easiest way being to define your own preset. First, you have to determine what the value range for that lvar is. Log the lvar values when at minimum and maximum brightness, I am going to assume that the lvar takes a value between 0 (off) and 1 (full brightness). I assume your pot axis range is -16387 - +16388. So, what you need to to is define a preset that scales the axis value to the lvar range and then sets the value to the lvar. This is such a preset - add this to your myevents.txt file (create this if it doesn't exist): Then you can assign your axis to this preset, using the left-hand side of the axis assignment panel, by selecting 'Send Preset to FS'. The preset should be listed under your Personal presets. See the WASM section in the Advanced User guide on using presets and the myevents.txt file. John
  3. No luas were auto-started, including the ipcReady.lua, as there was a failure getting a connection to the WASM module: Not sure why this was, but please update and try the latest beta which, as well as adding new functionality, has been recompiled with the latest SDK (0.23.1.0) which was released with SU14 / 1.35.21.0. This version is available here: John
  4. But your log shows the pot is working fine - it was just assigned to a control/event that wasn't doing what you expected (LIGHT_POTENTIOMETER_15_SET). As I said, assigning to that here gives the same symptoms that you saw (screen white) - nut in a different aircraft (Asobo A320). You just need to assign it to the correct control/preset/input event for the function you want to control.
  5. The DELAY option with CONNECTED wasn't reliable in the previous version, corrected in the attached. John FSUIPC7.exe
  6. Yes you can, also the heading is there. But that is ground traffic, you would also need to use the airborne offsets starting at 0xF000. Then that would be a P3D function.... John
  7. Looks to be a timing issue between two threads, hopefully fixed in the attached if you could try it. I have also updated the beta download to include this version. John FSUIPC7.exe
  8. No easy way that I know of. I am not sure if the position (lat, long, altitude) of AI traffic is available. If so, you could possibly do something by using the SimConnect_CameraSetRelative6DOF function to manipulate the current camera, available via offset 0x86A0, but I would have little idea on how to go about this without looking into this. And, as I said, you would need to determine the aircraft position first, and also probably the direction of travel so that you could determine the position to place the camera. All very complicated... John
  9. If its launching twice, something is launching it twice...I have no idea what this could be, sorry. That is extremely weird...I cannot see how that option can have anything to do with FSUIPC being launched. FSUIPC needs to be running to check that option, and there is no possibility that FSUIPC itself can launch another copy.
  10. Everything is working as expected here today, with both Run and RunIf. Not sure what happened yesterday, strange... Anyway, I have just released a new beta version re-compiled against the latest SDK. Please update to that and re-test. Any issues, please attach your files. John
  11. I suspect that you were still using the previous release - maybe your browser had cached the download. Anyway, I have released a new version, recompiled to the new SDK released yesterday with SU14. Please download and try this, and check it is installing 7.4.0d.
  12. Are you sure that you are using the correct version?
  13. No programs are started now here, with Run or RunIf. It looks like the latest update has broken quite a few things. I have a lot of work to do tomorrow...
  14. I don't understand this at the moment... it was all working as expected when I tested this. I will test further and let you know when an update is available. Quite a few issues with the latest SDK. Pain in the ass... xmas lunch today with quite a bit of wine. I will look into this tomorrow 😉 John
  15. Your log also shows lots of other errors which are rather worrying.... There is an SDK update with the latest release to SU14 last night/today. I am currently in the process of updating to the latest SDK and will make a new release when done and tested, hopefully tomorrow. John
  16. Good, I was only checking... I see you are using RunIf. I haven't tested with this - I will check this and update if needed.... John
  17. No, no chance. There are no facilities provided by Asobo/MSFS to implement this feature, and theere is no planto do so. Things have moved on..... There are several other options available that replace the need for these: hvars, input events, and presets/calculator code. But there are also so many new ways to control/assign. Have you looked at the presets available? See https://hubhop.mobiflight.com/presets/ - these are all available from FSUIPC by selecting assignment to presets. Hvars (html variables0 are also available, but these are difficult to discover and best best used via presets. Input Events are the latest innovation. Currently these are only available in the latest beta release of FSUIPC7, which I will release before the end of the year. You can try these in the latest beta, available from John
  18. All license details for products purchased from SimMarket can be found in your SimMarket account. Look at your Purchase History and click the relevant Order No.
  19. Ok, I will look into this next week. Is that mapping I proposed ok? I will also map the following helicopter throttle controls: AXIS_HELICOPTER_THROTTLE_SET -> Throttle HELICOPTER_THROTTLE_SET -> Throttle AXIS_HELICOPTER_THROTTLE1_SET -> Throttle1 HELICOPTER_THROTTLE1_SET -> Throttle1 AXIS_HELICOPTER_THROTTLE2_SET -> Throttle2 HELICOPTER_THROTTLE2_SET -> Throttle2 There is also AXIS_TAIL_ROTOR_SET, but I am not sure about this one.... If you could update to the latest beta at some point (currently 7.4.0b), I will post an updated beta here for you to try this when done. The latest beta is available from John
  20. License sent. John
  21. I understand your issue, but there is no way I could possibly allow calibration for any axis. Calibration is only useful for the main flight control axis, and I fully understand that this is currently not possible for the new axes for helicopter flight control. The only possibilities at the moment are to use the axis scaling functionality, as you are doing, or to write the axis value to an FSUIPC offset and have a lua script pick-up the value and apply any calibration needed before sending to the FS. I am not prepared to add further calibration pages for helicopter axes at the moment - I just don't have the time for such a large undertaking. What I could do is to map the helicopter-specific axis to the existing calibration sections (i.e. aileron, elevator, rudder, throttle, mixture, prop pitch). As I am not familiar with helicopter flight controls, does this seem reasonable, and if so what would the mapping look like? e.g. AXIS_CYCLIC_LATERAL_S -> calibrate as aileron AXIS_CYCLIC_LONGITUDINAL_SET -> calibrate as elevator AXIS_COLLECTIVE_SET -> calibrate as prop-pitch ?
  22. Are you sure that you are using the latest beta release, 7.4.0b? Please check this as your browser may have cached the download file. If that is not the issue, please show me your .log and .ini files... John
  23. So it was there...why couldn't you find it earlier? That log file ends after less than a second (94 milliseconds) and shows nothing. FSUIPC7 was also still running. Unless something is stopping it. Check your anti-virus. But I don't think it is going to reveal anything anyway. You are using an unregistered version. There is no way your pauses/freezes have anything to do with FSUIPC7. I have now finished for the day. 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.