Skip to content
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

Enable physics when cart is off-rail #24

Open
R-0ne opened this issue Jul 7, 2018 · 4 comments
Open

Enable physics when cart is off-rail #24

R-0ne opened this issue Jul 7, 2018 · 4 comments
Labels

Comments

@R-0ne
Copy link

R-0ne commented Jul 7, 2018

Hello,

Would it be possible for the cart to leave normal rails if it does not meet a stop rail for example ? this would allow to drop the cart several blocks at once to fall back on rails for theme park maps for example.

thank you

@SmallJoker
Copy link
Owner

The cart does not have physics enabled for the reason that it would break while going up- and downhill. However, it would be possible to turn that on as soon it's no longer on rails. Additionally do many cart railways rely on the behaviour that the cart stops when there's no rail to continue moving, so it should be an optional feature unless it's acceptable that carts slide away several nodes (depending on max speed).

@SmallJoker SmallJoker changed the title possible improvement of cart ? Enable physics when cart is off-rail Jul 7, 2018
@benrob0329
Copy link

I feel like making railways add a break or start/stop rail is a small price to pay for being able to have much more flexible cart routing and distribution.

@numberZero
Copy link
Contributor

railways rely on the behaviour that the cart stops when there's no rail to continue moving

Does that work reliably? I had great problems with cart passing several air nodes on a laggy server.

Anyway, I’d prefer to have explicit buffer stops do the job. These are nicer and more natural.

@SmallJoker
Copy link
Owner

SmallJoker commented Jan 3, 2019

@numberZero boost_cart does not skip rail node checks (any more) due to the pathfinder algorithm I implemented a while ago. So either it's caused by an outdated clone or by a new, yet unhandled case where the cart moves but on_step is not called.
However, it's still possible that the cart does not stop at start/stop rails because the pathfinder only checks whether there are continuous rail nodes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants