@djetdail Thanks! Your method works great. I appreciate your solution!
Posts made by Growler4135
-
RE: NEW WINWING ICP
-
RE: NEW WINWING ICP
@tptp149 That is GREAT news! I’m glad you got it worked out and can enjoy the new addition to your pit!
-
RE: NEW WINWING ICP
@tptp149 Happy New Year to you also!
My setup went so flawlessly that I didn’t have to do any troubleshooting. But, I can give you the steps I took:
- I did not plug in the ICP beforehand.
- Since I already had SimApp installed, I updated it to the latest version from Settings / System Configuration in the app. This is the version I have running now. V1.10.26_Beta *You can also get it from the Winwing download site.
- Back in Settings, I set the path to my BMS install: C:\Falcon BMS 4.37. (default install path for BMS) This is the current version 4.37.3 Hotfix 2.
- Returned to the main Device tab in SimApp and plugged in the ICP.
- It immediately showed up in the devices panel.
- Clicked on the ICP’s icon to enter the ICP connection screen and I tested everything.
- I started BMS Alt Launcher and set up the buttons on the ICP. I kept SimApp running in the background.
Once I got to the pit, the DED just worked.
Since everyone’s BMS set up differs greatly, I’ll offer basic troubleshooting tips:
Check software versions: BMS, SimApp, Windows Updates. (I am assuming a Windows install with BMS 4.37.)
Check if this line is added to your Falcon BMS User.cfg file: set g_bExportRTTTextures 1
If you are running any other display extraction software, disable that and try with only SimApp running.I hope some of this helps and you get the DED running!
-
RE: NEW WINWING ICP
@tteddy623 It was about 1 week from order to delivery. I ordered it on Dec. 22 and it arrived on Dec. 29.
The shipping seemed pretty quick with no delays for customs. -
RE: NEW WINWING ICP
My ICP arrived this afternoon. (OH, US)
Setup was a breeze using the Alt Launcher in 4.37. (Except the Warning Reset toggle. I’ll need to look into that.)
The DED works when SimApp Pro is running, and the performance is great. No lag between button press and display. (Be sure to enter the path to BMS in the SimApp setup.)
I’ve got it set up as a desktop stand, and it proved to tip when pressing buttons at the top of the panel. I solved that by using the adhesive dots that come with it and attaching the 2 extra metal brackets to the bottom of the stand. This gives it a wider base and doesn’t tip as easily.
Overall, I think this is a great addition to my desktop ‘pit’.-Growler
-
RE: Helios buttons not working while in-flight
@Todd1215 Thank you for pointing me in the right direction. The problem did stem from a resolution issue.
I’d set my in-sim resolution to 3440x1440p 164.90 Hz, and that is where I noticed the button failure. At your suggestion, I set my resolution to a random lower one, and the buttons worked again.
To try and replicate the issue, I set the resolution back to the original 3440x1440p and… the buttons still worked.
Not sure what the original problem was, but just changing the resolution and putting back seems to fixed it.
Thanks for the suggestion! You solved my problem. -
Helios buttons not working while in-flight
Odd Helios behavior here.
I’ve been running Helios to display MFDs on an external touchscreen and have mapped all the buttons and extracted displays. This worked well up until recently.
Not sure if it is a BMS 4.37 U1 issue or if it is a change to my system somehow. But now the Helios buttons no longer function after I launch to a flight. It is as if the touchscreen is not recognized after I’m in the pit.
I’ve tested the buttons in Alternative Launcher and in the Setup screen in the sim. The buttons register correctly but stop working after I launch to the pit.System specs:
BMS v. 4.37 U1
BMS config - set g_bExportRTTTextures 1
spacedesk display extraction v. 1.0.57
Helios v. 1.6.5900.0001
Windows 11 Home v.22H2 22621.1265
AMD Ryzen 9 795000X
64GB RAMAgain, the touch screen works great until I launch to the pit. I appreciate any ideas!
-
TFRP - Is this even possible?
I’ve recently added TFRP rudders to my system, and I want to smooth out the axis so they aren’t as jumpy. I know I can accomplish that with Target, but there’s a catch.
My HOTAS is a combination Warthog flight stick and Cougar throttle. I combine them with Target. That has been working well for ages now.
My concern is about the number of axes. The HOTAS combo uses 7 and the Windows limit is 8 per connected device (IIRC).
Adding the TFRP would require 3 more: 1 for rudder and 2 for each toe brake. So I imagine this config would not work. And, as far as I know, I can only run one instance of Target at a time.Is there other axis shaping software that I can use for the rudders?
Has anyone had experience with this situation?
Regards!
-
RE: Button Box Experience
@Vandal - It sounds like your project is coming along nicely! Using a jewelry tray is brilliant, really thinking outside the box (yeah, I did that). I over-sized the box I use, but It does leave room for expansion. I may put some white-board tape on it so I can jot down fight notes - C/S, UHF, VHF, Tacan, etc.
The RF switch is a good idea too. I’ve put that on my list of improvements.
After using my switches for a week or so, the ones I’ve found the most useful are for the auto pilot. (Especially useful when using Delilahs and LGBs.) I used a couple of ON-OFF-ON swtiches for those. Also having Master Arm and Ext Lighting Master is handy for fencing in and out.
I’ve been working with Inkscape, I’m glad there’s lots of Youtubes out there, it just takes practice to become proficient. It’ll give a much cleaner look over a resized jpg image.
Keep the updates coming!
-
RE: Button Box Experience
Yeah, there’s a big learning curve! Here’s a link that explains the PULLUP pretty well, http://www.ladyada.net/learn/arduino/lesson5.html.
I haven’t used any resistors in my build, but like you said, for myself that works fine. I’d want to square it up if I was building it for someone else though.I wound up not using any debouncing in my code. I haven’t had any issues after using it for a week. Are you looking at using any debouncing?
Thanks for the ref to Inkscape. I had never heard of it before. I’ll use in on my BMS Button Box 2.0! -
RE: Button Box Experience
Hey Vandal - It was an interesting project and I’m pretty happy with how it turned out. It’s interesting how easy the switches are to find when I’m in the pit. After a few minutes I don’t even have to look for them. Going Cat I is much easier, as well as setting AP modes.
I used a graphic of the panels from this site: http://xflight.de/pg_org_doc.htm. I used Windows Snipping Tool to grab the panels I was working with. Then I used Gimp (Photoshop wannabe) to lay everything out based on the dimensions of my project box. I did rearrange the Misc panel.
I printed it on matte photo paper and hot laminated it. It seems pretty durable. I used some spray photo adhesive to stick it to the top of box. That made a nifty template for drilling the holes.Here’s some pics from my build:
https://goo.gl/photos/t53QUnzXtU3QBQ4F9I’m interested in seeing how you get along with the Leonardo board.
On thing I learned with setting the device type…I’d set mine to Keyboard/Mouse/Joystick in the Arduino IDE. The Joystick part confused BMS and I lost all of my HOTAS mappings. I set it to just Keyboard and that works just fine. I’m not using any joystick functions in this project anyway.
Have fun!
-
RE: Button Box Experience
@Vandal - I got my button box built and tested today. Lots of wires and solder! I put the functions on it that I thought I used the most in the pit. I flew a couple of missions and it worked a charm.
Mounted it on a thriftstore tripod.
-
RE: Button Box Experience
Here’s some of the high-level issues I worked through:
- I use the keyboard method to send the key combos. This is a link to the Teensy documentation, but I believe it’ll work with any Arduino: https://www.pjrc.com/teensy/td_keyboard.html
- To Bounce or Not to Bounce - There’s a couple of Arduino libraries for handling noisy buttons/switches: bounce.h (legacy) and bounce2.h (newer). This seemed like the way to go, but for the life of me I could not figure out how to get the debounce objects into an array. I gave up and based my code on this video:
I’ve modified it a bit to suite my needs, but this is what I started with and it works. Let me know if you have any luck using the bounce libraries. I plan to revisit this in button box version 2.0. - Beware Double-Duty Key Combos - I found that some key combos gave unexpected results, [ctrl/alt/F8] must be used on my pc somewhere. I had to map a different combo.
It’s a fun project and I’m interested in how yours progresses. I can share my Arduino code if you are interested.
-
RE: Button Box Experience
@Vandal I’m going the same route with keyboard emulation and sending keystrokes that are mapped to my BMS Keyfile. I’ve worked though some quirks and will share my experience if you’re interested.
One of the first things I found I had to do was map individual on/off states instead of toggles. i.e. Add mappings to my key file for SimParkingBrakeOn (Ctrl/Alt/P) and SimParkingBrakeOff (Shift/Ctrl/Alt/P) and program the pin low/high accordingly. I just couldn’t see a sensible way to use the default keymap of SimParkingBrakeToggle.Some programming experience is a definite plus…be sure to brush up on handling arrays…you’ll need it!
Hopefully I’ll get the switches mounted in my project box and wired up this weekend.
Enjoy!
-Growler -
RE: Button Box Experience
Hey Vandal. Coincidentally, I started looking at my own button box project about the same time you started this thread. The local Radio Shack closed, and I scored a bunch of buttons and switches for cheap.
Have you decided on an interface board yet? I went with an Arduino-compatible Teensy LC, mainly because of the price, and I had an Amazon gift card. I’m new to the Arduino / C programming, but I think I’ve gotten the programming sorted out now.
I’m interested in how things are progressing for your project.
Regards,
Growler -
RE: Got 5 Cougar pots left, first come first serve
Habu_, do you still have the microstick available? Mine has gone tango-uniform.
-
RE: TARGET Script for Cougar Throttle Microstick
I believe I have it worked out. It was a matter of mapping the correct Axis Setup in the Cougar Control Panel and the corresponding axis in the TARGET Script Editor.
Now to figure out how to get the dual function of the Pinky Switch to work. (FOV & DX Shift).Cheers!
-Growler -
TARGET Script for Cougar Throttle Microstick
I’m trying to use a Warthog Flightstick with a Cougar Throttle. I’ve got the script running all the buttons and axes for both devices, except the microstick. I can get the y axis mapped, but the x axis never works.
Has anyone else tried this and have a snippet of script to share?Regards,
-Growler -
RE: A few random shots
The RC-135W “Hognose” model looks GREAT! Thanks BMS Team.