Jump to content

Lorby_SI

Commercial Member
  • Content Count

    3,268
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

1,512 Excellent

About Lorby_SI

  • Rank
    Developer

Contact Methods

  • Website URL
    http://www.lorby-si.com

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Or you could just use (A:PLANE·HEADING·DEGREES·TRUE, Degrees) (A:PLANE·HEADING·DEGREES·MAGNETIC, Degrees) The sim will convert the unit as required.
  2. Confirmed. I will upload a new version of the plugin shortly, where this is fixed. Edit: Version 3.17 of the SD plugin is available for download.
  3. With the latest version of AAO you can do this in a script: 1·(>K:ELEV_TRIM_DN|n) This will repeat the event n times. 1·(>K:ELEV_TRIM_DN|5) : elev trim down * 5 1·(>K:ELEV_TRIM_DN|10) : elev trim down * 10 As for the A - Vars there are several that contain information about the elevator trim position. But they have different values, and the same variable may even have different values in different sims. For advanced aircraft they may not contain any useful information, if the developer chose to use his own LVar instead. In AAO go to: Scripting -> RPN Scripts Editor -> Insert sim var -> filter by "trim". Insert the variables and use the "Test" button to check their values when you move the trim in the plane. Then figure out a multiplier that will map that value on the -16K/+16K value range of the _SET event. Something like this: INC (A:ELEVATOR·TRIM·INDICATOR,·Position)·16383·*·1000·+·(>K:ELEVATOR_TRIM_SET) DEC (A:ELEVATOR·TRIM·INDICATOR,·Position)·16383·*·1000·-·(>K:ELEVATOR_TRIM_SET)
  4. Can you please post a conctrete example? What LVars from what plane in which simulator did not work for you? And what values should they display? I wasn't aware that Lvars contain much useful information...
  5. Every author of a profile can use whatever K-Events, A-, L-, H- vars and scripts he wants. So if he creates buttons or gauges in a profile using events and variables that only exist in MSFS, that profile naturally won't work in P3D and vice versa. A profile made for the P3D V5 PMDG NGXu using the PMDG events from their SDK will not work for the P3D V5 QW 787 which expects LVars from the QW SDK. A profile made for the MSFS FBW Airbus, using LVars specific to the plane, will not work for the MSFS WT CJ4. If he uses standard A:vars and K: events on the buttons, those will usually work in all sims. Etc.
  6. The plugin is not partial to any simulator. It works with everything from FSX Acceleration to P3D V5. It is just that most of the available StreamDeck Profiles on the various sites were made for MSFS planes, so you will have to create your own. But for example the "little gauges" profile on flightsim to works the same with all supported sims.
  7. AAO doesn't have a trial period. There is only the demo version with the timeout that shuts it down after 20 minutes. Otherwise it is fully functional.
  8. Are you using the DEMO - version? That one shuts down after 20 minutes of operation.
  9. Sure, why not. Clipboard code has been added to version 2.08.
  10. You mean with AxisAndOhs? Did you try the three different speeds for "repeat"?
  11. Two provinces in Canada are using P3D for Air Attack Officer and tanker group training. This kind of training is not about flying the various airplanes and bombing fires, it is about learning how to coordinate tanker group operations around a wildfire. The key element of the training is actually not the flight simulator but the simulated radios, since adherence to proper communication protocols is essatial if you have a bunch of planes and helicopters that all want to go to the same spot. Hardware is usually just "good" sim computers with the exception of the twin cockpit sim for the AAOs, that uses projectors and/or screens. While graphics are of course important to everyone (who doesn't like nice graphics), they are not essential to the training. "Realism" per se, in the aircraft systems or the scenery is not really a requirement, since they aren't training pilots. VR is also just a concept, but not really an option - the AAO and his pilot have to be able to communicate freeley with each other, look at each other, point things out to each other. Besides, many seasoned pilots who act as role players really hate putting a box over their head. Government Services - Wildfire Training Solutions Inc
  12. Hello @ll, AxisAndOhs 2.07 b12 has been uploaded to the shops today and should be available in your accounts shortly. This version is mostly about bugfixes: Change: Scripts: Repeat K: events with “|n” in scripts Bugfix: Buttons and Axis couldn’t be changed when device is not attached Bugfix: MIDI mode for the SaitekPanels could get stuck Bugfix: handling of the key down/up value boxes Bugfix: value 16384 not available for the key down/up events (PMDG mouse events!) Bugfix: Scripts: Forced read of LVars Bugfix: Scripts: Initialization of LVars fixed Bugfix: Additional initialization of “onchange” axis values Please note that the high speed StreamDeck plugin version is progressing as well, the latest version 3.15 is available for download on the AAO website.
  13. It is still a bug though in the pure Live mode. The collision detection is supposed to stop an AI, but it stops you instead. Only explanation that I've got is that somehow the AI plane dataset has not been properly initialized, and its object ID is 0 by accident. That would then affect your aircraft instead of the AI. Would you mind sending me an email? Then I can concentrate on fixing the code, and you can test it to confirm? Address is on the last page of the manual.
  14. Can we please stick to the emails? At the moment I can't check this, I don't have any PMDG planes installed on my computer anymore. For the time being you will have to use scripts instead. Are you quite certain about the "0" key up event? When I added this code a few months back, I never had to use that. All mouse events just worked.
  15. For the record, this would be the most effective way of using the mouse codes for a PMDG event - you set it as the value to send to the event (the little box next to the Key Event selector - spinning the mouse wheel over the left and right half of the box makes for small or big changes of the number)
×
×
  • Create New...