Jump to content
The simFlight Network Forums

Swissdani

Members
 View Profile  See their activity

  • Posts

    25

  • Joined

  • Last visited

 Content Type 

Posts posted by Swissdani

  1. Did something change with the brakes?

    in FSUIPC Support Pete Dowson Modules

    Posted

    Hi John

    Thanks for getting back to me. Yes the calibration does look strange indeed and it looks way different then what it used to look in the past with the same pedals. It may actually be the start of a hardware breakdown. I will try to get hold of another pair of pedals and see how they are performing in the next few days. 

    I already did recalibrate the pedals in windows, but also there the window of movement seems to be very limit compared to before. 

    I already did what you suggested and re-assigend the brakes to FS control and there is actually a small brake movement. I also tried to assign the brakes via the FSL own controls panel which they most developed for the TCA thrustermaster stick and also there is no brake movement at all. Also with general aircraft like the standard F35 there isn't any brake movements.

  2. Did something change with the brakes?

    in FSUIPC Support Pete Dowson Modules

    Posted

    1 hour ago, aua668 said:

    Hi,

     

    Looking at your calibration of the brakes in the Airbus profile, the values seem a little bit strange to me: 

    LeftBrake=-14335,15604/16
RightBrake=-13567,-5760/16

    Is there really such a big difference between left and right brake? 

    In the 777 calibration profile you have a strange line included 

    !1=SlopeLeftBr

    Maybe you check the calibration of your brakes. First in Windows. Then check, that you have no assignment set in the simulator. And then check the generic calibration and especially the profile specific calibration for your brakes.

    Rgds
    Reinhard

     

    There is nothing set to the brakes in sim. I tried that last night manually and then the brakes actually do apply a bit. I saw that as well that the value for the right brake is much less than it used to be in the past. Might be an early indication of a hardware failure, but still at least the left brake shows perfectly normal values. I hope they last until the honeycomb charlie comes availabe.

    In windows the brakes to work and have movement in the system setting calibration page. Not full movement for the left brake, but there is movement. Problems applies to all my profile, airbus, 747, 777 etc.

  5. Did something change with the brakes?

    in FSUIPC Support Pete Dowson Modules

    Posted

    After a long month I finally had time to fly again, still on my 5.2 setup. Somehow all my airplanes lost the brakes that I set up via fsuipc. The rudder itself is working fine, but when I push down the pedals to brake nothing happens. The axes are still set in fsuipc as always and also the calibration is still the same. When I move the brake pedals within the fsuipc I see the values changing.

    Any idea what could trigger this behaviour?

  10. v4 to v5 transfer with hardware change

    in FSUIPC Support Pete Dowson Modules

    Posted

    Hi Pete

    I do indeed not have the original ini file with the fresh install, just overwrote ist.

    I changed now the JoyNames as suggested by you and yes the T.320 is the Thrustmaster airbus stick. The result after loading the sim is now:

    [JoyNames]
    AutoAssignLetters=No
    2=Alpha Flight Controls
    2.GUID={DEDD1DD0-1723-11EC-8007-444553540000}
    4=CH Pro Pedals USB Rudder Pedals
    4.GUID={DEDDBA10-1723-11EC-800D-444553540000}
    3=T.A320 Pilot
    3.GUID={DEDD6BF0-1723-11EC-800A-444553540000}
    0=Bravo Throttle Quadrant
    0.GUID={DED29680-1723-11EC-8002-444553540000}
    1=TCA Q-Eng 1&2
    1.GUID={DED2BD90-1723-11EC-8004-444553540000}
    0.WARNING=This joystick was ID 2, but was duplicated: review and fix assignments, reload settings
    1.WARNING=This joystick was ID 4, but was duplicated: review and fix assignments, reload settings
    2.WARNING=This joystick was ID 3, but was duplicated: review and fix assignments, reload settings
    3.WARNING=This joystick was ID 0, but was duplicated: review and fix assignments, reload settings
    4.WARNING=This joystick was ID 1, but was duplicated: review and fix assignments, reload settings
    A=<< MISSING JOYSTICK >> << MISSING JOYSTICK >>
    B=<< MISSING JOYSTICK >> << MISSING JOYSTICK >>
    D=<< MISSING JOYSTICK >> << MISSING JOYSTICK >>
    C=<< MISSING JOYSTICK >> << MISSING JOYSTICK >>


    So the numbers seem have to changed back to the state before I manually edited them.

     

    23 minutes ago, Pete Dowson said:

     

    I don't suppose you have the original FSUIPC6.INI file, from before you ran P3D with the new install? That would make this more foolproof.

    As it is, these are the assignable devices:

    [JoyNames]
    AutoAssignLetters=No
    0=Bravo Throttle Quadrant
    0.GUID={DED29680-1723-11EC-8002-444553540000}
    1=TCA Q-Eng 1&2
    1.GUID={DED2BD90-1723-11EC-8004-444553540000}
    2=Alpha Flight Controls
    2.GUID={DEDD1DD0-1723-11EC-8007-444553540000}
    3=T.A320 Pilot
    3.GUID={DEDD6BF0-1723-11EC-800A-444553540000}
    4=CH Pro Pedals USB Rudder Pedals
    4.GUID={DEDDBA10-1723-11EC-800D-444553540000}

    whilst looking at some axis assignments:

    [Axes.Airbus]
    RangeRepeatRate=10
    0=0X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
    1=0Y,256,D,2,0,0,0    -{ DIRECT: Elevator }-
    2=0R,256,F,66818,0,0,0    -{ TO SIM: STEERING_SET }-
    3=0S,256,D,22,0,0,0    -{ DIRECT: Spoilers }-
    4=1X,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
    5=1Y,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
    6=1S,256,D,3,0,0,0    -{ DIRECT: Rudder }-
    7=2X,256,D,9,0,0,0    -{ DIRECT: Throttle1 }-
    8=2Y,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-

    it appears that:

    * the joystick/yoke ID is now 2 (Alpha Flight controls), not 0.
    * the rudder ID is now 4 instead of 1
    * the throttle quadrant ID is now 0 instead of 2.

    That leaves the TCA Q-Eng 1&2 (now 1) and the T.A320 Pilot (now 3). Looking further in the INI there are these axis assignments

    [Axes.747]
    10=3X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
    11=3Y,256,D,2,0,0,0    -{ DIRECT: Elevator }-

    Which implies the one of those two as yet determined devices is also a joystick or yoke. If the T.A320 Pilot is a sidestick then my earlier deduction is wrong, and these settings would be more correct:

    * the sidestick ID is now 3 (T.A320 Pilot), not 0.
    * the rudder ID is now 4 instead of 1
    * the throttle quadrant ID is now 0 instead of 2.
    * the yoke ID is now 2 instead of 3.

    leaving just the TCA Q-Eng 1&2 which must have changed from  4 to 1.

    So I think the settings in [JoyNames] should now be:

    2=Bravo Throttle Quadrant
    2.GUID={DED29680-1723-11EC-8002-444553540000}
    4=TCA Q-Eng 1&2
    4.GUID={DED2BD90-1723-11EC-8004-444553540000}
    3=Alpha Flight Controls
    3.GUID={DEDD1DD0-1723-11EC-8007-444553540000}
    0=T.A320 Pilot
    0.GUID={DEDD6BF0-1723-11EC-800A-444553540000}
    1=CH Pro Pedals USB Rudder Pedals
    1.GUID={DEDDBA10-1723-11EC-800D-444553540000}

    Now you might be successful just changing those lines -- FSUIPC will try to force the ID change in the Registry. But this is not guaranteed. It is probably safer to change  the AutoAssignLetters=No parameter to Yes, then run P3D, and afterwards edit the letters in the [JoyName] section instead of the numbers.

    Pete

     

     

  12. v4 to v5 transfer with hardware change

    in FSUIPC Support Pete Dowson Modules

    Posted

    Hi guys

    I just jumped to v5 and also update some hardware parts (mainboard, gpu) together with a fresh windows install. I dropped than my "old" fsuipic6 files from the old disk into the newly installed one. In the sim my profiles are correctly loaded, however all my button and axis assignments seem to be gone within the profile, even they are still there in the .ini file. My flying hardware is all the same as before, no changes there.

    Any way to get my old profile back to work without having to assign everything again?

  17. Understanding problem regarding aircraft profiles

    in FSUIPC Support Pete Dowson Modules

    Posted

    6 minutes ago, John Dowson said:

    No! Please read my comments. Its
        ShortAircraftNameOk=Substring

    This is all explained un the User Guide, section User profiles for all control settings.
    Please read this. We provide this documentation so that we don't have to continually respond to questions like this....

    Not sure what this means. What has this got to do with profiles? You assignments are to specific devices, so they work independently.

    I did read it, but as a non-native english speaker I had my problems to fully understand it. I got confused because in the user guides it says that the substring thing is not satisfactory and now we should use profiles. Since I am not planning to have more than 3 different settings (Boeing, Airbus and general for the rest) I thought the substring way should be still enought for my going forward. 

    My understanding of the substring thing is, when I call my profile "Boeing" then all aircraft that have the name Boeing will use my Boeing-profile but this is not the case. 

    As I said I will dobule check the ShortAircraftNameOk=Substring again tonight, even I am pretty sure I already checked that before.

    What I still don't understand 100% where I have to use the substring, once I made sure the setting in [GENERAL] is set properly. Where should that "1=PMDG 747" entry go that you specified above?

  20. Understanding problem regarding aircraft profiles

    in FSUIPC Support Pete Dowson Modules

    Posted

    Hi Pete

    I am a long time user but just recently started to use the full potential of FSUIPC. Until my honeycomb yoke arrives I still use an old Saitek X52 as my joystick. I disabled the joystick in P3Dv4.5 and sent up all the axes, buttons nicely via FSUIPC, that worked all fine. I set up a profile called "Boeing" when I did the setup within a 747.

    Even after reading the User Guide and the advanced guide I still struggle to fully understand how to bring this "Boeing" profile to work with another 747 (different livery, still PMDG) or even a PMDG 777 aircraft? How should I tell FSUIPC to use the self created profile? I can see the "Boeing" entries in the .ini file, so I assume I did this part correctly.

    Can you give me a hint? Any help is much appreciated.

    Kind regards

    Dani

  22. Makerwys v4.801 fails to make data files

    in FSUIPC Support Pete Dowson Modules

    Posted

    1 hour ago, Pete Dowson said:

     I am away from early tomorrow until the following Friday (the 19th), but maybe John or others can help. But you can also try Lorby-Si support, because the MakeRunways_Scenery.CFG file is built by the Lorby-Si scenery export program, and that needs to be correct for MakeRunways to process the scenery files added via the Add-Ons.XML methods.

    If you have the Lorby AddonOrganiser, run that free-standing and see if that finds all your sceneries okay. If not, then the problem is to do with your folders not found under the correct names. You haven't renamed the Prepar3D.exe file have yo? Just check that it is there is the same folder you placed MakeRunways into. I get the feeling that you are placing it into the wrong folder.

    Another test: if you remove the scenery export EXE from the MakeRunways folder, then execute MakeRwys, if the folders are correct it should find all of the default scenery layers and any add-on sceneries added the old way, via Scenery.CFG.

    Pete

     

    Prepar3D.exe is where it belongs in the root Folder. The same place I put the makerways.exe and the Lorby.exe as well.

    Just to confirm you mean the Lorby Export.exe right? I can give that a try later this week.

    Yes, the Addon Organiser finds all my sceneries.

    Dani

  23. Makerwys v4.801 fails to make data files

    in FSUIPC Support Pete Dowson Modules

    Posted

    1 hour ago, Pete Dowson said:

    The Runways.txt file, which will certainly be there, is the log file showing everything it did. How big is that? Were any of the expected files produced?

    Also: are you using version 4.801, as per the title of this thread?  If so then that will probably explain it. The current version is 4.872!

    If the Runways.txt file is short enough, or you can cut and paste just the first page or so, then please show us what it says.

    Pete

     

    Hello Pete

    Thank you for your help.

    I am using Version 4.872. Just downloaded the programme yesterday. I saw that there was a new makerwys_scenery file (or similar Name) just below the .exe file. But there was nearlly no Information inside, just a few lines of text. Something with [AREA] if I remember correctly.

    I will post you the runways.txt file tomorrow or Friday, i will not make it back to my flightsim computer today.

    Dani

     

  24. Makerwys v4.801 fails to make data files

    in FSUIPC Support Pete Dowson Modules

    Posted

    Helle Pete

    Sorry for bringing that old topic back up again, but I am having the following problem.

    I tried to use makerwys.exe today for the first time after updating my RAAS Pro. I placed the makerwys.exe and the lorbysceneryexport.ext into the main Lockheed Martin/Prepar3dv4 root folder. However when I start the makerwys.exe I get the error message: Failed to make all of the data files. I did run the programme as administrator and I tried 2 or 3 times with the same result.

    From the manual I read that the Addon Organizer is not needed, still I installed it, but the result is the same. Any idea what I could be missing?

    Kind regards

    Dani

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