Jump to content
The simFlight Network Forums

Dumpcore

Members
  • Posts

    14
  • Joined

  • Last visited

Everything posted by Dumpcore

  1. After testing P3D V1, the problem persists. It's related wih my system, not a FSUIPC or P3D V2 issue. ;-)
  2. I'll do an additional test installing again P3D V1, and post the final result ;-) Probably something has changed in my system, not a P3D V2 problem.
  3. Finally -and after a lot of testing- I have found a fix. I have set this option in FSUIPC.INI file: AutoScanDevices=No Now, FSUIPC always recognizes my hardware and its settings, no matter if I plug my joy before of after the loading of FSUIPC :D From the documentation: --- AutoScanDevices: This is normally set to 'Yes', to make FSUIPC4 automatically re-scan all connected DirectInput devices each time the Options dialogue is entered. This makes sure devices newly connected are seen. If you don't want this to occur, set it to 'No'. The devices will then only be re-scanned if you press the 'reload' button in either the Axes or Button assignments tabs. If you never want it to rescan devices (for example, in Windows 8 there seems to be problems doing this), then set this parameter to 'Never' instead. Note that unless disabled here, FSUIPC4 automatically re-scans connections each time it detects any HID USB device connecting. This may help get over problems some folks have with badly behaving devices or USB ports, albeit with a noticeable pause or hesitation (which actually occurs even without any action by FSUIPC to re-connect). A message is logged when this occurs. Note that this doesn't go so far as to allow reconnecting to different USB ports during flight modes. --- Thanks for the support.
  4. Thanks for the clarification. After some additional tests, I have discovered that if I plug and unplug joy 1 twice, FSUIPC recognizes correctly my problematic hardware :razz:
  5. Pete, I only say that sometimes FSUIPC recognizes my joysticks and sometimes not, and I don't know why, and that never have had such problem until P3D V2. I am not doing nothing special with FSUIPC, after several years using your software. All my axes and buttons are assigned with FSUIPC, not in P3D. I understand that sometimes is very difficult to resolve such problems, but don't think users don't spend a lot of time trying to recreate their problems to find a valid solution. I'll do more tests, trying to know exactly what is happening in my system.
  6. After some testing, something in FSUIPC isn't working well. First of all, my software system specs: Prepar3D V2 FSUIPC 4927a Windows 7 X64 Pro, up to date with the latest updates Saitek X52 Pro (joy 0), up to date with the latest drivers. No profile loaded at startup Saitek Pro Flight Rudder Pedals (joy 1), up to date with the latest drivers. No profile loaded at startup I have backed my INI file, creating a new and fresh one from FSUIPC. Now, I have set a very simple configuration with my axes: [JoyNames] AutoAssignLetters=No 0=Saitek X52 Pro Flight Controller 0.GUID={2A5298C0-EBAA-11E2-8001-444553540000} 1=Saitek Pro Flight Rudder Pedals 1.GUID={2A5298C0-EBAA-11E2-8002-444553540000} [Axes] RangeRepeatRate=10 0=0X,256,D,1,0,0,0 1=0Y,256,D,2,0,0,0 2=0Z,256,D,4,0,0,0 3=0U,256,D,6,0,0,0 4=0V,256,D,5,0,0,0 5=0S,256,D,23,0,0,0 6=1X,256,D,7,0,0,0 7=1Y,256,D,8,0,0,0 8=1R,256,D,3,0,0,0 I can speak about two possible scenarios: 1) If I connect my hardware before starting P3D, FSUIPC loads my axes correctly. 2) If I connect my hardware after starting P3D, FSUIPC loads my axes correctly only for the JoyName 0, but not for the JoyName 1. If I push the button "Reload axes" inside FSUIPC axes menu, JoyName 1 still doesn't work (FSUIPC doesn't recognize JoyName 1). The general options of the INI file are: [General] UpdatedByVersion=4927a History=AONXYJW2M4O777I9GICX1 InitDelayDevicesToo=No InterceptTextMenu=Yes UseSystemTime=No UseMidMouseBtn=Yes MouseWheelMove=No MouseWheelTrim=No MouseWheelTrimSpeed=1 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No FixControlAccel=No FixMachSpeedBug=Yes DeleteVehiclesForAES=Yes AutoScanDevices=Yes VisibilityOptions=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=No SuppressCloudTurbulence=No MaxIce=-4 MinIce=-4 UpperWindGusts=No SuppressWindTurbulence=No SuppressWindVariance=No WindTurbulence=No TurbulenceRate=1.0,5.0 TurbulenceDivisor=20,20,40,40 SuppressAllGusts=No MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 SmoothBySimTime=No WindSmoothing=No WindSmoothness=2 WindSmoothAirborneOnly=Yes PressureSmoothness=0 TemperatureSmoothness=0 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=Yes ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=Yes RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=No LoadPlanMenu=No PauseAfterCrash=Yes BrakeReleaseThreshold=75 SaveDataWithFlights=No ZapSound=firework ShortAircraftNameOk=Yes UseProfiles=Yes EnableMouseLook=No AxesWrongRange=No TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No DontResetAxes=No InitDelay=0 GetNearestAirports=Yes OOMcheck=Yes WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 InitialStallTime=10 NormalStallTime=1 LuaRerunDelay=66 Console=No SetSimSpeedX1=76,24 ForceWeatherKey=79,24 PatchSIM1friction=Yes P3Dv2Fiddles=Yes UseASEweather=No FSVersionUsed="Lockheed Martin® Prepar3D® v2",2.0.9448.0 SimConnectUsed=2.0.0.0 I have never had this problem with FSX or P3D V1. I don't know if it is a problem of Windows 7, P3D V2, Saitek drivers, or FSUIPC.
  7. I am doing more testing about this problem. I'll post when I have clear where is the issue. Thanks. Update: the problem is associated with my Saitek X52 profile. I don't know exactly what has happened, but now it works well. If I find something interesting, I'll post here :razz:
  8. Hi, I am using P3D V2 and the latest version of FSUIPC (4927a). With P3D V2 I have had always the same problem with FSUIPC. If I connect the joystick when the simulator is running, and then I open the FSUIPC menu and reload the axis assignments, FSUIPC doesn't load the saved assignments. The only solution is to close P3D, disconnect the joy, connect again, and then start again the simulator. I have never had this issue with FSX or P3D 1.X. I am using Windows 7 X64. Thanks.
  9. OK, Only for better compatibility with other addons, and to avoid such ugly messages. I'll look that Lua example. Thanks for your quick support
  10. I am using FSUIPC with Prepar3D 1.4. I have noticed that some addons designed for FSX report a FS unknow version from FSUIPC when using Prepar3D, but such addons work perfectly with P3D. Should be possible to add an option in FSUIPC to report a FS specific version for some applications? I ask, but of course, I don't have any idea about this. Thanks.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.