Morten

Hi Pete and John I guess, you're right and the problem is still present - probably just me getting more and more use to compensate the lack of turning by using cross throttling... I read the "FSLabs A320 Steering/Tiller debate" link which John provided me. However I'm afraid it got too nerdy for me and didn't really catch the conclusion, if any. Please bare over with me, I'm just a regular user and have no skills whatsoever into programming and special FSUIPC mods. So in simple terms, please; 1. Is there actually a way to mix the tiller facility with my (physical) pedal rudder axis assignment? 2. If so, would I actually benefit with such a mix in order to make my front wheel turning more efficient? (During turns on the taxiway I notice that the animated tiller on the PMDG 777-200 actually DO turn - whether this animation is actually a valid reflection of a tiller process taking place for real I can't tell) Cheers, Morten

Hi John Thanks for your profound suggestions... Now I totally erased axis for my pedals inside the FSUIPC.ini and instead established axes directly inside the P3Dv4 controls environment. So far steering is back to normal again. Cheers, Morten

P3Dv4.4 FSUIPC 5.15 PMDG 777 Can't seem to configure my Saitek pedals correct through "send direct to FSUIPC Calibration" along with PMDG 777. Brakes and rudder works fine, but the front wheel works poorly, which means that I have to use my throttles violently as a compensation in order to make sharp turns. For my Saitek pedals ONLY I previously through the years used to send my Axis to "FS as normal axis" (rest of the "joysticks" direct to FSUIPC) which worked fine until FSUIPC/P3Dv4.3. From then on my other "joystick", my yoke, went totally bananas and out of control! No surprise here, as according to the manual, one is not supposed to mix "send direct to FSUIPC Calibration" and "FS as normal axis"...anyway this worked for a long time, until now when I don't seem to have no other choice than let all my axis on all my "joysticks" assign to "send direct to FSUIPC Calibration", which in practise wont work for my pedals! What is going wrong here? Would it perhaps help if I instead use "Send to FSUIPC Offset" ONLY for my pedals mixed with "send direct to FSUIPC Calibration" for the rest of the "joysticks"..? Cheers, Morten Attached files: log and ini. FSUIPC5.ini FSUIPC5.log

Hi Peter I'm afraid that your answer is not relevant in this case for several reasons: 1. I've had no issues whatsoever in terms of calibrating those exact same throttles prior to this 5.15 update. 1a. Also keep in mind that my update from 5.14 to 5.15 resulted in some screwed up throttles right away, which was the only reason for the need of a re-calibrating - That is, throttles screwed up, even though I did a copy/paste of the joystick values from the 5.14 ini file. 2. Your description of limits regarding to "less or equal to both Centres" makes no sense here, due to the fact that I always aime to make death zones plenty wide, in order to prevent sudden reverse mode when the intention was just put the throttles in neutral. 3. As mentioned before, for now with this 5.15 version I will only be able to EDIT the existing calibration which turns out fully successful - widespread death zones, or not. In other words, making a "virgin" reset before a new calibration is the only situation where hell is turned loose! So something seems to work out rather unexpected here with this 5.15 version. Cheers, Morten

This is what I'm doing and have always done, Pete! But now the "virgin" install won't let me set new values - an error sound is ringing every time I'm trying to set the new values.

Was about to finetune my "Separate throttles per engine" Joystick Calibration - for start hitted the Reset button per throttle as usually, then went on with setting values for Reverse/Max/Idle for all 4 throttles. Result: Respond from throttles where now totally wiped out in P3Dv4.4 /PMDG 777!! Tried again - this time without hitting the Reset buttons before calibrations. Then finished my calibrations as usual. Result: Succes! Have I missed something out? Perhaps forgotten something in the standard procedure? Or is there in fact a bug here..? Cheers

Thanks indeed Peter!! What would we do without you! All works fine again, except for them throttles which need a bit fine tuning - no problem anymore as they now are identified and recognised! A "mammoth" you say....well yes for little me at least, starting out with facing your elephant of a science manual 😰 Best, Morten

Hi Peter Thanks for your quick answer! However I'm a bit confused. Not quite sure what to edit from what...? Have struggled with this issue now for hours!! Hereby attached the involved files for clarifying or a quick edit maybe... Best, Morten FSUIPC5_From NEW pc.ini FSUIPC5_From OLD pc.ini FSUIPC5_Log from NEW pc.log

Hi Peter In the good old FSX days I was used to copy from ini to ini right away without any problems according to your guide here: "POWER USERS note: if you have a lot of investment in your Buttons, Keys, Axes or Joystick Calibrations via FSUIPC version 4 then you will want to retain most, if not all, of that work. This is okay—those parameter sections are identical in FSUIPC5, though many [General] section parameters no longer apply. These won’t be deleted, so to create a tidy file, use an editor to copy just the [Buttons …], [Keys …], [Axes …] and [JoystickCalibrations …] sections over from your FSUIPC4.INI file to your new FSUIPC5.INI file. After that, check they all work and possibly re-assign those which have changed." Now with P3Dv4, I found that this simulator totally ignore whatever copied values I put into the new applicable FSUIPC5.INI file, even though, strictly according to your guide above. Values that were originally based on the “Send direct to FSUIPC calibration” option. Moreover, what is really odd in my eyes, is that I copied and pasted from the exact same FSUIPC5.INI version - that is, from my second computer to my current main computer, both having the exact same installed P3Dv4 versions. But still my main computer wont react to ANY of the exact same" joystick" controls in use!! I can actually see all the assigned values inside the ingame FSUIPC GUI..! Before doing the copy/paste action, I strictly insured these actions: 1. Completely deleted ALL axis settings inside P3Dv4 on my current main computer. 2. Deleted FSUIPC from my P3Dv4 Modules folder on my current main computer. 3. Installed a completely fresh "untouched" FSUIPC5 version (identical to the version on the second PC) into the P3Dv4 Modules folder on my current main computer. 4. Ran a P3Dv4 session, just so that a FSUIPC5.ini would be created - didn't touch anything during that session / didn't open FSUIPC! .....No respond on any of the controls! What the heck am I missing out?!! Yes, of course I could do another configuration, BUT in this case we are talking about many physical controllers, including a 4-engine quadrant including reversers, mixture/propeller/spoiler pins and pedals with differential brakes, which would take me HOURS to complete and finetune! In use: Win.10 Pro 64, P3Dv4.3, FSUIPC5 vers. 5.14 Regards, Morten

OK Pete, I appreciate your help and quick answers. After you uncovered all the sorted details about how this autosave function is programmed and supposed to work with only 10 autosaves, I no longer see any point of change anything here. :) I'll be back with results...

