Seriously, what IS this???

frogpipe

Yesterdayz Trainz Member
Normal Speed Tree (Elm 01 on Mojave Route)
frogpipe_20130323_0001_zps1cb2372f.jpg


"Diseased" Speed Tree (Elm 01 on Mojave Route)
frogpipe_20130323_0000_zps87073c21.jpg


If you could over lay the two images, you notice it's the exact same location, I've just "turned" the camera a *fraction* to one side.

These things appear everywhere, happens to many different speed trees (built in and 3rd party), and seem to depend on camera position. That is to say, turning the camera or moving it forward or back, or watching a tree while passing in a train, causes this "effect" to come and go.

This is seen via an nVidia GeForce GTX550Ti and a few revisions of the drivers in DirectX mode - I can't use OpenGL because it results in single digit frame rates and huge torn polys all over the screen.

I thought it was confined to my own route (and suspected a corrupt speedtree somewhere), but now I notice it's in others as well and JetLog shows NO errors....

Has ANYONE else seen this?
 
Last edited:
Ahhhh ... Its the ever dreaded Dutch Elm Speed Twee desease.

Looks like a bolt of lightening hit it !

At the top of the human evolution chain for bravery, tops off first, with Speed Twee Lumber Jacks, then next come Steeple Jacks, then Roofers, and lastly Lion Tamers ... I have no exprience ... but I have a hat !
 
Last edited:
It could have something to do with mipmapping problems with the NVidia card. Are you using the 306 version of the Nvidia driver?

That one seems to be causing some issues with certain users.

Rico
 
v314.07

The other thread may have been mine. I got jokes and a few ideas but none of them proved to be it.

If there's another one I missed, I'd sure love a link to it - it's not a huge deal, but it aggravates my OCD....
 
It's not an N'vid problem, I get the same thing with AMD. It may be linked to load, I only get it when things have been running a while and it's getting hot in the box....
 
Gives new meaning to the term "Hot Box" ... Oil the bearings, knock the brass back into place, and change out, and repack the cotton wadding !
 
Hmm, it looks most like the uv-mapping coordinates get lost over time running the game. Could be due to something nasty like a memory leak somewhere, maybe even in speedtrees own code. Can't remember ever seeing this myself though.

Greetings from sunny Amsterdam,

Jan
 
@Dermmy - Just for clarity's sake, an AMD what? and can you post a screenshot?

Another thing I notice is that ALL speed tree objects in view will "pop" at the exact same time. So if I am somewhere where I can eyeball multiple trees, even if they are different ones, and I get that smeared mess it happens to all trees simultaneously.
 
I'll answer for Andy. :)

By AMD he means ATI and their Radeon products versus NVidia and their GTX.

I've had this issue to more recently and couldn't figure out why all of a sudden its happening. I've been too busy to check this with other things, but my feeling is something changed in the 3d graphics settings, perhaps there's something different about the latest updates we've received.

John
 
I've tried noodling with the graphical options, both in game and in the launcher, to no avail. None of them see to matter. (I note again that OpenGL is artifact filled, single digit FPS, and literally impossible to use.)
 
Back
Top