-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve collision with non-ship blocks. #9
Comments
The problem is essentially that the collision box of the moving ship is reduced to that of the player's size and not that of the ship. |
It would reduce the ammount of grief possible, making a huge barge and just clip into objects, setting it to actual blocks, and back, nom i just have eaten a chunk out of this.. whatever i clipped trough. |
This is a difficult problem to fix since collision detection is currently not possible for attached entities. However, in the current development MT builds it is now possible to change the player collision box size without effecting the selection box so in future it may be possible to increase that to the extents of the model. There will, of course, still be issues with axis-alignment as the model rotates. |
That is understandable, do you know of any preexisting issues for the engine that would allow you to implement this properly if resolved? |
I am not aware of any pre-existing issues and they'd likely be tagged as 'upstream' if there were since much of the limitation is down to Irrlicht itself. Non-axis aligned collisions may be technically possible but would require a lot of changes. |
There was a similar mod for minecraft which "solved" this by not allow the ships to turn. This could work for the mean time, perhaps a configuration setting? |
I would be fine with a configuration setting to disable turning, however, this would only be effective with the extended player collision-box, unfortunately an in-dev feature. Edit: Actually I am talking nonsense, the player collision-box is ignored because the player is attached to the controller entity. It is that which requires the extended collision-box, though still only available in-dev without making it's selection-box massive too. Another obvious limitation is that entity collision-boxes are only one single aabb box, unlike nodes that can be described by many (nodeboxes). This means there will be lot of 'false-positives' if much of the area is composed of 'air'. |
Ships tend to phase through non-ship blocks an objects. This leads to issues with replacing other blocks and objects other than the pilot getting stuck inside a ship block. It would be better if colliding with a block brought the ship to to a full stop where the pilot would have to reverse and maneuver around. See this screenshot for an example, a single cobblestone is taken up by a ship block.
The text was updated successfully, but these errors were encountered: