Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
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/