Pete Dowson

Your biggest problem is that you aren't actually assigning any axes in FSUIPC as actual axes. Look: [Axes] PollInterval=10 RangeRepeatRate=10 0=0X,256 1=0X,B,0,0,66420,0 -{ Entering=AXIS_THROTTLE1_SET }- 2=0Y,256 3=0Y,B,0,0,66423,0 -{ Entering=AXIS_THROTTLE2_SET }- 4=0Z,256 5=0Z,B,0,0,66421,0 -{ Entering=AXIS_PROPELLER1_SET }- 7=1Y,B,0,0,65762,0 -{ Entering=AXIS_ELEVATOR_SET }- 9=2X,B,0,0,66424,0 -{ Entering=AXIS_PROPELLER2_SET }- 11=2Y,B,0,0,66422,0 -{ Entering=AXIS_MIXTURE1_SET }- 13=2Z,B,0,0,66425,0 -{ Entering=AXIS_MIXTURE2_SET }- 14=4X,256 15=4X,B,0,0,65763,0 -{ Entering=AXIS_AILERONS_SET }- 16=4Y,1120 17=4Y,B,0,0,65762,0 -{ Entering=AXIS_ELEVATOR_SET }- 19=4Z,B,0,0,66382,0 -{ Entering=AXIS_SPOILER_SET }- Those are all individual little zones, without even the borders correctly defined, using the right-hand side of the Axis Assignments options tab. Why on Earth are you doing this? That area is a specialist place for specific events some folks need to occur on certain parts of a lever movement. All the NORMAL axis assignments are a much simpler process, one or two steps, and done only on the LEFT hand side of that tab. I really don't know how you arrived at doing what you've done. It makes no sense at all, and will never work the way you want. Have you ever any of the FSUIPC documentation? The User guide does have simple instructions, with pictures! You've even set calibrations for just about everything: Aileron=-16380,-512,512,16380 Elevator=-16380,-512,512,16380 Rudder=-16380,-512,512,16380 Throttle=-16380,16380 PropPitch=-16380,16380 Mixture=-16380,16380 LeftBrake=-16380,16380 RightBrake=-16380,16380 Throttle1=-16380,-512,512,16380 Throttle2=-16380,-512,512,16380 Mixture1=0,8192,8192,16380 Mixture2=0,8192,8192,16380 PropPitch1=0,0,512,16380 PropPitch2=0,0,512,16380 ElevatorTrim=-16380,-512,512,16380 Spoilers=-16380,16380 Flaps=0,16380 Reverser=-16380,16380 Aileron Trim=-16380,-512,512,16380 Rudder Trim=-16380,-512,512,16380 CowlFlaps1=0,16380 CowlFlaps2=0,16380 PanHeading=-16380,-512,512,16380 PanPitch=-16380,-512,512,16380 PanTilt=-16380,-512,512,16380 SteeringTiller=-16380,-512,512,16380 SlewAlt=-16380,-512,512,16380 SlewSide=-16380,-512,512,16380 SlewAhead=-16380,-512,512,16380 SlewHeading=-16380,-512,512,16380 Reverser1=-16380,16380 Reverser2=-16380,16380 even though those won't be used at all. And none of them are actually calibrated anyway -- all those are default values, set by simply pressing the "SET" buttons and then not actually doing the calibration. Again, there are step by step instructions doing the calibration in the User Guide. You are hardly making any use of anything else in FSUIPC -- hardly any buttons assigned, and one keypress. Why did you get FSUIPC? I can answer specific questions if you are puzzled by it all, but please do try to read and follow the instructions. Then delete the INI file and start again. Pete

What problem? Sorry, I haven't sen you post one in this thread, Are you talking about another? Pete

It's found. It's actually similar to the others -- different symptom, that's all. i'm having to remove the new Joystick Scanning altogether. Shame, it would have been nice. But there are obviously still flaws in Win10 which I can't find a way around. I'll be releasing 4.964, maybe late tomorrow, with the previous joystick scanning and a couple of other fixes. Pete

