Morten

Pete, it is related to the thread that you closed the other day: From this thread:

Okay, then...! In that respect I can certainly recognize the "funny" part of the yoke suddenly going completely bananas just before landing, about one out of 10 times (as mentioned to you before), but as irritating as it is, I can actually deal with that by just setting the sim on pause and replugging the USB connection and all returns to normal again...almost rutine! :) However dealing with a throttle quadrant that I have to re-calibrate in FSUIPC because the calibration has been lost every time I startup the PC and fly the PMDG in a new session, is pretty damn hard to deal with! Giving this another thought... if no one else has that kind of problem, I guess it potentially could be due to the fact that this selfmade quadrant was originally made as an analog "joystick" plugin - then during time I put the analog plug into an USB adapter which worked just fine up to and including Win 7 - but with Win 10, here was when problems started with "forgetting" calibration settings! Gordon Bennett! Just having a new session after rebooted the PC several times and NOW, all of a sudden, the quadrant within FSUIPC calibration suddenly remembers all data! Absolutely, having no clue why this relatively old problem suddenly, all at once, now is disappeared??!! The only thing I can think of is a newly Win 10 update this afternoon! Will however, of course, monitor this "miracle" the next couple of days and see if things are staying that way....!

Hi there I recently in another post learned that calibration of joysticks handling PMDG aircraft tend to make unpredictable troubles: "If you want to assign in FSUIPC, for PMDG aircraft Send to FS as Normal Axis AND select the "Axis_" controls. And do not calibrate in FSUIPC no matter where you assign" In my case, most of my avionics are controlled by commercial "joysticks", consisting of yoke, spoilers, mixture, pedals, etc, which have calibration tool software along with the equipment - However my 4 throttle quadrant consists entirely of homebuilt equipment! Would anyone perhaps have any suggestion to into which alternative tool I successfully would be able to calibrate this throttle quadrant when FSUIPC is not an option? Regards, Morten

Well sorry for my part also, but what you don't seem to realize is when your customers finally has done all assigning and calibration according to your comprehensive and relatively complex manual, they will usually only return to you for help if something goes wrong - that could be months or even years after. Because of that it is obviously essential that you stick to the exact same terms as used in in your own FSUIPC manual and program. No vague and "agreed terms" please, which would have the tendency to confuse everyone else than folks in your own staff. Put on top of that language barriers from your customers from all around the world! Furthermore, take into account the fact that FSUIPC, as in my case, is only one out of 5 other plugins that has to be calibrated, adjusted, etc. Fortunately for most part though, with clear and straightforward manuals - otherwise it simply wouldn't be possible to get to the point of actually flying within my limited spare time! Experienced professionals as I guess we both are - in my case a construction architect - unfortunately have a very bad habit of taking for granted that everyone understand what we are explaining to them within our usually professional (..arrogant?) insider language. Because of that, it is sometimes best for everyone if we would leave that to other good and patient folks to communicate for us ;) In agreement to this, for leaving out any misunderstandings I would be most grateful if you at least, for everyone's sake, please would stick to the exact and fully expressed terms as it occurs both in your program and in your manual as in this example: 1. Send direct to FSUIPC Calibration 2. Send to FS as normal axis 3. Send to FSUIPC Offset Thank you. /Morten

Hi Pete May I ask you to please answer me precisely, specifically and directly according to my questions. Which of the following environments would you recommend me to calibrate my PMDG: 1. Send to FS as normal axis inside the FSUIPC environment? OR 2. Calibrate my axis entirely inside the P3Dv4 settings environment? Morten

Hi Pete 1. In my specific situation I'm using PMDG 777 most often. However occasionally I use these other aircraft for VFR: 2. Standard P3Dv4 Mooney Bravo aircraft 3. Third party DC3 by Daniel Fuernkaess, Manfred Jahn, Alexander M. Metzger, Hans-Joerg Naegele, Mike Cyul, Warwick Carter, Jan Visser So in this particular situation of mine what would you advise me to do regarding calibration methods and profile systems for each aircraft? Regards, Morten PS. Actually my very least occasional problems is NOT with my rudder/brake pedals (occasionally the pedals are completely "dead" by start up a session. But immediately solved by simply replugging the USB connection with absolutely no further incidents whatsoever!) As I wrote to you my main problem is my 4 quadrant throttles and my yoke!

Thanks indeed Pete for taking your time and getting back to me with a quick response... I'll look into your answer in depth and get back to you if any further questions. Regards, Morten

