cb2e72f breaks attaching on everything . Locomotives can now

• pull wheelies
• if they don't like being at the front of the train , they just move anywhere they want in the freight chain
• some time they like to just move side ways because it's fun to sway.
• If a locomotive decides to quit smoking the smoke from the exhaust can be found on another car .
  Get the jest of it ? Its just a dance of chaos !

Probably a mod conflict, because these changes dont effect any of those systems.
We'd also need details how to replicate the issues if it's not a mod conflict.

Here is access to my One-drive , //link removed by eternal// , Everything in the Traincraft 5 beta directory is my testing environment , take everything including the Map and my last compile . In the Map there are a few test tracks . It is possible , it is a problem from a previous commit , I didn't compile commit since early last week

"and my last compile" so by that im guessing this isnt a release version? even though we are at release stage?
Also even for testing purposes, i need to constantly state, its against the license to distribute the jar file.

Good point , forgot that more than just you will see this . Test the map . it has some trains running that will eventually do something

Given theres no steps to replicate the errors, the only one i can get to happen is the chunkloading issue, using chicken chunks will almost always prevent the error. The sad part is that chicken chunks has become rather unreliable over the years, it was the go-to chunkloading mod back in 1.6.4.

I just had an idea for our own chunkloader that might not have a significant impact on performance, and would prevent these issues, even obsolete any need for chicken chunks.

the error in question:
http://i.imgur.com/4vlAJTZ.png

Well. It is always possible that this is not caused by TC itself. Make sure you got our latest release version and test this on a new map only with TC. We actually need the WHOLE steps to reproduce the error.

UPDATE: well apparently the fact chicken chunks prevents this error usually is an odd coincidence because we actually don't use that part of it, all of chicken core we use is for NEI.

I really don't know how to fix this error and it has plagued me since i started the port.

But long run, I can confirm the issues in this thread are in fact a duplicate of #196
and not caused by cb2e72f