That FSUIPC text documents IS FSUIPC4.LOG!!!! I said earlier, Windows is classifying it as a text file, because it is made of text. You have Windows options set wrong. You've evidently never read the FSUIPC4 User Guide where it clearly tells you, very near the beginning, tto change this option. I think it actually tells you how to do it too! I've deleted the posts with your files. The KEY file is your private registration and you willv lose it if you publish it like that! NEVER upload files without them being requested. Pete

No, it isn't worth it. Just writte down what files you see there starting with "FSUIPC". That will do. I'm SURE you have a log and for some reason cannot see it. It is produced at the same time as the INI file. Pete

I'm sorry, but that is simply not possible. The very first thing FSUIPC does when it starts is create a LOG file. You are either looking in the wrong place, or you have Windows hiding file types from you. The LOG is an ordinary text file. Tell me, what files DO tyou see in the Modules folder? I know all this! You've now repeated yourself 3 times. Sorry, but I need to move forward! That doesn't help me fix the problem and move forward though! Please try again. Pete

Thanks. Despite the new scanning working now on my only Win10 installation, it seems obvious that the nice neat new joystick scan cannot work on Win10. Which is a shame, because it is on Win10 that most of the Joystick ID problems are seen. Very annoying. I will revert to the old method (saved all the old code) and make another release, which will be the same as 4.963 but including the fix for your Throttle Sync problem. I'll save the new scan code and maybe ask folks to try again in, say, 6 months, in the hope that Win10 might be fixed. Pete

In that case FSUIPC4 has never actually run at all, which would explain why it couldn't see your Saitek. Even if your latest sessions didn't run FSUIPC, there would still have been a Log from an older session with FSUIPC. You are not deleting files at all, are you? Please don't! Try just re-running the FSUIPC installer first, and check that it works, that there is an FSUIPC entry in the Add-Ons menu. Then try putting 4.963f back into the Modules folder and trying again.

Same place as the FSUIPC4.INI Pete

You stated your problem in the first post! You supplied the Install log. I need the run time log, please.. It is the one named FSUIPC4.LOG. Pete

That was the problem in 4.963e. It happened here too in 4.963a through e, but only on Win10. It is not in any way related to any previous problem, it is new and related to joystick scanning. Please add these lines to the [General] section of the FSUIPC4.INI file Debug=Please LogExtras=x200000 Then repeat the problem and show me the resulting Log file. I also will need to see your FSUIPC4.INI file please. This was all discussed in the thread about "Volunteers to test FSUIPC joystick scanning" above. Pete

I've moved your support question to the Support Forum so it can be answered. Please ALWAYS post support questions to the Support Forum! You are lucky I saw it! So, where's the FSUIPC4.LOG file? I ALWAYS need to see the Log for support questions. And in this case, also your INI file. No. 4.963e hangs 100% on Windows 10. The ONLY change from e to f was that fix. One parameter in one line. I need you to reinstalled 4.963f and get the log please. There's no way it can move forward without folks being helpful and responsible with bug reports. Pete

All the user facilities. it doesn't change to interface to external programs. Please refer to the User guide in your FSUIPC Documents folder, in the FS Modules folder. That's all about user facilities. Pete

Mindstar did have some problems, which were caused by a bug in FS and P3D to do with airport definition for AI plans. See item 18 in the list of changes in 4.96 (in the FSUIPC History document). I provided parameters to help work around this -- by preventing FSUIPC requesting departure and arrival airport information for AI traffic (So use of these will affect any traffic oriented utilities you use). The Mindstar GPS appears to be the only add-on affected by this serious FS bug. i think L-M have either now fixed it in P3D, or it is on their list to do so. I'm sure Mindstar support would have told you this and helped you. BTW Version 4.96 is out of date in any case and not supported. Please update to 4.963. Pete

No. there is no monitoring of AI traffic, no actions about them, no deletion of anything. Deletion is only done by external utilities or, often, by FS itself when there's a deadlock or other problem. FSUIPC is just reading and supplying information. Pete

