Jump to content
The simFlight Network Forums

Ross McDonagh

Members
  • Posts

    28
  • Joined

  • Last visited

Posts posted by Ross McDonagh

  1. On 12/14/2020 at 6:17 AM, John Dowson said:

    Ah, then that could be why you had assignments to your new device when it was connected. You should certainly activate this. Maybe be a good idea to manually remove the previous assignments first. If you need any help,  activate the joyletters facility (change ini parameter AutoAssignLetters in [JoyNames] section to Yes), start P3D/FSUIPC briefly, then attach your .log, .ini and .Joyscan.csv files.

     

    Will do John I’ve got some stuff sorted for the moment but it needs work.  I’ll post these when I can probably tomorrow.  Thank you so much. 

  2. 1 hour ago, John Dowson said:

    I’m not sure what the Honeycomb software you mention does, but usually if you are assigning in FSUIPC you don't want any additional device software running, so I would try without that first. What does this software do?

    The Honeycomb/Aerosoft Software seems to enable the LED’s for gear/annunciation panel on the Bravo-as seen in the video.  It’s quite a bear and there’s only a 5 page manual!  It has all kinds of LVAR’s and such.   It seemingly auto assigns GEAR/FLAPS and it also seems the autopilot button.  That brings me back to a new question:

    ..I’ve programmed the Autopilot button in FSUIPC-but because I can’t figure out how it works/how to set it in the honeycomb software, my FSLabs rotorbrake control code for Autopilot is HALF working-I press the AP button and it animates in the cockpit BUT the autopilot won’t stay engaged. 

     

    1 hour ago, John Dowson said:

    I’m not sure what the Honeycomb software you mention does, but usually if you are assigning in FSUIPC you don't want any additional device software running, so I would try without that first. What does this software do?

    I’ve checked all the assignments... The ONE thing I have assigned in P3D is the steering axis on my Thrustmaster Airbus sidestick Z axis-I use this for ground steering in every aircraft.  
     

    1 hour ago, John Dowson said:

    Did you make any assignments in FSUIPC after you plugged it in? FSUIPC won't do anything unless you make assignments. If you didn't make any, then the assignments must be coming from P3D

    I had made no assignments until I had the devices re-plugged in and perhaps that was due to them not going to the same USB ports?  My rudder was assigned in FSUIPC to flaps and my left/right brakes were spoilers and something else.  I’ve got the axes sorted.  It’s onto the buttons at this point and trying to figure out how to make the shifted functions in LINDA work to adjust the rotary switches in each aircraft which I’m still not sure is totally possible....  

     

    Thanks as always for your help John I appreciate it very much 

    I’m sure I’m not the only one trying to figure this out-I’ll keep messing around and see what I can bring back to the community. 

  3. Hello all, 

    I’ve just moved into a new house and finally just about completed my setup (waiting on the TM Airbus Add On if it ever decides to ship) 

     

    Previously I had a great setup going with the Honey alpha, CH Throttle Quad, Logitech Rudder Pedals and the TM Airbus Sidestick and Throttle...   I used rotorbrake for the FSLabs and some custom control codes and keyboard bindings for the PMDG and TFDI Aircraft I use. (The CaptainSim 76 and FeelThere E Jets are another story altogether) 

    Fast forward to me moving a few blocks up the street the day after my Honeycomb Bravo throttle arrived.  I plugged in the Bravo and left the CH unplugged.  My axes went nuts-flaps were assigned to brake pedals, spoilers to the rudder axis....   I deleted all axes and buttons in P3D but SOME functions of the Bravo work in the 737... Gear, trim and the CRS knob come to mind.  I can’t get throttle 1 to work but throttle 2 does work.  I’ve attached a video and my FSUIPC.ini

     

    My questions are:

    1. Should I just delete the FSUIPC.ini and start from scratch with each aircraft?   OR can I remove the CH Throttle assignments and go from there?  

    2. FSUIPC (and windows) don’t seem to recognize the rocker/toggle switches on the Honeycomb-Linda DOES recognize them but I’m trying to keep it fairly simple-I had a few issues trying to sync LINDA (which I previously had only used on the QW787 and Aerosoft A330) to sim with the 737 module 
     

    3. It seems the Aerosoft/Honeycomb software doesn’t play well with FSUIPC...  When it was installed a few things were working and when I uninstalled the Honeycomb software-the gear and some other functionality stopped working.  (but my throttle 1 started working again)  Any ideas on this are welcome! 

     

    This has been a 1-2 hour a day affair for the last few days.  I’m anxious to get back in the air but it’s been a grind trying to get this to work.  

    Lots of confusing stuff and I feel like I’m slowly getting there but need a bit of expert direction from the folks around here 

     

    FSUIPC6.ini

  4. On 8/26/2020 at 8:07 AM, John Dowson said:

    For the FSlabs A3xx, they do indeed use the ROTOR BRAKE event/control as a custom control, with the parameter specifying the action. There is a tutorial on how to use these with FSUIPC over on the FSLabs forums:
    https://forums.flightsimlabs.com/index.php?/topic/22402-v440-update-in-depth-tutorial-to-bind-switches-and-push-buttons-to-keyboard-or-hardware-for-the-a3xx/

    There was also a recent support question on these that may be of interest: 

    John

     

    Glad to see I’ve helped out a bit John 

  5. 5 hours ago, John Dowson said:

     

    I think they are actually parameters to the Rotor Brake control, which has been re-purposed in the FSLabs A3xx  aircraft.

    That still means I can send it as a custom control for FSUIPC? 

    5 hours ago, Pete Dowson said:

    Those look like "custom control" numbers. You can assign to those in the Buttons and Switched tab by selecting <custom control> from the drop down list (I think it's the first item). Then you can enter a control number (thosde above) and a parameter, if needed.

    You can have any number of assignments to the the same button, but to do this you have to edit the INI file and add them there. 

    Assign the first action. Then open the FSUIPC settings file (.INI) and find that assignment -- eg search for that control number. Then duplicate it with a different entry number (the number before the =), and change the control number to your second action.

    For this make sure you do NOT have repeat selected.

    Please see the Advanced Users guide for more details of what you can do with button assignments.

    You can edit theINI file with the Sim still running, and get your changes recognised by using the "Reload ..." button on the Buttons & Switches tab.

    Pete

     

    Thanks Pete.  I appreciate the help.  I had always used macros back in the 2D cockpit days.  Looking forward to doing it right this time 

  6. After some spending some time researching/ learning after the help John and Pete gave me in my other thread here earlier in the week, I think I’m about ready to try and ditch the mouse macros to button controls that I was using as a solution to bind my autopilot controls to my honeycomb yoke switches.  My question/issue in this is that with the A3XX series (or any Airbus) the autopilot controls are a momentary push/pull type of switch to select the desired mode.  I am using the 4 rocker “switches” on the honeycomb yoke (and I intend on using the same type when my honeycomb bravo throttle arrives in the fall.  See pics for what I mean   
     

    Now instead of being actual switches they’re actually buttons which remain depressed/active so long as the position is up or down.  For example if the switch is up, button 23 is continually “pressed” and if the switch is down, button 22 is continually pressed.  With my current mouse macros, in one airbus (Aerosoft) it shows the animation of the autopilot/FCU switch shows permanently pushed or pulled in even though the autopilot mode activates as desired. 


    Bearing that in mind,  I found these parameters (offsets?  Lvars?  Both?) on the FSLabs Forums to send thru FSUIPC to my switches.   The italicized text is copied from a thread over there   

    All of these are as above (rotor_brake) commands:

    Alt(itude) Push (left-click): 71249 (mouse click), 71252 (mouse release)
    Alt Pull (rt-click) : 71250 (mouse click), 71253 (mouse release)

    Alt(itude)increase:   71261
    Alt decrease: 71262  

    I can send the increase/decrease commands to my CH throttle switches (3 way switches-up/off/down no problem.  

    What I’d really like to do and need guidance on is how to send Alt Pull/Push AND Mouse release while the switch remains depressed. 
     

    So for instance when I select my switch up (thereby depressing button 23) I’d like to send the commands:

    Alt(itude) Push (left-click): 71249 (mouse click), 71252 (mouse release)

    In the same push as it were even though button 23 remains “on”

     I realize that I can’t send 71252 (mouse release) as a “control to send when button released” because “button 23” never becomes released so long as it’s in the up position.  
     

    Any guidance would certainly be appreciated! 

    CB2C5B65-D9FD-4049-91B3-1A617DA027DC.jpeg

    3FF9E94B-4E5B-4688-BBCA-E95975864D10.jpeg

  7. 2 hours ago, John Dowson said:

    Ok. No need for your log (at the moment!), now that I understand what is causing your issue.

    It's a good idea to try LVARS and the custom controls first. You should maybe ask on the FSLabs forums about controls for the FCU/Autopilot, as I expect there would be some form of control/lvars if the standard FS controls don't work. You can always use mouse macros for control of the ones that aren't supported.

    Ok John, I’ll hold off on the log.  
     

    In the meantime, I’ll ask about control sets over in the forums.  The head developer replied to my GPU hang issue so I’ve got some updating to do 

     

    thanks so much for all your help! 

  8. 1 hour ago, John Dowson said:

    You can just attach the log file to your post (either drag and drop or by using the 'choose files' link just below where you enter your comments.

    Will do.  With the great advice you’ve given I’m going to remove the 3 way switches and try to find out a way to turn the switch off and on. 

    I can’t thank you enough for your patience with me.  I recall Pete doing the same with a friend of mine when we first discovered FSUIPC way back when and my friend telling me how great it was and he put up a YT video which I came back to to make macros all these years later.  

     

    My plan is going to be to clear out all the macros and try to get the LVARs setup.  I found a list of LVAR and rotorbrake codes on the FSL forums but I didn’t see many of the specific controls I’m looking to program (mainly for the FCU/Autopilot) so I’m not sure if FSL uses an FS command or not.  

  9. 2 minutes ago, John Dowson said:

    Anyway, I suspect that one of those buttons may be continually firing, but I need to see a log file with button logging activated (as previously requested) to confirm that. You could try removing those two assignments as well, to confirm that they are the cause of your problem.  Remove one at a time, starting with the last one first.

    I did indeed find and remove that.  So the landing light (and taxi, strobe lights) is a 3 way switch on the A320.  The landing light is retract/extend/on while the taxi light is Off/Taxi/Takeoff and the strobe is Off/Auto/On.

    Obviously the honeycomb alpha doesn’t have a 3 way switch.  I was meant to setup button 21 for “down” and 22 for “up” but put the repeat on there so it would cycle thru both settings because on the honeycomb when the switch is up, the button remains pressed.  

    How does one unassign a macro after it’s been made and how would I get you the log file?  

  10. 12 minutes ago, John Dowson said:

    Mouse macros emulate a mouse operation on the UI, which then alters the model somehow, either by sending a control/event or changing the value of a variable. Its more efficient to just send the control/event or modify the variable directly, rather than via the mouse operation. Also, different models of the same plane may have different rectangle ids for the same button/switch, whereas the control/event or variables would be the same. So, controls/events are more general, and can apply to many aircraft, and variables can be aircraft specific, but generally work for that series of aircraft, whereas mouse macros tend to be specific to that model.

    You need to check the documentation for that aircraft. Some add-on aircraft re-purpose unused controls, whereas others use 'custom' controlnumbers (e.g. PMDG). The 'Rotor brake' control you mentioned looks like it has been re-purposed to control various actions depending upon the parameter.

    To get a list of the lvars available for your aircraft, you can assign a button or keypress to the List Local Panel Vars control, which will list the available lvars (and their current values) for you. There is also a lua script (included in the provided examples) that does a similar thing.

    John 

    Thanks John, I’ll give it a whirl.   Of all things after my reinstall and deletion of the macros, I got a GPU hang climbing out of FlyTampa KBOS.  I shut the computer down in disgust, then got mad at it, turned it back on, went to (of all places) FlyTampa Las Vegas (with pretty much everything turned up to 100%) and did a SID/STAR/visual flying around at night with no problems but some reduced frame rates.  

    So I take it once I list the LVAR’s I should be able to see what controls are what inside FSUIPC and go on from there?   I’ve now got the manuals in my phone (well most of them) so I’ll be going thru those today while I’m at work.  I have all afternoon today to hopefully sort issues  and then I’m really hoping to fly all day tomorrow.  

  11. 6 hours ago, John Dowson said:

    No, your ini contains the assignments to the macro file. The macro file itself is the name you gave It - it's in your installation folder, called A320 Test.MCRO.

    John, attached are all the Macros I can see

    Please let me know if you need more.  I would probably delete and restart the macro making particularly since I have to completely reinstall the FSLabs A320.  Just want to get a fresh start on this.  I've been waiting 11 years to fly this bird and finally have a system capable enough to do it, but it seems not without some headaches and heartaches first.

     

    A320 Test.MCRO.bakA320 Test.MCROTFDI 717.MCRO.bakTFDI 717.MCRODefault Test.MCRO

  12. 18 minutes ago, adrem said:

    I've never used LINDA myself, but I would guess that it's much easier to use than you imagine. When used with one of their modules for addon aircraft, such as the one for FSLabs that John has linked above, it is to custom cockpit controls what FSUIPC is to default sim controls. You just select a joystick button in a drop-down menu and the cockpit control in another dropdown and you've created an assignment. You don't have to worry about macros, Lvars, rotor brake codes and other nonsense - the aircraft modules take care of that under the hood.

    Adrem, thank you so much for the comforting words!! 

  13. 2 hours ago, John Dowson said:

    No problem. If you are starting afresh, you should investigate lvars. Check the documentation on this (which will be in your Documents folder, under an FSUIPC6 folder).  You can get the user (and advanced user) guides there as well (to put on your phone!).

    A good place to start with lvars (and lua) would be the LINDA module for the FSLabs A320. You don't have to use LINDA, but its worth checking out what they use (offsets & lvars) to control the aircraft. It will be quite advanced, but should should be able to get some good tips if you take a look. Try https://www.avsim.com/forums/topic/502679-fslabs-airbus-a3xx-x-15-3-jul-20/ for info + the download (also looks like it's been recently updated).

    I've a similar problem on my flight PC at the moment - it randomly reboots during a flight on occasion. Only when using one sim, but quite regularly, and with no crash or event reported anywhere that I can find...very frustrating!

     

    Thanks John, I’ve definitely taken a look at that recently.   I just feel like the mouse macro/button pressing is an easier way for me to program and get in the air while still having my controls working the way I want them to.  I used to use macros for FS9/X as well because back then (and now!) the LUA and LINDA stuff just seemed way over my head and too advanced for what could be done with some mouse clicking.  
     

    I’m also wondering why the macros should be a last resort?  I don’t believe many of the addons have controls to send for specific button pushes in the flight deck unless I’m missing them-and if there are I’d love to get a list of said controls for the FSlabs and TFDI aircraft (for now)  

     

    second edit:

     I’ve found something called rotor brake which I have no clue what it means or really how to work it but I think this may be what you’re trying to get at?  
     

    https://forums.flightsimlabs.com/index.php?/topic/22402-v440-update-in-depth-tutorial-to-bind-switches-and-push-buttons-to-keyboard-or-hardware-for-the-a3xx/&do=findComment&comment=168581

  14. 6 minutes ago, John Dowson said:
    27 minutes ago, Ross McDonagh said:

     

    No, your ini contains the assignments to the macro file. The macro file itself is the name you gave It - it's in your installation folder, called A320 Test.MCRO.

    Thanks so much John.  I will post this up tonight for you.  I also greatly appreciate your patience with me as I’m trying to get my feet back under me after a long time away from FS and Windows PC’s.  I’m trying to find an FSUIPC6 user guide to read on my phone while I’m at work.  
     

    At the moment as I mentioned, I had to uninstall the FSLabs A320.  I’d really like to start fresh when I put the aircraft back in.  

    I’ve spent a lot of time trying to configure everything and not very much time flying.  The biggest thing I wanted to do with this new PC/sim setup was fly the FSLabs and of course it’s being a giant headache for me between the GPU hangs at night and then the macro sticking on the other hand I’m ready to rip my hair out lol

  15. 2 hours ago, John Dowson said:

    You also seem to be using mouse macros for everything... It is better to use standard controls/events if/when they work. If not, you should try to see if an lvar is available for that function. You should use mouse macros as a last resort, when standard P3D controls don't work and there is no lvars available.

    I use mouse macros for push/pull on the autopilot, landing lights, autopilot engage/disengage when the P3D command is different for an add-on etc.  It seems easier to do the macro (I used macros in FS9/FSX with much success) and configure my controllers for each add-on aircraft.  I also have no idea what an lvar is. 

  16. 1 hour ago, John Dowson said:

    Ok. I would like to see your macro file though, to see if anything is already assigned to that id. If its already there, and you also have assigned a button/switch to this macro, then this may be activating it. Logging 'buttons and switches' would also help if this is the issue.

    Where do I find the macro file?  I thought that was in the .ini ??

  17. Thanks John, I actually had to uninstall the FSL A320 for now.  I will report back when I reinstall tonight.  It was causing DXGI errors.  
     

    My other addons did work as advertised but the FSL causes problems so uninstalling that and I’m going to attempt to reinstall afterward.  Is it possible to reset all my macros and begin again?   

  18. 4 hours ago, John Dowson said:

    Could you post your FSUIPC6.log and FSUIPC6.ini files and I'll take a look to see if there is anything else there that could be interfering.

    Good morning John, I’ll do this here in a little bit.  

    2 hours ago, John Dowson said:

    When you create the macro, are you giving the name of an existing macro file? If so, what happens if you give a new file name?

    Yes indeed I’m using my profile specific name.  I will try a different one and report back when I post the .ini and log files 
     

    3 hours ago, John Dowson said:

    Do you also get the issue if you remove (i.e. temporarily rename) the macro file (or files) that you have already created for the A320?

    How can I temporarily rename the file? 

  19. 9 hours ago, John Dowson said:

    Maybe also try testing with this disabled, as well as any other add-on or plugin you may have running or recently added.

    So with everything else I have completely disabled, this macro making still sticks.  Just as in the video.  I tested a default airplane it didn’t stick, I tested a different livery/engined FSLabs A320 and it did it again same click spot.  Finally I tested the TFDI 717 and it worked fine.   So it’s only with the FSLabs A320.  What should I do from here?

  20. 15 minutes ago, John Dowson said:

    do you notice any slight flickering when you git the escape key

    -Yes and there’s also flickering if I attempt to type in a name.  Say I tried to type “TAXI” it would flicker the T and keep deleting it as if I was simultaneously pushing T and backspace... 

    15 minutes ago, John Dowson said:

    Ok. Could you also try with a default plane. I've just tried here with FSUIPCv6.0.10 and P3Dv5 HF2 and its working as expected.

    I will indeed.  Probably won’t be til late tonight I’m on an 18 hour day at work today 

    15 minutes ago, John Dowson said:

    It looks as though FSUIPC is receiving (or continually receiving) a mouse click for that rectangle id.

    That’s exactly what seems to be happening.  I’ve no idea how to fix it.  Even hitting the x on the simconnect window won’t allow me to get out of there. 

     

    15 minutes ago, John Dowson said:

    Have you managed to create a mouse macro for that aircraft previously?

     

    I have indeed, this was actually the last switch I was attempting to program on my honeycomb yoke.  I have autopilot and other light functions already programmed to several devices.  
     

    I will update as soon as I get home and see if that fixes it.  I has successfully programmed the macro to all the other lights on the overhead and this was the last one.  I also installed GSX so I don’t know if that matters or not.  
     

    Thanks so much for the reply John.  Very glad to hear you’re carrying on the FSUIPC tradition and honored to get a response from Pete himself an FS community legend.  

×
×
  • 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.