Closed corriedotdev closed 5 years ago
You need to provide better steps to reproduce. I have no idea from your steps how to recreate the issue,
Will try and recreate with the standard example with climbing wall. Update: @thestonefox can I share an exe link to a demo with the issue. There are no errors in the game and no way I can see to recreate but its consistent using this example. Its just using the same camera rig system as the example. Cheers.
If it can't be recreated consistently then it becomes very difficult to debug unfortunately.
Still working on trying to recreate and have been for some time as we are wanting to release without this issue. Screenshot does show something though, the player has launched themselves forward then getting stuck in mid air, if they take a step in physical space they fall again.
Thanks for your time, but are there any attributes on the players collider mesh that could be linked to sticking to surfaces. The objects dont have material attributes like bounce etc so was curious if the player had it? It seems something related to the player hitting the play space!
Still working on it, but if theres any thing anyone can think of regarding player physic attributes that we can play around with and adjust values that would be a good start!
Update: Managed to recreate quite simply in the test scene.
Attempt to grab a blue cube from an edge and proceed to throw yourself towards the edge or face. Not on top of but at the edge itself. After an attempt or two I was able to recreate quite easily.
A demonstration of this can be found at the link below. I have attempted to try and debunk it myself for a month but no avail.
You need to provide steps to reproduce in an example scene
Its very easy to recreate once you know how to throw yourself to the object. The GIF linked above is an visual representation on how to do it.
I'll try to repro it. Sounds like the falling state might be getting tripped up. Are you on latest @corriejgreen? I fixed a similar issue several months ago.
@mattboy64 I think I'm a version behind. Just updated to latest and will experiment. Will update in the next day or two once I have resolved any conflicts.
There is definitely something off with climbing and triggers. I have found that if I am already within a trigger and I start climbing (I am talking about climbing where you throw yourself upwards, i.e. you aren't always holding onto the wall), everything is fine, but if I hit a trigger above me while climbing and throwing myself upwards, I get sent back to the ground or the play area bucks around wildly.
Update to this as i have just gotten around to importing the 3.1.0 > 3.2.0
I have imported the latest version and still getting the issue, i should fall to the ground if the gameobject im on has fallen no?
1) If i land on a moving gameobject, where is the check to fall to the ground as it isnt triggered 2) If i throw myself onto the object and land just on its edge (a cube) i get stuck there and it doesnt always push me ontop or let me fall.
Im still investigating, if anyone has any ideas please share. This is recreatable in the latest version of vrtk.
Latest version of VRTK is 3.3.0, have a test with that. It won't probably change anything but then you are at least on the same version everyone else is on.
For troubleshooting is a better support channel to use, GitHub issues isn't great for discussions.
On it @bddckr updated to the latest and working on repo. Have a month to solve the issue now.
Cheers
Closing this as it's related to an older version of VRTK (v3.3) the master branch is now on VRTK v4. Feel free to request to reopen if the issue is still present.
Environment
Steps to reproduce
Game Builds using the climbing rig from the climbing demo. On some game builds the user will select an object, try to launch themselves up onto a ledge or to an area, but will soon hit an invisible collider - feels like an invisible wall around the blue playspace grid if enabled.
Expected behavior
The player should be able to launch themselves into space, to grab an object or complete an action.
Current behavior
Sometimes - same assets used in another level work for example. Levels one works fine on the project but levels two and three SOMETIMES have this invisible wall issue on a game build, not unity editor runtime.
If anyone has a remote idea on what could be causing this do let me know, its possible ive changed something but the game works flawlessly in the engine but have this issue on game builds.