Probably. Sorry, it is a value I read from FS. I'm not all that knowledgeable about what everything means. I would see if you can contact Herve Sors about it if you need to know more. Same for the other value. But you could always monitor them yourself, see how they behave. I request SimConnect to supply values when they change by more than a certain amount. How often specific values may change by less I don't know -- 18 Hz does sound familiar -- but there's little point in flooding the system with thousands of messages telling me about minute changes. For the body accelerations the "Delta" (minimum change seen) is 0.0001 (of the units used), and for the World accelerations it is 0.001. I've no idea why they are different -- I think i took advice, long long ago. Pete

Okay! The work-around is to enumerate All devices, not just Attached devices. Somehow they've broken the "attached" device checking in Win10, as it works fine in Win7. I've modified my code to cope, and have already uploaded 4.963f to the Download Llinks subforum. Please use that. I'd like to see the log still please, but only with the "LogExtras=x200000 parameter set if there's still a problem. Pete

No, it's okay. I managed to repro the problem. The work-around is to enumerate All devices, not just Attached devices. Somehow they've broken the "attached" device checking in Win10, as it works fine in Win7. I've modified my code to cope, and will upload 4.963f to the DownLoad links subforum today. Pete

It's just this one function. The callback is supposed to be repeated called by Windows until either I say enough or it says there's no more. Once I've invoked this procedure it's out of my control, theonly code in my program is when it calls me. The logging shows it simply doesn't call me after the first device. I've posted this as a question on MSDN but i'm not hopeful for an answer that way. It looks like I'll have to test for Win10 and not include this improvement (on the very system in which it is most needed!). Such a shame. I'll continue to look for a solution. Maybe sleeping on it will give me some bright idea. Pete

Managed to test on Win10 ... and I get EXACTLY the same results. It's a Win10 bug!!!! Drat. Win10 is the main one with the Joystick ID missing problems, and the very function I found which would enable it to be fixed is broken! :-( Not sure what I can do about this ... I'll experiment here. Pete

Managed to test on Win10 ... and I get EXACTLY the same results. It's a Win10 bug!!!! Drat. Win10 is the main one with the Joystick ID missing problems, and the very function I found which would enable it to be fixed is broken! :-( Not sure what I can do about this ... I'll experiment here. Pete

I've just asked Sabrefly to show a log from another update. i'mve nearly finished zeroing in, and it is starting to look like a problem with the Windows function I'm relying on. Are you using Win 10 too? Anyway, since you can't find the links in that other thread, i repeat the very lst one here: Please show me the log using this one: FSUIPC4963e_TEST.zip So far I've only tested on Win 7. I'll see if I can connect my two game controller devices to my one and only Win10 PC. -- not easy. it's only got one USB port (it's a Surface Pro) so I need to free up a USB hub from somewhere ... :-( Pete

Please show me the log using this one: FSUIPC4963e_TEST.zip So far I've only tested on Win 7. I'll see if I can connect my two game controller devices to my one and only Win10 PC. -- not easy. it's only got one USB port so I need to free up a USB hub from somewhere ... :-( Pete

It can only be done using a plug-in, and one has already been written. I think it is featured in the User Contributions subforum. Mostly the Saitek throttle suits the more usual way of engaging reverse -- assigning "throttle n decr" to be button which is actuated when you pull a lever right back. I'm sure that is what it is for. Just program it to repeat whilst held, the program the release to the "throttle n cut" control so that you get idle again when released -- unless of course you want to keep reverse on without holding back pressure until you move the lever forward a little. Ah, I see my first answer was wasted. Sorry. Well, I think there's also a different solution there to deal with that separately too. I'm not sure if that's here or elsewhere, i just remember seeing it somewhere. In actual fact the reverse reflectors on aircraft only have two or three positions. I think what you are thinking of is the slower effect because it's a physical movement. But equally they are not returned with full reverse thrust applied. Pete

The link is to "FSUIPC 4.963d_TEST.zip" and it must be there because Sabrefly has already downloaded it and run it! I think it's in the last message on page 2. I'm working on an extra few lines of logging, but so far it points to something actually going wrong INSIDE the EnumDevices function of Windows direct input (dinput.dll). I note you said "P3D crashes". Can you get any crash details, because Sabrefly couldn't. What version of Windows are you using BTW? Pete .