Rendering spline problem

[paulogoncalves]

Hi all,

When i try to add track spline, i´m always getting this problem:

I´ve tried several different tracks, and always get the same problem in junctions.
Anyone had this glitch? Any solution?
I´m on Trainz Plus Beta 136958, but in the latest stable release, it has the same problem.

Thanks in advance.
Paulo Gonçalves

 

[MickC57]

Really odd. You probably have done this, but have you checked that they are all on the exact same elevation.

 

[Dinorius_Redundicus]

Could it be a problem of your Trainz performance settings being set too "low"? Or perhaps, not sufficient memory in your video card?

 

[JCitron]

It could be the new imposter system not acting well with these splines. Some splines are "heavier" than others and cause performance problems in general and this new system appears to not like them. Some grass splines and grass objects by JVC have issues with the textures causing an outright performance drop. Dan Gavel ran into this with some of his cloned grass. I can't remember the kuids. Remember too that many people cloned the original assets and if the originals have a problem then the clones will too.

You can try replacing the grass with something else and see if that helps. Keep in mind that one rotten asset has an accumulative effect across the route because they are used everywhere. Removing that one bad asset from the route may improve things overall. Been there and done that recently actually.

While the beta version has improved performance, it's still not there yet even if it's better than the "live" version.

 

[wreeder]

Create a bug report using the link in the announcement thread for that build. Using a fresh blank baseboard and just the track, make a list of the steps you take to reproduce the problem. Looks to me that the renderer is confused by one switch overlapping another switch.

 

[pware]

Anyone had this glitch? Any solution?

From your posted image one thing that I noticed is that you appear to be using two different track assets

The pair of converging tracks on the right are lacking check rails and frogs where they intersect - indicating that a non-procedural track is being used. The track on the left, which diverges into two tracks does have the check rails and frogs at the point of divergence as well as the moveable switch blade at the junction point - indicating a procedural track is being used. This, of course, may make no difference to the problem but it would be worthwhile eliminating that possibility by using the same track assets in the junction set.

I would suggest following the suggestion of @wreeder above by making two identical but separate junction sets, one with the procedural track and the other without. This, at the very least, could eliminate (or confirm) this possibility.

 

[paulogoncalves]

Thank you all for the suggestions/responses.

I will try again, and see how´s going.

Thanks again.

 

[Fineas10]

Even tough it seems not to have anything to do with it, try turning on Full V-sync in Trainz launcher.