Ron Attwood

Lama. It's pretty stable to fly without feeling dumbed down. Once you've got it started!

AXIS Collective set got my hopes up then dashed them! 😀 The daft thing is that the lever doesn't react to the mouse except when the engine is running. This is so frustrating, it's not as if I'm asking for anything exotic. The bottom line is that I don't understand LVARS and the all the other exciting things you chaps take as ordinary. I need to be talked to like a 5yo. 😕 I really do appreciate your taking the time, but I'll just content myself with what I've got. By tomorrow I'll probably have forgotten all about bloody helicopters anyway. Dangerous things!

I've tried everything that has AXIS, HELICOPTER, THROTTLE and SET in any order. None of them work. I'm think this is a Toag problem. Thanks for responding though. In the meantime I'll settle for starting on the runway! Shame, lovely helicopter though, the Lama. Cheers John

Me again. 🙄 Problem with helicopter throttle. The sims assignment for throttle is SET_HELICOPTER_THROTTLE 1_AXIS which works. FSUIPC7's is AXIS_HELICOPTER_THROTTLE 1_SET doesn't work Why not use the sims assignment then? I hear you ask. Because I loathe Asobo's mess. I want no part of it. FSUIPC handles everything. I've been to Toag's Discord and they speak in coder's hieroglyphics. I have tried various other throttle settings in FSUIPC but no luck Can you please shine a light on this?

Top tip. Also I never realised about the profile thing. If I got a new paint I'd have to point it to the appropriate profile. In the end I'd have l list as long as your arm of Comanches. 😂 Thanks for your time John. I expect I'll be back in the future with more 'insurmountable problems' 🙄

I think I know the problem. MSFS controller system makes a preset for EVERY plane I jump into. In the olden days my first job with a new sim was to disable all the controls. Then FSUIPC took care of everything. Never a problem. I'll leave you in peace and try to come to terms with 2024 'system'.

Log set to Buttons and keys FSUIPC7.log These are from my .ini file. 8=HD,17,K80,24 -{Key press: lalt+P}- 9=PC,1,K50,24 -{Key press: lalt+2}- 11=RC,33,K69,9 -{Key press: lshift+E}- 12=RC,38,K81,9 -{Key press: lshift+Q}- 13=PA,1,K74,8 -{Key press: J}- 14=PA,2,K50,24 -{Key press: lalt+2}- 15=RA,7,K69,9 -{Key press: lshift+E}- 16=RA,9,K81,9 -{Key press: lshift+Q}- 17=RA,6,K87,9 -{Key press: lshift+W}- 18=RA,8,K83,9 -{Key press: lshift+S}-

Sorry. Yes, key strokes. I wasn't aware of the difference. I'll get on it. 😁

My God! I've just looked at the log file. Who'd guess that so much went on under the bonnet? FSUIPC7.log FSUIPC7.ini

Is it possible that FSUIPC can 'forget' assignments? Or is 2024 controls system snatching then back by nefarious means? This is mostly keystroke assignments. As lovely as it is 2024 is..is..well, trying.

Wouldn't you know, I've just gone over to 2024 and The Duke now works with the 'normal' assignments. I could cry sometimes! 😁 EDIT: But it changed back with SU3 🤣

I've been struggling with this BlackSquare mixture thing for ages. Today, thanks to this thread, I've cracked it! As John said earlier, "Why not? Have you tried? It is incredibly easy and explained well:' I've used FSUIPC since forever and I maintain that it's like brain surgery, Easy when you know how. 🤣

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