Warthog Dial
-
It’s USB, so the interface should just be assignable from that single USB connector.
My expectation would be to use the wheel to drive the ANT ELEV in a Hornet sim, since that’s missing on the Warthog throttle set and is how it’s done on a Hornet throttle. The button could be anything you want another button for, though pressing the button could also act as a “shift key” to provide two different scroll actions.
-
It’s USB, so the interface should just be assignable from that single USB connector.
My expectation would be to use the wheel to drive the ANT ELEV in a Hornet sim, since that’s missing on the Warthog throttle set and is how it’s done on a Hornet throttle. The button could be anything you want another button for, though pressing the button could also act as a “shift key” to provide two different scroll actions.
I wrote them last night and got this reply…
"CUBESIM
2:07 AM (8 hours ago)
to meHello,
You can check out our video,the two rollers are together, one going forward and one going backwards,
http://www.cubesim.com.cn/pd.jsp?id=49#_jcp=2
It is like a mouse, you can map any function to it.
Best regards!
Garfield.Zhou
From CUBESIM
www.cubesim.com.cn
https://www.facebook.com/CubeSimGarfield/
PayPal:[email protected]"
Which doesn’t seem to answer the question of how/if it works in BMS. If it is like a mouse, then shouldn’t you be able to map the antenna elevation to a mouse wheel? I can’t on my install. -
I kind of thought that too…that the “two rollers” are a single one that will work in two directions. I also suspect “like a mouse” and “is a mouse” are two different things - the Cursor Controller is “like a mouse”, forex - it’s a quadrature device and not like a joystick.
I would also think that just how you can map it will be highly dependent on what controllers you are using - it may be that the only way you can map this is by DX assignment (which I still don’t understand myself, really) but it shouldn’t be a difficult thing to map it via the options in Setup - all of those items in that list are assignable to any key or controller by simply actuating the switch and Saving a new keyfile. This is the way I assign all switch functions other than what is reserved for flight controllers - Cougar, rudders, etc. - by Setup.
-
I kind of thought that too…that the “two rollers” are a single one that will work in two directions. I also suspect “like a mouse” and “is a mouse” are two different things - the Cursor Controller is “like a mouse”, forex - it’s a quadrature device and not like a joystick.
I would also think that just how you can map it will be highly dependent on what controllers you are using - it may be that the only way you can map this is by DX assignment (which I still don’t understand myself, really) but it shouldn’t be a difficult thing to map it via the options in Setup - all of those items in that list are assignable to any key or controller by simply actuating the switch and Saving a new keyfile. This is the way I assign all switch functions other than what is reserved for flight controllers - Cougar, rudders, etc. - by Setup.
Interestingly enough, before I wrote the last post I had tried in the regular UI, and it didn’t work. Just now I tried the Alternate Launcher and it did map ant.ele. to the mouse wheel. One more thing to wonder about. BMS maps antenna ele. along one axis, up/down, right? So, how would it work if one scroll wheel only goes one way and the other goes the reverse? Wouln’t that require 2 axis’ ?
I keep thinking about what you wrote about their vid., how they seemed to be demonstrating ant.ele but the carat wasn’t moving -
Yes…so I don’t know what he has it actually assigned to, or if this is just a very early video to show how it mounts and is actuated and is actually connected to nothing at all. The foamies in the one page make me think this was a post on prototyping progress.
Yes - ANT ELEV should only have one axis - up/down being a function of how you move the pot, given that there is only one pot involved. However, there are also key commands for most if not all of the analog inputs (i.e.; one for ANT ELEV -> up and another for ANT ELEV -> down) and this is probably what he’s referring to as “two scrolls” - I’d chalk this up to “lost in translation” between Chinese and English. But this is how I get around Cursor drift with a converted Cougar TQS that I use with Mac Falcon 4: Allied Force. I have the Cursor functions mapped to arrow keys via a utility called ControllerMate. My Cursor is dead solid this way and does not drift. I suspect one can do the same thing using Foxy or maybe T.A.R.G.E.T. with a non-converted Cougar TQS.
BTW - I have noticed that the Mac version of FAF and the PC version of FAF are not the same animal. The Mac version seems to include many RW modeling improvements in A/G and surface to air threat tactics that are not in the PC version - surface to air threats are far more reactive and manpads are far more prevalent. Some of these features appear to have been incorporated into the recent 4.35 BMS release, and kudos to the devs for that. I’ve been noting such improvements over the last few releases, and celebrating them!
-
……
Which doesn’t seem to answer the question of how/if it works in BMS. If it is like a mouse, then shouldn’t you be able to map the antenna elevation to a mouse wheel? I can’t on my install.
It’s a USB device. It’s acts as an independent DX Device. Just like adding an MFD or a UFC. Therefore, you can assign any BMS DX Callback to the three actions (scroll up, scroll down, button push) plus, as Stevie mentions, shift functions for those as well.
In the video he does show it controlling radar elevation via scroll up/down. I assume the button push would be TDC designate/undesignated.
-
It’s a USB device. It’s acts as an independent DX Device. Just like adding an MFD or a UFC. Therefore, you can assign any BMS DX Callback to the three actions (scroll up, scroll down, button push) plus, as Stevie mentions, shift functions for those as well.
In the video he does show it controlling radar elevation via scroll up/down. I assume the button push would be TDC designate/undesignated.
Thx, A_B,
You’re right , of course. I was thinking only in terms of axis’. So, you think this will work in BMS? -
It’s a USB device. It’s acts as an independent DX Device. Just like adding an MFD or a UFC. Therefore, you can assign any BMS DX Callback to the three actions (scroll up, scroll down, button push) plus, as Stevie mentions, shift functions for those as well.
In the video he does show it controlling radar elevation via scroll up/down. I assume the button push would be TDC designate/undesignated.
I’d question the TDC for BMS only because that’s not how Cursor Enable works on the Viper (which constantly messes me up), but probably correct for DCS…functionally, but not ergonomically. Undesignate should be on the Pinky switch.
-
I’d question the TDC for BMS only because that’s not how Cursor Enable works on the Viper (which constantly messes me up), but probably correct for DCS…functionally, but not ergonomically. Undesignate should be on the Pinky switch.
Me, too, Compadre. But, I think A_B has a point, if we think of it for FCR radar elevation. If we could get that in BMS I for one would be real happy. Right now I have Undesignate on the pinky ,a duplicate TMS up on the slew press for “designate”, and cursor enable on my “weapon selector” switch(Project Bug stuff). The point is that the Cubesim unit gives people some cool options, assuming it will work with BMS. I. for one, would prefer a “real” ant.ele., instead of my current DX on the China Hat. Plus, for the BMS Viper Folks, it gives a good alternative as well.
-
Thx, A_B,
You’re right , of course. I was thinking only in terms of axis’. So, you think this will work in BMS?I’m not positive, obviously, but I don’t see why not. And that is how it’s presented (in general).
-
I’d question the TDC for BMS only because that’s not how Cursor Enable works on the Viper (which constantly messes me up), but probably correct for DCS…functionally, but not ergonomically. Undesignate should be on the Pinky switch.
Right. Makes sense. TDC, etc. is in DCS.
-
I can’t see any reason for it not to work with BMS…but what is more of a concern to me is that the BMS Hornet in about no way models RL Hornet HOTAS or cockpit functionality. Forex - there are no such things as Cursor Enable, DED, TMS, DMS, etc. in a Hornet cockpit. And even if you could model all of the Hornet’s HOTAS switches BMS in no manner models how they should work. You can get around a lot of this by simply not mapping/selecting/allowing non-Hornet features…or remapping Viper assignments functionally, but that doesn’t really solve the problem. It’s a Viper sim, and I’m personally ok with that.
Something interesting to me is that you can buy a set of WINWING Hornet throttle grips as separate items - which makes me wonder if it might be possible to adapt and mount them on a Warthog throttle base. I have one of those sitting around doing nothing at all, and it might be a way to get some use out of it (I wish the WH throttle stalks were metal, though). I have the same sort of thoughts about the WINWING switch panels - they are clearly built to emulate a Hornet, but most of the switches are simply in the wrong places left to right, etc. wrt the cockpit diagram. I’ve considered buying a set of these and re-hosting them into another box that would put them where they should actually be, as well.
-
It looked pretty interesting to me - for antenna elevation and now it seems whatever else you want to map the button to in BMS. Price-wise, it is, what, 10% of a warthog price for only 2-3 functions?
-
I can’t see any reason for it not to work with BMS…but what is more of a concern to me is that the BMS Hornet in about no way models RL Hornet HOTAS or cockpit functionality. Forex - there are no such things as Cursor Enable, DED, TMS, DMS, etc. in a Hornet cockpit. And even if you could model all of the Hornet’s HOTAS switches BMS in no manner models how they should work. You can get around a lot of this by simply not mapping/selecting/allowing non-Hornet features…or remapping Viper assignments functionally, but that doesn’t really solve the problem. It’s a Viper sim, and I’m personally ok with that.
.Hi, Stevie.
I’m not sure what you mean here, beyond the obvious fact that our Bug does not have RL Hornet avionics, HOTAS, cockpit functionality , etc. . You have stated elsewhere you like the BMS Viper because the “compromise” of our Hornet “drives you nuts”. If that’s what you mean, I certainly respect that. However, I have to disagree that " there are no such things as Cursor Enable, DED, TMS, DMS, etc. in a Hornet cockpit. And even if you could model all of the Hornet’s HOTAS switches BMS in no manner models how they should work". In the BMS Hornet we do have all those things and everything works(with Viper avionics,of course). As for HOTAS, mine has a weapon selector switch, Sensor control(of sorts, and which I could go even further on), a TDC on the throttle with press to designate ,an undesignate and FOV as on the RL Hornet, and a fair simulation of the dispensible switch( operates as on Bypass). I give myself a “passing grade” on this as I have my DCS HOTAS set up 90+ % the same way.
As for cockpit functionality , the Dev’s actually came up with a good compromise on the original design. And if I can “toot the BMS FighterS Mafia horn” for a moment, we’ve made it better. Yes, the switch labels aren’t right, but they do work.
I invite anyone interested to visit the “Project Bug” thread over in General -
What I mean it that it is just a USB controller, so there is no reason for it NOT to work with BMS - all you need do is assign it like any other USB controller. How/what you assign it to is up to you - your only limit is what BMS callbacks are available.
So as far as the BMS Hornet goes…you may not be able to use it in a “Hornet-like” manner, but you can still use it.
-
I just received one and the cable for the USB is glued to the PCB. I have pulled as hard as I feel is safe without a significant chance of breaking the cable. I may be able to use something like nail polish remover but am wondering if I should just send it back. Any suggestions?
https://drive.google.com/file/d/1DtlqF9yNWD6nxFEJ1KWz_5BWzS_Z6rCw/view?usp=sharing
https://drive.google.com/file/d/1EAFekEEGVMNIxSUJLo0auTH0OFWfAfF-/view?usp=sharing
-
A couple of things you could do -
-
take a soldering iron along a small area of the PCB and see if it’s heat-glue. If so, you should be able to free it by applying some heat.
-
better yet, get a single edged razor blade or #11 X-Acto and free it by cutting along the PCB and not the wire - looks easy enough to scrape the glue from the PCB and not cut the jacket of the wire.
…also, see if a bit of alcohol might not remove the glue - looks like something dripped, to me.
-
-
A couple of things you could do -
-
take a soldering iron along a small area of the PCB and see if it’s heat-glue. If so, you should be able to free it by applying some heat.
-
better yet, get a single edged razor blade or #11 X-Acto and free it by cutting along the PCB and not the wire - looks easy enough to scrape the glue from the PCB and not cut the jacket of the wire.
And is it OK to scratch or gouge the PCB or will that cause problems? I think it may be super glue
-
-
As long as you don’t scratch through to any of the traces (and I think you’d have to work hard to do that…) scratching the bare side of the PCB isn’t a problem.
…if it is Super Glue, there are also Super Glue removers out there…or try nail polish remover.
-
If anyone wants to print it by himself:
Description and STL files can be found here https://forums.eagle.ru/topic/212255-f18-radar-elevation/Concerning connection, I would hook it up with either MMJoy2 or FreeJoy:
https://simhq.com/forum/ubbthreads.php/posts/3899105
https://github.com/FreeJoy-Team/FreeJoy…this with the benefit of having the possibility to hook up some more switches and buttons.
So: The first step for your pit is set. Keep going!