Jump to content
The simFlight Network Forums

David Wilkinson

Members
  • Posts

    24
  • Joined

  • Last visited

About David Wilkinson

  • Birthday 02/04/1950

Profile Information

  • Gender
    Male
  • Location
    Napier, New Zealand

David Wilkinson's Achievements

Apprentice

Apprentice (3/14)

  • Dedicated Rare
  • Collaborator Rare
  • Reacting Well Rare
  • First Post Rare
  • Conversation Starter Rare

Recent Badges

0

Reputation

  1. Yes John, I appreciate both aspects of what you say here, and whole heartedly agree. I wasn't resisting you, or trying to push an alternative app, I was just responding to your questions and letting you know how I got it going.
  2. Hi John. Sorry about the delay in responding. I do not use the Asobo Baron. I am using the Black Square B58P. I found that SPAD.neXt reads the aircraft's AnalogBaron.xml file and I just select the Lvar I want to use from a dropdown list. Job done. Cheers
  3. Hello John, I couldn't find a way to do it in the FSUIPC7 User Interface (although I'm sure there is a way). But FSUIPC7 didn't expose the Lvars I shared above so I was stumped (which is what brought me to this conversation). I am confident that you John, could though, by using the method you outlined to me in another post I put up on a different subject (Left & Right alternator switch assignments) Of course, in the process, replacing the Alternator switch lvars with "LVAR_FUEL-SWITCH_PUMP_1" & "LVAR:VAR_FUEL-SWITCH_PUMP_2" and remembering to use the appropriate sim command "CIRCUIT_SWITCH_ON:4" or "CIRCUIT_SWITCH_ON:5" as pre-conditions. While searching around for a lead/tutorial on how to define custom presets and assigning spare FSUIPC offsets I accidentally discovered that SPAD.neXt does expose them from the "Online snippets" search. I was able to download the settings directly into my switch configurations and it was done. 🙂 Now I am moving on to the same battle with the De-icing switches (Fuel Vent & Stall Warning) that do not seem to appear in any list anywhere. So I will still be searching for some logical, unambiguous instructions about how to define presets etc as mentioned above.
  4. Yes John thanks. I got it working. Unfortunately in my naivety, years ago, I built my cockpit using all SPDT toggle switches so I only have the physical option of "Pump OFF" or "Pump HIGH". Also, for the fuel pumps, electrical circuits 4 and 5 control whether the pumps have power. “A:CIRCUIT SWITCH ON:4, bool”, and “A:CIRCUIT SWITCH ON:5, bool” So, for the left pump switch: “Set LVAR:VAR_FUEL-SWITCH_PUMP_1 to #"; where # is the state of the switch. 0=Off, 1=Low, 2=High.' and Set CIRCUIT_SWITCH_ON:4 to 1 (or 0 for off) For the right pump switch: Same as above except use “Set LVAR:VAR_FUEL-SWITCH_PUMP_2” and for the electrical circuit use “Set CIRCUIT_SWITCH_ON:5 to 1” (or 0 as appropriate) Regards David
  5. @John Dowson, how did Asobo respond to your enquiry?
  6. Thank you once again John, Your input "The easiest way to do this. . . ." is most helpful indeed. Thank you. I have found that I cannot use my type of switches to trigger any "Toggle" action. What I see happening in the sim is the virtual switch rapidly toggling until I move my switch back to off. So the information you provided regarding adding the Lvars is the answer to my question. Very much appreciated indeed.
  7. My Main Switch Panel for my DIY Cockpit build has a number of Single Pole Double Throw toggle switches (ON-ON); two of which are labelled "L_ALT" and "R-ALT". These are wired to a couple of BU0836 Bodnar boards. I want these two switches to control the positions of the left and right Alternator switches of the Black Square Baron B58P in FS2020. From within FS2020, in "Devmode/Tools/Behaviors/LocalVariables" I can see a couple of likely candidates for binding named "BKSQ_alternatorSwitch_L" and "BKSQ_alternatorSwitch_R". However, these are not showing up in the FSUPC7 dropdown list "Control to be sent when button pressed". They are not exposed in the "Options/Controls" search from within FS2020 either, (or in SPAD, or Axis&Ohs) So I cannot get these switches to work. Can someone point me in the right direction with this problem please?
  8. Sorry. I noticed that the other forums are not for support requests. Except for one, which is for FSUIPC7/FS2020 and therefore is also not appropriate for my query. I solved the problem it myself in any case but cannot delete this post.
  9. Ooops! I did delete that section. I noticed though, that it was all back there again after I ran P3D - however, this time the <<MISSING JOYSTICK>> line was not there. I have found out what I was doing wrong! 1. I commented out the original two .ini file entries for the standard encoder inc and dec actions. 2. Then went back to the UI and assigned the VOR obi inc/dec fast actions. 3. Then I manually added four new lines to the .ini file as discussed previously. 4. then uncommented the original two entries. That's all fine, but what I didn't do then was to comment out the two lines added in step 2 above. Consequently, then, with duplicated entries for rapid movement there were confused results in the sim. It seems to be all working well now. Thank you yet again John.
  10. Thank you again. I notice now that the [JoyNames] section now has a list of joysticks with letters but the old list with numbers is still there along with the <<MISSING JOYSTICK>> line. Should I delete those old numbered entries?
  11. Thanks for that link to the lua event method. It looks intriguing to my old 'vb.net' brain. I will follow that line of methodology if I cannot grasp the compound button way of doing things. Here is the procedure that I followed to set these encoders up. 1. In the FSUIPC.ini file, in the [buttons] section, comment out the existing small increment and the small decrement assignments by inserting the ';' character, AFTER the '=' sign to preserve the index number. For example:- 64=; P6,26,C65665,0 -{VOR2_OBI_INC}- 65=; P6,27,C65664,0 -{VOR2_OBI_DEC}- 2. Start P3D and go to ADDONS/FSUIPC to display the UI. 3. Go to the "Buttons + Switches" tab. 4. Add the required large increments and decrement assignments by selecting from the offsets offered in the dropdown list. Which should then be shown in the .ini file like this:- 88=P6,26,C1029,0 -{vor2 obi inc fast}- 89= P6,27,C1028,0 -{vor2 obi dec fast}- 5. Click “Save” & Exit P3D. 6. Open the FSUIPC.ini file and scroll down to the [Buttons] section. Remove the ‘;’ from lines 64 & 65 to reinstate those commands. 7. Manually type in the Compound button-condition. Which should look like this (indexed as appropriate):- 90=CP(+j6,b18)6,26,C1029 ,0 -{vor2 obi inc fast}- 91=CP(-j6,b18)6,26,C65665,0 -{VOR2_OBI_INC}- 92=CP(+j6,b18)6,27,C1028, 0 -{vor2 obi dec fast}- 93=CP(-j6,b18)6,27,C65664,0 -{VOR2_OBI_DEC}- 8. Save & close the FSUIPC.ini file. Run P3D. I followed this procedure for both the VOR1 & VOR2 encoders ('.ini' file attached) and tested it to find that all changes are happening fast - that is by increments of 5°. On page 29 of the Advanced Users Manual I noticed that the Controls I have used for "fast" look like they should be turning the gauge dial through + or - 10° 1028 Vor2 Obi Dec Fast (–10) 1029 Vor2 Obi Inc Fast (+10) But I notice just 5° rotation. I have rechecked that the references to the press-buttons are correct. (that is j6,b18) It's almost like the '-' prefix is being ignored. Is there something else I have forgotten that would make it respond to the + or - correctly? For example, I noticed this line in the ini file under [JoyNames] J=<< MISSING JOYSTICK >> << MISSING JOYSTICK >> Is this possibly interfering? Cheers David FSUIPC6.ini
  12. Thanks John It's freezing cold out in my garage now (where my sim is) so I'll try this out tomorrow and see how I get on. Have a good day sir. David
  13. Thank you John. VERY much appreciated. I am actually working with FSUIPC6 and P3Dv5 (I couldn't find the FSUIPC6 forum, sorry) I have been studying the "Compound Button Conditions" section of the manual (and the two sections prior) and have been looking through the FSUIPC6.ini file. So I have distilled the following from your response and the manual - please direct my understanding in the right direction. (Note that I am starting with the VOR2_OBI rotary encoder.) I need to create 2 assignments on button press:- small inc/dec large inc/dec Steps to do this are as follows: Via FSUIPC User interface - First; comment out the existing small increment and the small decrement assignments. (I can't see a way to do this in the UI) Then; add the required large increments and decrement assignments (I assume this is done in the usual way - selecting from the offsets offered) From within the '.ini' file (editing with NotePad++) Reinstate the commented out small increment and the small decrement assignments. Add the compound Conditions Regarding the last bullet point I am thinking that I would add these manually in the .ini file and then I can select them from the dropdown menu in the UI to assign them to the button press action. So I would be appending my offering to the bottom of the [buttons] section as 84=CR(+j6,b18),P6,26,1029 -{vor2 obi inc fast}- 85=CR(-j6,b18),P6,26,65665 -{VOR2_OBI_INC}- 88=CR(+j6,b18),P6,27,1028 -{vor2 obi dec fast}- (I haven't been able to find this parameter value so 1028 is a guess/place-holder) 89=CR(-j6,b18),P6,27,65664 -{VOR2_OBI_DEC}- Comments & advice sought Kind regards David
  14. I have encoders on the instruments in my Sim panel that are used to adjust things like Course, or Heading, or ADF Card. Sometimes I need to turn one to a new setting very different from its present one. This is sometimes takes me a while to do when the thing changes by just one degree at a time. These encoders are equipped with press buttons that are not currently being utilised. Is there a way to create a conditional setting that will trigger increments (or decrements) of 10 degrees while the button is pressed?
×
×
  • 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.