For one reason or another...anyway, the fact is that things are not working, so what would you suggest me to do in order to solve this problem?

No Pete I already excluded all the odd ones. The 123 autosaved files are all saved by FSUIPC as confirmed in both the Flight Simulator X Files folder and in the FSX flight loader browser itself.

Confused or not. All I can say is that, for some reason, my FSUIPC is keeping 132 FSUIPC autosaves back from the year 2009! My FSUIPC.ini looks like this: [AutoSave] AutoSaveEnabled=Yes Interval=120 Files=10 SaveOnGround=Yes Next=7 1=Fri 044157 2=Fri 044837 3=Fri 045636 4=Fri 045836 5=Fri 050235 6=Fri 051233 7=Fri 042401 8=Fri 042601 9=Fri 043758 10=Fri 043958

No such "strange reason", please! As it is the file name is unclear because autosaves are kept over such a long period - if not possible to add any further identity to the autosave files, would there perhaps then be a way to edit the ini file so that autosaved files only are kept for a week?

DDD HHMMSS, Okay now I know that at least - I must have missed it somewhere in your comprehensive manual.. However, unfortunately not that easy. A date is also required in order to make sense of it all. "Fri", "Mon" etc. is not clear as there's obviously lots of these during the month and years.

Each time I have to load an autosaved flight I'm having a hard time to figure out the logic behind the numbers within the saved file. As it is, the only clue I can handle is the week day and a preview. However in some situations, when for instance I have to load a certain autosaved panel status into the FMC of a PMDG 777 there will only be these cryptic numbers present which leaves me with absolutely no idea of what to choose. Am I missing something?..certainly hope so!

No it hasn't. Just for your information, I finally solved the mystery by simply creating and saving a new "Default Flight" as advised from one of the many simmers who had ran into the same mess. So now GPS error messages are all gone and FSUIPC will autosave my flightplan created flights normally again! In fact this action also solved some other abnormal behavior regarding my AI traffic. Is guess, my old Default Flight over time has become "infected" with bad data during all kinds of scenery addon manipulations, FTX Global, Pilots Mesh and so on...

Autosave is enabled and everything else is being autosaved - further more I'm not even able to make a regular FSX save during a fligtplan executed flight. I know by now that it has nothing to do with FSUIPC. However with your skills and experience you might perhaps have an idea of what to look for while we are at it..? After a crash, for instance, FSX will normally reload the same flight - but as it is, instead a popup turns up saying: "Error loading GPS_Engine. The flight plan will not be used - OK" If I then hit the OK button, the flight will end completely. Rather frustrating... Arhh Okay, I just learned that this bug is well known and is described all over the net - seems to be caused from a Microsoft update somehow. Unfortunately the solution to the problem is not crystal clear...all sorts of suggestions!

Hi Pete Something strange has happened - FSUIPC will no longer create autosaves when I fly with IFR flightplans. After, for instance a crash, an error dialog box pops up, saying something like: "GPS error. Autosave will not be available". What is going on, do you know? I'm using the latest version 4.929. Cheers, Morten