Ron Attwood

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

As I said John, I have no assignments in MSFS for the TPM. Every button/switch on it is handled by FSUIPC. G=Pro Flight TPM System G.GUID={C8DA6E60-25B7-11E6-8001-444553540000} is the controller in question.

Sorry I've taken so long to get back. Attached is my ini and the log. MSFS has only two button controls assigned to different controllers, not this one. Everything else is handled by FSUIPC. That was my very first thought. My hunch, based on no technical knowledge is that MSFS thinks an electrical thing has been switched so I'll turn stuff off. Oh, I did two runs, one starting from the runway i.e. ready to fly. No conflict. Starting from a parking spot i.e. C&D- Conflict FSUIPC7.zip

..And not by design. This probably is outside of your sphere of influence but I'll ask anyway. I have several controllers, one of which is the Saitek TPM throttle/bank of switches. All the switches are assigned via FSUIPC, no issues there...Except. One of the switches does the strobes and when starting an aircraft switching on the strobes switches off the battery thus knocking out avionics etc. Switching everything back on (Battery, Alternator, avionics on the same bank of switches) the strobes switch minds it's own business. Now, could that be an FSUIPC thing or an MSFS/Asobo thing?

Yes, it's not quite what I thought it would be, but it'll do until you can rework it maybe?

Actually, that does the job, thanks. The reason I asked was because I sometimes forget to start FSUIPC until the sim has started in full screen and the system tray is hidden resulting in a bit of a faff. Just to make sure, it will connect to the sim when it loads an aircraft, or before? I'll have another go and watch carefully.

Is it possible to have an option to not minimise to the system tray on starting FSUIPC7?

Thank you John. I shall save that list to my desktop...In case.

I'm so pleased I happened upon this thread. I've been driven mad by Avionics Master Set and every vaiation of it. I very nearly resorted to letting MSFS do the job but that would be giving in eh? Due to your input here I now have the avionics switch working, albeit upside down. On is off and vice versa. but I can live with that. Are there any other commands like that? Is Asobo taking notice of you? Anyway, thanks. EDIT: I assume those controls are in the paid for version already?

When I clicked the register button a pop up appeared saying that the 'Registration checker has stopped working and will close' My guess is it (FSUIPC) didn't want to be installed on F:// where the beta was installed and a registry key still told the installer it was there. So I cleaned out the registry and tried again. This time, C:// appeared in the 'install to' slot and it installed properly. A case of uninstallers don't remove everything eh? 🙂

I have bought it from SimMarket 15 minutes ago. Downloaded it and tried to install it as a fresh, brand new install. It insists that the Registration checker has stopped working. All details entered on the form as as per my details on SimMarket. I uninstalled the beta completely in order to start afresh.

Well, that's a matter of opinion. I never, ever found it so. I suspect no-one else did either. But it's your baby, I'm only a customer.

I have. Been using it for yonks. That's why I asked. Perhaps there is a misunderstanding. In the beta you click 'Show' then assignments theneither Axis, buttons or keys as separate windows. closing each one in turn. As you know, in previous versions one window four tabs. Tidier.

Will the layout be the same as previous FSUIPCs? i.e tabbed Axis/Buttons etc.

Sorry I've been so long answering. I've sorted out what I wanted. Assign buttons to keystrokes! Eye point up = Up arrow. Eyepoint down = You'll never guess. 🙂 Thanks for you time. 👍

Having sorted that out. 😀 Is there an answer to the eyepoint situation? This is starting to sound trivial now that I have got the results I want. They're just not where I want them.

My brain is addled by all this new information. Sorry. Scrub what I said. In and Out are on switches assigned to key presses + and - . For or Up and Down MSFS takes over. I don't know if there is a keyboard command for Up and Down. Just to be clear, all I want is adjustable Up Down In Out. Not specific 'views'.

Oops!