Originally posted by TRS
Was wanting a official explanation for this. But from the quote from Phyter, its a performance issue. I call that boloney!
Have you seen how Hyper Rails has to remove all crossties when editing the track? NL2 uses B-splines or FVD which take more to calculate. The editing tools may have to re-plot huge lengths of track in realtime at 30-60 FPS, the higher the better, to match the mouse movements. This takes a lot of calculation to do just for the curves, but the crossties will make it more complicated. Then you have to factor in the geometry curvature detail level, which needs to stay high in order to get an accurate depiction of the track shaping. (HR had very low curvature detail especially on distant tracks.) This isn't even counting the additional objects, spline changes, texture mapping, etc.
To an extent, I think you're correct; NL could render editing track in very basic geometry without textures and with crudely detailed crossties and other objects, but at some point it's going to take too long to draw large sections of track being edited.
But it doesn't really matter anyway, at least if the new editor has better object placement and view control tools. (The multiple viewports is a plus, although it's not my style.) The options for hiding objects has expanded from NL1's editor, which should enable a cleaner editing environment in orthographic views.