Hi Thomas If this is really the case in relation to PMDG, this is very cruisel for me and my settings! However you were a bit fast in your answer, so please confirm if I got you right: Types of axis assignments as it shows up in your program: 1. Send direct to FSUIPC Calibration 2. Send to FS as normal axis 3. Send to FSUIPC Offset So what you are telling us is that we have to stick to No.2 "Send to FS as normal axis" in the case of PMDG. CORRECT? As it is my separate yoke, pedals and 4 quadrant throttles are all currently assigned to No.1 "Send direct to FSUIPC Calibration" AND I got problems with P3Dv4/PMDG 777! A. My yoke will occasionally go completely bananas/uncontrollable whenever I disconnect the autopilot on approach - then I have to set sim to pause and reconnect the USB yoke before it will work normal again. B. FSUIPC keeps to forget my separate throttles per engine Joystick Calibration. Which means that I have to recalibrate my throttles all over again when starting a new sim session. Obviously pretty annoying! NB. I have already disabled ALL my axis settings inside the P3Dv4 settings. Also I'm fully aware of that P3D occasionally tend to put them back again, so I have an eye on that. Nevertheless, problems as described above keeps on ruining my sims! Question is, if all this is because of using a wrong FSUIPC axis assignment type? Regards, Morten FSUIPC5.ini

Hi there Thomas I much appreciate your interest for this subject. However I'm sorry to tell you that you unfortunately completely missed out the very obvious and straightforward point to the subject, which is simply to add a version number to the zip file. That's all! Cheers my friend

Hello Pete Really now, that is not a reasonable argument: (Because) "That it has always been the case". Old men as we are, better be rational and keep evaluating according to development in our present time. In other words, plane and simple, naming a Zip file according to the relevant version number is what EVERY other developer does in these days, away from you! About detail properties for the "Install FSUIP5.exe": It says, file version 5.1.5.1 which obviously gives no clue to the present FSUICP version 5.154 in this relevant case!

Hi There On your site you kindly inform us about this: If you download a version which is not the same as displayed on this page, *please* empty your browser's cache or make sure you have specified the right download folder, thank you. Also try pressing Ctrl-F5 which should force a direct reload of the page in case your ISP is caching any links on this page. However unfortunately your download zips only show: "FSUIPC5.zip" without any version number whatsoever. If one after the extraction of the zip file then check the actual "Install FSUIP5.exe" one will only get the version of the installer version itself and NOT the actual FSUIPC version. So how would you expect us to verify that we actually have downloaded the most recent version? Cheers, Morten

Come on Pete, what do you take me for! Of course I know all about that. But at the time parking brakes had already been released by me long time before this blocking occured. However as I wrote above, this issue has now been completely solved with help from John. Thanks Pete for that reminder!

Yes! The "Direct to FSUIPC" choice solved the blocked foot brakes after landing! Thanks John!!! (Pedals regarding to steering is however still chosen to be "Direct to FS", as it was the only way to solve my PMDG 777 steering problems - strange...but whatever it takes!) Cheers, Morten

Oh dear...not quite, actually. By disabling P3Dv4.4s own joystick controllers and sending everything through FSUIPC - including the brake on my pedals: "to FS as normal axis" I get an allround perfect and steering setup - EXCEPT for the fact that brakes now seems to block 100% whenever I start taxing and after landing. When taxing I have to hit the food brake in order to release brakes which I haven't touched in the first place at all! Upon landing, it's not enough to hit the food brake twice (as in the good old FSX days). The only way I can release brakes here is when turning the Autobrake button off and on several times, otherwise I'm completely stuck in the middle of the runway with ruined tires! Unfortunately, as I wrote before, to enable P3Dv4.4s own controls only for the pedals is NOT an option for me - Because I'm not allowed to mix my sims controls with FSUIPC as it is. Otherwise my yoke suddenly becomes uncontrollable and go bananas! Frustrating because the sims own controller has an option to define null zones for the brakes which FSUIPC unfortunately don't have (at least to my knowledge). In other words, according to this link, the missing Null zones is what causes exactly this issue: https://www.avsim.com/forums/topic/512544-777-prepar3d-v4-ils-parked-and-blown-brakes-on-landing/?do=findComment&comment=3662099 Any idea to sort this problem out, strictly, within the FSUIPC environment, please?

Fully agree - hate those beeps, not knowing what the heck is going on...

