TSRE Shape Viewer: General discussion.

[Goku]

Next TSRE version will include new Shape Viewer. It already works!



Features included in first version:
- open s, eng, wag and con files directly from window file explorer or using File menu
- view shape in 3d view [1]
- browse directory files [2] and search them [3] (useful for route shape directory)
- view loaded file content and select it [4] (still needs to be done)
- view shape texture list, disable/enable them [5]
- export textures
- view shape hierarchy items, disable/enable them [6]
- view loaded file info [7]
- ofc. tools can be shown/hidden using View menu

Future version:
- view animations
- export shape do .obj file
- load and view some scenery around shape

Any ideas, suggestions?

[longiron]

Goku,
I suggest you get a poll of the community for the export of shape file to obj functionality. You are treading on one of the community's sacred cows.

If you could add LOD functionality instead of needing programs like PolyMaster, that would be great

An Enthusiastic Supporter

[Switch Tender]

Excellent work Goku. Can't wait to start using the new tools.
Thank you.

Randy

[xavivilla]

Any ideas, suggestions?

See the shape with the seasonal textures (spring, summer, autumn and winter) snow and night.
And if possible the new OR option, night with snow

Thanks for your great work.

[Garry]

There is a current program called "shape viewer" which I use for editing the .sd file.
It gives bounding box values so that the blue outline when the object is selected fits around the object.
Garry

[conductorchris]

This is excellent, Goku. We've needed a shape viewer that keeps up to date with newer open rails formats like .dds

Christopher

[Ermel17]

Hello. Any news about the project? Of the exit or the provision?

[Goku]

I had a long break. But now resuming my work.

[Scottb613]

Hi Goku,

Welcome back then...


If - you decide to do anything with shape file editing - could you possibly include some type of optimization routine to address MSTS models... For years we’ve had to create sub-objects for any shape files over 10,000 polys - and a single object could have no more than 2,800 polys - and now these limits are no longer necessary with ORTS... In fact - these limits are now wasteful as each division spawns a whole new set of draw calls... This practice has been so commonplace - that 3DC chose to incorporate these fixed numbers in their MSTS exporter - without any means to bypass them... While I fully realize this is not your problem - 3DC seems to be an orphaned product without any means to modify the exporter - so - if it’s not too much trouble and it fits the scope of your tools - some external optimization routine that works on shape files would be extremely beneficial to the modeling community...

Anyway - just than’s for reading this...

Appreciate all you do whatever you decide - best of luck...

Regards,
Scott

[Goku]

Firs version available in .6975