Jump to content

mx22

Members
  • Posts

    274
  • Joined

  • Last visited

About mx22

  • Birthday November 25

Recent Profile Visitors

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

  1. Had the same happen to me last weekend. I've marked application as trusted in Kaspersky to allow it to run. But yes, would be nice if developer looks into this.
  2. I think the biggest issue is that mouse device needs to be close to the surface to work properly. At that point, regular mouse is probably just as good...
  3. Thanks, I figured it out - online price was already discounted, so it was only extra 10% during the checkout. Just waiting for them to process and ship it now...
  4. Hello, Not sure if I'm missing something, but what does one need to do to apply VIRPIL's 10% Christmas Discount to their order. I'm trying to order their collective base and grip - site automatically applies 10% Collective discount, but does not apply Christmas discount. Is there a code I should be using? Thank You!
  5. Not sure if it would help, but I had a problem on F16 getting the throttle to move from idle into off position (the one where you have to 'twist' quadrant to the back). What solved the problem was going into Axis Command screen and adjusting deadzone to remove the very start of the throttle movement (used by virtual buttons created in Virpil software). In my case, it was moving deadzone from 0 to 4 (I'm using 'classic detent' on CM3, so your value could be different). Also, make sure you are using the same axis for throttle input as for virtual buttons. Interestingly enough, on F18, I did not have to do deadzone trick. Go figure... P.S. Binding axis in DCS. I found you have to move axis all the way through it's movement before DCS registers axis movement. Not sure why, it seems a bit counterintuitive. You can also manually assign axis through dropdown menu.
  6. I've just tried AirLink at 90Mhz and Virtual Desktop at 120Mhz in a quick Free Flight mission in F16. I don't see myself going back to wired Link, though I would really like to test how long battery lasts in a longer missions with either of these options. Strangely enough, I had no keyboard problems in AirLink, but ran into some issue in Virtual Desktop - keyboard presses did not register at all at first, but started working a few minutes into the flight. Go figure...
  7. Ahh yes, sorry I was looking at the menus - I thought it would work like the VR mod previously and would render mask everywhere...
  8. How did you enable the mask? At least by default, I don't have one enabled and get the whole right/left eye render.
  9. I've owned Rift S since it came out and just this weekend bought Quest 2 to see how it stands up to Rift S and if it's worth upgrading. Picture quality and screen door effect - Quest 2 wins hands down. I'm on a somewhat older machine this day (16GB RAM and 1080ti) and performance between two is compatible when I set Quest 2 to 90Mhz. This is through third party 'Link' cable, I have not tried Virtual Desktop yet. I have ASW locked at 30Mhz and the only time I see fps drop is when I'm on a large airfield with a lot of ground units or flying over large cities at very low level - but I had the same problem with Rift S so it's a moot point... As far as DCS goes, I simply fail to see any reason to go with Rift S over Quest 2. In my racing sims, I still need a bit of tweaking for a final decision - the most obvious problem for me is that all objects in the distance are somewhat fuzzy (for example road in front of me is sharp, but a tower over the same road in a bit of a distance is noticeably fuzzy/blurry) and I can't figure out how to fix that. It's a bit annoying given that picture otherwise is better that what I get with Rift S. As it stands at this moment, I will probably go ahead and sell my Rift S in the next week or so. I've been really impressed so far with Quest 2 and personally think it's a much bigger jump for me then what I had when I went from CV1 to Rift S... G2 is probably better, but it's twice the price and my system probably won't be able to handle it as good as Quest 2... P.S. Probably worth noting here, with Rift S the whole screen is evenly sharp, but with Quest 2 I found that center is sharp, but things get blurry towards the edges. Perhaps a smaller sweet spot. I really need to experiment more and probably get alternative face shields to see if I can fix it. It was really bothering me the first time I put the headset on, but I got used to this in about an hour/two and no longer notice it all that much.
  10. Just a quick heads up if anyone gets into the same problem... Virpil Support rescued the day for me - in Configurator tool settings (CTRL + F12) I had to enable 'Show Developer information (SetPCB)' option. This enabled manual selection of the base's PCB via a dropdown near the bottom edge of the app window. Once proper PCB was selected, everything started working.
  11. So there seems to be a lot of 'first look' videos on YouTube, but I don't think I've seen any comprehensive reviews on either Libra or the new Orion. Are they worth the price? How's the feel of the movement, adjustability? How do these stack up against Virpil's Mongoost/Warbird?
  12. Yes, I only have Virpil's T50 base and grip. I've actually tried flashing on my other computer too where this would be the only joystick to be connected at all...
  13. Thanks a lot for the heads up - sure was worth a try. Sadly, same result as before.
  14. Thanks a lot, I actually stumbled across this page yesterday. Unfortunately resetting my firmware by shortening the pins did not resolve my problem. It looks like joystick flashes and updates firmware just fine via either VPC software or by first removing existing firmware via shortening pins as described in the link - I can see name update based on the firmware version in VPC software.
×
×
  • Create New...