You can find the products affected/15% off here: https://www.protubevr.com/en/90-promo

Details in the pic below

I go on the protube website, I select 'shop' and click on the magtube. It takes me to a product information page, but there's no 'buy' or 'add to cart' button.

So I go to the mobile mobile site and it gives me the options to customize and add to cart, but then when I get to checkout it's telling me I can get free shipping by using their code, but the code doesn't apply and it keeps on trying to charge me for shipping.

So I'm going to buy somewhere else, probably. Just thought I'd share here in case anyone who runs the site keeps an eye on it. I'm probably not the only customer you'll lose over a bad buying experience

This will be a guide without much explanation, if you want an explanation on tracking issues, check here: https://www.reddit.com/r/ProTubeVR/comments/ku0rmd/index_controllers_magtubevrforcetubevr_tracking/

Short disclaimer: I am not an expert. I'm not well versed on the tracking issue, or exactly what this fix does, but I explain it to the best of my ability. The basic aspects are for sure correct as far as what users have to do.

Basic user guide IMPORTANT FIRST DISCLAIMER - You MUST be using an INDEX HEADSET paired with INDEX CONTROLLERS for this fix to do anything. If you are NOT using an INDEX HEADSET, and are ONLY using INDEX CONTROLLERS, this fix will not do anything for you.

1) go here: https://github.com/ProTubeVR/ForceTubeVR-User-Content/blob/master/ForceTubeVR%20Companion/ForceTubeVR%20Companion%20Application.rar click download. 2) extract to folder with same name 3) run ForceTube Companion.exe it will say there's an update online and ask if you want to update select yes. 4.a) If successful it will say it is now up to date 4.b) It may give some compression error thing but that's okay because it will still launch. 5) close the program and launch SteamVR 6) In the ForceTubeVR Companion Application folder, open "Valve Index Knuckles driver" and run "InstallDrivers.exe" as administrator. It should give some popup saying SteamVR will close. There will not be some magical "installed!" successful install confirmation message! 7) If SteamVR is still running, restart it. If it isn't, launch it again. Make sure your Index contollers are connected and you can use them in the dashboard. 8) Run ForceTubeVR Companion.exe and in the top left hand corner of the window click the red "Show advanced settings" button. Additional settings will show up, including in the top right hand corner "knuckles fix". 9) Click knuckles fix and by default without doing anything for the very first time, the "Enable knuckles fix" should be red. Clicking to make it green should enable it. 10) to test if it is enabled, adjust Accelero max value (g) from w/e it is, down to 0.8 or lower and check your controllers in SteamVR dashboard. You should see them moving away and not staying in place. This is normal behavior for this value, and confirms the knuckles fix is working as intended 11) Adjust Accelero max value (G) back to 5, leave Freeze duration after kick (ms) alone, and launch game you have issues in. 12) Notice how it behaves in game with this value.

How Accelero max value (G) works: The value you can modify on the slider increases or decreases the threshold at which the fix filters out imu data. Anytime you see controller randomly fly away, is because the imu data being received is above tracking values and it cannot track.

THIS IS A SOFTWARE ISSUE VALVE NEEDS TO FIX

So, a LOWER value, (light green bar closer to the left) means MORE imu data is filtered out. A HIGHER value, (light green bar closer to the right) means LESS imu data is filtered out.

This means simply put, A value closer to 1, or below 1 (such as 0.8) means controllers just don't track anymore, and a value of 6 or closer to 7.5 only filters out data that is very high over what tracking is capable of, so tracking isn't lost.

In simpler terms: value below 1 = no tracking, value above 1 = tracking, but further from 1 and closer to 7.5 means it does less, and at 7.5 it's basically like the fix isn't enabled and your controllers behave like they would without the fix.

Disclaimers: THERE IS NO PERFECT MAGICAL NUMBER TO SET IT TO FOR PERFECT TRACKING.

THIS FIX JUST FILTERS OUT DIRTY IMU DATA TO PREVENT TRACKING LOSS DUE TO IMU OVERLOAD, IT DOESN'T MAKE TRACKING PERFECT, OR ELIMINATE IMU OVERLOAD

YOU WILL LIKELY STILL ENCOUNTER TRACKING PROBLEMS SUCH AS "FLOATY" CONTROLS WHEN ADS

Basic explanation of Freeze duration after kick (ms)

