A public issue, wiki and roadmap only repository for the NeosVR project.

Issues are used to discuss items such as Bug Reports, Feature Requests and Documentation requests with the Neos Team. You can find the issue list here

If you'd like to make a new issue you can click here to start the process. You'll need a GitHub account to make issues and one can be created by clicking here

Please do not submit security exploits to the public GitHub. You can report them privately at https://moderation.neos.com

If your issue directly relates to another user or group rather than a general bug or feature requests for the software, please make a ticket at https://moderation.neos.com instead.

• Be as descriptive as possible. Explain what happened prior to problem, what does the problem look like and what you expected instead. The better the description, the less back and forth will be needed and the greater likelihood of getting the issue solved
• If you experience a problem, make sure it’s reported. If you wait for someone else to report it instead or the developers to notice themselves, it might not get fixed for a long time (or at all)
• See if you can find a way to reliably replicate the bug. If the developers can reproduce the bug on their end, it significantly helps with its resolution
• If you experienced a bug, including the log files can significantly help in resolving the issue. See here how to find the logs: http://wiki.neosvr.com/subdom/wiki/index.php?title=Frequently_Asked_Questions#Where_can_I_find_log_files.3F
• If you have crashed, frozen or encountered hardware issue, include the additional Unity log as well.
• If you have crashed or frozen, check for crash dumps and include those as well
• Even if your exact suggestion isn’t implemented, it’s still very useful, because it helps us see what issues you’re dealing with and incorporate those into future decisions, or address the problem in an alternate way
• Please keep issues on topic and conversation calm and factual. Bringing emotion makes issues harder to deal with and will only hurt their resolution and impact our overall development speed. Remember we're human as well.

If you're unsure about an issue and want to ask others or solidify your report before you post, you can use the #bugs-and-feedback channel in our official Discord (https://discord.gg/neosvr). Please be aware that things can get lost in the flow of conversation or might not get immediate response. If you want to make sure the issue is logged and doesn’t get missed, always log it on GitHub after the discussion.

Due to a wide variety of models, rigs and types of files, not all of them will import correctly. You might encounter things like:

• Vertices being randomly messed up, stretching where they shouldn’t (either with static model or when using blendshapes)
• Model failing to import at all or crashing Neos
• Fingers being mangled after avatar is equppiped

If you can share the model file itself, send it over to developers for testing. This significantly increases the chance of the issue being fixed, as we can analyze what is going wrong with the file.

At any time, there are many different features and issues that we’d like to implement or fix, but there’s only a few that can be worked on at the time. There are several factors that determine the priority:

• Severity: If it’s something with serious global impact on usability or security of users, it will be very high on the list.
• Demand: The more people request a given feature or issue to be fixed, the higher its priority. This changes over time, so don’t hesitate adding your voice even if it was already requested. Becoming a supporter or donating will give your requests higher priority as it helps grow and support our team
• Complexity: Some things are significantly quicker to implement/fix than others. If something is a trivial fix it might get addressed very quickly even though it doesn’t have as high demand or severity
• Prerequisites: Certain features or issues cannot be (efficiently) addressed without other, much bigger features or architectural changes done first. Our goal is long term sustainability and stability of the codebase, so certain things can take a lot longer to get addressed despite the demand. We will try to communicate whenever this is the case.

Note that the priorities are constantly shifting and evolving based on the feedback and demand from you, the community. If something is determined to be low priority at the moment, it doesn’t need to stay that way, just make sure your voice is heard through the right channels and we’ll listen!

If the request is not feasible on our end, we'll try to offer alternatives or explain why it can't/won't be implemented. We knows it sucks getting a request denied, but we'd rather be upfront about it rather than give an empty promise on something we know we can't deliver.

Sometimes you might also see certain features being done out of order completely. Developing can be quite draining task sometimes and we like to work on certain things just for fun or for the satisfaction of it to refocus our brains. Plus it makes sure that certain low demand, but nice things get attention from time to time too!

You can vote on any issue by clicking the Emoji button at the top right of the original post and adding a +1 (thumbs_up). This allows the issue queue to be sorted by number of reactions.

• Issues sorted by votes

If you're a Patreon supporter you can also vote on the issues by sending /priorityIssue <issue number> command to the "Neos" bot account in Neos (make sure your Neos account is actually linked to Patreon). Currently you can have 1 issue set as your priority, you can change your vote at any time. The score is proportional to the level of support.

• Patreon Priority Issues

This repository also contains Neos Roadmap, you can find this here