Resetting FSUIPC 6/profiles P3D V5

[Ross McDonagh]

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

[John Dowson]

2 hours ago, Ross McDonagh said:

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?  

You can delete the CH throttle assignments if you wish. But really, it does no harm leaving them there. They just won't be used (unless you reconnect that device). 
If you aren't going to use it again, it may be worth removing those assignments just so that your ini is a bit cleaner/more readable.

2 hours ago, Ross McDonagh said:

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 

I suspect that those switches have numbers outside of the range that fsuipc supports (0-31). You can check this in the windows game controller config window. If thats the case, you cannot assign using the UI, and you have to use lua to access (which is why LINDA can see them, as that is a lua based system).
There is an example lua provided called HidDemo.lua (in the lua examplex zip file in your FSUIPC documents folder). You can use that, but you will need to edit to provide the correct product and vendor ids.

2 hours ago, Ross McDonagh said:

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! 

I'm not sure thats correct. There are known issues with the Honeycomb when using MSFS due to the way some of the buttons continually fire, and folks seem to be using FSUIPC to get around this.

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 ordered a honeycomb flight alpha yoke, but I don't think its arriving now until mid January.

2 hours ago, Ross McDonagh said:

I deleted all axes and buttons in P3D

Its better to disable controllers completely as P3D has a tendency to automatically re-assign. If you haven't disabled controllers, check the assignments again.

2 hours ago, Ross McDonagh said:

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

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.

John

[Ross McDonagh]

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. 

[John Dowson]

Btw, are you using the "JoyLetters" facility? If not, it is possible that the same joy id number has been used. Please check the user manual on how to activate/use this facility if not already.

[Ross McDonagh]

5 hours ago, John Dowson said:

Btw, are you using the "JoyLetters" facility? If not, it is possible that the same joy id number has been used. Please check the user manual on how to activate/use this facility if not already.

I have not used said facility but I will certainly take a look John thank you again.  

[John Dowson]

19 hours ago, Ross McDonagh said:

I have not used said facility but I will certainly take a look John thank you again.  

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.

 

[Ross McDonagh]

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. 

[John Dowson]

@Ross McDonagh FYI, I have also identified an issue where axis can be lost when adding an aircraft to an existing profile. See this support request for further details: 

 

This has been corrected in the attached version, so please try with this:

FSUIPC6.dll

John