Ron Attwood

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

Odd one this. I use the Saitek trim wheel. Always have, always will. From FXS onwards FSUIPC has always recognises it. Indeed it does now for MSFS. However. For the Just Flight Arrows and their Hawk, the wheel is reversed. Nose up is now nose down. (Keep reading) This is ONLY JF models. EVERYTHING else works properly. I've been on to Just Flight and got nowhere, although Mark was as helpful as he could be. The options I have is to check the 'Reverse Axis' box in FSUIPC and change back for ANY other aircraft. (PITA) Make a profile for Arrows based on etc. and one for Hawks based on something else *sigh* Or Horror of horror, use MSFS to assign ONLY the trimwheel. Which is what I'm doing at the moment. Still here? 🙂 The question is, is there something different that Just Flight are doing that prevents them from seeing FSUIPC control. They say they use the trimwheel but use MSFS to assign it. This is just on the off chance you have Arrows etc and have come across this. Cheers, Ron

Damn me if you haven't hit the spot again! For the record, all my controllers are driven by windows. Looking at the properties of the Saitek\drivers I went to the system32\drivers and lo and behold there were two identical driver files but different dates. I took them both out but there was a 'hiccup' and only one made it to my desktop. I then removed the trim wheel and restarted. I expected window to run through it 'new thingy' thing but it didn't. Eventually I replaced the driver file, restarted and then started MFS. The trim wheel was operational right off the bat, no faffing. FSUIPC doesn't need to be 'nudged' into finding it. LG Thanks John...Again. 🙂

Saitek Trim wheel. Anyone who has one knows you have to give it a twirl before windows recognises it. 'bing bong' However, 🙂 having twirled it then started MFS, FSUIPC doesn't automatically assign it to it's task as per every other controller. You have to go into Assingments\ Axis move a control then Rescan, twirl the trim and THEN it will show as Axis elevator trim. Have I missed a trick? Is it a known foible? It's a routine I've got into so it's not desperate, but know what it's like when you have ab itch.

A bit of over enthusiasm eh? I'll un-check it. Thanks again.

Gosh! The whole family. 🙂 As a for instance Landing Lights On: Parameter 0 (Switch moved down) Checked 'Control to repeat while held... Landing Lights Off Parameter 0 (Switch moved up. Same for Strobes Alternator, Master Battery and Master Avionics EDIT: Gentlemen you are priceless! Parameters, who'd believe it. I now have all my switches work as on and off. Thank muchly

I keep meaning ask about this but I keep forgetting. I have a Saitek TPM which has nine toggle switches. I've assigned them to various lights etc. All my assignments features Down for ON and OFF when released. All except Nav lights. There appears to be only 'Toggle nav lights' as opposed to Nav light ON and nav lights OFF. Question is, have I missed something or is that how it is? No biggie but a tiny itch that needed scratching. 🙂

Thanks John. I figured something along those lines but I would never been able to put it so succinctly. I had a look at the log and it all seems OK to me. Like the Bye bye. 🙂

Does any of this mean anything to anyone? This first one corresponds to a broken up/static like voice coms (TS) while on a flight Error 03/07/2021 20:33:51 Application Error 1000 (100) Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60c0b1e3 Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60c0b1e3 Exception code: 0xc0000005 Fault offset: 0x000000000016ed1a Faulting process ID: 0x32c0 Faulting application start time: 0x01d77031dc633031 Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.17.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.17.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Report ID: 48b738d2-b86c-462a-b3fa-5158bf3ae674 Faulting package full name: Microsoft.FlightSimulator_1.17.3.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App Culminating in a CTD (Flight sim has stopped working, close the app? type) Error 03/07/2021 20:34:19 Application Error 1000 (100) Faulting application name: FSUIPC7.exe, version: 7.2.0.1, time stamp: 0x60d1ebf7 Faulting module name: FSUIPC7.exe, version: 7.2.0.1, time stamp: 0x60d1ebf7 Exception code: 0xc0000005 Fault offset: 0x0000000000019884 Faulting process ID: 0x1ed8 Faulting application start time: 0x01d770321749bfe1 Faulting application path: C:\FSUIPC7\FSUIPC7.exe Faulting module path: C:\FSUIPC7\FSUIPC7.exe Report ID: 63cb65cd-d870-4383-b684-b2e224a4b2e6 Faulting package full name: Faulting package-relative application ID: I rejoined the flight and carried on until the end. Finished at 22:08ish. I didn't notice anything untoward but found this in the Event Viewer Error 03/07/2021 22:08:41 Application Error 1000 (100) Faulting application name: FSUIPC7.exe, version: 7.2.0.1, time stamp: 0x60d1ebf7 Faulting module name: FSUIPC7.exe, version: 7.2.0.1, time stamp: 0x60d1ebf7 Exception code: 0xc0000005 Fault offset: 0x0000000000019884 Faulting process ID: 0x1ed8 Faulting application start time: 0x01d77043dc98d8a5 Faulting application path: C:\FSUIPC7\FSUIPC7.exe Faulting module path: C:\FSUIPC7\FSUIPC7.exe Report ID: de3dcc08-d842-4d2e-8d8b-aeb377431552 Faulting package full name: Faulting package-relative application ID: I can't think it was FSUIPCs fault but thought you may be able to throw some light on it. Cheers, Ron