Jump to content
The simFlight Network Forums

Search the Community

Showing results for tags 'ipc.control'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Product Support Forums
    • FSUIPC Support Pete Dowson Modules
    • MyTraffic Support Forum
    • FeelThere Support Forums
    • FS Commander Support Forum
    • Flying W Simulation
    • AConstable Traffic Sounds Support Forum
    • Fabio Merlo Products Support Forum
    • Elite-Air Studio Support Forum
    • Nikola Jovanovic Support Forum
    • Intrasystems Support Forum
    • FScene Support Forum
    • Taburet & DanVFR Support Forum
    • Environ Scenery
  • simFlight DE
  • FS MAGAZIN (DE)
  • simRussia
  • FSUIPC Client DLL for .NET

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 3 results

  1. Hi Pete I am analysing the Control values used by FSLabs A320X to operate various switches for LINDA. For most they use FSX Control ROTOR_BRAKE (66587) but for others they use control 196881. I am using the LUA function ipc.control(value, param) to send commands into the simulator. The value of 66587 (ROTOR_BRAKE) is no problem but I am not sure that control values outside the normal range (e.g. 196881) are transmitted. Under FSUIPC Options and Settings users can set a custom control value from 65536 to 131070 (x10000 to x1FFFE). Does this upper limit apply to the LUA ipc.control(value, param)? I need to send params in the range 0x00010000 to 0x00FF0000. When I do send the control ipc.control(196881, xxxxxxx), I see in fsuipc4.log the line "FS Control Sent: Ctrl=196881. param:xxxxxxx" which suggests the control is sent but I am not seeing the expected effect. Any comments would be welcome. I am currently, using FSUIPC4 4.968 and P3Dv3.4 but the question equally applies to FSUIPC5.
  2. Hi folks, I am trying change altitude on MCP by rotary encoder, unfortunately I am not sure if I send to ipc.control correct data ipc.control(70032, altitude) value in altitude is correct, I have there (100,200....1000,1100.......12000....) It works only for first three hundred, and then even though I change altitude value by rotary, the value on MCP will not change. Could someone help me? Thank you. EDIT: I tried to send it real altitude /100. This works fine, but only for increasing altitude. If I turn with rotary to anti-clockwise position, the value is decreasing, but altitude on MCP in FSX is still increasing. EDIT2: Solved, I don't know why, but if I send there ipc.control(70032, 536870912) it is decreasing. EDIT3: Sorry, I have one more problem. When I send there real altitude, it is increasing till 35700. Why? I also noticed when I quick turning with rotary the value which I send to ipc.control is e.g. 2100 but it sets only 2000.
  3. hello pete hope is all good i have a question i bought the mindstar aviation G1000 software, since the MS1000(shortcut for mindstar g1000) have there own ini file for controls and they also offer not just a keyboard control they can control directly with fsuipc offsets or fs control , since the g1000 have a lot to program i run out of keyboard combination and by looking at the fsuipc control pdf i see there is a lot of empty control there is anyway i can assign the function from mindstar to this empty control ? or if you have another idea that can help me for example: in the ms1000 .ini file there is a command name PFD_DIRECT_TO = here it can be either CTRL+1 or FSUIPC:0x1234(some offset) or 0x23432(some control ) and basically from what i understand when i press on the pfd direct to button its going to the lua file (i am using linda) , looking for the function and execute the control 23432 which is the PFD_DIRECT_TO please let me know if it is possible or if you have a better/different idea THANK YOU VERY MUCH !!!!
×
×
  • 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.