K4bel123 Posted June 7, 2014 Report Share Posted June 7, 2014 Hi Pete, first of all I really like FSUIPC because of all of its nice features. Also it made the joystick disconnect problem on my Windows 8.1 PC disappear. But when I assign the POV of my Saitek yoke to the pan view axis, the view will stutter most of the time. This problem appears although I get good fps (24-30). Also my elevators and my ailerons as well as the throttles and so on stutter. It seems like if FSUIPC is sending data not constantly to FSX. I cannot assign the hat switch of my yoke to FSX because then my joystick will disconnect again. I really hope you´ve got an idea on how to fix that problem. Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 7, 2014 Report Share Posted June 7, 2014 when I assign the POV of my Saitek yoke to the pan view axis, the view will stutter most of the time. This problem appears although I get good fps (24-30). Also my elevators and my ailerons as well as the throttles and so on stutter. It seems like if FSUIPC is sending data not constantly to FSX. I cannot assign the hat switch of my yoke to FSX because then my joystick will disconnect again. I really hope you´ve got an idea on how to fix that problem. FSUIPC is sending PAN_VIEW controls to FS at the same speed at which it sees changes, and is smooth here, just the same as when assigned in FS. Maybe your "delta" is set incorrectly? It should be 1 for a POV hat. The value is displayed in the axis assignment tab, and it's the first number after the axis name (i.e. the first number after the first comma) in the assignment line in the INI file's [Axes] section. FSUIPC will ignore changes in the axis value less than the Delta. BTW make sure you are using a current version of FSUIPC -- 4.934 is the oldest supported for FSX. Pete Link to comment Share on other sites More sharing options...
K4bel123 Posted June 7, 2014 Author Report Share Posted June 7, 2014 (edited) Thank you Pete for your quick answer, I have tried to change the delta but it remains 0 and it still stutters. But I don´t think that this is the problem because not only my pan view but also the other controls are stuttering. It really seems to me as if FSUIPC was running at a too slow data transfer rate or it is suppressed by some other program. I also have got the newest version of FSUIPC. Edited June 7, 2014 by K4bel123 Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 7, 2014 Report Share Posted June 7, 2014 I have tried to change the delta but it remains 0 and it still stutters. But I don´t think that this is the problem because not only my pan view but also the other controls are stuttering. It really seems to me as if FSUIPC was running at a too slow data transfer rate or it is suppressed by some other program. There's nothing which makes FSUIPC "run at too slow data transfer rate". It deals with inputs from devices when inputs from devices arrive. If all of your controls are "stuttering" I think you must have a problem with your USB system. Maybe you are routing them all through an unpowered hub, or similar? Try connecting everything direct to the PC. I also have got the newest version of FSUIPC. Many folks have said that, but when they checked the version number they were well out of date. Only version numbers mean anything. "newest version" means nothing. Pete Link to comment Share on other sites More sharing options...
K4bel123 Posted June 7, 2014 Author Report Share Posted June 7, 2014 I have plugged in each device in a separate USB of the PC (directly). My FSUIPC version 4.934. Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 7, 2014 Report Share Posted June 7, 2014 I have plugged in each device in a separate USB of the PC (directly). My FSUIPC version 4.934. In that case there should be no problem. I can only think there is something wrong with the controls themselves? Pete Link to comment Share on other sites More sharing options...
K4bel123 Posted June 7, 2014 Author Report Share Posted June 7, 2014 I tried my controls with the Majestic Dash 8 Q400 and the controls worked nearly perfect. But with the default C172 and other addon aircrafts the controls will stutter. After about half a minute into the flight the other controls don´t lag anymore but when I use the hat switch, they stutter again aswell as the POV itself. I don´t think that there is something wrong with the controls themselves because when I assigned them within FSX they worked just normal. Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 7, 2014 Report Share Posted June 7, 2014 I tried my controls with the Majestic Dash 8 Q400 and the controls worked nearly perfect. But with the default C172 and other addon aircrafts the controls will stutter. After about half a minute into the flight the other controls don´t lag anymore but when I use the hat switch, they stutter again aswell as the POV itself. I don´t think that there is something wrong with the controls themselves because when I assigned them within FSX they worked just normal. There's no difference as far as FSUIPC is concerned between any of the aircraft. It simply passes through the values it receives at the rate it receives them. If you assign to the FSX controls it will be slightly longer because it will be sending controls to FSX first then intercepting them for calibration -- assuming you are also calibrating in FSUIPC? For better efficiency you should use the "direct to FSUIPC calibration" option which bypasses FSX. But that doesn't apply to Pan View which isn't a calibratable axis, and it sometimes cannot be used with add-on aircraft -- such as the PMDG 737NGX which also processes controls by intercept. Also, if you are calibrating, try to NOT use the "F" filter option, as that does make response slower as it needs to sample values to operate the filtering. The filter option is only for extreme cases of jittery actions usually caused by poor power supplies in remote parts of the world. Finally, If you find FSX assignments better (which goes against what most users find), why on Earth are you using FSUIPC for assignments? You do realise that you can assign everything in FSX and still calibrate and so on in FSUIPC? The only point of assigning in FSUIPC is if you want different controls assigned for different aircraft. Pete Link to comment Share on other sites More sharing options...
K4bel123 Posted June 7, 2014 Author Report Share Posted June 7, 2014 I really find FSUIPC much better than FSX. I originally buyed FSUIPC two days ago in order to not get the joystick disconnects on windows 8 anymore. By now I have realised that it is much more than that and I don´t want and (because of the joystick disconnects) can´t go back to making the assingments within FSX. But I would really like to find out why there is a lag when I use FSUIPC. Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 7, 2014 Report Share Posted June 7, 2014 I really find FSUIPC much better than FSX. I originally buyed FSUIPC two days ago in order to not get the joystick disconnects on windows 8 anymore. By now I have realised that it is much more than that and I don´t want and (because of the joystick disconnects) can´t go back to making the assingments within FSX. But I would really like to find out why there is a lag when I use FSUIPC. Well, I would like to know too, because i can think of no reason and it simply isn't a normal problem. Perhaps you can find your FSUIPC4.INI file (in the FSX Modules folder) and paste its contents into a message here and I'll check your settings in case there is anything strange. Pete Link to comment Share on other sites More sharing options...
K4bel123 Posted June 8, 2014 Author Report Share Posted June 8, 2014 That would be kind of you. Here it is: [General]UpdatedByVersion=4934History=6DG4MCGVTOAT1JSHBB4PQAxesWrongRange=NoTCASid=FlightTCASrange=40AxisCalibration=NoDirectAxesToCalibs=NoShowMultilineWindow=YesSuppressSingleline=NoSuppressMultilineFS=NoAxisIntercepts=NoDontResetAxes=NoInitDelay=30GetNearestAirports=YesOOMcheck=YesWeatherReadFactor=2WeatherRewriteSeconds=1CustomWeatherModify=NoSimConnectStallTime=1LuaRerunDelay=66Console=NoInitDelayDevicesToo=NoNewInterceptTextMenu=NoUseSystemTime=NoUseMidMouseBtn=YesMouseWheelMove=NoMouseWheelTrim=NoMouseWheelTrimSpeed=1JoystickTimeout=20PollGFTQ6=YesBlankDisplays=NoFixControlAccel=YesFixMachSpeedBug=NoDeleteVehiclesForAES=YesAutoScanDevices=YesVisibilityOptions=NoOneCloudLayer=NoCloudTurbulence=NoCloudIcing=NoGenerateCirrus=NoSuppressCloudTurbulence=NoMaxIce=-4MinIce=-1UpperWindGusts=NoSuppressWindTurbulence=NoSuppressWindVariance=NoWindTurbulence=NoTurbulenceRate=1.0,5.0TurbulenceDivisor=20,20,40,40SuppressAllGusts=NoMaxSurfaceWind=0WindLimitLevel=200WindDiscardLevel=400WindAjustAltitude=NoWindAjustAltitudeBy=2000SmoothBySimTime=NoWindSmoothing=NoWindSmoothness=2WindSmoothAirborneOnly=YesPressureSmoothness=0TemperatureSmoothness=0DisconnTrimForAP=NoZeroElevForAPAlt=NoThrottleSyncAll=NoWhiteMessages=NoShowPMcontrols=NoSpoilerIncrement=512MagicBattery=NoRudderSpikeRemoval=NoElevatorSpikeRemoval=NoAileronSpikeRemoval=NoReversedElevatorTrim=NoClockSync=NoClockSyncMins=5ClearWeatherDynamics=NoOwnWeatherChanges=NoTimeForSelect=4LoadFlightMenu=NoLoadPlanMenu=NoPauseAfterCrash=NoBrakeReleaseThreshold=75SaveDataWithFlights=NoZapSound=fireworkShortAircraftNameOk=SubstringUseProfiles=YesEnableMouseLook=NoDelayedMouseLookZoom=NoThrottleSyncToggle=57,8AllEngHotKey=48,8FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0SimConnectUsed=10.0.61259.0[JoyNames]AutoAssignLetters=No1=Saitek Pro Flight Yoke1.GUID={7DC78210-E8D2-11E3-8006-444553540000}0=Saitek Pro Flight Rudder Pedals0.GUID={7D0EE070-E8D2-11E3-8004-444553540000}[WideServer]WideFSenabled=Yes[buttons]ButtonRepeat=20,102=P1,1,C65567,03=P1,4,C65656,05=P1,6,C65910,06=P1,7,C65907,07=U1,4,C0,08=P1,5,C65655,09=R1,2,C65607,010=R1,3,C65615,0[AutoSave]Next=1Interval=60Files=10SaveOnGround=NoAutoSaveEnabled=No[GPSout]GPSoutEnabled=NoPort=COM1Speed=4800Interval=2000PosTo6Decimal=NoSimModeIndicator=NoSentences=[GPSout2]GPSoutEnabled=NoPort=<none set>Speed=4800Interval=2000PosTo6Decimal=NoSimModeIndicator=NoSentences=[sounds]Path=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Sound\Device1=Primärer SoundtreiberDevice2=Lautsprecher (Realtek High Definition Audio)[Axes]RangeRepeatRate=100=1X,256,D,1,0,0,01=1Y,256,D,2,0,0,02=1Z,256,D,4,0,0,0[JoystickCalibration]AllowSuppressForPFCquad=YesExcludeThrottleSet=YesExcludeMixtureSet=YesExcludePropPitchSet=YesSepRevsJetsOnly=NoApplyHeloTrim=NoUseAxisControlsForNRZ=NoFlapsSetControl=0FlapDetents=NoReverserControl=66292Reverser1Control=66422Reverser2Control=66425Reverser3Control=66428Reverser4Control=66431MaxThrottleForReverser=256AileronTrimControl=66731RudderTrimControl=66732CowlFlaps1Control=66162CowlFlaps2Control=66163CowlFlaps3Control=66164CowlFlaps4Control=66165SteeringTillerControl=0MaxSteerSpeed=60Throttle=-16380,16380Throttle1=-16384,-13523,512,16383/8Aileron=-16380,-2152,0,16380/8Elevator=-16380,-512,512,16380Throttle2=-16384,-13133,512,16383/8[Profile.QW757]1=QWSim C32A Air-Force 2 WV[Axes.QW757]RangeRepeatRate=100=0X,256,D,7,0,0,01=0Y,256,D,8,0,0,02=0R,256,D,3,0,0,03=1X,256,D,1,0,0,04=1Y,256,D,2,0,0,05=1Z,256,D,22,0,0,06=1V,256,D,4,0,0,07=1P,0,F,66416,0,0,0[JoystickCalibration.QW757]AllowSuppressForPFCquad=YesExcludeThrottleSet=YesExcludeMixtureSet=YesExcludePropPitchSet=YesSepRevsJetsOnly=NoApplyHeloTrim=NoUseAxisControlsForNRZ=NoFlapsSetControl=0FlapDetents=NoReverserControl=66292Reverser1Control=66422Reverser2Control=66425Reverser3Control=66428Reverser4Control=66431MaxThrottleForReverser=256AileronTrimControl=66731RudderTrimControl=66732CowlFlaps1Control=66162CowlFlaps2Control=66163CowlFlaps3Control=66164CowlFlaps4Control=66165SteeringTillerControl=0MaxSteerSpeed=60Aileron=-16384,0,0,16256Elevator=-16384,-96,0,16288Throttle=-16384,16383Throttle1=-16384,-13523,512,16383Throttle2=-16384,-13133,512,16383LeftBrake=-16383,16384/16RightBrake=-16383,16384/16Rudder=-16384,0,0,16256Spoilers=-16383,-16128,-14464,16384/16[buttons.QW757]0=P1,15,C65752,01=P1,16,C65853,02=P1,0,C66654,07=P1,6,C65910,08=P1,7,C65912,010=R1,22,C66634,011=R1,2,C65607,012=R1,3,C65615,013=P1,0,C66654,0[Profile.Duke B60]1=RealAir Beech Duke V2 GREAL Winglets[buttons.Duke B60]0=P1,15,C65752,01=P1,16,C65853,02=P1,0,C66654,07=P1,6,C65910,08=P1,7,C65912,010=R1,22,C66634,011=R1,2,C65607,012=R1,3,C65615,0[Axes.Duke B60]RangeRepeatRate=100=0X,256,D,7,0,0,01=0Y,256,D,8,0,0,02=0R,256,D,3,0,0,03=1X,256,D,1,0,0,04=1Y,256,D,2,0,0,05=1Z,256,D,4,0,0,06=1V,256,D,5,0,0,07=1P,0,F,66416,0,0,0[JoystickCalibration.Duke B60]AllowSuppressForPFCquad=YesExcludeThrottleSet=YesExcludeMixtureSet=YesExcludePropPitchSet=YesSepRevsJetsOnly=NoApplyHeloTrim=NoUseAxisControlsForNRZ=NoFlapsSetControl=0FlapDetents=NoReverserControl=66292Reverser1Control=66422Reverser2Control=66425Reverser3Control=66428Reverser4Control=66431MaxThrottleForReverser=256AileronTrimControl=66731RudderTrimControl=66732CowlFlaps1Control=66162CowlFlaps2Control=66163CowlFlaps3Control=66164CowlFlaps4Control=66165SteeringTillerControl=0MaxSteerSpeed=60Aileron=-16384,0,0,16256Elevator=-16384,-96,0,16288Rudder=-16254,64,64,16383Throttle=-16384,16383LeftBrake=-16384,16383/24RightBrake=-16384,16383/24Throttle1=-16384,-13523,512,16383/8Throttle2=-16384,-13133,512,16383/8Spoilers=-16383,16384/16[Profile.Dash 8 Q400]1=MJC8Q400_AUB[buttons.Dash 8 Q400]0=P1,15,C65752,02=P1,0,C66654,07=P1,6,C65910,08=P1,7,C65907,010=R1,22,C66634,011=R1,2,C65607,012=R1,3,C65615,013=P1,0,C66654,014=P1,1,C65567,015=R1,5,C65655,016=R1,4,C65656,017=P1,20,C65602,0[Axes.Dash 8 Q400]RangeRepeatRate=100=0R,256,D,3,0,0,01=1X,256,D,1,0,0,02=1Y,256,D,2,0,0,03=1Z,256,D,4,0,0,04=1V,256,D,5,0,0,05=1P,0,F,66416,0,0,0[JoystickCalibration.Dash 8 Q400]AllowSuppressForPFCquad=YesExcludeThrottleSet=YesExcludeMixtureSet=YesExcludePropPitchSet=YesSepRevsJetsOnly=NoApplyHeloTrim=NoUseAxisControlsForNRZ=NoFlapsSetControl=0FlapDetents=NoReverserControl=66292Reverser1Control=66422Reverser2Control=66425Reverser3Control=66428Reverser4Control=66431MaxThrottleForReverser=256AileronTrimControl=66731RudderTrimControl=66732CowlFlaps1Control=66162CowlFlaps2Control=66163CowlFlaps3Control=66164CowlFlaps4Control=66165SteeringTillerControl=0MaxSteerSpeed=60Aileron=-16384,0,0,16383Elevator=-16223,0,0,16383Rudder=-16384,0,0,16383Throttle=-16384,16383LeftBrake=-16384,16383/24RightBrake=-16384,16383/24Throttle1=-16384,-13523,512,16383/8Throttle2=-16384,-13133,512,16383/8Spoilers=-16383,16384/16[Profile.C172]1=Cessna Skyhawk 172SP Paint1[buttons.C172]0=P1,15,C65752,02=P1,0,C66654,07=R1,4,C65656,08=R1,5,C65655,010=R1,22,C66634,011=R1,2,C65607,012=R1,3,C65615,013=P1,1,C65567,0[Axes.C172]RangeRepeatRate=100=0X,256,D,7,0,0,01=0Y,256,D,8,0,0,02=0R,256,D,3,0,0,03=1X,256,D,1,0,0,04=1Y,256,D,2,0,0,05=1Z,256,D,4,0,0,06=1V,256,D,6,0,0,07=1P,0,F,66416,0,0,0[JoystickCalibration.C172]AllowSuppressForPFCquad=YesExcludeThrottleSet=YesExcludeMixtureSet=YesExcludePropPitchSet=YesSepRevsJetsOnly=NoApplyHeloTrim=NoUseAxisControlsForNRZ=NoFlapsSetControl=0FlapDetents=NoReverserControl=66292Reverser1Control=66422Reverser2Control=66425Reverser3Control=66428Reverser4Control=66431MaxThrottleForReverser=256AileronTrimControl=66731RudderTrimControl=66732CowlFlaps1Control=66162CowlFlaps2Control=66163CowlFlaps3Control=66164CowlFlaps4Control=66165SteeringTillerControl=0MaxSteerSpeed=60Aileron=-16384,0,0,16256Elevator=-16384,-96,0,16288Rudder=-16254,64,64,16383Throttle=-16384,16383LeftBrake=-16384,16383/16RightBrake=-16384,16383/16Throttle1=-16384,-13523,512,16383/8Throttle2=-16384,-13133,512,16383/8Spoilers=-16383,16384/16 Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 8, 2014 Report Share Posted June 8, 2014 Not a lot very wrong there. But there are a few oddities. Looking at calibrations, for instance, in all cases you have Throttle=-16384,16383Throttle1=-16384,-13523,512,16383/8Throttle2=-16384,-13133,512,16383/8 You don't want both the generic throttle and the two separate throttles calibrated. I see from your axis assignments you only have the generic throttle (i.e. one lever) assigned and it isn't shown as being mapped to the two separate throttles, so if i were you I'd delete all of the "Throttle1=" and "Throttle2=" lines in each Calibration section. On the other hand, if you'd intended to map the generic throttle to the separate throttles, so you could have a reverse zone, then you need to enable that mapping after by pressing the 'reset' button on the generic throttle on page 1. If you do retain the separate throttle calibrations, the /8 on those lines means that you have the Filter option enabled on them. As I said earlier you don't want that unless you are happy with the slow response it might give. Filtering is very rarely needed on any modern devices with decent power supplies. (The option was originally put in to help a user with a very variable power supply somewhere in the countryside in Asia). Additionally, on those calibrations, you do seem to have a very large idle zone. using up pretty much half of your entire throttle movement. Why is that? You have filtering on the toe brakes as well ....? Also, for ALL of your calibrations you don't really seem to have followed the advice (the numbered steps) in the user guide. The minimum and maximum values for every axis are pretty much the actual minimum and maximum you can possible get. This leaves no room for minor variations which are bound to occur even in the best controls (which I'm afraid Saitek are a long way from). I suggest you get out the FSUIPC User Guide and re-calibrate all your axes carefully, following the steps as advised in the Calibration chapter. I see nothing which would particularly make the operation of the main control axes -- aileron, elevator, rudder, at all "jerky" -- unless you do have dual assignments after all. Do you actually disable controllers in FSX? It isn't usually suffiicent to just delete the assignments, as FSX has the habit of remaking them. Pete Link to comment Share on other sites More sharing options...
K4bel123 Posted June 8, 2014 Author Report Share Posted June 8, 2014 Where can I download the User Guide? I don´t think that it´s a hardware problem or something else. Maybe FSUIPC doesn´t get enough CPU power in my other aircrafts than the Majestic Dash 8 Q400. Is it possible that FSUIPC is trying to do something else in the background e.g. connecting to the internet in order to check the validation of my FSUIPC key, because I´ve got a nicely working joystick, a new computer with good USB connections and FSX is running nicely. I cannot imagine an other problem. Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 8, 2014 Report Share Posted June 8, 2014 Where can I download the User Guide? You've never even looked at the FSUIPC documentation? The ZIP you downloaded containing FSUIPC includes an Installation and Registration document. it tells you exactly WHAT gets installed, AND where it is! Did you never even bother to look at that? All the documentation and lots of extra stuff is installed in a folder mysteriously called "FSUIPC Documents", right next to FSUIPC itself in the Modules folder. I don´t think that it´s a hardware problem or something else. Maybe FSUIPC doesn´t get enough CPU power in my other aircrafts than the Majestic Dash 8 Q400. Is it possible that FSUIPC is trying to do something else in the background e.g. connecting to the internet in order to check the validation of my FSUIPC key, because I´ve got a nicely working joystick, a new computer with good USB connections and FSX is running nicely. I cannot imagine an other problem. FSUIPC is doing nothing else. There is no code in FSUIPC at all to connect to anything except FS itself. There is no internet connection whatsoever. It busies itself populating the offsets for client applications to use, and responding to their requests. That's it's no.1 task, it's prime reason for being, dating right back to FS98 days. The joystick calibration came later, then button and key programming , and then axis assignment, which was added to allow folks to have different axes for different aircraft types -- eg sidesticks for Airbus, yokes for Boeing, G-sticks for helicopters, and so on. I think you must have something wrong. If you really have disabled controllers in FS, and don't have the Saitek software running ands spoiling things, then I can only think you have a corrupt installation of FSX. The facilities you are using are used by hundreds if not thousands of users without problems, I've no idea what you have going on there. Sorry. BTW, judging from your INI file you have no good reason to make axis assignments in FSUIPC in any case, so I still don't know why you are doing that. The axis assignment facilities were a late addition to FSUIPC. As I said before, you can still calibrate in FSUIPC if you wish, no matter where you assign. But you ought to make a better job of it, following the instructions, as I said, or that is also really a bit of a wast of time too. Regards Pete Link to comment Share on other sites More sharing options...
K4bel123 Posted June 9, 2014 Author Report Share Posted June 9, 2014 I have now reinstalled fsx and fsuipc and set up everything the same way as described in the manual but although I haven´t got any addons installed, all controls stutter the same way as before. Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 9, 2014 Report Share Posted June 9, 2014 I have now reinstalled fsx and fsuipc and set up everything the same way as described in the manual but although I haven´t got any addons installed, all controls stutter the same way as before. I'm sorry, but I am at a loss to understand this. Assuming you have controllers disabled in FS (which otherwise have always been the cause), it happens no where else and has never been reported at all before you, so i can't really help at all. I suggest you assign in FS -- in any case, judging from your posted settings, you aren't really utilising the axis assignment facilities in FSUIPC for anything useful at all. You would accomplish the same thing with FS assignment, and, according to you, with better performance. Pete Link to comment Share on other sites More sharing options...
K4bel123 Posted June 9, 2014 Author Report Share Posted June 9, 2014 But the problem is that when I assign it in FS my joystick disconnects after some time because I have got Windows 8.1. Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 9, 2014 Report Share Posted June 9, 2014 But the problem is that when I assign it in FS my joystick disconnects after some time because I have got Windows 8.1. Hmm. I'm wondering then if Win8.1 is the reson for the problem in the first place. One thing to check for -- make sure there are no extra DirectX DLL modules in the FSX folder. Folks have had problems with FSUIPC not even being able to connect to devices because of some add-ons installing extra DX8 modules. Oh, but you said you'd not added anything yet? A "virgin" FSX apart from FSUIPC? I really don't know what to advise. FSUIPC uses the standard Windows DX8 API calls, same as FSX. I really don't know why FSX disconnects and FSUIPC doesn't -- presumably something slightly different in the way the calls are made or timed. But it is the same interface, and the results should be the same. There is nothing in FS or in FSUIPC which will make things jitter or stutter assuming only one of them is reading the values. It should be perfectly smooth. I'll do some checks here and see if I can add anything to tell me what is going on on your system. Pete Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 9, 2014 Report Share Posted June 9, 2014 I'll do some checks here and see if I can add anything to tell me what is going on on your system. I've changed the way the polling limiter works inside FSUIPC to see if it helps. this is a device to ensure smooth polling without adversely affecting FS performance. Over the years it has become quite complicated to achieve such harmony, but i think I've simplified it somewhat and it may well be better on your system. I've tested the changes here and they make little difference on my system, but try it on yours and let me know: Download FSUIPC4934cTest.zip, and placed the DLL in the FSX Modules folder, replacing your 4.934. Regards Pete Link to comment Share on other sites More sharing options...
K4bel123 Posted June 9, 2014 Author Report Share Posted June 9, 2014 Pete, I think I cannot stress enough how happy I am right now. It seems to work (really nice). I just wanted to reset my pc and send it back. I´m gonna test this out a bit more but I think that you´ve saved me from giving back my great pc. Thank you very much. BTW, what did actually cause this problem in the DLL? With best regards, Julius Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 9, 2014 Report Share Posted June 9, 2014 BTW, what did actually cause this problem in the DLL? I don't really know. I'm a little surprised it's made such a difference, as it's about the same here. As i say, I just simplified the way in which it works out how and when to poll the joysticks. it can't just loop as fast as it can because it needs to let FS do other things. Even in a multi-processor PC like everyone has now, you can't let one thread take 100% of the time in its processor, it has to allow others in too. I just changed the way it did that, as an experiment really. Anyway, glad it worked okay! Pete Link to comment Share on other sites More sharing options...
K4bel123 Posted June 10, 2014 Author Report Share Posted June 10, 2014 I have tested it now but it only seems to work sometimes. Also I get a huge drop in fps (prior to the new DLL: about 30fps at Munich @max graphics; now: 18-25 fps at Munich @max graphics). Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 10, 2014 Report Share Posted June 10, 2014 I have tested it now but it only seems to work sometimes. Also I get a huge drop in fps (prior to the new DLL: about 30fps at Munich @max graphics; now: 18-25 fps at Munich @max graphics). Don't know why it "only seems to work sometimes", as it isn't going to be changing the way it operates, but a small drop in fps would be something I would be afraid of with any changes to the way it was setup. I get neither problem here with a virgin FSX install -- no measurable difference in frame rates at all, but nor in axis "smoothness", But then I am using Windows 7. Are you restricting FSX to only using one core on your PC? I really can't see how a minor change in one thread can have anything but a miniscule affect on FSX performance. Anyway, i'll discard those changes. I'll upload one more version, something less drastic than the last. After that I can only think that your problem just isn't soluble. Pete Link to comment Share on other sites More sharing options...
K4bel123 Posted June 10, 2014 Author Report Share Posted June 10, 2014 I run FSX on multiple cores. I have tried using my Saitek yoke on my laptop using FSUIPC and I tried some other joystick both on my PC and my laptop. I always get those lags. So I think that neither my yoke nor my PC are the problem, but that there is some program that somehow intereferes with FSUIPC. I´ll try to figure that out but I don´t think that I will succeed. Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 10, 2014 Report Share Posted June 10, 2014 Anyway, i'll discard those changes. I'll upload one more version, something less drastic than the last. Try FSUIPC4934dTest.zip. It is somewhat between the original and the last one. You can also vary its polling rate yourself, to try to get better than the default. The parameter PollInterval=10 in the main [Axes] section tells FSUIPC to poll all axes at 10 mSec intervals (i.e. 100 times per second). That's always been the default. You can try faster polling (minimum value here is 5 mSecs, or 200 times per second), but you may be better to try any higher value to poll less frequently. On my test system, '5' definitely impacts frame rates, but I see no difference in axis smoothness nor frame rates between, for example, 10 and 20 (100 pps and 50 pps). I think FS's poll rate is a lot slower, around 20 pps or less (a value of 40 or 50 here). BTW there is also a separate PollInterval parameter in the main [buttons] section, which controls the button polling rate, defaulting at 25 mSecs (=40 pps). You can change these values, to experiment, whilst FS is running Just edit the INI file, then go to the FSUIPC Options, and tell it to reload axes (a button on the Axes tab) to force it to re-read all of the [Axes] sections. Similar method for buttons. After this i've run out of ideas I'm afraid. Pete Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now