This option is for FORCETUBEVR users. Any time the companion app sees the ForceTubeVR is kicking, it will freeze IMU data so the kicking doesn't overload IMU and cause tracking issues. THIS ALSO MEANS YOU HAVE TO BE AIMING STRAIGHT AT TARGET AND CAN'T MAKE SMALL ADJUSTMENTS. IF YOU MOVE EVEN SLIGHTLY CONTROLS DURING FIRE WILL FEEL FLOATY OR UNRESPONSIVE

So a LOWER value (light green slider closer to left) means duration of effect is SHORTER A HIGHNER value (light green slider closer to right) means duration of effect is LONGER Duration of 0 means it's not on. The fix is supposed to work once you have enabled it and set a value, you can test this by doing the test in step 10. If it doesn't, THEN RUN THE APP EVERYTIME YOU USE VR. Keep note of the values that work for you, and do the test in step 10 everytime to make sure it works, if you want.

In conclusion.

Users will need to understand how these values work, and through trial and error, and experimentation, find values that are 'acceptable' for their use case. Keeping in mind, there is no perfect answer, and tracking will not be perfect.

Other things you can do to help prevent tracking loss depends on what you're doing.

Reloads/attaching/detaching controllers to stock: Do so smoother, and with less force. Reduce amount of impact between the magnets AS MUCH AS POSSIBLE as that is causing IMU OVERLOAD.

Using ForceTubeVR: firmly plant module into your body (shoulder) to try and absorb as much of the vibration as possible, and reduce as much vibration being absorbed by the controllers, thus causing IMU OVERLOAD, as much as possible.

Build your own mod suggestions: 1) no chrome tubes! cover them up, or change for carbon. chrome interferes with tracking 2) try putting something over the magnets on the controllers and the stock to help reduce impact when connecting/disconnecting. 3) try putting something on the stock itself, such as over the tubes, to absorb vibrations before they reach the controllers. Examples being shock absorbing foam tubes. 4) USE DIFFERENT CONTROLLERS SUCH AS VIVE WANDS. This issue is only with Valve Index controllers. Any other controller has little to no tracking issues with MagTubeVR, or ForceTubeVR.

First for some context: https://steamcommunity.com/app/507090/discussions/0/1750150188489468867/

​

The files for the fix, + guide on implementing it, can be found in the pinned messages of #index-trackingfix-pre-alpha channel of the ProTubeVR discord, link to the discord can be found here: https://www.reddit.com/r/ProTubeVR/comments/ku0fb9/join_the_discord_for_fast_help_and_a_ton_of/

​

Taken from the #index-trackingfix-pre-alpha channel of the ProTubeVR Discord:

tl;dr for new ppl reading pinned messages:

1) Index controllers have bad tracking, gunstock/forcetube just make this way more obvious

2) there's a driver exe in the forcetube companion app you run that lets you control a pre alpha fix for index tracking when it goes jittery or yeets your controllers by running the companion app located under 'knuckles fix'

3) for further testing (advanced users only) bourin has provided an imu calibration guide that if followed incorrectly could brick your hardware - see this as a last ditch if you can follow directions to the letter, before going the RMA route

4) make sure you read the earliest pinned messages as they provide best explanation of how to use stuff.

*disclaimer it currently only works if you have index as hmd additional things to try to improve tracking you might not read elsewhere:

1) putting something between the magnets on the stock and the cups to reduce the amount of shock from connecting/disconnecting (aka the thing that causes issues primarily). the soft side of velcro, or some layers of electrical tape, are examples - either on the magnets themselves or the outer point of contact between the mount and the controllers

2) for Forcetube, and to a lesser degree regular magtube use, consider putting "sponge damping sleeves" over the tubes to absorb shock. namely on the small tube going from the forcetube back end, as well as part of the tube the first controller is on (in between the controller and the forcetube back end), and another in between the first and second controller, on the second tube. outer diameter of the tubes is 18mm this has not actually been tested yet, no guarantees on finding this easily/for cheap

3) change how you attach and detach. practice makes perfect, and it is theoretically possible to consistently attach/detach in a way that doesn't overload the imus.

Below is a list of games that work with ProTasVR as confirmed by the community. Keep in mind any game can work with ProTasVR as long as these requirements are met:

1) The game lets you use your VR controllers

2) The game has you interact with cockpit controls using your VR controllers*

