SpeedTrees in Surveyor and Driver...

[Dermmy]

I am developing a small single-board mini-route (or diorama) purely to experiment with 3D vegetation and discover what is - and isn't - possible using this new media.

The route is intensively detailed and uses a lot of 3D vegetation.

I Surveyor I am experiencing constant crash-to-desktop. Place more than a couple of new trees- crash. Move the cursor more than about 20 meters - crash. Sometimes just pan the camera - crash. Any movement of the camera at all results in 5 - 10 second freeze-frame while I wait for the crash. Sometimes it does, sometimes it doesn't.

OK - lots of content = crash. I can accept that. But here's what has me mystified:

Place some rolling stock (hi poly, animated bogies etc) load the route in Driver and the thing is flawless. I have tried to crash it and can't. Drive end-to-end at high speed with camera view '2' and one forefinger jammed on the right cursor key and the other on 'PgUp/PgDn'so I now have a high-speed rotating zooming camera on a moving platform and never the slightest hesitation. Go to Camera '4', with cursor speed set to max and rocket from end to end - nary a stutter. I can zoom all over the place for hours in Driver. Frames in the mid 30s and not the slightest hesitation.

Back to Surveyor, move the cursor - crash.

FYI the crash by-passes Auran's report screen , it goes straight to 'Trainz has encountered a problem and needs to close. Please tell Microsoft etc etc'.

What I would LOVE to know - as a routebuilder - is why the dramatically different experience in Surveyor and Driver? Why is one almost unusable and the other runs like a blue-chip investment.

No criticism of the program or the content expressed or implied. I would just love to know what - if anything - can be done in Surveyor to alleviate a problem which is possibly going to stop work on a small route which performs flawlessly in Driver...

Andy

 

[clam1952]

Not getting any problems with crashing in the Retail TS12 in surveyor and I have an awful lot of trees still to plant, however, I suspect having 8Gb of ram may be helping. The draw distance is down in surveyor compared to driver though.

Maybe the difference is maybe due to this?

When in surveyor it loads everything in the objects, track and paint tabs, thus that delay when clicking tabs ( hardly get it now with increased ram)

When you are running driver it's only loading the assets in the route which is going to be considerably less.

The theory in my case is that the extra ram, although Trainz is only going to be using 4GB, it can have all of it, the OS is using it's own chunk and the rest is maybe being used for disk caching?

Could try disabling any unused assets and see if that makes any improvement?

 

[RoysTrainz]

andy i am very surprised and want to help out

you know my routes are pretty dense with pofig ultra and jvc vegetation and so far no glitch no crash nearby far in between zoom surveyorpov different setting(play with this maybe helps) and or send me a copy of you diorama and i test it on my computer for you. And get you out of misery.
what nivdia setting and driver version etc etc recently using or upgrade perhaps?
anyway waiting to be able to help you solve this quick.

Regards,

Roy :wave:

 

[Dermmy]

Thanks Roy, but I have fixed the problem simply by reducing wind speed to its lowest setting. I prefer it that way anyhow and hadn't noticed that creating a new route returns wind speed to default setting - at least I assume that's what changed the setting. I certainly didn't do it manually!

Why it crashes Surveyor but has no effect in Driver remains a mystery...

Andy