BenBaron

Hi Henry, the problem is that there simply is not a "general" profile that makes the AP section work with any aircraft. The default throttle profile that comes with the HC Configurator download has the AP section defined for use with a default piston like the G1000 Cessna. But it already won't work with the default airliners that come with X-Plane as they are using different autopilot variables and commands. So...it all comes down to which specific aircraft you are targeting. You can also check out our dedicated download area to see if there already is a Bravo profile f

Thanks for your warm feedback Eric and glad you got it solved. Have fun. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.

Hi, we are aware of the issue and will have a solution shortly...for the profiles as well as for the naming conventions in the HC Configurator software.

Hi guys, I can only say that with my alpha version of Brussels performance is a no brainer, even with a complex aircraft like our CRJ. That is happening with a 6 year old Desktop and a 2 year old Gaming notebook. And that is pre explicit optimizations for performance. So...I doubt anyone would need to loose sleep over removing things like terminal interior or visible pax just to get a resonable flying experience. And just to confirm everyones impression: the visual fidelity and attention to detail is indeed outstanding in the scenery.

Hi Eric, I am assuming you are using the default throttle profile which is tailored to the default piston aircraft like the G1000 Cessna. So, you can check in our download section if there is a specific profile for your aircraft already available. Alternatively, if everything else works as you want it to with the default throttle profile, you can also just remove the LED mappings from that one by switching into "LED-Mode", "Select LED" you want to clear and deleting their conditions using the small trash bin symbol next to them. Finally, select "Apply Changes" and the L

Hi and welcome to our forums. Are you aware that there are specific profiles for different aircraft? There are simply too many of them out there to get them all covered via a single profile. The one for the Zibo you can download, import and activate from our dedicated download section. The default profile is very baseline for default pistons like the G1000 Cessna and only contains mappings for the autopilot selector and increase/decrease rotary as well as some LEDs. So...if this one does not work with the Zibo...I am not surprised.

Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.

Hi Eduardo: no..there are no known issues with having side-by-side installations of the software for different simulators...they are completely independant from each other.

Sure Eduardo. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.

Hi Gérard, glad to hear that it is working out as intended so far...even I implemented that behaviour in the backend some time ago, I never got to testing it out myself, so knowing it does indeed work is great :-). You also should be able to safely remove the legacy properties and only keep the arrays to declutter your profile. The next version of the Configurator will actually also do this for any imported profile, thus automatically converting legacy profiles into their new counterparts.

Hi Henry and welcome to our forums: it is important to understand that the profiles you import or create via the HC Configurator work completely independant from the X-Plane ones. Thats why you will also never see aynthing from them in the X-Plane controls menu. What you have to do is activate the profile you want to use direcly from the Configurator itself, so its mappings can be used in sim: Apart from that, as the two control mapping mechanisms are completely independant, you also have to make sure that there are no doubled button bindings as otherwise you will

Hi Ova, I only now got to looking into your profile and found the same thing you did: with the default Cessna G1000 and the KingAir it all works without a problem, so I figured you might be using a plane that is simply not acknowleding "sim/autopilot/altitude_up".

Hi Ova and welcome to our forums: easiest way is to attach the profile here for review.

Hi Jason and welcome to our forums. Depending on the aircraft of choice you might want to download a specific profile that makes them work from our download section. Apart from that, the profile you want to use needs to be loaded and activated in the ConfigTool, before it is seen in the sim. That includes the "Default_Throttle" profile, that already comes with the software download.

Hi Andreas: please make sure you are not installing into c:/ as what you are seeing indicate a writing rights issue. Also, have you tried running only with the v4 version installed?

Nice you got it sorted out. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.

I hope that there is still a response coming in the future, as we are also interested to know, if this is an issue on our side...which of course can always be. But without a combined effort this is next to impossible to figure out in this case.

Hi Eduardo, you have to clear out those buttons for the Alpha, that you want to map via different means, in the ConfigTool: Select the button whose function you want to remove, select the trash-bin symbol in the upper right hand corner and "Apply Changes" for your profile.

Hi Gérard: actually the bridge module "should" be able to work with that as it is able to store more than one variable per condition already...it is just the ConfigTool that can only take one variable per condition. Have you tried it out with a manually edited profile.json? Apart from that, it sounds like you should also be able to achieve what you want via multiple press-events.

Eduardo: as you are having the Honeycomb entry with sub entries...you are good.

That is strange, indeed. You could try swapping the mappings for gear up and down in the profile. Maybe something has been (mis-)wired in your Bravo.

Glad it works like you want it to now Waleed...have fun. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.

Hi Waleed, try the attached profile and see if it works like you want it to. I've removed the Flaps assignment on the Yoke for you. AFC_Yoke_Config_PMDG_T7.json

Hi Tristen, make sure that you have no double bindings for the gear lever defined, so that there is nothing mapped to it in P3Ds control menu.

Hi Waleed, no problem...so...as you are writing about "PMDG T7 settings" I am assuming you are using our PMDG T7 HC profiles from the download section for Alpha and Bravo. Is that correct?