安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题






I've got a version 1.1 up now and I can't reproduce this rendering problem anymore. Let me know if this fixes it for you.
Had never seen this before and I like to think I thoroughly test my stuff before I put it up on the Workshop. Having said that, I did see what you were talking about when I initially placed the signals on a test map just a few moments ago. Is that when you are seeing it also? Before any lines have been created or any trains have run on the track?
After a couple of trains had passed each other in a simple passing loop, the lenses had sorted themselves out and I did not see this rendering problem again. Not sure why this is happening now. Thanks for the heads up. Also, is anyone else having this problem. I've been thinking about going back to my signals and re-texturing them ( I was never quite pleased with the way they turned out) and I will have another look at the lenses then if this is a common occurance.
https://www.transportfever.net/filebase/index.php/Entry/589-US-RailRoad-Crossing/