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
There are other mods for a 3D model of a Departure Board attached to a platform or station:
Dynamic Departures / Arrivals Displays
https://steamcommunity.com/sharedfiles/filedetails/?id=2749557458
Dynamic Arrivals Board
https://steamcommunity.com/sharedfiles/filedetails/?id=2735568495
https://media.discordapp.net/attachments/998619674092773386/1004823841316540546/IMG_0216.jpg
https://media.discordapp.net/attachments/998619674092773386/1004819238680285294/image0.gif
https://media.discordapp.net/attachments/998619674092773386/1004820011833098391/image0.jpg
Or for small branch stations
https://media.discordapp.net/attachments/998619674092773386/1004823828947537950/IMG_0214.jpg
1. When a vehicle is diverted to an alternate platform/terminal, show the new terminal number with a exclamation mark.
2. Fix crash due to API change: "util.CameraController:focus()" now needs an additional bool parameter.
khustbubel : Does this fix your problem?
"Error message: error:"
which gives a program line number, error message, and a "stack traceback" ?
Do you mean that it works OK for one station, but then crashes when you change to another station?
Is it not simpler to make and edit the Line Data file using a text editor? Have you tried this, but have problems?
Is common-api still supported? I've read that it caused some problems.
Change the width of the Display Window by typing a numeric value and then ENTER in the new "Display Width" option in the Control Window.
The previous method of resizing the Display Window by dragging its edge caused problems for some users, with the window continually growing wider or narrower.
Perhaps after the width is set using displayWindow:setSize(), then displayWindow:getContentRect() gives a different width value.
I've added a new variable (widthAdjust) to account for any difference.
You can see whether 'widthAdjust' has a non-zero value (whenever you select a station) by un-commenting the print statement at line 617 of res/config/game_script/DepartureBoardGui.lua. I've not seen the problem here and 'widthAdjust' is always zero. Perhaps it depends on the screen resolution?
Please tell me if this fixes the problem. If not, I'll need to add an option to specify the Display Window width numerically, rather then by dragging the side of the Display Window.
What OS do you use? Both RustyBucket and doug who reported this problem have profiles which include "Transport Fever 2 Mac/Vulkan Beta" group. Does this suggest that it occurs only on MacOS?
The Departure Board display window is re-sized whenever the text changes, in order to adjust the height to the number of lines of text. It reads the current width and uses this when it sets the new size. So the width should stay the same.
This is at line 566 in \res\scripts\departure_board.lua
If anyone sees something wrong here, please tell me.
Try changing 'rect.w' in line 566 from:
displayWindow:setSize(api.gui.util.Size.new(rect.w, WINDOW_HEIGHT + nTextLines*17))
to:
displayWindow:setSize(api.gui.util.Size.new(options.displayWindowWidth, WINDOW_HEIGHT + nTextLines*17))
Does that make a difference? If not you could change it to:
displayWindow:setSize(api.gui.util.Size.new(450, WINDOW_HEIGHT + nTextLines*17))
which should fix the display window with at 450 (or whatever number you use).
Wenn die Mod aktiviert ist, zeigt sie eine Schaltfläche ("Abfahrt") in der Taskleiste am unteren Rand des TF2-Bildschirms an. Klicken Sie auf diese Schaltfläche "Abfahrt", um das Kontrollfenster der Abfahrtstafel zu öffnen, in dem Sie eine Station und andere Optionen auswählen können. Weitere Informationen finden Sie in \docs\info in der Mod.
Exception type: Lua exception
This error is usually caused by modding. Some game resources contain incorrect data.
Details:
Error message:
File name: D:/SteamLibrary/steamapps/workshop/content/1066780/2692112427/res/config/game_script/DepartureBoardGui.lua
Key: game/res/gameScript/DepartureBoardGui.lua_guiUpdate
Minidump: C:/ Program File (x86)/Steam/userdata/170578554/1066780/local/crash_dump/b9787831-bbf8-4c86-946f-039155cbc98b.dmp
Mod: "Departure Board" (*2692112427, 1) (consider removing this mod and contacting the mod author)
This is how error message was shown on my screen after the game had crashed.
"No. There isn't anything between Error Message, and File name." OK, That makes the problem difficult to find.
After the game was 100% loaded up.....it ended up frozen when I was trying to click on "Departure". Nothing was moving. Trains, cars, pedestrians, planes, etc. Nothing was moving til the game crashed and disappeared off my screen. That is when the error message I told you about pops up exactly how I showed you in my last comment.
That is the information which I need.
"Then the game seemed frozen". When does this occur? As soon as the game map appears? Or not until you click on the "Depart" button on the taskbar at the bottom of the screen? Or later when you change options or select a station in the Departure Board Control Window?
Does the error still occur is you set the Graphics Settings to "Low" before you load the game? (That should use less memory).
Does the error occur if you make a new game, without any mods, then save it, and then load it with just the Departure Board mod? Perhaps it is a combination with some other mod which causes this problem to appear. I want to find and fix this problem, but I need clues.
Exception type: Lua exception
This error is usually caused by modding. Some game resources contain incorrect data.
Details:
Error message:
File name: D:/SteamLibrary/steamapps/workshop/content/1066780/2692112427/res/config/game_script/DepartureBoardGui.lua
Key: game/res/gameScript/DepartureBoardGui.lua_guiUpdate
Minidump: C:/ Program File (x86)/Steam/userdata/170578554/1066780/local/crash_dump/b9787831-bbf8-4c86-946f-039155cbc98b.dmp
Mod: "Departure Board" (*2692112427, 1) (consider removing this mod and contacting the mod author)
As I said before, the error message says to remove the mod, and contact the author.
There should be a "_stdout.txt" file in your folder
C:/ Program File (x86)/Steam/userdata/170578554/1066780/local/crash_dump/
At the end of this "_stdout.txt" file, there is usually information such as "stack traceback" which gives a line number, such as "/res/scripts/departure_board.lua(562)" or "/res/config/game_script/DepartureBoardGui.lua(757)". What are these line numbers?
Does the game fail to start, or does the game start and show the map, and then crash when you open the mod by clicking "Depart" on the TF2 taskbar? Or later when you click something else?
Nicht Verbunden : Meinten Sie "klicken, um eine Station auf der Karte auszuwählen" oder "wählen Sie eine Station aus dem Menü der Abfahrtstafel"?
Dies geschieht hier nicht. Also, was ist der Unterschied? Welches Betriebssystem verwenden Sie (Windows, MacOS?). Ich verwende Windows10. Die Schaltfläche "Pin" sollte automatisch gesetzt werden, wenn das Abfahrtsanzeigefenster geöffnet wird. Geschieht dies? Wenn nicht, tritt das Problem auf, wenn Sie den "Pin" setzen?
Name of the mod : Departure Board
Posted : Dec 24 @ 5:54am
Updated : Dec 25 @ 6:10am
I don't see anywhere it would say what version this mod is, so I don't know what you mean by current version. I also wanted to say that the game crashes after loading this mod, so I am guessing the information you are asking for might be the following
Minidump: C:/ Program File (x86)/Steam/userdata/170578554/1066780/local/crash_dump/b9787831-bbf8-4c86-946f-039155cbc98b.dmp
I guess that is what you are asking for, because I have no clue what other version of this mod is out there besides the one I have. I also tried to unsubscribe and subscribe back again to see if that helps, but I still experience crashes again after adding this mod back on.
Firstly, are you sure you've got the current version of the mod? I've had no reports of crashes since the update on 25.Dec 14:10 UTC (see comments below). Steam should update it automatically when you're logged in online, but to make sure, unsubscribe the mod and then subscribe again.
Does the game fail to start, or does the game start and then crash when you open the mod by clicking "Depart" on the TF2 taskbar? Or later?
When a crash occurs, the game will write a crash_dump text file into Steam\userdata\<your userId>\1066780\local\crash_dump
Is there useful information at the end of this file such as a "stack traceback" or a line number or variable name in a DepartureBoard file? for example:
stack traceback:
... 2692112427/res/scripts/departure_board.lua(562): displayDepartures
res/scripts/departure_board.lua(611): DoDepartures
res/config/game_script/DepartureBoardGui.lua(935): ?
https://steamcommunity.com/sharedfiles/filedetails/?id=2693633798
You can drag the right edge to adjust the width and it will remember the width in the game savefile. The only places where the mod changes the size of its Display Window is on startup (where it sets it from options.displayWindowWidth, from the .save.lua) and when the text is updated, where it gets the current width (displayWindow:getContentRect()) and then sets the window size with that same width and a height which depends on the number of text lines. There are no other places where displayWindow:setSize is used. Check that the two .lua files, res/config/game_script/DepartureBoardGui.lua and res/scripts/departure_loard.lua have the same Date Modified time.