FeistyLemur

I was getting shoot cues on him. I was in wide acquisition ACM mode which auto locked him when I chased him and had him in single target track. It's completely possible it was misconfigured because I don't really know what I'm doing yet with aa mode in the hornet and still learning the plane. If that's proper behavior for the missile as its losing energy I guess, when I switched targets I actually locked the damn missile which I would have been guiding still with my stt lock on him, so maybe that's why it seemed to suddenly fly right in my face, or it just fully ran out of energy. In any case I guess it would be one embarrassing letter home to the family from the Navy.

It was not set to loft, it was not set to anything looking at the hud, It just said 7M whatever It was set as , but I was about 5 miles behind him firing 7Ms at him with him locked up. Both at high speed, I was closing on him but I don't recall the closure rate, I was at full mil and doing about 580ish knots. How the hell did I outrun my own Aim 7 though that seems goofy?

So, I tried two missions tonight. And the second I just left now there was some weird shit going on. It was the ready 5 mission for the hornet in the first mission of the default campaign. So I fight the two mig 29's, Aim 7Ms are not hitting anything, I end up getting them both with my aim 9s and my wingman gets shot down. There's what looks like a mig 23 left which makes a run for it so i lock him and am chasing him Something is locking me cause I have a non stop warning tone but theres nothing showing on the EW. Anyway I fire no less than 4 Aim 7ms at him which all miss (maybe I had them set up wrong for target size and whatnot as I'm still figuring it out, not sure). The weird thing is I decide okay ill go to guns im 3 miles away and closing on him but he's doing the crazy ivan going by my gun reticle tracking. Im closing in and I see another dot to the right im closing on thats closer, so i think ok hes got a buddy, so i lock the other target and nose onto it, I start closing then I'm way fast cause im right on it and by the time i realize it poof, i blow up im hit like i collided with it. So I look at the combat log after, it was one of my own Aim 7s, still flying in that direction about 500 feet off the ocean and I literally flew into it and was killed by my own missile. What the fuck?

Yeah that's exactly what happens. Button starts acting up. Shut down and reboot computer, immediately bring up virpil software. Problem is still there. Only goes away based on time it seems. I went away and watched a movie for a couple hours and came back and it was working at one point even without a reboot. Or while the computers off overnight it starts working again. Or unplug the throttle for an extended period of time and plug it back in and it works again. It's very quirky. But it is isolated to only the right grip on the throttle and so far has only appeared in some of the buttons on the grip. I'm assuming there is some kind of board behind there all the buttons attach to since there is only a five pin cable coming down the tube to the main control board. It could be a fault with that or any of the cabling. Position and movement of the throttle makes no difference at all it seems.

The issue shows in the Virpil software as well. For example last night when I was messing with trying rebinding my sticks from scratch, all of a sudden button 31 began triggering button 20. Those are the two momentary press buttons on the right throttle face. Closing VA and DCS entirely I brought up the Virpil software and could confirm that it was actually registering multiple physical button presses when pressing button 31 and flapping between registering as 20 or 31. After being turned off overnight the problem went away. It very much behaves like a hardware problem, yet I can't discount the results I got by not running VA/vaicom and then tinkering with the settings. Though I can't really fathom how third party software would make the physical buttons misbehave on the throttle.

It isn't losing it. It's an issue with the buttons only specifically on the right hand throttle grip behaving erratic after a certain period of use. I did experience VA losing the joystick as well as described, because changing USB ports was part of my troubleshooting for this issue as well. In that case it was solved by simple removing joystick one, and re-adding it, did not even have to redo the keybinds in the Vaicom profile. Knock on wood I hope it stays gone following my turning VSPX and debug off in Vaicom today, because my throttle is at the very end of it's warranty period which adds some urgency, and having to send it back to Lithuania would be a downer. Especially for a very goofy and difficult to reproduce issue.

Well, it appears to be a va/vaicom problem since it's gone when va/vaicom is not running. After disabling VSPX and and debug under the vaicom tabs, my buttons have not acted up today yet while using it. It could be a coincidence and some sporadic problem with the throttle will reoccur, but at least for now it's not recurring. Not trying to be a smart ass doesn't seem entirely true either. I was referring to Vaicom interacting with DCS not voice attack itself. Either way it's splitting hairs just to be contrary and a waste of time. I'm aware of what Vaicom is since I was using since it's very early days but thank you very much for the lesson on what it is.

I have just one defined joystick in voice attack and it's the CM throttle as joystick 1. Using the forward back and center press of the lower rear hat on the throttle grip. I've been running with the same install for probably years now with Vaicom doing its own auto update feature within voice attack, but have not updated VA which is still 1.8.7 and just started to notice this. That doesn't sound entirely true either since Vaicom knows what module you are playing and sets itself accordingly to whether your radios are tuned. It even displays communication results in the window. Such as as the tanker answering back on the refueling mission I just did to try it. I did have Debug mode checked in Vaicom and I'm not sure why, so I just disabled that as well as VSPX processing as another troubleshooting step.

So the past several days I have been troubleshooting a problem with my throttle. I initially thought my throttle was failing because the hat switch I use for voice attack was becoming unresponsive. So I've spent some time conversing with Virpil support over this. However, the problem started to get more and more odd. Not only would the voice attack bound hat switch stop fully responding, now another hat switch would do it. So in my troubleshooting I ended up moving my .diff files out of my DCS folder to rebind and see if something became corrupted. As I was doing so, the buttons on my right VPC throttle started going even more batty. The two momentary press buttons were both registering as the same button. In frustration I gave up for the night. Today I decided to copy my old .diff files back fully bound, and try running DCS without voice attack up and running. I flew a whole mission without any issues, and all buttons remained properly working. It seems when this happens even closing voice attack and DCS, the problem will persist. Even rebooting the computer did not solve the problem (button still acting odd after reboot using only the VPC test software to test). It seems the only thing that works is waiting a while and the throttle buttons start working normally again. So I'm kind of at a loss for how this could be a cause of this, yet the results are what they are. Has anyone else had any similar issues with voice attack or vaicom? I'm using Vaicom Pro with all the packs and 1.8.7 voice attack. I guess I should probably try upgrading that as a test since its on v.1.8.9 on the website. But still this is extremely odd behavior to me.

The way they work on mine if I configure them as 8 way, when they go diagonal they press both buttons at the same time, so if I press the hat down, then it rolls ever so slightly left or right it will activate both. So if you can imagine left is button 20 and down is button 21, as you move to the bottom left corner you now have 20 and 21 pressed at the same time, and will have triggered whatever you have bound to 21 inadvertently. When set as 4 way, they do not do this, however they now require you to be more precise than before to activate that direction. It's very easy to slip back or forward and it will now blip on or off unless you hold the hat straight down and do not deviate at all. The place this becomes especially annoying is having them bound to my voice attack keys for push to talk. As you're holding the hat down to transmit for example, and moving the throttle it becomes easy to make it blip on and off and mess up your voice attack commands, or break voice attack entirely because it has a tendency to get confused as to whether the button has been released or not, so it will actually invert the function and its stuck on hot mic with the button released. Causing me to have to restart voice attack when it gets stuck like this.

Has the feel of the hats improved quality wise at all though? Like for example I've always had some issues with mine with incorrect direction presses where ill try to press left for example and it presses left and down at the same time activating both. The lock sensor I wasn't aware of but that seems quite useful. One review I watched said the lock is really good on the CM3, it's definitely a con on the CM in that it's got a noticeable amount of play and is fiddly to activate. So I would hope that the lock up is more positive as well. Does the CM3 have any kind of idle button press on the axis like the warthog throttle has to accompany the detents?

I started with a warthog and I truly grew to hate it over time. The center bump by virtue of it's design is so horribly stiff that it makes it impossible to do small adjustments. I had to take the thing apart and clean / re-grease it I don't know how many times. I followed the guides for polishing the plastic of the mechanism to reduce stiction which helped. Having an extension helped considerably to mitigate the stupidly harsh centering but I still had to break the thing open and keep replacing the grease. I would never recommend one to anyone to be honest. Their grips on the other hand are fantastic. Now that they sell the warthog / viper grip separately I see no reason to use their base. Even the warbrd will blow it away for a reasonable cost and you can use every grip on the market with it, and the T50 is better still with the level of adjustability it has. If you aren't already in the ThrustMaster / Virpil ecosystem however, you might give some consideration to the VKB gunfighter ultimate. It's a downside that you're limited only to VKBs grips, but they do have a very good base with the unique dry clutch system, and their new Ultimate grip which is all metal is supposed to be really nice.

Is there anyone out there who upgraded from one of the older throttles to the CM3? I currently have the CM which I believe was their second product introduced in either 2018 or 2019. My main question is if the hat switches have improved a lot, because I find some of them pretty fiddly and of questionable quality on the CM. They're pretty mushy and imprecise, especially the lowest hat on the right side of the throttle, which also just failed today and I'm hoping will be still replaced under warranty which I'm just barely still under. I did watch some reviews that rave about it and the build quality having improved over the years, and kind of have a hankering for afterburner detents, but am curious about a direct comparison from someone who upgraded.

I'm disappointed with winwing too, and I don't even have one. The reason is I looked at the shipping cost and its over $300 US to ship to my location, which is more like 400 in leafbucks. So no super taurus for me unless winwing ever gets NA distributing or a sane shipping cost. Also for OP you can use autohotkey to absolutely anything you want when it comes to binding keys to controllers. It's very powerful and useful if you get into scripting for it.

I guess I just answered my own question, so disregard this. I got antsy and cut the connector open on my extension cable and found the pins on the Virpil stick had forced the red wire out of the housing in the female connector enough to make intermittent and finally no contact. So that's something to watch for with extensions I guess. And it didn't damage anything permanently.

My experience with them with the throttle I bought was pretty good with the CM2 throttle. It had one dead toggle switch, and they shipped me an entire new inner button assembly for it since it's all one piece and not easy to replace a switch, and did not ask me to ship the other one back, also duties and shipping were all paid on the replacement. That was a while back though. I will soon find out how good they are these days though since I just got an MCG, and VFX and the MCG has a busted off flip trigger that I had to open a ticket for. I guess that's 2 out of 2 orders needing a support ticket, but the amount of time I spent screwing around with my TM warthog re-greasing and maintaining that thing was not any more enviable.

So, I have a MT50 base board and sensors, which I mounted in my BRD stick and got through Roman, not Virpil. Everything has been working well since I got it a few months ago until now. Have been using it with my TM F-18 grip. So my F14 grip came in and I was wanting to test fit it, I removed the F-18 grip, forgetting to unplug USB as I removed it (not sure if this could damage it or not). So I remembered at this point to unplug it. Tried out my F14 grip just for fit for a few minutes, then decided I should back up the profile for the current set up before really trying it. So I put the TM grip on, plugged it in, opened the software, and I notice none of the buttons are working right. I found I could press the trigger, and all the buttons would light up at once, pressing other buttons resulted in no response. At this point I tried firmware updating it, resetting the profile and creating a new one, same problem. Tried the F-14 grip, deleted profile, created a new one for the right grip. Buttons not working on it or the Axes on the stick itself. The main Axes on the sensors are working normal. So I got back out my original controller for the stick and tested both grips which work fine with it. I also tried testing the pins on the cable for continuity from end to end which there was. At one point as I was testing with the virpil chip, I had the stick off and tried the pinky button and it started spamming output in the log in the virpil software over and over. For those more experienced with the virpil controllers, is there anything else I should be trying? My next thought was to make up a new cable as a test, the one I have isn't the tightest fit on the connector but it was working, and I've seen some threads of people complaining about having to get the connector to sit just right, but they're older.

You cost me money dburne. I couldn't stop myself from ordering this mod. These little teensy dampers on the toe breaks are very interesting to me, they look small enough I could possibly fit them somehow in my flight stick base. I looked at your page but wasn't able to find those specific ones on there, could you tell me what model they are?

If anyone out there owns a BRD-N stick built by Roman and want's a curved stick for it, I made a 3d printed one that works better than expected for plastic. Probably not as good as rigging something up with that Virpil aluminum extension, but it costs a lot less money, assuming you already have a printer with a 315mm or greater build height. It's published with instructions here. Thing files for BRD-N Curved Extension by FeistyLemur - Thingiverse

Poverty. That's what's next. I've sold my soul to Lithuania, and a very helpful Russian.

I always wanted to try making one with igus bushings (or linear ballbearings), rods, and printer belts to kind of emulate the sliding style throttle the mig29 has. It seems like it might be precise and offer a lot of resolution compared to a rotational movement, along with keeping the grip (and therefore the buttons) at a constant angle. What I learned making myself a button box though is don't expect to save any money. Projects get expensive and are incredibly time consuming.

I had to put on the auto browse checkbox to get mine working. It works great now.

The lighthouses were not something I wanted to deal with, but really it's still inside out just better inside out than the Rift. Tremendously better, so much so it made me reevaluate not wanting to deal with lighthouses. As it happens my room has sockets at a pretty optimal position for two of them. I actually went ahead and ordered an index, I plan to just 3d print some lighthouse wallmounts. They're still infinitely less of a pain than the cameras from the original rift which I used to have in a 3x sensor setup. It's hard for me to stand the toilet paper roll vision of the Rift now having tried the index. Plus there's talk about forced facebook login coming to the Rift S and I'm not signing up for facebook.

I've been playing exclusively in VR on the Rift S since it came out. Today I tried a Valve Index and I have to say the Index is so much better because of it's huge FOV. I compared in the hornet and sitting centered I have to tilt my head up to fully see the upper mirror, and I cant see the side mirrors in frame. With the index, I can see 3/4 of the side mirrors and the vertical FOV honestly feels like real life to me. I could read the gauges and the color MFD way better, and even spotting planes was better. But it doesn't stop there, the tracking was so much better, and the smoothness of the high refresh rate and overall feel of performance was better. It was night and day for the index. I have never tried a quest 2, and never will cause I'm done with oculus after they forced Facebook login. But after watching reviews the index is still the king of FOV besides the pimax stuff. The G2 has an abysmal FOV, and by the sounds of this forum, abysmal performance so I'm giving it a pass. One thing though I do have a very narrow IPD, 60, and that reduces FOV, but no matter what the index is going to be better.

I just wish he could understand me telling him to **** off in voice attack when he makes fun of non three wires.