News:

Due to heavy spamming attempts on this forum, automatic registration has been disabled. We will approve registration requests as quickly as possible (unless you're a spammer of course :) )

Main Menu

Diffrence in high when using different track libraries

Started by BR430, October 25, 2024, 05:04:22 PM

Previous topic - Next topic

BR430

Hello David,

I noticed a problem by visualization in 3D.

In my trackplan I used to sorts of tracks, Roco Line and Roco Line with roadbed. First I did not recognize it, but now.

The parts are connected. In 2D no porblem.

But in 3D it looks:

VerbindungGleise.png It would be better an information, what's the difference height and as in reality, the rails should be connected.

The track will go into a building and that's why I cannot use roadbed.

Greetings,

Bastian.

David

The problem is that the track height is always calculated from the baseboard.
The rails on the track with roadbed are usually a lot higher than rails without roadbed.

We've realized this earlier, but we've not yet decided on a way to fix this.

This is only a problem with mixed rails.


Using the rail top for the height will not work, as this will be confusing when creating the tabletop.

Maybe we can add a warning in 2D that there is a height difference, and lift the connecting side in 3D. However, this wil result in a slope.

David Hoogvorst. Founder and Owner of DRail Software. Creator of AnyRail.

BR430

Hello David,

just a warning should be enough, I guess.
Only in 3D-projection should be no difference between the rails top surface.

I believe everyone using different rail parts is aware of the difference in height.

Greetings.