Jump to content


  • Content Count

  • Joined

  • Last visited

About mx22

  • Rank
  • Birthday November 25

Recent Profile Visitors

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

  1. Ahh yes, sorry I was looking at the menus - I thought it would work like the VR mod previously and would render mask everywhere...
  2. How did you enable the mask? At least by default, I don't have one enabled and get the whole right/left eye render.
  3. 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
  4. 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.
  5. 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?
  6. 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...
  7. Thanks a lot for the heads up - sure was worth a try. Sadly, same result as before.
  8. 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.
  9. Just wondering if anyone came across similar issue. I've decided to check VPC software out and sure enough, I needed to flash joystick's firmware - firmware failed on the last step (after flashing the software and auto-rebooting joystcik) with an 'ERROR. Device PCB' message. Sadly, now joystick is no longer listed in Windows 'USB game controller' so I cant use it. VPC Configuration Tool however still sees it, however when trying to re-flash firmware I still get the same error with the same results. I've tried clicking on 'restore factory defaults' in the firmware updater, but it throws the err
  10. Would you mind sharing your kneeboard?
  11. Yes, I've deleted the whole DCS.openbeta\Config\Input\FW-190A8 folder before reinstalling the module. I did not try changing controls after the reinstall, so I don't even have this folder anymore...
  12. Controls are messed up For some reason all of my controls are messed up - there are a lot of duplicate entries: Also, my stick section appears to be all mixed up and looks different than what other users have (there is a thread in the main forums with screenshot): I've tried running DCS repair, as well as deactivating module and installing it from scratch, but still having this problem. Is there a specific file that I should perhaps try deleting? Thank You!
  13. I don't have 'a' or 'b1' options under stick category: Am I missing something?
  14. Can you tell me the names of your assignments and what they do? I already tried all possible options under 'Stick' menu (except of 'MG131 fire' which cannot be used on my end at all) and can't get wing cannon to fire. MG131/151 controls cowl gun only. Thanks!
  • Create New...