Mpre Speed Tree Nonsense....

frogpipe

Yesterdayz Trainz Member
Behold...

frogpipe_20121228_0002.jpg


frogpipe_20121228_0001.jpg


As you can see I turned my "head" slightly to go from normal bark to barf bark... Any wisdom?
 
Oh, and I'm getting this crap again in the jet.log

? 25:14.6 : GetShader > Failed to get CG shader
? 25:14.6 : GetShader > Cannot get technique[Branches] - No effect loaded.
? 25:14.7 : TNIG_ShaderSet > Cannot get technique[Branches] - No effect loaded.
? 25:14.7 : TNIG_ShaderSet > Cannot get technique[Branches] - No effect loaded.
? 25:14.7 : TNIG_ShaderSet > Cannot get technique[Branches] - No effect loaded.
? 25:14.7 : TNIG_ShaderSet > Cannot get technique[Branches] - No effect loaded.
? 25:14.7 : TNIG_ShaderSet > Cannot get technique[Branches] - No effect loaded.
? 25:14.7 : TNIG_ShaderSet > Cannot get technique[Branches] - No effect loaded.
? 25:14.7 : TNIG_ShaderSet > Cannot get technique[Branches] - No effect loaded.
? 25:14.7 : TNIG_ShaderSet > Cannot get technique[Branches] - No effect loaded.
? 25:14.7 : TNIG_ShaderSet > Cannot get technique[Branches] - No effect loaded.
? 25:14.7 : TNIG_ShaderSet > Cannot get technique[Branches] - No effect loaded.
? 25:14.7 : TNIG_ShaderSet > Cannot get technique[Branches] - No effect loaded.

I got rid of a bunch of trees already because I was getting this error, leaving only the trees that worked ok. Now the trees that were ok seem to have gotten "infected"....
 
It's either Dutch Elm disease or turn your slider (tree detail) up a notch. I've had that before, no idea how I fixed it.
 
Or get TRS2009. I have a copy of TRS2010 which I have never used because of Speed Trees, and I will not buy TRS2012 for the same reason. It is essentially Bloatware.
 
This is caused by the delay in loading the graphics. Have you done any disk maintenance lately like a defrag if you have a platter hard drive? This helps load in the graphics files faster.

John
 
A delay? Don't think so, I can "turn" or "move" just a touch and watch it go from great to crap all day long, it is totally dependent on 'camera' position.

In fact I once even watched to pop back and forth when I wasn't moving at all.

I'll have to do some more testing, but it *seems* that it happens with DirectX but does not happen with OpenGL. Unfortuately for me, DirectX = 25 fps (locked in the options file) whereas if I switch to OpenGL it drops to 4 - 13 fps.

It also appears that I can see this "effect" and NOT have those errors appear in jetlog.txt, so it would seem they are unrelated.

nVidia GTX550Ti if I didn't mention that already. Latest drivers (whatever number that is, can't recall and I'm on another computer at the moment).
 
Last edited:
The latest NVidia drivers maybe the issue. I've noticed worse performance with these than what we had before. Unfortunately, the older drivers don't support my 680. The trade off is nice looking trees and 4-13 fps, or striped bark and 25 fps.

John
 
Sorry to disagree but no problem with performance with the latest Nvidia drivers here. That particular tree looks like one I binned a while back actually for just that reason.
 
Back
Top