Open InsaneGrox opened 3 years ago
I recall this having been discussed before. The proposed mechanism/solution would be that there would be a facet that can be toggled to force priority on the dashboard in the event that it is obstructed (either visually or with a collider.)
Related issue, #500.
I don't know that a toggle is a good idea, it should just always do so. I can see situations where people turn it off and forget to turn it back on, or don't realize they toggled it off them being up the creek.
People might get confused at where little items they spawn from inventory are going at first.
They may, but I have to admit I don't see it as much different than now, things spawn behind the inventory all the time, and i have a few that spawn above and behind me.
Perhaps a message on the inventory of some kind would help that? but I truly think it is a small trade off.
I've also had situations where things I spawn, spawn above me and I have to either back up or look directly up.
People might get confused at where little items they spawn from inventory are going at first.
So I don't see that as being an issue
If it renders over absolutely everything then it will also render over your avatar as well. It would be quite jarring for your hands to disappear if you move them in front of your dash right? It should probably only selectively render over everything in non-userspace. This might be simple enough to achieve by setting a hard limit on how low the render queue can be set on materials and just have the dash a little below that or something similar.
I also suggested a culling system for this specific issue that when dash is open it basically is like a orb around you that culls away everything that could obscure the dash
If it renders over absolutely everything then it will also render over your avatar as well. It would be quite jarring for your hands to disappear if you move them in front of your dash right? It should probably only selectively render over everything in non-userspace. This might be simple enough to achieve by setting a hard limit on how low the render queue can be set on materials and just have the dash a little below that or something similar.
Would probably be fine to just have the default gloves in the dash, they already exist in userspace IIRC.
It seems like it would be more intuitive if it was simular to when your avatars hands stary too far from your local space. Only over render your dash if a significant portion is currently being obscured imo
Rendering dash over everything or culling by distance would mean the user's avatar won't be rendered, but what's worse holding an object in hand to save/send it would mean that object won't be rendered too.
This one seems to be either a duplicate of #984 or very, very closely related.
Is your feature request related to a problem? Please describe.
Currently it is possible for the Neos Dash & anything else user-space to get obstructed by accident or maliciously... This seems like a bit of a problem when the neos dash is almost vital for many things. (this should also include raycasts prioritizing the dash even when something is in the way if it doesn't already) This would also solve the issue of getting in an avatar with blindingly low near-clipping values and being unable to respawn yourself without the emergency gesture (which almost nobody knows)
Relevant issues
I couldn't find any through searching.
Describe the solution you'd like
Force userspace stuff to render over everything world space. Maybe even have this optional. I just think that I'd rather have user space stuff rendering over world space stuff looking slightly awkward over people getting in the way of my dash or even the possibility of malicious users blinding me so I can't use said dash. The radial menus already do this so why doesn't the dash?
Describe alternatives you've considered
I can't think of any that would solve my problem aside from a personal space setting or something that can outright disable screenspace stuff.
Additional context
This is primarily an annoyance concern more than anything. This should probably be implemented before neos's playerbase gets too large and to the point of where people blinding eachother becomes commonplace. (this is also a minor self-moderation concern as malicious players could blind the host and prevent them from doing anything)...