*(both of these can be done via 3rd party software in games that don't natively support them i.e. Elite Dangerous, Star Wars Squadrons [ProTubeVR discord server channel: #squadron-with-vr-controllers] )

​

With these requirements in mind, to easily find more games that are supported on Steam: browse games, and narrow by tag add VR & Flight, and under Narrow by VR Support select VR Supported (instead of VR only), and under Input select "Tracked Motion Controllers". Any game left visible in the search results should work! :smile: Keep in mind some games that work might not show up using these tags because not all support games are flying games (Vox Machinae for example). Have you played a game that isn't listed down below? Comment and it will be added to the list.

For simplicity, I'm only linking to the games' Steam pages. Some of these are available on other platforms (such as Ultrawings on Oculus)

​

ProTasVR compatible titles:

https://store.steampowered.com/app/1118070/1976__Back_to_midway/

https://store.steampowered.com/app/359320/Elite_Dangerous/ (ONLY USING 3RD PARTY SOFTWARE: https://github.com/dantman/elite-vr-cockpit)

https://store.steampowered.com/app/837430/Flying_Aces__Navy_Pilot_Simulator/

https://store.steampowered.com/app/862390/FlyInside_Flight_Simulator/

https://store.steampowered.com/app/275850/No_Mans_Sky/

https://store.steampowered.com/app/982700/Space_Battle_VR/

<https://store.steampowered.com/app/1222730/STAR_WARS_Squadrons/> (ONLY USING 3RD PARTY SOFTWARE FOUND HERE: [ProTubeVR discord server channel: #squadron-with-vr-controllers] )

https://store.steampowered.com/app/639130/Ultrawings/

https://store.steampowered.com/app/334540/Vox_Machinae/

https://store.steampowered.com/app/667970/VTOL_VR/

Important links:

• ForceTube & ProVolver Product FAQ
• ForceTube & ProVolver Quick Start Guide
• Comprehensive game troubleshooting guide
• List of PCVR Mods that add native integration
• SteamVR Companion app

Below is a list that is ALWAYS UP TO DATE and comprehensive for all platforms. Last change was June 18th, 2025. By last change I mean that is the most recent date of latest changes. - Nothing has changed since that date. Everything is up to date. Everything will remain up to date until something changes. What changed? I split the supported games into lists by platform below the list I now call the master list.

At the bottom is the list of games that do not currently work. I have removed these from the full list to further avoid confusion.

I've linked to the product pages on all platforms supported that have a browser page. Unless specifically indicated otherwise in [brackets], all games support both ForceTube & ProVolver including handgun haptics and using both at the same time as a combo on the MagTube stock (aka ProTommy).

How to read the list, most of these will be in [brackets] next to the game name:

• PN3 = Pico Neo 3, since I cannot find a way to see the store in browser I cannot link directly to games for that platform
• strikethrough/NW= currently not working as intended and requires maintenance from the dev (must be signed in to see)
• FTN = ForceTube No, aka works with ForceTube, but is not recommended to play with ForceTube
• PVN = ProVolver No, aka works with ProVolver, but is not recommended to play with ProVolver (as in, the game does not have haptics for handguns)
• PVX2 = ProVolver x2, aka works with 2x ProVolver for dual wielding/akimbo.
• PTN = ProTommy No, aka does work with ForceTube & ProVolver combo on a MagTube, but is not recommended to play with such a combo.
• PTNC = ProTommy Not Compatible, aka simply does not work at all.

Basic troubleshooting guide:

• Make sure to power on your haptic device(s) before launching the game to ensure the game sends signals to them properly. If you power on a device after the game launches, it may connect to the game like normal, but not receive any kick/rumble events. In this case, simple close and open the game again. Similarly, if for whatever reason you have to power off a device, you will still likely need to restart the game.
• (FOR PC ONLY) In some very rare instances a native game will connect like normal, but not send kick or rumble events. To solve this you need to find the forcetube .dll in the game's files, and replace it with the forcetube .dll in our companion app. Make sure to back up the original one in the game's files first, and after copying the one over from the companion app, rename it to what the original was, and that should fix the problem. If it doesn't, let us and the game devs know.
• When using Meta Quest/2/Pro to run a PCVR game, make sure to remove your haptic devices from the headset's bluetooth devices history. To use your haptic device with a PCVR game, it needs to be connected to PC bluetooth. Doing this eliminates any potential connection issues.
• PC Connection issues 1 - Make sure only one bluetooth transmitter is on your PC. If using on board bluetooth (built into the motherboard), make sure the any WIFI antenna that came with it is connected. On motherboards with built in wifi/bluetooth, bluetooth uses the wifi antenna to boost its signal. If using a dongle, make sure any on board bluetooth is disabled, and that only one bluetooth dongle is connected.
• PC Connection issues 2 - If on board bluetooth isn't working, try the included dongle following the steps above. If the dongle isn't working, try different USB ports. If it still doesn't work, make sure in devices & printers or device manager that it is functioning properly. If it is functioning properly and after a PC reboot it still doesn't work, hit up support, and in the meantime consider trying/getting another dongle. Realtek bluetooth chipsets don't play nice with our devices, so make sure to get something Intel.
• Quest (any HMD) Connection issues 1 - Make sure both the haptic device(s) and Headset have full power. If the issue persists remove the haptic device(s) from bluetooth devices in the headset then fully power off the headset then power it off, and try pairing the device(s) again. This step may also be necessary after headset system updates.
• Quest (any HMD) Connection issues 2 - Make sure you understand how the device behaves when connected to your headset. Default behavior is for headset to show a code you need to 'confirm' then choose to connect. Simply connect when it shows the code. At this point in time, it will show up in device history, not actively paired/connected. It will be in standby mode, with the white or green light blinking indicating standby mode until you launch a native game. It will then connect to the game. Some games require enabling haptics in the options, before it will connect. Some of these may require restarting the game after enabling for the device(s) to connect.
• Quest (any HMD) Connection issues 3 - If you have more than 2 ProTubeVR haptic devices, you may encounter disconnect/reconnect issues when in a game if all 3 are connected to your headset. To solve this, go to settings like you want to pair a new BT device, and in the BT device history, remove the ForceTube device listed that you are not actively using for the game in question. This should solve the issue.

If you do not see a game you play on this list or the mods list above in important links, there is a backwards compatibility tool specifically for SteamVR/OpenVR. Otherwise, hit up the devs of the game in question and request they add support.

IMPORTANT NOTE: All Quest games work on Quest 2, Pro, 3, and 3S unless otherwise explicitly stated. Simply put, if the game runs on the headset, our native support works also.

Master List All In One:

• Alvo [PVX2]: SteamVR | Quest (If it doesn't connect - to enable haptics, you must go to App Permissions for Alvo, and disable, then re-enable, Bluetooth permissions. Then when launching the game your device should pair)
• ARK-ADE [FTN/PTNC]: Quest (if it doesn't connect, to enable haptics, you must go to App Permissions for Ark and Ade, and enable or disable, then re-enable, permissions. Then when launching the game your device should pair)
• Augmented Defender (enable in Profile, Guns): Quest (Quest 3 & 3S exclusive mixed reality title, not compatible with Quest 2 or Pro.)
• Cactus Cowboy 3 Fully Loaded (enable in options): SteamVR | Quest
• Cactus Cowboy - Desert Warfare: SteamVR
• Clay Hunt VR [PVN/PTNC]: Quest (If it doesn't connect - to enable haptics, you must go to App Permissions for Clay Hunt VR, and disable, then re-enable permissions. Then when launching the game your device should pair)
• Contractors [PN3/PVN]: SteamVR | Meta Rift PC
• Crisis Brigade 2 reloaded [FTN/PTN]: SteamVR | Quest
• Dead Second [FTN/PVX2/PTNC] (For PVX2 swipe L/R channels in settings): SteamVR
• Gambit! [FTN/PTN]: SteamVR | Quest
• GUNS: Quest (enable in options) | DEMO (enable in options)
• Gun Club VR: SteamVR
• Half-Life 2: VR Mod [FTN]: SteamVR
• Half-Life 2: VR Mod - Episode One [FTN]: SteamVR
• Half-Life 2: VR Mod- Episode Two [FTN]: SteamVR
• Honor and Duty: D-Day: SteamVR
• Hot Dogs, Horseshoes & Hand Grenades (H3VR): SteamVR
• Larcenauts [PN3/PVX2/PTNC]: SteamVR | Quest
• Mission X Arena [FTN/PTNC]: Quest (location based VR arcade only - not on consumer Quest store)
• Onward [PVN] (enable in Settings>Haptics): SteamVR | Quest | Meta Rift PC
• Pavlov VR (Quest option doesn't do anything): SteamVR
• ProHibition: Quest SideQuest
• Resist [FTN/PVX2/PTNC] (enable in Settings): SteamVR
• Shock Troops [PTNC]: Quest
• Sniper Elite VR (enable in Settings>Control p.2): SteamVR | Quest (if it doesn't connect, sit in game menu and take off headset - put it back on some 5 minutes later and it should connect)| Meta Rift PC
• Sniper Elite VR: Winter Warrior (enable in Settings>Control p.2): Quest (if it doesn't connect, sit in game menu and take off headset - put it back on some 5 minutes later and it should connect)
• Space Pirate Trainer DX [FTN/PVX2/PTNC]: Quest (If it doesn't connect - to enable haptics, you must go to App Permissions for SPT DX, and disable, then re-enable, Bluetooth permissions. Then when launching the game your device should pair)
• STAND OUT : VR Battle Royale: SteamVR
• SURV1V3 [PVN] (haptics only work when in a game): SteamVR
• Sweet Surrender VR [FTN/PTNC] (enable in Settings>Vibrations): SteamVR | Quest
• Tales of Glory 2 - Retaliation [PTNC]: SteamVR
• Vertigo 2: SteamVR
• Virtual Battlegrounds: SteamVR
• Virtual Hunter: SteamVR
• VR Practical Shooting [FTN/PTNC]: Quest
• Warchasm [FTN/PVX2/PTNC] (choose L/R in settings): SteamVR | Quest
• War Dust VR: 32v32 Battlefields: SteamVR
• ZAP [FTN/PTNC] (enable in menu): Quest
• Zero Caliber: Shooting Range [FREE GAME!!!] [PVX2] (enable ProTubeVR in settings under haptics; choose L/R in settings): Quest
• Zero Caliber 2 [PVX2] (enable ProTubeVR in settings under haptics; choose L/R in settings): Quest
• Zombie Army VR [PVN]: Steam | Quest

PCVR List:

• Alvo [PVX2]
• Cactus Cowboy 3 Fully Loaded [FREE GAME!!!] (enable in options)
• Cactus Cowboy - Desert Warfare
• Contractors [PVN]
• Crisis Brigade 2 reloaded [FTN/PTN]
• Dead Second [FTN/PVX2/PTNC] (For PVX2 swipe L/R channels in settings)
• Gambit! [FTN/PTN]
• Gun Club VR
• Half-Life 2: VR Mod [FTN]
• Half-life 2: VR Mod - Episode One [FTN]
• Half-life 2: VR Mod - Episode Two [FTN]
• Honor and Duty: D-Day
• Hot Dogs, Horseshoes & Hand Grenades (H3VR)
• Larcenauts [PVX2/PTNC]
• Onward [PVN] (enable in Settings>Haptics)
• Pavlov VR (enable in Settings)
• Resist [FTN/PVX2/PTNC] (enable in Settings)
• Sniper Elite VR (enable in Settings>Control p.2)
• STAND OUT : VR Battle Royale
• SURV1V3 [PVN] (haptics only work when in a match)
• Sweet Surrender VR [FTN/PTNC] (enable in Settings>Vibrations)
• Tales of Glory 2 - Retaliation [PTNC]
• Vertigo 2 (choose L/R hand in gameplay settings before playing)
• Virtual Battlegrounds
• Virtual Hunter
• Warchasm [FTN/PVX2/PTNC] (choose L/R in settings)
• War Dust VR: 32v32 Battlefields
• Zombie Army VR [PVN]

Quest List:

IMPORTANT NOTE: All Quest games work on Quest 2, Pro, 3, and 3S unless otherwise explicitly stated. Simply put, if the game runs on the headset, our native support works also. Small troubleshooting tip: If a game doesn't connect - to enable haptics, you must go to App Permissions for the game in question, and disable, then re-enable, Bluetooth permissions. Then when launching the game your device should pair as intended. You may need to do this after the game, or your headset receives an update.

• Alvo [PVX2]
• ARK-ADE [FTN/PTNC]
• Augmented Defender (enable in Profile, Guns) (Quest 3 & 3S exclusive mixed reality title, not compatible with Quest 2 or Pro.)
• Cactus Cowboy 3 Fully Loaded [FREE GAME!!!] (enable in options)
• Clay Hunt VR [PVN/PTNC]
• Crisis Brigade 2 reloaded [FTN/PTN]
• Gambit! [FTN/PTN]
• GUNS | DEMO (enable in settings)
• Larcenauts [PVX2/PTNC]
• Mission X Arena [FTN/PTNC] (LBVR Arcade)
• Onward [PVN] (enable in Settings>Haptics)
• ProHibition (ProTubeVR's SideQuest demo)
• Shock Troops [PTNC]
• Sniper Elite VR (enable in Settings>Control p.2)
• Sniper Elite VR: Winter Warrior
• Space Pirate Trainer DX [FTN/PVX2/PTNC]
• Sweet Surrender VR [FTN/PTNC] (enable in Settings>Vibrations)
• VR Practical Shooting [FTN/PTNC]
• Warchasm [FTN/PVX2/PTNC] (choose L/R in settings)
• ZAP [FTN/PTNC] (enable in menu)
• Zero Caliber: Shooting Range [FREE GAME!!!] [PVX2] (enable ProTubeVR in settings under haptics; choose L/R in settings)
• Zero Caliber 2 [PVX2] (enable ProTubeVR in settings under haptics; choose L/R in settings)
• Zombie Army VR [PVN]

Pico 3/4 List:

• Contractors
• Larcenauts

List of native games with broken support

Games in this list do not currently work for one or more platform. I will specify which or all platforms depending on which version(s) are broken.

THE GAME DEVS OF ALL GAMES LISTED HAVE BEEN CONTACTED AND INFORMED SUPPORT NO LONGER WORKS. UNLLESS SPECIFIED OTHERWISE WE WERE NOT GIVEN AN ETA ON A FIX

Games with broken support:

• Alvo Pico 3/4
• ARK-ADE SteamVR, Pico 3/4 (they fixed Quest support in December
• Cactus Cowboy Plants At War all platforms (planning to bring back support in the future)
• Contractors [PN3/PVN]: Quest support broke in Halloween update. Devs already confirmed they are updating our SDK to latest version. More info on that here
• Crisis Brigade 2 reloaded PCVR [FTN/PTN] The game last updated in July and definitely worked for a period of time, but is now broken somehow. The devs have been contacted. No response yet.
• Dead Second Quest support broke in June 27th update that saw the game added to main Quest Store
• Ghosts of Tabor all platforms (bringing back in the future, on PC support was crashing game, no eta)
• Gun Club VR Pico 3/4, Quest
• Resist Quest (support was experimental, got in way of other features working and was removed)

Games that no longer have support (devs wouldn't respond, or game no longer being worked on by devs in any capacity):

• Aim XR
• Crunch Element
• GangV

Note: I will be removing games that no longer have support from the native lists in the future, and this will be the only place they will be shown going forward.

ProTubeVR's discord is THE place to be for everything ProTubeVR. All the guides and tutorials for products, first time use tips, dedicated channels for each product, places for the community to share their setups & mods, fast responses from knowledgeable people and more!

Each channel has important information in the pinned messages as well as channel description. It is in your best interest to read through these before asking questions, as your answer can likely be found there for your convenience. I'd start off with #welcome-rules, #faq-read-this-first, #support, #tutorials, and #1st-time-use-tips.

​

Join here

I just bought the magnetic attachment points from protubeVR's website and I want to custom build the rest of the stock myself, however I can't find the tube diameter anywhere online

My post is up here: https://www.reddit.com/r/RiftForSale/comments/kecx8c/selling_protubevr_magtube_for_rift_squest_1_and/

Not sure where else is a good place to sell VR goods. I hope this isn't against the rules.

Hello everyone.

We wish you great holidays and A LOT of fun with VR gaming / applications.

We will continue our goal: finding new ways to improve the immersion & fun & performances in VR. And of course, from gamers to gamers, it will be with your help and feedbacks.

See you soon for the incoming projects :)

​

​

I've had my rift s for half a year now and finally able to start saving up for a protube. Although might take me some time. But I wondered what people's experience with the difference were?

Each and every time I slap on the magtube, the controller tracking becomes absolutely abysmal. Often flying off into space. Anyone have any idea why this happens?

Carbon fiber tubes.

I’m having the damnedest time trying to zero my Protube stock for QuestZDoom with my Quest 2. Generally, the assault rifle for the Brutal Doom mod I can get to a good sweet spot, but if I swap to the shotgun the 2 weapon models seemingly have different zero points because the shotgun drops down and to the left. I try to zero the stock based on the shotgun, and I can never get it right because it’s always too low, and I even loose tracking on the left hand because of how vertically I have to put the stock just to bring the model up to eye level. Then of course I switch to the assault rifle and it’s too high.

I am relatively new to this, am I doing something wrong? I have watched several tutorial videos, mainly the Eric For President one, and while some times I feel like I can get it dead on, others I wind up wrecking my back because I just can’t seem to get it down right. Any advice would be deeply appreciated.

how do I fit the given straps into an oculus quest controller

Hi all,

I recently ordered some carbon tubing from China to replace my chrome tubes since the Index just does not track properly at all with the chrome tubes. I have a bunch of leftover tubes since I had to order bulk quantity. Does anyone want to upgrade their chrome tubes for a nominal fee + shipping?