Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Oh for goodness sakes. You can't fail to see that "rough handling" is a problem. Move the control one notch or twenty, EVERY movement results in a "rough handling" warning. This problem MUST be fixed, period!!
This problem MUST be fixed, period!!
This is quite intentional, and is to allow any trains that are ahead of the AI that 'SPADded' to get far enough ahead to avoid collisions/issues.as is the fixed 2min wait on SPAD
That's a pretty long list of not much information...Currently, (TNI_)physics, portals, turntables, splines, moving overlapping sliders etc. need all attention first
You seem to like making up stories based on what was intend to be a fairly quick and simple reply. There's no lost code, or even changes to the programmers in this case. However it simply has not been as high of a priority as other tasks, both new development and bug fixing/updating.A bit disturbing is if N3v can't find it in their program code.(reply #10)
I would call the original coder and say: hey how are you? pretty please, where is it in the code?
Oh for goodness sakes. You can't fail to see that "rough handling" is a problem. Move the control one notch or twenty, EVERY movement results in a "rough handling" warning. This problem MUST be fixed, period!!
I sometimes wonder if the rough handling nagbot is more provoked into action by what is written into an engine spec combined with the general specifications of a locomotive rather than the simple act of driving. ... I had two locomotives both of the same class, but made by different makers. One of them .... I could drive and the nagbot remained asleep. With the second locomotive .... the nagbot was constantly squeaking every time I touched the controls.
On the rare occasions when I have noticed the message .... it appears to be related to the loco being driven so it may be an engine spec issue
So in light of this I've decided to ignore the nagbot from now on, but it would be awfully nice if there was a way to switch it off.
... With that said, however, I noticed on routes where the transition curves have been implemented, this message doesn't pop-up. I noticed a correlation too that this message started appearing once that was implemented. So my thinking is, if there are not transition curves implemented, then the message should be off by default.
John what transition curves are you talking about? Is this some new Trainz Plus feature? Or maybe the royal mess up with the track spline in TRS19 SP1 or SP2? I never installed SP1 or SP2 - just went to SP3 beta as it fixed all the errors - right? I still use the classic NA regional (100240) when I open TRS19. And I'm not a Plus (subscription) user.
I have fixed track and I have spline track in TRS19. IMO Fixed track is a nightmare to work with anywhere beyond level track. Sadly it was never fully implemented to make it more usable.
The Trainz track spline is a piecewise 3D cubic Bezier and as such can't form an exact fixed radius curve or a normal transition type curve. Transitions give a smooth curvature transition between tangent track and fixed radius track. Typically it's a linear variation of curvature over a specified arc length. You can't in any real fashion set and enforce tangents at intermediate vertices of curve sections which is necessary to form transition and circular geometries even in an approximate way.
If they are measuring lateral acceleration now in Driver and pinging users when they exceed some thresh hold then they do need to redo surveyor track laying tools and more likely the track spline.
Bob Pearson
On the tracks there's a parameter to add transition curves. You click on the lower properties question-mark "?" on the very bottom of the "advanced-pullout". You can then set the angle and percentage for the curve. If you have the Legend of the BNSF, you can see this in action and it's not just a Platinum/Gold/Plus thing and has been there since TANE I believe.