Rift CV1 owners are concerned at the recent decision to stop selling the Rift CV1 accessories only 6 months after the sale of the last headset. Of particular concern is the lack headset cable which is probably the most fragile component. The expectation that we should buy a whole new headset if this $50 part fails is a major concern.

Many circumstances can occur outside of warranty conditions like

* pets can chew this cable
* accidental twisting over time fatigues the cable
* accidental falls can pull the cable from the PC

All these circumstances are not Oculus' fault and should not be handled under warranty. However the end user do have the expectation that they can repair a commonly failing part for their headset.

Consumer rights in the USA are very weak and favour companies over consumers. However in the EU, Australia and New Zealand the laws state that spare parts should be available for a reasonable amount of time after the product is discontinued. 6 months is not very reasonable considering that most users have an expectation that PC components should last between 3-5 years.

Ref: https://www.consumer.vic.gov.au/products-and-services/problems-with-a-product/cannot-be-repaired

A survey of 250 Oculus users seems to suggest that most Rift owners expect to get approximately 4-5 years from their headset

https://imgur.com/8n0R2ik

Source of results can be found in comments for above image.

Many of us understand that this cable was possibly being made by a third party who has made the decision to no longer supply them to you. However you made the design decision to go with a proprietary cable so unfortunately the onus is on you to abide by consumer laws and will have to either make freely available design specifications and connector patents so a 3rd party can make them or source a new supplier for this cable so you can sell it yourself.

Your quality end user support compared to other VR headset vendors has earned you a great reputation in the VR community in recent years. This quality support has definitely helped accelerate the growth of your marketshare with as Oculus owners recommend your headset to family and friends based on how good your after market support is. Please don't tarnish this reputation and abandon the early adopters that have helped to grow your ecosystem. We want to remain Oculus customers but it becomes the standard that headsets (including the Rift-S) will be abandoned 6 months after the product is discontinued from sale many of us will have second thoughts about buying future Oculus products as well as using the Oculus store.

More voices here - https://www.reddit.com/r/oculus/comments/cynbei/for_those_who_need_a_replacement_oculus_rift/
and here - https://www.reddit.com/r/oculus/comments/cyfsk3/rift_cable_no_longer_for_sale_i_need_a/

Everyone who has upgraded to the Rift S from the CV1 has encountered a downgrade in tracking in various games. A great example would be shooter games where you have to aim down sights, which causes you to lose tracking since the controller is too close to the headset. Supporting the external cameras would allow more people to upgrade from the original rift without sacrificing their tracking. Also people with the Rift S would have the option to purchase more cameras to “enhance the experience”. The only issues that can possibly be encountered would be USB bandwidth errors from having the sensors and the Rift S, however 1 or 2 external cameras should provide a more seamless experience to the Rift S.

Tracking of the Rift S Touch Controllers seems to fail despite the controller being in plain site. In the attached video, you'll see that the initial loss is caused by (intentional) occlusion; however, the previously occluded controller isn't picked back up again despite no longer being occluded. In order to be positional tracked by the cameras again, it must be moved significantly. Note: this seems to happen if two things occur:

1. Occlusion of one controller
2. Synchronized movement between occluded controller and visible controller

This causes issues with FPS games so far, specifically ones where a two-handed pistol grip is being used. The off-hand is occluded by the gun-hand, and is moving in-sync with the gun-hand. If the off-hand is brought back into view for any reason (ex. reloading), it takes a moment for the controller's actual position to be recognized again. This results in failed actions like reloading as the hand never moves until after the player has already attempted to do said action.

On the original Rift, you could calibrate your height during setup. It allowed seated play by sitting down and adjusting your height as such so you'd be sitting and be for example 6'0 and be sitting down instead of crouching. I don't have the strongest legs and it's not comfortable for me to stand up, I'm sure people have the same issue and I've also met a few people who couldn't even move their legs and were either in a wheelchair or they just sat in bed/a chair all day exploring a new world when they couldn't with our own reality. I'm not saying to remove the whole other function for calibration, but I'm just asking you make it avaliable to those who aren't as strong/capable as others regarding their own physical health problems.

This feedback ticket is targeted for the use case of using the Oculus Rift in a business environment, but the requested feature can also benefit consumers.

Business customers can’t install the software in common network environments. Most businesses use a proxy to communicate with the internet. The Oculus installer does not respect the proxy settings of the system, causing an "e.ishttperrorcode is not a function" error when trying to create a user account or logging in with an existing one. This is not the only bug when trying to install the Oculus software from within a restricted network environment, but a major one.

Since the Oculus products and services are marketed as “Oculus for Business” one would expect the installation process to function even in a fairly restricted network environment, since that is what a majority of businesses are working with.

Either those bugs need to be solved, or Oculus needs to provide an offline installer. Ideally, it should be possible to use the Rift runtime without creating an Oculus account at all.