Jump to content
The simFlight Network Forums

aua668

Members
  • Posts

    381
  • Joined

  • Last visited

  • Days Won

    10

Posts posted by aua668

  1. Hi,

     

    Here a small test script setting the three values and resetting the eyepoint after 3 seconds. In my case Longitudinal has no effect in P3D 2.5.

     

    Rgds

    Reinhard

    -- test eyepoint setting
    
    -- play with these values
    local lLateral = 33100
    local lLongitudinal = 10000
    local lVertical = 14000
    
    -- be sure, that the virtual cockpit view is the active view !
    
    
    ipc.control ( 66530 )	-- first reset view
    
    -- calling first with a different value then the last called value is necessary, as otherwise the control is not triggered
    -- it is only fired, if the value differs from the last call. So I make the dummy call with 1
    -- that is a speciality of the ipc.control function to avoid calling with the same value too often
    
    ipc.control ( 66988 , 1 )		
    ipc.control ( 66988 , lLateral )
    ipc.control ( 66990 , 1 )
    ipc.control ( 66990 , lLongitudinal )
    ipc.control ( 66989 , 1 )
    ipc.control ( 66989 , lVertical )
    
    ipc.sleep(3000)		-- wait 3 seconds
    
    ipc.control ( 66530 )	-- finally reset view again
    
    
  2. Pete,

     

    I use P3D 2.5 with FSUIPC 4.948 under Win 7/64. I wanted to use the following P3D controls in a LUA script to move the eyepoint of a cockpit camera:

    EYEPOINT_SET_LATERAL       66988
    EYEPOINT_SET_LONGITUDINAL  66990
    EYEPOINT_SET_VERTICAL      66989
    

    Lateral and vertical are working fine. Only Longitudinal gives no reaction. The events are logged in the logfile. I can manipulate the eyepoint via EYEPOINT_BACK and EYEPOINT_FORWARD without any problem.

     

    Could you please check, if your code is correct for that control (and I am pretty sure it is correct).

     

    Best regards

    Reinhard

     

  3. Pete,

     

    One question: Is there a possibility in future versions of FSUIPC, that the parameter in the macro call from LUA will be passed to mouse macros as the mouseflag? 

     

    Example:

    ipc.macro("XXX:MyMouseMacro", 17)
    

    triggers the mouse macro in file XXX.mcro with parameter 17 as mouse flag.

     

    Why would this be nice?

     

    With certain payware aircrafts, you need to work with mouse macros. And some of them need a sequence of the same macro with different mouse flags (e.g.17, 11, etc.). You have an example in your documentation.

     

    But some aircrafts need a certain delay between mouse down and mouse up. As in macro sequences there is no mechanism to generate a short delay, you must implement this via a LUA code and with some ipc.sleep(xxx) between the several macro calls. But to call these different commands with different parameters you have to create seperate instances of the mouse macro with the relevant parameters.

     

    Example:

    1=MyMacro=RX3170*X8b90
    2=MyMacro11=RX3170*X8b90,11
    3=MyMacro17=RX3170*X8b90,17
    

    and then I can use this in my LUA like this:

    ipc.macro("XXX:MyMacro")
    ipc.sleep(1000)
    ipc.macro("XXX:MyMacro17")
    ipc.sleep(300)
    ipc.macro("XXX:MyMacro11")
    
    

    So passing the parameter to the mouse macro as the mouse flag would simplify the coding: Only one macro entry in the macro file and you can pass any parameter as mouse flag from LUA (especially useful if you have to experiment with the flags to find the right sequence).

     

    So no new functionality, but maybe you have a chance to check, if this enhancement could be implemented easily.

     

    Best regards

    Reinhard

     

  4. Hi,

     

    If you really want to know, how to fly this bird especially the handling of torque and prop pitch, read this article (entry #6):

    http://forum.aerosoft.com/index.php?/topic/91246-climb-data-and-cruise-power-tables/#entry674234

     

    And you should get the revised FDE files in the pinned topic in that forum. The modification is great. The only thing which you shouldn't adjust according to the instructions is the propeller_moi, if you are using P3D 2.5. For FSX it's fine.

     

    Rgds

    Reinhard

  5. Hi,

     

    Pete's assumption will be your problem - pretty sure about that. I fly this wonderful plane with the GoFlight Hardware and it's working fine. Here my Profile (your's should look similar but surely not the same). So it's just for your reference.

     

    Rgds

    Reinhard

    [Profile]
    Created=25/05/2014 20:54:18
    
    [Axes]
    RangeRepeatRate=10
    0=GY,256,D,9,0,0,0
    1=GZ,256,D,10,0,0,0
    2=GR,256,D,23,0,0,0
    3=GU,256,D,17,0,0,0
    4=GV,256,D,18,0,0,0
    5=YX,256,D,1,0,0,0
    6=YY,256,D,2,0,0,0
    7=YV,256,D,36,0,0,0
    8=TX,256,D,13,0,0,0
    9=TY,256,D,14,0,0,0
    10=RX,256,D,7,0,0,0
    11=RY,256,D,8,0,0,0
    12=RR,256,D,3,0,0,0
    
    [Buttons]
    0=PY,20,C65987,0
    1=PT,8,C65992,0
    
    [JoystickCalibration]
    Aileron=-16384,-996,-193,16383
    AileronTrimControl=66731
    AllowSuppressForPFCquad=Yes
    ApplyHeloTrim=No
    CowlFlaps1Control=66162
    CowlFlaps2Control=66163
    CowlFlaps3Control=66164
    CowlFlaps4Control=66165
    Elevator=-16384,0,512,16383
    ExcludeMixtureSet=Yes
    ExcludePropPitchSet=Yes
    ExcludeThrottleSet=Yes
    FlapDetents=Yes
    FlapEnds=-12561,-3823,2184,8192,16384
    FlapStarts=-16384,-8920,-2002,4733,13289
    Flaps=-16383,16384/16
    FlapsSetControl=0
    LeftBrake=-14000,14000/16
    MaxSteerSpeed=Q0,15,25,40
    MaxThrottleForReverser=256
    Mixture1=-7542,1536,1536,16380/8
    Mixture2=-7932,2304,2304,16380/8
    PropPitch1=-16384,-16384,-15000,16383/8
    PropPitch2=-16384,-16384,-15000,16383/8
    Reverser1Control=66422
    Reverser2Control=66425
    Reverser3Control=66428
    Reverser4Control=66431
    ReverserControl=66292
    RightBrake=-14000,14000/16
    Rudder=-16384,-903,704,16383
    RudderTrimControl=66732
    SepRevsJetsOnly=No
    SlopeSteeringTiller=10
    SteeringTiller=-16383,-3456,780,16384/24
    SteeringTillerControl=0
    Throttle1=-16128,-11597,-6627,16128/8
    Throttle2=-16128,-11487,-6214,16128/8
    UseAxisControlsForNRZ=No
    
    
  6. Hi,

     

    Please provide the LUA code for your question. With that it's easier to answer. Typically if you have such a problem, you did something wrong in the design of your program. Because typically you have some events (button or key presses) changing some offsets and you react on changes in offsets to display things (e.g. on some hardware device). I made many such modules for GoFlight hardware without ever having the problem you described. So if you provide the code we could check.

     

    Rgds

    Reinhard

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