#Valve hammer editor 3.5 configuration windows 10#

With a low-level API, AMD's ACE has the potential to help better utilize certain resources, particularly if the developers spend some effort to better optimize their code. When you pressed button 0 on your yoke, this sent the PARKING_BRAKES control, as assigned: Its actually assigned to turn off autopilot. This is yet another new anomaly.Ģ So it looks like the button assignments on your yoke are working. Non of the yoke buttons are working as originally set up, The only axis that is functioning is the rudder pedals and that is intermittent at bestģ I don't see any other Button changed messages logged. Did you try any buttons on your other devices? If so, FSUIPC is not seeing these. Yes the auto throttle cut off switch is on the Jetmax TQ just as in the actual 737, It no longer works.

#Valve hammer editor 3.5 configuration windows 10#

MS Windows 10 updates and the addition of some FlyTampa scenery, The computer is used exclusively for flight simulation and only P3Dv5,2 is installedĥ It may also be worth trying to initially configure with a stock aircraft as well, just to check if you can assign your devices in a nin add-on a/c. Also try rebooting first, if not done already!ħ Oh - and I see that you have installed FSUIPC6 in your Documents folder: My throttle, yoke and rudder pedals where working with the default F 35Ħ P.S. I did not change the installation destination that is where I found it, yes kinda odd. John as a user of Multiple variants of FSUIPC I can say this process of setting this new computer up has been exhausting for FSUIPC is not the only program that has been an issue. ChasePlane took a Jetline representative to remote in and after 45 minutes determined it was a keyboard issue. That worked for 3 days and the same issue resurfaced. After disconnecting my flight peripherals and adding them back one by one I isolated the issue to the Jetmax TQ-specifically to the fuel cut off lever.

No more issues with ChasePlane and I got a new shinny keyboard.