Jump to content
The simFlight Network Forums

John Dowson

Members
  • Posts

    12,287
  • Joined

  • Last visited

  • Days Won

    253

Everything posted by John Dowson

  1. Each button has a flag, so how can that be independent of the button being pressed? But yes, sorry, for the "latch flags", on one press the flag is set, on the next, the flag is cleared. However, I think the issue is that compound button conditions are meant to allow 'you to specify actions for one button which are dependent on the state of another button'. I just don't think this will work correctly if using for the state of the same button. But is doing this of any use, even if it did work? The result would be that C1 and C2 would be triggered on alternate button presses, so you would get C1 on the first press, C2 on the second, C1 on the third, C2 on the fourth, etc I guess there is no reason why it shouldn't work (in theory), but i would have to look at the code and test in FSUIPC6 or 7 to see why, and only those versions would be updated. FSUIPC will re-write the ini (or certain sections of it) at different times. If you are manually changing the ini buttons sections, the best way to do this is to - open the FSUIPC button assignments tab - load or reload the ini in your editor, make your manual changes and save - click the 'Reload' button in the button assignments tab to load your changes John
  2. Just took a look and I couldn't get the default space key assignment ('Mouse - control view direction (on/off)') to do anything, either with FSUIPC6 running or not. When pressing the space bar, the mouse cursor changes to cross-hairs but I cannot change the view direction. Same when using shift+O. It also seems that the FSUIPC 'mouse look' function is difficult to control when using the thiss on its own - not sure why. I find the best setting for me is to have the P3D Advanced mouse controls active, as well as the FSUIPC Mousewheel 'Move' and 'Mouse look' options checked. The space bar still sort-of resets the view (not sure why!) and ctrl+space does a proper reset. John
  3. Only events available via SimConnect will be logged. No, not as far as I know, which is next to nothing about these new event types. John
  4. It scans for all lvars by id and stops when a null lvart name is received, so if an lvar is not listed it is not available. You must have missed it - if you have added it successfully, it must be known to FSUIPC otherwise you would get an error. I meant also with Mobiflight of course. Does that use the Mobiflight presets? They are the ones available in the events.txt file. You could copy the ones that you want to use from that to your myevents.txt file if you want to use them, and be certain of the control number to use for them in offset 0x3110. John
  5. Of course only C1 works, as you are testing the flag on the button that is being pressed. So, flag 11,11 is always set when button 11,11 is pressed, and it is never not set when the button is pressed, which is what you C2 assignment is checking for. For C2 to work, you would need to do it on release, i.e. 101=CU(F-11,11)11,11,C2 But then this us the same as not using a compound condition at all, as in effect you are saying that you only want the press event to be sent when the button is pressed, and only want the release event to be sent when the button is released. This makes no sense. You should only use such compound conditions on different buttons (or button flags) to the one you are assigning. So you should dedicate one button that is used to determine what the other buttons send. When it is on (or the latch flag for that button is set), your other buttons would perform one function. When it is off (or the latch flag is cleared), your buttons would perform the second other function. No, sorry. That would be pretty complicated (all your button assignments would also need to be done in lua) and I don't have time to look into such requests, sorry. John
  6. Sorry, I don't understand. What has this got to do with, for example, Cowl flaps? Reverse zone only applies to throttle/thrust.
  7. Please be aware of the difference between a preset and a hvar. Hvars DO NOT show in the drop down menu - you need to define a macro to set/activate the hvar, as you have found. An easier way to use hvars is to define your own preset to activate the hvar. To do this, you would create a file called myevents.txt and add lines of the form: presetName#(>H:hvarName) where presetName is the name of the preset (and will appear in the drop-down menus) and hvarName is the name of the hvar. Using this method, you also don't need to make the hvars known to FSUIPC via the *.hvar files. it is just, for example: ipc.activateHvar(“H:AS01B_MFD_1_Range_DEC”) John
  8. For lvars, you can just use the Add-Ons->WASM->List Lvars function - that will list all available lvars for the current loaded aircraft. Interesting. As you are in the events page and you execute them, they are probably events or K vars. You could try executing them from FSUIPC using the calculator code 1 (>K:AIRLINER_LS_On) They could also be one of the new 'B' variable types, or an F type input event. See https://devsupport.flightsimulator.com/questions/1859/b-input-events-and-the-simconnect-and-gauge-apis-f.html John
  9. Yes, I need to know what version of FSUIPC you are using. If its FSUIPC3, that is no longer supported, sorry. But, you can achieve what you want by using a lua script (including having your button assignments in lua). However, I've never used FSUIPC3 (before my time!) and have no idea if lua is even available in that version... But, why use a timer? It would be simpler to use a compound button control, where the function of a button depends upon whether another button is pressed. See the Advanced User guide for details on compound button assignments. John
  10. Sorry for the delay in responding to this. I'll take a look tomorrow, but could you let me know: - are you using any of the FSUIPC6 mousewheel controls (Mouse look, Move or Trim)? - do you have the P3D 'Enable Advanced Mouse Controls' option checked/active or unchecked/deactivated? - is this just an issue with the CPFlight MCP? Does the view point move/operate correctly when using a default aircraft? - what do you mean by 'position goes to zero position'? Also, please attach your FSUIPC6.ini. Thanks, John
  11. This should be corrected in the attached version. John FSUIPC7.exe
  12. Yes, I know... I'm not sure if this is possible (or if it would even work that well. I can look into this though when I have time. I am also thinking if adding another checkbox for presets, so only presets would be display when using this checkbox, and they wouldn't be displayed when selecting FS control. I will look into this at some point, although I'm not sure when this will be at the moment - too many other higher priority things to do I'm afraid! John
  13. Not sure why this would be... Check two things: 1. That you are updating the correct file - where is the location of the file you are updating? 2. That it isn't being synced/copied back by a cloud service (such as OneDrive) Other than that, I don't understand why this would be happening - maybe ask on the Asobo forums. John
  14. This is not currently working (i.e. triggering presets from offset 0x3110) - I will look into this. John
  15. You can add lvars to offsets, but not hvars. I am also working on functionality to let the user add any simvar (or A type variables) to a free offset. This should be available in the next release, hopefully by the end of the week (but depending upon how much time I get for development!). I will check the use of controls to activate presets at offset 0x3110 sometime today, when I get a chance, and let you know what I find. John
  16. No, just on the client. FSUIPC7 running on a client PC is completely independent of FSUIPC7 running on the FS pc. All you need to do on the FS PC is to update the MSFS simconnect config, as stated. If it can't connect, it is probably either firewall issues (check by temporarily disabling any firewalls on both the client and FS PCs) or windows network issues (check that both client and FS PCs are in the same workgroup and can see each other).
  17. As I said, I haven't tested activating presets via offset 0x3310, but I see no reason why it shouldn't work. I will take a look this week to confirm. You can list available lvars using FSUIPC. However, as the MF hubhop preset page only has 8 presets for the Asobo A320, I doubt you will have much success. Best sticking to the FBW A320 if you want such control. John
  18. 👍
  19. All documentation is public and available, and should be installed in an FSUIPC6 sub-folder of your Windows Documents folder. John
  20. I see you are also using FSUIPC7. You posted in the wrong forum - there is a specific sub-forum for FSUIPC7 - I will move this post. For FSUIPC7, things can get complicated and (almost) every aircraft requires a different set-up. The latest version of FSUIPC7, v7.2.16, comes with the MobiFlight preset list available for assignment. You should also use the MobiFlight HubHop preset site (https://hubhop.mobiflight.com/) to search for the calculator code to control many functions. MSFS aircraft tend to use lvars and hvars for many functions, if not more complex calculator code. Go to the MF HubHop website, filter by the aircraft you are trying to control, and you will see a list of the presets available. You can also search by subsystem, etc. For example, for the A320, you will see presets for FCU speed inc/dec, as well as pull/push... You can translate the calculator code shown there for use in FSUIPC7 assignments, if you know what you are doing, but this can be quite complex. In the latest version of FSUIPC7, you can assign directly to these presets (as well as provide your own presets). If not already using the latest version, please download it. Documentation for this functionality is in the Advanced User Guide, under the WASM section. John
  21. Also, you don't say which aircraft you are using to test this (or I can't remember...!). If using the PMDG aircraft, for example, you should see if any custom controls are provided. See this FAQ entry for setting things up for PMDG aircraft: John
  22. By the way, the settings I provided (that you are using) are just general settings. The AP functions work differently in different aircraft/AP systems. For example, to control the IAS in more complex aircraft you may need to use the Autopilot Airspeed Hold Var (see offset 07E2) simvar. This may be indexed (for dialed in and active), but currently only one value (index 1) is held in FSUIPC offsets. You can set-up profile specific assignments to set up these functions correctly for different aircraft. John
  23. Then switch your assignments around. Don't swap the values, swap the virtual button numbers. Looking at the heading assignments, for example: Button numbers 0 is being used for slow inc, 1 for fast inc, 2 doe slow dec and 3 for fast dec. To switch these, you would change to: You shouldn't need to do this...Are you its not being changed but you just can't see it? What control do you see (in the FSUIPC7.log file) when you use your mouse to switch to IAS mode? Try assigning the Bravo IAS button to the same control. FSUIPC provides logging facilities so that you can see what controls are being used when you operate the buttons, switches etc in the UI. You should use the facilities to work out what is happening and then assign your controls accordingly. I really don't have time to do this for every FSUIPC user, sorry. John
  24. But presets are NOT visible when you list hvars. Listing hvars lists hvars (known to FSUIPC7), not presets. hvars known to FSUIPC7 can be used in macros and in lua scripts. Presets are names assigned to a calculator code string. This string can contain code to activate (one or more) hvars, set lvars, send events, etc. Please understand the difference... Do you mean if the hvar is made know to FSUIPC7, then it is useless to create a preset for that hvar? If so, I disagree - it is just another method of activating that hvar. Otherwise, I do not know what you mean... What existing one (preset)? Are you using the MobiFlight events file (events.txt)? How are you testing? If trying to activate a hvar using calculator code, you have the wrong format - it is ' (>H:A320_Neo_PFD_BTN_LS_1)' (note the > symbol). But you cannot assign a hvar to a button. You can assign a button to a macro that activates a hvar, to a lua script that activates a hvar, or to a preset that activates a hvar. Which is it? How are you doing this? FSUIPC only sends what you ask it to. If its sending the correct code, whatever that may be, and it is not working, then either the wrong code is being sent or that code does not work in the loaded aircraft. You can use FSUIPC logging to see what is being sent. First, check that activating that hvar has the desired affect, using either the Add-ons->WASM->activate Hvar... menu item (if the hvar is known to FSUIPC7) or the Add-ons->WASM->Execute Calculator Code.. menu item if it isn't, or try both. Also, the index numbers start at 0, not 1, so the control number of the first preset in your myevents.txt file (assuming you have no events.txt file) will be 0x40000 or 262144. Sorry about that - it is correct in the documentation, have you read this yet? If not, please do NOT post again until you have. You are taking up a lot of my time to use functionality that is documented. Please RTFM. That activates the hvar. What affect that has in the aircraft is up to the aircraft. I presume it should push the PFD LS button. Not sure that will work in the Asobo A320 though - looks to be for the FBW A320 according to HubHop. May also depend on the FBW version (stable/dev). That sounds VERY old. I can't see how you can still have that as all documentation is removed when you re-installed (by the uninstaller that is automatically ran) FSUIPC7 and the latest version installed/ Please check your installation log file (InstallFSUIPC7.log) to find out where your documents are installed, or install again and make sure that you have checked to install the documentation. It could fail to install a document if that document is open, but you should get a message to that effect during the installation process. The latest Advanced User guide attached. FSUIPC7 for Advanced Users.pdf
  25. Yes, this was the old method of starting FSUIPC7, in very early releases before the EXE.xml functionality was introduced. Under your windows Documents folder, in a sub-folder called FSUIPC7. The install locations are documented in the Installing and Registering FSUIPC7.pdf, which is included in the FSUIPC7 zip file you downloaded (and also in the FSUIPC7 Documents folder). Please read this document first. There should also be a link to the FSUIPC7 Documents folder under your FSUIPC7 installation folder. 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.