OK… never mind as I’ve found the problem. For some strange reason, this statement “USE HAT1_SENSITIVITY (20)” will not co-mingle nicely. So I’ve remarked the culprit as I’d rather have the microstick LOCK/UNLOCK funtionality, and now radar cursors as analog will even slew diagonally, and more accurately.
Latest posts made by dodgerdog
-
RE: Microstick LOCK/UNLOCK compiles for only MIX or MIY
-
Microstick LOCK/UNLOCK compiles for only MIX or MIY
Hello, I am hoping somebody can help me figure out how to get the Foxy compiler to successfully compile LOCK/UNLOCK for both MIX and MIY. Currently, I’m only able to get the compiler to successfully compile either MIX or MIY, but not both. When trying (see below) to define lock/unlock for both MIX and MIY, I get this cryptic compiler error stating I have max exceeded number of logical flags or more than 48 which does not make any sense. Here’s a snippet of the Foxy statement, and attaching a screenshot of the compiler error:
USE SWAP (TOEBRAKES, MICROSTICK)
Rem ** USE SWAP TOEBRAKES AS MICROSTICK configured Cougar CCP, and in the Falcon UI for the purpose of Radar Cursor controls
MIX /I LOCK (MIX, LASTVALUE) 6 25 ( 1 2 3 4 6 10 12 14 17 21 25 30 36 43 58 65 71 76 80 84 87 90 93 95 97 98) MSY(2-) MSY(2+) MSY(0)
/O UNLOCK (MIX)
MIY /I LOCK (MIY, LASTVALUE) 6 25 ( 1 2 3 4 6 10 12 14 17 21 25 30 36 43 58 65 71 76 80 84 87 90 93 95 97 98) MSX(2-) MSX(2+) MSX(0)
/O UNLOCK (MIY)NOTE: What I am trying to accomplish is a solution whereby I can configure L and R toebrakes within Falcon BMS 4.33 for Radar Cursor as an analog mouse using the UNLOCK function, and S3 (out) button to use the microstick as a digital mouse or LOCK (MIX and MIY, LASTVALUE).
-
Dunc's config just for assign microstick to toe brakes for radar cursor slew
Hello, In reading through Dunc’s config was wondering can the microstick be assigned to left/right toe brakes in CCP for Falcon configuration as x/y radar cursor slew, and still be able to use microstick as mouse statement in Foxy for clickable 3d pit?
Here’s what I have so far in CCP, and in Foxy while trying to figure out while I troubleshoot/solve LBRK/RBRK are not appearing as drop down choice in Falcon’s avionics config section:USE ZERO_MOUSE
USE FORWARD (MICROSTICK)
Rem ** Microstick is setup as LTBrake and RTBrake as configured Cougar CCP, and in the Falcon UI for the purpose of Radar Cursor controls
MIX /I 6 25 (1 2 3 4 6 10 12 14 17 21 25 30 36 43 58 65 71 76 80 84 87 90 93 95 97 98) MSY(2-) MSY(2+) MSY(0)
/O ^
MIY /I 6 25 (1 2 3 4 6 8 10 14 17 21 25 30 36 43 58 65 71 76 80 84 87 90 93 95 97 98) MSX(2-) MSX(2+) MSX(0)
/O ^ -
RE: YAME64 suite
Hello, Now that I’m over the BMS hooks not being present within BMS so that display instruments update values while in Falcon’s #D outside views, I’d like to discuss a couple of issues that I’m hoping somebody can provide some solutions.
1.) The YAME UI is very small on my computer - which is a Windows 10, 64bit I7 CPU with 3200X1800 touchscreen display. I’ve tried all the compatibility troubleshooting steps to no avail. I also have a second 1920X1080 display/monitor connected. In trying to drag the UI to the second monitor, the display is still micro small.
2.) The touchscreen with the 3200X1800 display functions, but the OSB button positions do not seem to line up with the callbacks. Meaning when touching OSB’s, the function is offset slightly to where the button position displays.I’m really liking the capabilities of YAME especially the MFD piece - thanks so much for all of your efforts!
-
RE: YAME64 suite
Hello, I’m new to YAME, but not Falcon 4. My intention is to implement YAME where previous older version of BMS and SP use to have a view called “cockpit ghost MFD” - which unfortunately does not exist anymore. So far, I’ve been able to get the client to display MFD and some instruments - looks good, and thanks to whomever has provided YAME as such an elegant solution. However, I’m noticing that when in the 3D world, and outside of the cockpit views like “chase” for example - the YAME objects do not update until I’m back in the jet? Is there a configuration setting or something to enable YAME to display/update the MFD’s and instruments while the view is say “chase” or something similar?
Yes, thanks for ruling out any issues - understood, and really not what I was trying to convey. I was hoping there was a setting or parameter that hooked YAME to outside the cockpit views so that the MFD’s and instruments are updated, dynamic, and in sync. Is that even possible?
-
RE: YAME64 suite
Hello, I’m new to YAME, but not Falcon 4. My intention is to implement YAME where previous older version of BMS and SP use to have a view called “cockpit ghost MFD” - which unfortunately does not exist anymore. So far, I’ve been able to get the client to display MFD and some instruments - looks good, and thanks to whomever has provided YAME as such an elegant solution. However, I’m noticing that when in the 3D world, and outside of the cockpit views like “chase” for example - the YAME objects do not update until I’m back in the jet? Is there a configuration setting or something to enable YAME to display/update the MFD’s and instruments while the view is say “chase” or something similar?
-
Trying to find functions for ACM slew, and radar submodes - if they still exists
Hello, I’ve combed through the keyboard commands template - with BMS 4.33, are there key commands for “ACM slew” and “Radar Submodes” or are they a thing of the past now?
-
RE: Throttle as Keyboard using USE THR_RANGE Foxy Statement - is not working
I’m happy with the statement as is - and I did have to read the Cougar syntax manual to “remember” - doh. However, I do appreciate the tips…
-
RE: Throttle as Keyboard using USE THR_RANGE Foxy Statement - is not working
I have solved the issue - forgot that there needs to be a valid “manual calibration” stored after flashing firmware. The values in this posts throttle statement are once again a calibrated precision.
-
RE: Throttle as Keyboard using USE THR_RANGE Foxy Statement - is not working
I’m not understand in the USE THROTTLE use to work even in very early BMS versions. The Cougar throttle is plugged into the Cougar joystick which in turn plugs into a USB port on the computer. The “wheelbrakes” macro for a key of “w” piece of the throttle statement does work. Is it just no longer feasible to use a calibrated statement like the above anymore? Thanks…