Jump to content
The simFlight Network Forums

Freccia

Members
  • Posts

    73
  • Joined

  • Last visited

Posts posted by Freccia

  1. 51 minutes ago, Pete Dowson said:

    Is this with a prop plane, or jey? With a prop, as you increase throttle for takeoff the "propwash" from the prop is disproportionally down one side (normall the left), so you need to use more and more right rudder to compensate.

    No, it is not a propeller aircraft, but a jet (A320, MD 82).

    58 minutes ago, Pete Dowson said:

    Not sure why the throttle calibration would affect anything you describe. 

    If you assign and calibrate in the Sim then you need to follow normal Game Controller calibration instructions. If you are using FSUIPC then there is a step by step list of things to do to achieve proper calibration of any selected axis. See the User guide, calibration chapter.

    I read here: https://www.flythemaddog.com/forum/index.php?/topic/10903-plane-landing-problem-goes-on-one-side/

  2. Hi, I was trying to figure out why the plane has difficulty going straight (not just during take-off but also during the taxi). I have to continually make small corrections, which are minimal during the taxi phase but which are really annoying during take-off.

    I read in the forums that the problem could be solved with a proper calibration of the throttle axis, but I have no idea how to do it.

    Can I have your help?

    Thank you.

  3. Hi, recently I had a problem with ProAtc X and the moderator of their forum, among other things, noticed that in the log file there were thousands of lines (almost 4000) of this type:
     

    2019.03.13-12:00:38 - - ComRadioUpdate: status=0; avmaster=1; activefrq=13220
    2019.03.13-12:00:39 - - ComRadioUpdate: status=0; avmaster=1; activefrq=13220
    2019.03.13-12:00:40 - - ComRadioUpdate: status=0; avmaster=1; activefrq=13220
    2019.03.13-12:00:41 - - ComRadioUpdate: status=0; avmaster=1; activefrq=13220
    2019.03.13-12:00:42 - - ComRadioUpdate: status=0; avmaster=1; activefrq=13220
    2019.03.13-12:00:43 - - ComRadioUpdate: status=0; avmaster=1; activefrq=13220
    2019.03.13-12:00:44 - - ComRadioUpdate: status=0; avmaster=1; activefrq=13220
    2019.03.13-12:00:45 - - ComRadioUpdate: status=0; avmaster=1; activefrq=13220
    2019.03.13-12:00:46 - - ComRadioUpdate: status=0; avmaster=1; activefrq=13220
    2019.03.13-12:00:47 - - ComRadioUpdate: status=0; avmaster=1; activefrq=13220
    
    2019.03.13-12:00:48 - - ComRadioUpdate: status=0; avmaster=1; activefrq=12780
    2019.03.13-12:00:49 - - ComRadioUpdate: status=0; avmaster=1; activefrq=12780
    2019.03.13-12:00:50 - - ComRadioUpdate: status=0; avmaster=1; activefrq=12780
    2019.03.13-12:00:51 - - ComRadioUpdate: status=0; avmaster=1; activefrq=12780
    
    etc...

    He wrote this to me: "Looks like a switch / Joystick button is signing all the time the active frequency."; advised me to ask for help here on your forum, because I told him that I set all the axes and buttons of my joy with FSUIPC.

    But I'm sure I've never set any buttons that had anything to do with radios.

    What could be the problem?

    Thanks for your help.

  4. Hi everyone, I wrote a question in the Aerosoft forum and they answered me this way: "turn off the internal view system of the Airbus via the options in MCDU3."

    I believe they referred to these options:

    mcdu.jpg

    Regarding these options, the manual says: "VIEW SYSTEM: You open the view bar by clicking the gray triangle in the upper right or left) corner If you do not like this, you can use the other viewing system".

    It looks perfect, right?
    But no.
    Even if the "VIEW SYSTEM" option is set to OFF, the F11 key continues to be assigned to "PEDESTAL VIEW".

    I had thought about buying a third-party addon for the views (for example ChasePlane), but I'm afraid I would not solve anything, since the aircraft.cfg file continues to predominate over everything.
    I'm right?

  5. 10 minutes ago, John Dowson said:

    So the [CAMERADEFINITION.004] is overriding the default P3D spot view. I guess you would need to remove (or comment out) the whole section so that the original view is still available. 

    I just tried John, erasing the entire section I completely lose the pedestal view (both from the main menu and from the view bar), and there's no way to see it.

  6. 15 hours ago, spokes2112 said:

    As John mentioned the camera definitions in the aircraft.cfg override any of the same/similar global camera definitions when the aircraft is loaded.
    If you can live without the F11 command for the pedestal view then -

    1) The AB 320/321 not loaded in sim
    2) in the aircraft.cfg find the camera definition for the "pedestal view" and comment out the HotKeySelect line as shown below -
     //HotKeySelect=3 (NOTE - this COULD be HotKeySelect=2, do not have the 320 and the P3D SDK somewhat conflicts with the FSX SDK
    3) Load the AB 320/321 up in the sim
    4) Use the FSUIPC command "View Camera Select 3"

    You will now have your spot view but lose the pedestal view.
    You could get them both back but it would require good knowledge of the camera system and the use of
    HotKeySelect & View Camera Select #
    https://www.prepar3d.com/SDKv4/sdk/cameras/camera_configuration.html

    Hi spokes2121, I did as you advised me, and I modified the file aircraft.cfg (Aerosoft A320 CFM Professional folder) like that .

    [CAMERADEFINITION.004]
    Title                     = "PEDESTAL VIEW"
    Guid                     = {237c7e20-8f54-4035-8a6a-73338e0561e3}
    Origin                     = Virtual Cockpit
    MomentumEffect                 = No
    SnapPbhAdjust                 = Swivel
    SnapPbhReturn                 = False
    PanPbhAdjust                 = Swivel
    PanPbhReturn                 = False
    Track                     = None
    ShowAxis                 = No
    AllowZoom                 = TRUE
    InitialZoom                 = .8
    SmoothZoomTime                 = 0
    ZoomPanScalar                 = 0
    ShowWeather                 = Yes
    XyzAdjust                 = True
    ShowLensFlare                = False
    Category                 = Cockpit
    PitchPanRate                = 25
    HeadingPanRate                = 25
    InitialXyz                = 0.56, 0.350, -0.28
    InitialPbh                = 68.0, -0, 0
    //Hotkeyselect                = 3

    Here's what happened

    bar.jpg

    1=Ok

    2=Outside view - Top down

    3= Outside view - FlyBy

    4=ok

    5=ok

    6=ok

    7=ok

    8=Outside view - Loked Spot

    9=ok

    F11 button=Outside view - Loked Spot

    Wow, a little bit of confusion 😂

    Tips?

  7. Really sorry, but I did not understand.

    I checked and actually in P3D Options -> Key Assignments. By default 'F11 is mapped to "View Camera 3". However, this assignment works only with the default planes. If I load the Aerosoft A320 and try to press F11 but it works differently, as I wrote before.

    I have loaded a plane by default and the assignment of a button of my joy to "View Camera 3" works perfectly, but if I switch to the A320 it will not work.

    I saw the file FSUIPC.ini and in the Buttons section there is this:
    18 = P0,2, K122,8 - {Key press: F11} -

    Can it serve?

  8. Hi, with Prepar3D (v. 4), I very often choose the following option from the menu: Views>Change View>Outside>Spot.

    Is it possible to assign a button of my joy, using FSUIPC, which reproduces this? I looked at the list of views, but I did not understand which one to choose.

    Can you help me?

    Thank you.

  9. Ok Pere, thanks for the explanation. Now I start to understand better and I can add details.
    When I use the "mouse macros" I click with the left mouse button, I hold it down and drag the mouse to the position speedbrakes full open.

    Note however that FSUIPC only records the left click (# 3 of "Mouse action codes"). In fact, by opening the macro file, the only recorded operation is the left mouse click (1=sb-full=RX40000170.3).

    If I understood correctly, FSUIPC would have had to record one of the sequences written by John, for example: a string containing the # 9 (Left button & drag) and one with # 13 (Left release). But FSUIPC does not want to register them.

    I do not know if I need it, but if I press the TAB key on my keyboard, nothing happens at all, but I can write macro name.

    However, I also tried to use Linda with the "Aerosoft A3XX Professional v0.6 beta (24 Jul 18)" module, but I did not solve anything. Linda needs FSUIPC to work and is just a nice graphical interface. 😊

    However I do not give up! If I can find a solution somewhere I'll write to you.

    It's a matter of principle now.

  10. Hi John, I tried to modify the macro file by inserting the various strings you suggested, but it does not work; that lever does not move.
    I open a parenthesis: is there a difference between these two strings (example)?
    1[space]=[space]sb-full-press[space]=[space]RX40000170,9
    1=sb-full-press=RX40000170,9

    However, I have tried them all in both formats, but they do not work under any circumstances.

    On other issues (Microsoft's C / C ++ gauge SDK, lvars) I'm totally ignorant.
    What I know is that I have Prepar3D v. 4.4 running on Windows 8.1 (64bit) and using the Aerosoft A320-A321 Professional.

    I purchased FSUIPC with confidence and is a great product. I hope you will help me to solve this question.

    Thanks.

     

  11. Hi Pete, I think the speedbrakes lever is not "spring". It is set to the desired value (1 / 4 - 1 / 2 - full etc.) and when it is no longer needed it is retracted.

    If I use this axis I must continually keep in the desired position (it is difficult, because the excursion is short) and, when I release the speedbrakes are retract.

    I understand what you want to tell me, and I have also tried. But that fucking lever does not move.

    I also tried this method, but I was frustrated by the failure.

  12. Hi Pete, as I wrote before I already tried to set the speedbreakes lever with an axis. The image that I put on, this, shows an axis (they are not ON / OFF buttons).

    joystickhotasone-2-jpg.jpg

    In the rest position their value is zero and the maximum value for the right one is -16834, the left one +16834.

    Even if it is uncomfortable to use that axis for speedbrakes (the hike is too short), I still tried to set it, but I did not get any results. Maybe I'm wrong, I do not know.

  13. Tanks Pete, now it works well.

    From this morning I'm trying to solve a problem with the speedbrake lever. I almost always use the Aerosof A320 on Prepar3d (see 4.4) and I can not in any way set speedbrakes using FSUIPC; let me explain better, I can only set the toggle to arm or disarm the air brakes, but I can not understand how to move the lever of the airbrakes in flight, to set it to 1/2 or Full (for example).
    On the FSUIPC command list there is speedbrake incr. and speedbrake decr., but there is no way to make it work by assigning it to keys.

    Yet I managed very well to assign two keys to the flaps (incr. and decr.), Because the speedbrakes lever is so difficult?

    Obviously if I try to move the lever of the speedbrakes with the mouse works, but I wanted to assign them to two keys of my joy.
    I also tried to assign them to an unused axis, the one in the figure, but it does not work anyway.

    joystickhotasone-2-jpg.jpg

    Do you have a suggestion to give me?
    Thank you.

  14. Maybe I solved it. Following Pete's advice, I opened the Option>Controls menu and in "Other" I removed the checkmark of "Enable Controller (s)".

    The problem has solved, wow!

    But now, I do not know why, the joy selector that allowed you to rotate the head to the pilot (right, left, up, down) does not work anymore, and I do not know what the option to assign in "Control send when button pressed" .

     

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