Ahhh okay.... I'm afraid that you misunderstood me using the term "sensitive" - I'm not literally referring to the joysticks as the being sensitive. They are working perfect now in EVERY sense! What I was referring to was what was my experience with the newest version of P3Dv4.4 being ultra sensitive/intolerant to mixes between buttons assigned directly under the options of P3Dv4.4 and axis assigned under FSUIPC - with the result of joysticks going bananas! Although not a purely correct mix - anyway at least tolerated in P3D versions up to v 4.4. All according to what I wrote earlier: So, in other words, trough your effective advice, to disable controls completely in P3D and do all calibration and assignments within the FSUIPC environment is what made everything perfect to all my joysticks in P3Dv4.4. So for now: - Everything works perfect! - Happy ending! - Morten being happy! - End of troubles! Cheers, Morten

What?? "all the fuss" .......? I was struggling my arms off in order to get things right here - I finally ended up with succes, as you well know partly through your advice to disable P3D controls, and partly through my own experiment of letting pedals axes go through "Send to FS as normal axis". So no more "fuss", just happiness. But you asked me about some analytic questions, which I answered. Nothing more to it. 😃 Yes indeed, I'm off flying! Cheers, Morten

Throttles: "direct to FSUIPC calibration" Spoilers: "direct to FSUIPC calibration" PropPitch: "direct to FSUIPC calibration" Mixture: "direct to FSUIPC calibration" Yoke: all axes: "direct to FSUIPC calibration" Hat switch on yoke: "Send to FS as normal axis" (NEW assignment) Pedals, rudder: "Send to FS as normal axis" (fairly NEW assignment. Solved front wheel steering problems ) Pedals, brakes: "Send to FS as normal axis" (fairly NEW assignment) P3D "Use Controllers": Disabled (fairly NEW assignment. Solved throttles unable to be calibrated correctly and yoke going bananas after disabling autopilot) ALL buttons assigned through FSUIPC (NEW assignment) ______________________________________________________________ "Calibrating?" Yes of course! "Check in the P3D support forum". No way Pete, check yourself if you like. For my part I'm just happy now that everything works again! /Morten

Yes I'm sure. All the sim hardware including throttles, yoke and pedals has been exactly the same all the time. All I have changed is new monitors and according to those I changed resolutions and the fullscreen setup. Also installed MS Office. And of course I can't tell whether any MS update could have had any influence here. /Morten

However rather strange... Up till the latest P3Dv4.4 conditions were more tolerant without problems. Now conditions apparently are extremely sensitive in every sense - strictly, either FS control assignments for everything OR strictly assignments through FSUIPC, even including buttons! 😲 Amazing that all my joystick troubles during the last couple of months only comes down to this fact!! Cheers, Morten

My dear Pete This was indeed your best advice of the year!!!!!!! EVERYTHING now works as expected, yoke, throttles and pedals! Wow! 😃

I tried to mix tiller and rudder, assigning both to the pedals through "Send direct to FSUIPC Calibration". Not an option, at least not to my PMDG 777-200. The tiller mix reacted by turning the wheel all the way to each side. Not possible to go straight forward. I found the best solution till now, by assigning the axis rudder (no tiller mix) to my pedals and use "Send direct to FS as normal axis". This makes my front wheel turn fully perfect again as it use to couple a month ago! However my yoke, which is assigned trough "Send direct to FSUIPC Calibration", still go bananas if I choose to turn off the autopilot, as described above. No axis whatsoever, is no longer assigned inside P3D - Options - Axis Assignments. So what the heck is going on here?

Okay Pete, got it! In fact my 'some what' common sense already told me before I even started this configuration!..hi, hi...life aint easy. The steering issue however, is left to solve - not for common sense to solve.. quite a drag...!!

Moreover, according to this my previous statement and the following discussion, I've chosen as an experiment to completely keep my pedals out from FSUIPC. Which means that my pedals currently is calibrated within the P3D settings environment only, whereas my throutles and yoke is still calibrated inside the FSUIPC environment and send "direct to FSUIPC". With this combination I unfortunately still find my yoke going completely bananas and uncontrollable. It will happen mostly during an ILS approach, if I then choose to abort the autolanding and disconnect the autopilot in order to make a visual approach instead, then the yoke will turn all the way to the right and become totally out of control! The only way I can overcome this is by replugging the yoke into the USB slot and from then on it will be controllable again. All together, for some reason quite a mess here these days...?! Cheers, Morten

Ok thanks, I'll get it a try. What is noticeable though, at least in my case, is that this lack of steering came about after updating from P3Dv.4.3 to v.4.4 - might be a random event, might not be... /Morten