Stele

Sorry for closing without checking outsides, got it replicated this time. Same happens for the right red. If you disable top light and flip it on with a hotkey, lower lights repair themselves. If top is disabled in the first place, but does not happen. Setting to zero with a hotkey, works fine too. Interaction between halogens and leds must depend on state zero which is skipped when using keybinds.

In your log: Input general active_cab = 0.00 radmor_splitter_cab = -1.00 Outpurt general actual_cabin = 1.00 Output Ty2 cab = 0.00 In generic vehicle code Output_General.data[(int)GENOUT.actual_cabin] = (int)trainset.CabinDir; //1 in your log DeviceRTF.IsVoltage = radmor_adapter_pwr & (radmor_splitter_cab == cabinDir); //-1 != 1 So like only thing wrong is splitter set to cab B. Was your log saved before you flipped it? Like if it flipped by itself? It is set to 1 on load and never touched in bot behavior. EU07 for example sets it according to direction, but that block is not present in Ty2.

It broke shader on wagons when I tried to spawn reversed one to test for whatever (likely unrelated) reason. 😄 Sorry, I don't have setup to test scenarios. Somebody else will have to. Could you check that GENOUT value when bug happens? It's the only place in code that I found that could mess it up.

Anything extra to trigger it? Reverser changes VehicleControllerBase.Direction in jumps 1/0/-1. Radio splitter checks VehicleControllerBase.cabinDir and it's 1 all the time in my tests. Only suspicious line that could switch that value is (common for all vehicles) cabinDir = (int)vehicle.trainsetInfo.CabinDir * (int)vehicle.DirectionInTranset; which could mess if it's spawned in reverse in the first place. That value can be checked in debug panel in outputs table. Output_General.data[(int)GENOUT.actual_cabin] = (int)trainset.CabinDir;

Can't duplicate. Turning with mouse into red position and then pressing "L" turns all three into white. "Ctrl+L" into zero.

Like tutorial tells you to use shortcuts? What "L" does in most cases? Sets to Pc1 (white triangle on front) even with individual switches? It should be doable in this case to be fair.

And fixed. Fast move in one direction was able to get position index out of bounds.

Bot always sets first group (halogens but not top left, causing other bugs) on the lowest level, ignoring all vehicle specific code. Switching it so spawn in TrainsetState.tsShunting sets halogens in both cabins, supposedly causes some problems with tutorial. For now I'm only adding conditions to disable aft leds when you have wagons attached. But it solves nothing. Hacky solutions to have leds at all without rewriting whole lights system bites back.

Checking history of the file, it was wrong from the very beginning. Crazy to slip by for so long.

Przepięte na ich dedykowane tekstury. Dzięki za wyłapanie.

Silnik ma limit klipów grających na raz. Może to też być ograniczone sprzętowo. Widzę jedną różnicę w konfigu ładowania dźwięków między nimi, oprócz liczby pozycji. Zobaczymy czy uda mi się zduplikować ten efekt w pierwszej kolejności, bo wg opisu przestawianie tej flagi w ciemno może mieć odwrotny efekt. Nie, ta opcja nie ma nic do rzeczy z ilością klipów grających na raz. Nie mogę też zduplikować problemu lokalnie w edytorze. Liczba odtwarzanych jednocześnie klipów jest ustawiona na 32. Podobno wybierane są najgłośniejsze jeśli liczba jest przekroczona.

I'm not an author of those skins, but it feels like deliberate choice. All liveries have differend decal mesh and those stickers use separate uv space. If author watend to use flamable sign there, he'd just use existing one. I looked over photos of dozen tankers and couldn't find one with blank red or black sticker though.

AKP-4E used in EU07 and other old locomotives has rise speed of 6-12s, depending on the pressure. Newer 160EC, 8s. In game all move to max height in 6.(6)s so they are even a bit too fast compared to reality. It is a problem irl too. Rapid changes in wire height are a base for speed limit. In game those gradients might not be correct in some places where viaduct model or road do not match real dimentions perfectly and wire must go lower to prevent clipping.

Podkolorowana emisyjnosc pomaranczowych lampek. Wszystkie swiecily na czerwono.

@BrejSki Jakie ustawienia graficzne miałeś? Motion blur i antyaliasing głównie. Nie mogę zduplikować takiego smużenia.

Not much can be done with how unity lights work with our global setup if we want to keep the desk and timetable lit. Changing source cone radious moves it a bit further from emitter so top of the screen isn't as overburned.

Wiem. Po prostu rysunki i zdjęcia jakie miałem zawierały jedynie pojedynczy ślizg a potem poszła copypasta pantografu do reszty taboru. Zrobienie nowego ciągle kołacze się z tyłu głowy. Ma ktoś rysunek i/lub zdjęcie z bliska (czyli zdemontowanego albo siedząc na dachu) podwójnego ślizgu by to zrobić ładnie?

Dodałem miganie guzika przy spełnionych warunkach i odwróciłem warunek kabiny na nieaktywną.

Porównałem z EU07 i na oko świeci gorzej, ale parametry światła i flary są takie same.

@PL_Andrev Jaki pojazd jest na screenie? Końcówki powinny mieć flary widoczne z daleka tak samo jak światła czołowe.

Dodałem jeszcze MCO, TCU i trakcję ukrotnioną, bo również nie były zapięte. Część panelu nadal nie działa z braku symulacji odpowiadających jej przekaźników, ale dolny rządek i mam nadzieję wszystko sterowalne z kabiny, działa.

Aktywacji kabiny nie mamy zaimplementowanej... Ba, w nieaktywnej nie wiem czy zareaguje na wciśnięcie guzika. Przy testach osłony sprzęgu na stówkę włączałem przy aktywnej kabinie. Nie mamy również migania guzika przy spełnionych warunkach.

What key/switch behaves like that for example? I tried some added in that commit and they worked fine on my end. Their implementation also looks the same at a glance.

I can't replicate it in any of them. Positions are set in wheels and levers properly and it works in game. Fast move is not hardcoded to shift and by default only works with left shift.

I've loaded it to up 200%. Shovel itself gets some garbage scale data on every pickup, but those are numbers on seventh place decimal and stay constant while shoveling. Coal itself is a bit more susceptable, getting something on sixth place decimal. Still not something that should be noticable by eye. And its not cumulative between shoveling movements. Scale is not touched by script there. All that comes from floating point errors in unity matrix math.