Thanks for the info. That was in one of the densest parts of the route so I am more than happy with 30fps. I have my vertical sync set to half.In the screenshot you show, with red at that second line, that aligns with rendering at 30 fps.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Thanks for the info. That was in one of the densest parts of the route so I am more than happy with 30fps. I have my vertical sync set to half.In the screenshot you show, with red at that second line, that aligns with rendering at 30 fps.
Sample shown. Each entry has a popup menu.To find Inspect Baseboard:
- Open a route in S20.
- Using Marquee Tool, select a baseboard
- Open the contextual menu
- Select "Inspect Baseboard"
- Then on the Inspect Baseboard window, you can right click textures listed for more options.
This is a known issue, the garbled data in the config file is the reason why saving sessions will sometimes be marked faulty. It also appears to be random.Does anybody know why I would get this when saving a new session...
This is in the config.txt
kind "profile"
category-class "YP"
category-region "AU"
category-era "2010s"
description
thumbnails
{
default
{
image "thumbnail.jpg"
width 240
height 180
}
}
kuid <kuid:30577:101366>
username "WSR TLR-3 - Default"
map-kuid <kuid:30577:101365>
min
___/
_________
__:___<______
____i_*_____o___t_!_____________e "��> ��������T�"
d_=_._n_______>_r_-_g_____________)_u_____[_<_-_______0_m_ "�Q�(-!���$| ������������ �"
_____
p_y____________
______e___y_______n_l____
q___._4_c_"_________d__ "R��������Z�,������Q�d��R�q�R���C�X�c�S�;���T�������� i9���)'a'>��T�"
h____"p&__;
trainz-build 5.7
I deleted it and tried again, and the config.txt was in the correct format except for the end which ended in the following..
rule-data
{
}
min
CM does not like the "min" at the end... why is it there.?
First time happened to me.This is a known issue, the garbled data in the config file is the reason why saving sessions will sometimes be marked faulty. It also appears to be random.
I am wondering TLR would work with current multi-track industries, if the driver command "Drive to" was used instead of Navigate to". With "Navigate to" you can enter the industry without specifying the track. With "Drive to" you must specify the track even if there is only one options. Then again, maybe "Drive to" does not work because of this requirement.I suspect that it’s the same problem it’s multi track stations and industries. The AI can’t determine the different tracks without information from the configuration file. For multi-track industries the config file needs updating, but for multitrack stations (especially where the user has constructed the layout by placing several individual platforms together) it’s a bigger problem
Hi, TLR won’t work with multi track industries as they exist now. Eg, I have a 4 track coal mine, oil refinery and multi track port in one layout. TLR will only use coal loader track 1, the oil refinery only uses the delivery track and the multi track port doesn’t register at all.I am wondering TLR would work with current multi-track industries, if the driver command "Drive to" was used instead of Navigate to". With "Navigate to" you can enter the industry without specifying the track. With "Drive to" you must specify the track even if there is only one options. Then again, maybe "Drive to" does not work because of this requirement.
Yes, but I was referring to the industries which have several tracks for different products. E.g. Auran’s oil refinery. This has separate tracks for importing and exporting. The TLR doesn’t know which to use unless the industry.gs is updated.The JR MIN2 (multi track industries version 2) are working just fine.
They are loading / unloading just as they did before.
Actually, designating a track is required by the "Drive to" command even if there is only one while it is not for "Navigate to". Also, the method of entering the info is different. "Navigate to" has two input fields while "Drive to" is through selecting.@sw1500 You can select the platforms on both Navigate to & Drive to.
And your point is..???Actually, designating a track is required by the "Drive to" command even if there is only one while it is not for "Navigate to". Also, the method of entering the info is different. "Navigate to" has two input fields while "Drive to" is through selecting.