Ron Attwood

Thanks John, I appreciate the offer, but coming to my senses I realised that I probably won't be flying this helicopter very much after the initial enthusiasm wears off. What beats me is how many ways do you need to make an axis work. As far as I can see you need at most 11 axis to assign. Anyway, I promise I wont bug you any more about throttles. 😁

Me again. 😕 What is it about throttles and MSFS? This time it's Taogs HUEY. Throttle only responds to the MSFS in game controllers. AXIS_HELICOPTER_THROTTLE_SET in FSUIPC works fine for the Flyinside 206 and G47 but none of the options for throttle work for the Huey. I've had to resort to the MSFS assignment for it. Question is is there a workaround. Some bright spark suggested I get SPAD! 🙄

Stand down. I figured it out. Milviz, for reasons best known to themselves, use different commands to everyone else Instead of AXIS_THROTTLE_SET, they use THROTTLE_AXIS_SET_EX1 This is my .ini extract 2=DZ,256,F,65765,67096,0,0 -{ TO SIM: AXIS_THROTTLE_SET, THROTTLE_AXIS_SET_EX1 }- Back to real life. 😁

First let me make clear I don't think this is an FSUIPC7 problem. This is manifested only on Blackbird/Milviz's F-4 Corsair. The command works on every other aircraft that it's assigned to. I've posted on the Milviz Support forum but there's a deadly hush. I just wondered if you could throw some light on it. The axis works with the in-game controls but not in FSUIPC7 Log and .ini attached FSUIPC7.ini FSUIPC7.log

Well done, Everything works. At least as much as I want it to. Admittedly, I don't ask very much of it but I couldn't be without it. 😁

I lost my 'key presses' back because the yoke wasn't being recognised. Now, thanks to you providing the wherewithal i.e. the new 7.4.13a .exe my yoke is now recognised so that I can assign key presses to buttons on said yoke. I had to make new assignments because the yoke now has a different code #243728C0-B24E-11EB-8001-444553540000 Did I say thank you?

Thanks John, got my key presses back. Of course I had to make new assignments for the yoke, 7 in all! Where do I find the time? 😀 So sorry I posted in the wrong thread. I'd like to say it won't happen again but don't bet on it. 🙄

Latest update doesn't recognise/find my Fulcrum yoke. The yoke is recognised in Windows and in MSFS and works. All my buttons and key presses are handled by FSUIPC since...forever. MSFS handles the axis. [JoyNames] 0=Joystick - HOTAS Warthog 0.GUID={D1794640-246D-11E6-8001-444553540000} 1=CH Throttle Quadrant USB 1.GUID={7DCB45F0-282A-11E6-8003-444553540000} 5=MFG Crosswind V2 5.GUID={E6A97680-25B6-11E6-8001-444553540000} 6=Pro Flight TPM System 6.GUID={C8DA6E60-25B7-11E6-8001-444553540000} 7=Pro Flight Cessna Trim Wheel 7.GUID={27DB16B0-2669-11E6-8001-444553540000} A=Joystick - HOTAS Warthog A.GUID={D1794640-246D-11E6-8001-444553540000} B=CH Throttle Quadrant USB B.GUID={7DCB45F0-282A-11E6-8003-444553540000} D=Throttle - HOTAS Warthog D.GUID={921BB790-2520-11E6-8001-444553540000} E=MFG Crosswind V2 E.GUID={E6A97680-25B6-11E6-8001-444553540000} F=Pro Flight TPM System F.GUID={C8DA6E60-25B7-11E6-8001-444553540000} G=Pro Flight Cessna Trim Wheel G.GUID={27DB16B0-2669-11E6-8001-444553540000} 3=Throttle - HOTAS Warthog 3.GUID={921BB790-2520-11E6-8001-444553540000} C=<< MISSING JOYSTICK >> << MISSING JOYSTICK >> (Fulcrum yoke) I've uninstalled/reinstalled a couple of times, no joy. Ouch! Sorry. 😣 Attached log FSUIPC7.log

I can't make head nor tail of this. Brakes aren't even assigned in this profile. I feel I'm just digging a bigger 'stupid' hole for myself. It's me taking my BMW to a dealer and he gives me a workshop manual and says "It's all in here" and I'm supposed to understand it. FSUIPC7.log

