As per the conversation above, our support may be lacking for several of those, but we do support them at least to a degree. My inclination is to claim support for them and improve where needed over time rather than just saying we don’t support them at all. Is everyone else on the same page here, or do we need to prune that list a bit?
iOS Support in particular is a bit tricky, specifically since we rely on Avian which stopped development at java 9, but yeah, we might just state that and fix it over time
Well thats what I was thinking. Now actually getting them to all work properly is a different subject.
But speaking of that? Who is working on jme3-vr?
I would list all of the ones that we notionally support with little asterisks next to the ones where there are caveats. Then be up front about those caveats.
We don’t support one-button push to all platforms but if you want to make a JME game on one of those platforms, you are part way there already at least.
There hasn’t been a great deal of VR-related forum activity recently. I’d suggest checking the GitHub history for jme3-vr to find out who the most recent contributor(s) were, then ask them here for status information if they’re still active.
Then have asterisk under that says Mac and IOS require extra setup or something like that.
Then double asterisk that says VR Oculus is under development.
Edit: Or instead of asterisk use bracketed numbers.
[1]
[2]
etc
I just redid the ios one. Not sure if its totaly correct because I am going off what others say. We can fix it if it’s wrong but I think its pretty close.