Jump to content
The simFlight Network Forums

aceridgey

Members
  • Posts

    21
  • Joined

  • Last visited

Posts posted by aceridgey

  1. 8 minutes ago, Pete Dowson said:

    Not in FSUIPC, but I can't say P3D hasn't changed as I don't know.

    I can't really help in any case without details. Please find the FSUIPC4.LOG file (in the P3D Modules folder) and paste its contents here.

    This assumes you have a plug-in called "DynamicFriction.lua" in the Modules folder. Have you?

    Pete

     

    I have got that file in the modules folder yes..

     

    Is this the log?

     

    ********* FSUIPC4, Version 4.949h by Pete Dowson *********
    Prepar3D.exe version = 3.3.5.17625
    Reading options from "D:\Prepar3D v3\Modules\FSUIPC4.ini"
    Running inside Prepar3D v3 on Windows 8.0 (it's actually windows 10)
    Module base=1F100000
    User Name="Alex Ridge"
    User Addr="deleted"
    FSUIPC4 Key is provided
    WIDEFS7 not user registered, or expired
          156 System time = 27/08/2016 08:43:55
          156 FLT path = "C:\Users\Alex\Documents\Prepar3D v3 Files\"
          156 ------ Module Version Check ------
          156        acontain.dll: 3.3.5.17625
          156             api.dll: 3.3.5.17625
          156        controls.dll: 3.3.5.17625
          156      fs-traffic.dll: 3.3.5.17625
          156             G3D.dll: 3.3.5.17625
          156        language.dll: 3.3.5.17625
          156            sim1.dll: 3.3.5.17625
          156        visualfx.dll: 3.3.5.17625
          156         weather.dll: 3.3.5.17625
          156          window.dll: 3.3.5.17625
          156 ----------------------------------
          156 Trying D:\Prepar3D v3\Modules\SimConnectP3D2.dll
          156 Found it: trying to connect
          156 FS path = "D:\Prepar3D v3\"
          281 ---------------------- Joystick Device Scan -----------------------
          281 Product= Saitek X52 Pro Flight Control System
          281    Manufacturer= Saitek
          281    Vendor=06A3, Product=0762 (Version 1.35)
          281    Serial Number= Saitek
          281 -------------------------------------------------------------------
          281 LogOptions=00000000 00000001
          281 -------------------------------------------------------------------
          281 ------ Setting the hooks and direct calls into the simulator ------
          281 --- CONTROLS timer memory location obtained ok
          281 ### Failed to obtain SIM1 Frictions access: no frictions facilities available!
          281     Reason 6: SIM1 base=613D0000
          281     FrictionAddr=614F7218 contains 00000000
          281     BrakingAddr=614F84D8 contains 3F0CCCCD
          281 --- FS Controls Table located ok
          281 --- Installed Mouse Macro hooks ok.
          281 --- Wind smoothing fix is installed
          281 --- All links okay (except older global weather setting method)
          281 -------------------------------------------------------------------
          297 SimConnect_Open succeeded: waiting to check version okay
          297 Trying to use SimConnect Prepar3D
        54859 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.3.3.3 (SimConnect: 3.3.0.0)
        54859 Initialising SimConnect data requests now
        54859 FSUIPC Menu entry added
        54875 C:\Users\Alex\Documents\Prepar3D v3 Files\Cub Default.fxml
        54875 D:\Prepar3D v3\SimObjects\Airplanes\Piper_J3Cub\Piper_J3Cub.air
       297594 D:\Prepar3D v3\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.air
       329765 System time = 27/08/2016 08:49:25, Simulator time = 08:48:47 (07:48Z)
       329781 Aircraft="PMDG 737-800NGX Norshuttle LN-DYJ"
       335765 Starting everything now ...
       335797 Run: "C:\Program Files (x86)\EZCA\EZCA.exe"
       335859 ASN active function link set
       335859 Ready for ASN WX radar
       337125 Weather Mode now = Theme
       340812 Advanced Weather Interface Enabled
      1818922 Sim stopped: average frame rate for last 1422 secs = 55.2 fps
      2250890 Sim stopped: average frame rate for last 406 secs = 56.5 fps
      2318156 Sim stopped: average frame rate for last 37 secs = 53.7 fps
     

  2. You are only logging Axis inputs -- the flooding I was talking about tend to be the other events.

     

    However, I don't know what you are doing with that spoiler axis. Do you keep moving it very very fast so somehow resulting in alternate larger numbers and zero (???), or is the axis faulty, or is it the PMDG aircraft trying to set it to zero against your wishes?

     

    If I were you I'd test things on a default aircraft before worrying about your axes on a PMDG one.

     

    Pete

     

    Hi there,

     

    No idea what is happening with the spoiler axis, it is set to a axis wheel and is fixed. 

     

    Other aircraft don't seem to have this issue.

     

    Alex

  3. Log file

     

    ********* FSUIPC4, Version 4.934 by Pete Dowson *********
    User Name="Alex Ridge"
    User Addr= removed for forum post.
    FSUIPC4 Key is provided
    WIDEFS7 not user registered, or expired
        84646 System time = 05/07/2014 11:47:28, Simulator time = 12:55:08 (11:55Z)
    [Continuation log requested by user]
    Running inside FSX on Windows 7
    Module base=50A50000
        84646 LogOptions changed, now 10000000 00000001
        84974 Advanced Weather Interface Enabled
        92556 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5620 (0x000015f4) SPOILERS_SET
        93024 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 0 (0x00000000) SPOILERS_SET
        93320 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5620 (0x000015f4) SPOILERS_SET
        93960 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 0 (0x00000000) SPOILERS_SET
        94038 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5620 (0x000015f4) SPOILERS_SET
        94209 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5621 (0x000015f5) SPOILERS_SET
        94272 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5994 (0x0000176a) SPOILERS_SET
        94334 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 6637 (0x000019ed) SPOILERS_SET
        94443 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 7360 (0x00001cc0) SPOILERS_SET
        94506 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 7667 (0x00001df3) SPOILERS_SET
        94568 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 7909 (0x00001ee5) SPOILERS_SET
        94646 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 7966 (0x00001f1e) SPOILERS_SET
        94740 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 7438 (0x00001d0e) SPOILERS_SET
        94802 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 7059 (0x00001b93) SPOILERS_SET
        94880 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 6726 (0x00001a46) SPOILERS_SET
        94974 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 6136 (0x000017f8) SPOILERS_SET
        95052 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5803 (0x000016ab) SPOILERS_SET
        95114 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5620 (0x000015f4) SPOILERS_SET
        95442 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5842 (0x000016d2) SPOILERS_SET
        95520 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5727 (0x0000165f) SPOILERS_SET
        95582 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5620 (0x000015f4) SPOILERS_SET
        95894 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 0 (0x00000000) SPOILERS_SET
       104568 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5620 (0x000015f4) SPOILERS_SET
       104802 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 0 (0x00000000) SPOILERS_SET
       105348 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5620 (0x000015f4) SPOILERS_SET
       105519 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 0 (0x00000000) SPOILERS_SET
       106128 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5620 (0x000015f4) SPOILERS_SET
       106284 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 0 (0x00000000) SPOILERS_SET
       106892 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5620 (0x000015f4) SPOILERS_SET
       107235 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 0 (0x00000000) SPOILERS_SET
       107594 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5620 (0x000015f4) SPOILERS_SET
       107672 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5803 (0x000016ab) SPOILERS_SET
       107766 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 6110 (0x000017de) SPOILERS_SET
       107828 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 6268 (0x0000187c) SPOILERS_SET
       107906 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5980 (0x0000175c) SPOILERS_SET
       108000 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5620 (0x000015f4) SPOILERS_SET
       108515 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 0 (0x00000000) SPOILERS_SET
       108671 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5620 (0x000015f4) SPOILERS_SET
       108842 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 6171 (0x0000181b) SPOILERS_SET
       108920 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 6397 (0x000018fd) SPOILERS_SET
       108983 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 6082 (0x000017c2) SPOILERS_SET
       109076 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5620 (0x000015f4) SPOILERS_SET
       109310 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 0 (0x00000000) SPOILERS_SET
       113678 Sim stopped: average frame rate for last 29 secs = 28.8 fps
       117968 LogOptions changed, now 00000000 00000001
  4. Assuming you are talking about reactions in a fighter or stunt aircraft, where you expect and need an immediate response, and not in an airliner which has natural inertia in all axes and even throttle results on the engines, there are only two causes of delays I can think of, and they should usually be barely noticeable.

     

    The first is using the Filter option in FSUIPC's calibration. That needs a sequence of inputs to formulate the next result going into FS, and can in some circumstances and controls produce a slight lag. The filter option is only suitable for drastic control instability, of the type usually caused by bad power supplies.

     

    The second is caused by having the Delta value, in the axis assignments tab, set too low. The default of 512 or 256 should be good for a properly calibrated (in Windows) axis. If it is too low you will get multiple small changes flooding the message queue.

     

    There is actually also a third possibility I've just thought of and that is where add-on aircraft (or other programs, actually) are flooding the message queues with commands too. I've noticed that some of PMDG's aircraft repeatedly send the same controls over and over for no reason apparent to me. To see if this sort of thing is responsible, enable Event logging in FSUIPC's logging page and take a look at the log generated.

     

    Pete

     

    Hi Pete, hope you're well and thank you for the reply.

     

     

    I am indeed talking about PMDG aircraft where I am physically looking at the Yoke and moving my joystick at home. I will enable the log reporting and get back to you shortly

     

    Alex

  5. Well, it's lucky that through an oversight some of the axes assigned "direct to calibration" are let through even if calibration has not been set. That doesn't happen on all axes, and didn't used to happen on FS9. I haven't fixed it for fear of messing installations up like yours where althoguh you assigned "to calibration" you never actually went to the calibration page and enabled it.

     

     

    Best to delete the [Axes] line for that if you are not using it, or it could interfere. It's the one to D,25.

     

     

    Yes, of course. You've not read much of the supplied documentation, then? Miscellaneous page: there are mouse move, mouse look and mouse trim options. Yours is mouse look, and you can do it with the middle mouse button held down, much better than the space bar. It applies to all views as far as I know, at least in virtual cockpit mode.

     

    Regards

    Pete

     

    I also use EZDOK which goes on the basis of a middle mouse button. I assume it will be ok for space bar too? Is it called 'Mouse Move'?

     

    Thanks again Pete, you're a superstar of the fs world! 

     

    Cheers once again

  6. Spoilers are set to an axis on my throttle ont he x52. I will do a proper calibration but to be honest, they are not too far off the default.

     

    Reverser I tried setting it to an axis on the throttle, now it's just a button with repeat if hold.

     

     

    I'll get back to you on that,

     

    p.s the default FSX controls allowed one to pan in spot view by holding the space bar and then moving the mouse. Is it this possible to set up through FSUIPC?

     

    Alex

  7. Updated settings 

     

    (Working now with reinstall of latest version)

     

     
    [JoystickCalibration]
    AllowSuppressForPFCquad=Yes
    ExcludeThrottleSet=Yes
    ExcludeMixtureSet=Yes
    ExcludePropPitchSet=Yes
    SepRevsJetsOnly=No
    ApplyHeloTrim=No
    UseAxisControlsForNRZ=No
    FlapsSetControl=0
    FlapDetents=No
    ReverserControl=66292
    Reverser1Control=66422
    Reverser2Control=66425
    Reverser3Control=66428
    Reverser4Control=66431
    MaxThrottleForReverser=256
    AileronTrimControl=66731
    RudderTrimControl=66732
    CowlFlaps1Control=66162
    CowlFlaps2Control=66163
    CowlFlaps3Control=66164
    CowlFlaps4Control=66165
    SteeringTillerControl=0
    MaxSteerSpeed=60
    Elevator=-16380,-512,512,16380
    Rudder=-16380,-512,512,16380
    Throttle=-16380,16380
    Aileron=-16380,-512,512,16380
    SlopeAileron=3
    SlopeElevator=3
     
    [Axes]
    RangeRepeatRate=10
    0=1X,256,D,1,0,0,0
    1=1Y,256,D,2,0,0,0
    2=1Z,256,D,4,0,0,0
    3=1R,256,D,3,0,0,0
    4=1V,256,D,22,0,0,0
    5=1S,256,D,25,0,0,0
  8.  

    Yes, I assumed you were using FSUIPC's axis assignment from your original message, but there are several ways of assigning everything there and different controls you can use.  Hence my question.

     

     

    That's the INI file, with your settings. did you try logging, as I suggested?

     

    First off, your FSUIPC is out of date. Version 4.920 is no longer supported.. You need to update.

     

    Second, you have very little actually assigned in FSUIPC: the only axes you have assigned are listed in your INI file:

     

    [Axes]

    0=1Z,256,D,4,0,0,0
    1=1V,256,D,22,0,0,0
    2=1S,256,D,25,0,0,0

     

    These are, respectively, Throttle, Spoilers and all-engine Reverser. All are assigned "Direct to FSUIPC calibration", but these are your calibrations:

     

    Elevator=-16380,-512,512,16380

    Rudder=-16380,-512,512,16380
    Throttle=-16380,16380
    Aileron=-16380,-512,512,16380
     
    which include only "Throttle", making the other two assignments pretty useless. Furthermore, these calibration values are the default values set by FSUIPC ready for you to adjust to suit your particular controls. It seems you've not yet actually processed througfh the necessary and documented steps to proper calibration.
     
    If, as you say, your elevators and rudders are working then you evidently must have these assigned in FSX, not in FSUIPC. The default FSUIPC calibration values will still apply, of course, but not being true calibrations they may not be having the best results. Really you are in danger of having conflciting assignments because assignments in FSX will conflict with any similar ones in FSUIPC. You should choose one or the other. You can still calibrate in FSUIPC either way, but there is little point if you simply leave the calibration values to default.
     
    Maybe you deleted some earlier INI file and are left with some later changes, forgetting you'd deleted everything beforehand? Otherwise i cannot imagine how you've had successful use of these facilities in FSUIPC before now.
     
    Regards
    Pete

     

     

    Hi Pete,

     

    What I will do, is install the latest once again, and consult the manual to properly set up the axis.

     

    I have all the buttons assigned through FSUIPC (gear flaps etc etc), If I just install the new version will these controls still stand?

     

    Alex

     

     

    edit:

     

    p.s,

     

    Pete, I just realised that I disabled the axis in fsuipc and enabled the default assignments through fsx, just so I could continue my flight, hense why they are not showing in there.

     

    My usual calibration is 

     

    > Axis Assignment > Move joystick to positive elevator >>  Send Direct to FSUIPC Calibration >> Elevator 

     

    Alex

  9. More information needed I'm afraid. How is it assigned -- i.e. which mode of assignment and which control? Is it calibrated in FSUIPC or not? Is this with FS9 or some older version, or FSX or P3D? What actual version of FSUIPC?

     

    If you don't know any of these things, maybe you can paste in your FSUIPC INI file from the FS Modules folder? That would fill in many of the answers.

     

    Additional, however, is whether it is the same with default aircraft as well as whatever add-ons you are using.

     

    Finally, you could, for yourself, try some of the logging facilities to see what is going on -- axis logging, for example. See the Logging tab in FSUIPC's options menu.

     

    Regards

    Pete

     

    Apologies for the lack of information.

     

    It is assigned through the FSUIPC Axis assignment and exported through fsuipc settings (giving more limited options for alerions elevators etc. rather than the full list).

     

    It is calibrated through FSUIPC.

     

    FSX

     

     

     

    Here is the log..

     

     

    P.s Elevators, rudders and buttons working fine.

     

    [General]
    UpdatedByVersion=4920
    History=3EVK1ANA9V4G8VZUK60L7
    InitDelayDevicesToo=No
    UseSystemTime=No
    UseMidMouseBtn=Yes
    MouseWheelMove=No
    MouseWheelTrim=No
    MouseWheelTrimSpeed=1
    JoystickTimeout=20
    PollGFTQ6=Yes
    BlankDisplays=No
    FixControlAccel=No
    FixMachSpeedBug=No
    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=No
    ShowPMcontrols=No
    SpoilerIncrement=512
    MagicBattery=No
    RudderSpikeRemoval=No
    ElevatorSpikeRemoval=No
    AileronSpikeRemoval=No
    ReversedElevatorTrim=No
    ClockSync=No
    ClockSyncMins=2
    ClearWeatherDynamics=No
    OwnWeatherChanges=No
    TimeForSelect=4
    LoadFlightMenu=No
    LoadPlanMenu=No
    PauseAfterCrash=No
    BrakeReleaseThreshold=75
    SaveDataWithFlights=No
    ZapSound=firework
    ShortAircraftNameOk=Substring
    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
    LuaRerunDelay=66
    Console=No
    FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0
    SimConnectUsed=10.0.61259.0
     
    [JoyNames]
    AutoAssignLetters=No
    1=Saitek X52 Pro Flight Control System
    1.GUID={97D76E00-1A0A-11E3-8007-444553540000}
     
    [buttons]
    ButtonRepeat=20,10
    1=P0,1,K77,11
    2=P1,1,K77,11
    3=R1,21,C65615,0
    4=R1,19,C65607,0
    5=P1,2,C65758,0
    6=P1,3,C65759,0
    7=R1,0,C65588,0
    8=P1,5,C65853,0
    9=P1,7,C65570,0
    10=R1,26,C65602,0
    11=P1,24,K82,9
    12=P1,6,K71,11
     
    [AutoSave]
    Next=1
    Interval=60
    Files=10
    SaveOnGround=No
    AutoSaveEnabled=No
     
    [GPSout]
    GPSoutEnabled=No
     
    [GPSout2]
    GPSoutEnabled=No
     
    [WideServer]
    WideFSenabled=Yes
     
    [sounds]
    Path=D:\Microsoft Flight Simulator X\Sound\
    Device1=Primary Sound Driver
    Device2=Speakers (ASUS Xonar Xense Audio Device)
    Device3=Digital Audio (S/PDIF) (High Definition Audio Device)
    Device4=S/PDIF Pass-through Device (ASUS Xonar Xense Audio Device)
    Device5=Digital Audio (S/PDIF) (High Definition Audio Device)
     
    [JoystickCalibration]
    AllowSuppressForPFCquad=Yes
    ExcludeThrottleSet=Yes
    ExcludeMixtureSet=Yes
    ExcludePropPitchSet=Yes
    SepRevsJetsOnly=No
    ApplyHeloTrim=No
    UseAxisControlsForNRZ=No
    FlapsSetControl=0
    FlapDetents=No
    ReverserControl=66292
    Reverser1Control=66422
    Reverser2Control=66425
    Reverser3Control=66428
    Reverser4Control=66431
    MaxThrottleForReverser=256
    AileronTrimControl=66731
    RudderTrimControl=66732
    CowlFlaps1Control=66162
    CowlFlaps2Control=66163
    CowlFlaps3Control=66164
    CowlFlaps4Control=66165
    SteeringTillerControl=0
    MaxSteerSpeed=60
    Elevator=-16380,-512,512,16380
    Rudder=-16380,-512,512,16380
    Throttle=-16380,16380
    Aileron=-16380,-512,512,16380
     
    [Axes]
    0=1Z,256,D,4,0,0,0
    1=1V,256,D,22,0,0,0
    2=1S,256,D,25,0,0,0
     
    [Keys]
    2=32,8,1127,0,1128,0
  10. Hi there Pete and gentlemen.

     

    Been a register FSUIPC user for years and this is the first support query (says a lot about how good the product is).

     

    My issue is that suddenly without changing a setting, the ailerons are not being picked up in the simulator. 

     

    In Axis assignment the X axis is still being picked up and assigned ot alerions, but that is just not materialising in the sim.

     

     

    Looking forward for your response,

     

    Alex

  11. hi guys,

    i recently bought fsuipc, and had a go at setting axis and stuff, but i dont think it went right, so i think i reset the defualts in fsuipc and went back to FSX control surfaces.

    basically now, in the pmdg 747, [fsx], if i move the yoke slightly right, the pmdg yoke will go fully to the right.... if i do it left, there is no problem, it follows my yoke exactly.

    i am using saitek pro flight with rudder pedals. i only noticed this since fsuipc was installed and i have configured my yoke again through fsx and there seems ot be no problems there

    best regards

    Alex

×
×
  • 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.