Thanks for your efforts at trying to teach an (very) old dog new tricks, but I've had to give it best. Considering there are only two helicopters I use this on, I'll let MSFS handle just this one button. I do appreciate the axis fix though.

Thanks. That'll keep me from hanging round bars for a while. 😉

Hi. It's the Flyinside B206 and tha Flyinside B-47. I haven't tried other helicopters. I'll see what happens to them.

SET_STARTER1_HELD works in MSFS controls but it doesn't work in FSUIPC. In the scheme of things not a big deal, but you know how it is, like a pebble in your shoe. 😃 Actually, in MSFS it's called SET_STARTER1_HOLD. Would E for O be the cause? Ron

Deep joy! That worked a treat. I looked at the Advanced User Guide, somewhere I didn't think I was clever enough to look at. I was right! You are on a different level to ordinary folks. 😃 Thanks for being here.

Helicopters! I've tried and failed, to get 'Axis Collective Set' and 'Axis Helicopter Throttle Set' to be reversed. I've had to resort to MSFS controls to do this job. Until now I've managed to get FSUIPC to handle everything. It's a pain having to go to MSFS, turn off those controls when I swap to a fixed wing. If it can be done in FSUIPC would you be so kind as to point me in the right direction? I did search but found nothing. Not to say there isn't though.😉 I forgot to add, I'm using v 7.3.16

Please forgive me John. I didn't see this thread and thought the thread about loss of control was, as I said, relevant in a small way. I'm sorry to have got it so wrong.

Sorry, I'm late on parade. I've read through this thread and my issue seems to be related in a small way. I'm on 7.3.12 and all my axis work just fine...Except Condition levers! The said levers work correctly as mixture levers but not in any form of turbo prop condition. i.e Axis Condition lever, Condition lever Set 1,2, etc. The aircraft I've tried it with are Asobo's C208, Kingair 350i and Orbx's latest PAC 750. Strangely it works properly on Milviz's PC-6, odd. It grieves me to have to resort to MSFS controls for just that one function. Oops! Just noticed 7.3.13a. I'll give that a go. Ron I'm back. No, no joy

I make no apologies for bringing this thread back to life but it has given me the answer I've been looking for. I have the JustFlight Hawk and like every other plane I have that requires it I have the left hand throttle assigned to Axis throttle. No problem. Until JF brought out V1.5. The throttle refused to work. I bugged JF with it but they were nice but no answer (Works OK here) I had to resort to using MSFS controls (the ONLY assignment!) to get it to work. Other planes took over, as they do and the Hawk was parked. Today I got it out again and the irritant raised it head again. I came here to ask for a clue but like a good boy I did a search and I spotted this thread. That led me to try 'Throttle Set' IT WORKED! Just underneath it is Axis_throttle_set_Ext. THAT WORKED! Anyway, thanks for the service. 😃

You wouldn't believe how many time I've scrolled through the file looking for anomalies. I just didn't see for looking.

Out of date! My God, my very bad! I usually jump on an update tout sweet. Thanks John, 'preciate it. 🙂

J=<< MISSING JOYSTICK >> << MISSING JOYSTICK >> K=<< MISSING JOYSTICK >> << MISSING JOYSTICK >> H=<< MISSING JOYSTICK >> << MISSING JOYSTICK >> I've seen this for some time now and although I can detect nothing untoward the .ini file seems to think it's significant. Every pirce of kit attached to the sim is mentioned and I haven't discarded anything. It's not important, so finish your coffee first. .😁 .ini attached EDIT: Just remembered, CH yoke replaced by Fulcrum recently and a Saitek throttle quadrant bit the dust but that one was, I think, before MFS & FSUIPC7 FSUIPC7.ini

Thems my thoughts. Lets call it a day. Muchos gracias.

It's not a worry per se, more of a 'this is very odd' The strange thing about the Saitek wheel is, it's not automatically recognised by Windows. You have to rotate the wheel to get a USB 'bing bong' 🙂 There's a gremlin in there somewhere and I'm not qualified to find it. John, don't fuss yourself about it. I fondly believed you'd say 'Ah yes, we know about this'. You're not a God after all. 🙄

I have. That's not really the point. Why just the JF aircraft? It works fine with MFS controls but not with FSUIPC. Ron

I forgot to mention I use the Saitek Trim Wheel which uses an axis. That may well be the issue. Beats me. I'll put it down to another SDK restriction or some such. Thanks for answering though. Cheers, Ron