Some dynamic tracks render wrong
#1
Posted 17 May 2015 - 08:35 AM
http://i.imgur.com/6Cn7e8q.png
In msts:
http://i.imgur.com/1JuZSoB.png
Fix is easy, just use -radius for positive angle http://i.imgur.com/cnPtHmo.png
If you don't have route with positive angles in dyntracks, here is one: koniec.org/ccc_dyntracks.zip
#3
Posted 17 May 2015 - 09:55 PM
as I understand you have programming skills, you could have a look at DynamicTracks.cs and see if you can provide a patch.
#4
Posted 18 May 2015 - 02:02 AM
Lutz
#5
Posted 18 May 2015 - 09:25 AM
Lutz_s, on 18 May 2015 - 02:02 AM, said:
That explains why it's not come up before and I can relax about this issue for 1.0. Thanks. :lol:
#6
Posted 18 May 2015 - 10:15 AM
Lutz_s, on 18 May 2015 - 02:02 AM, said:
I think that absence of positive angles in dynamic tracks is just a bug in RE. MSTS creates track sections for both negative and positive angles and if you change angle value in .w file and sectionidx in route tsection.dat everything works fine in game and RE.
In my editor it'll be core feature for track placing.
#7
Posted 18 May 2015 - 01:59 PM
Goku, on 18 May 2015 - 10:15 AM, said:
In my editor it'll be core feature for track placing.
Hi Goku,
Help me understand; By "positive" or "negative" angles do you mean track curve to left or right as viewed along Z axis from the shape pivot?
best,
vince
#8
Posted 18 May 2015 - 03:55 PM
#9
Posted 19 May 2015 - 01:17 AM
#10
Posted 19 May 2015 - 04:08 AM
#11
Posted 19 May 2015 - 04:30 AM
#12
Posted 19 May 2015 - 06:11 AM
#13
Posted 08 December 2016 - 10:39 PM
But now I see that not only shape rendering is broken, but track paths too. And I don't know how is it even possible? Why train does not just follow TDB and tsection path?
http://www.elvastowe...962#entry211962
#14
Posted 09 December 2016 - 02:00 AM
http://koniec.org/cc...ntrack_test.zip
Two dyntracks are only rendering wrongly
Everything works ok in MSTS Game and MSTS RE.
* It turns out that weird train circles was TSRE bug wisible only in OpenRails.
Was:
TrackSection ( SectionCurve ( 0 ) 40038 30 15 )
Should be:
TrackSection ( SectionCurve ( 0 ) 40038 30 0 )
In MSTS and TSRE it was not visible, because these apps choose between line/curve by SectionCurve ( LINE/CURVE ), not second value.
#15
Posted 09 December 2016 - 01:49 PM