My friend gave me some complicated treeline models to convert and use them in my route. The models are shown in the right way in RTS and Shape Viewer but in TSRE they look "strange and in a dark way" (in OR in a better way but still a little bit dark) and in MSRE/MSTS there is an error like "no extended model" and they cant be shown. I understand that MSRE/MSTS is too old to normally represent some complicated models but can you fix the render of that models in TSRE?
Here you can see the difference:
https://imgur.com/a/RIyvFcO
Rendering in TSRE
By looking at this picture I see that TSRE and OR are unable to use proper lighting mode and use standard lighting properties with normals instead of "cruciform" mode designed for 2d trees.
I don't know why, but there is clearly a problem inside this shape file or TSRE/OR implementation.
I don't know why, but there is clearly a problem inside this shape file or TSRE/OR implementation.
Here it is:
https://drive.google.com/open?id=1di5bo ... ZW-SGjduR5
But when i converted the model into .s format there was not errors....
Open your file in notepad and find this line:
vtx_state ( 00000000 0 -5 0 00000002 )
"-5" value tells OR and TSRE that standard lighting with normals should be used.
For 2D trees you should use "-9" value.
I don't know why RTS and SV look different than expected.
vtx_state ( 00000000 0 -5 0 00000002 )
"-5" value tells OR and TSRE that standard lighting with normals should be used.
For 2D trees you should use "-9" value.
I don't know why RTS and SV look different than expected.
Can i just fix it manually by changing -5 to -9 opening shape as a text file?
Yes. Just use text editor that handles unicode encoding. Don't use default windows "notepad".
Yes. I use Windows 10 now and new builds are compiled in Windows 10.