I am just ask for a conformation or perhaps a workaround... I noticed that in a "Career Scenario", that while the F3/F4 track display shows an upcoming signal, the 2D Map does not show the trackside signals at all. Using the same trackage on a "Standard Scenario" the signals will appear on the 2D Map. The problem... I am using the Call("GetNextRestrictiveSignal"), to control/light a physical signal, but it only seems to work on Standard Scenario's. Is this because the Call("GetNextRestrictiveSignal") references the 2D Map to get its information and since there are no 2D Map signals on a Career Scenario, the call returns bogus data ? Is there a way to read the F3/F4 signal data ? Thank You all in advance for all that reply. --Gary
Indeed signals are hidden from the 2D map in Career mode for gameplay reasons - the driver should not "cheat" by checking the map but drive following the signal aspects he encounters as in RL. But there has to be a way to achieve want you want. Problem is all LZB scripts are compiled as binary .out files and hide their secrets... Have you tried GetNextSignalState()? If there's one person who knows it would be Maik Goltz . He's very busy, but sometimes he's dropping in here giving some useful advice.
torfmeister, thank you very much for the reply. As for calling GetNextSignalState(), I am not... I am using the Engine Script to gather up the information I need. I do not think that GetNextSignalState() is available for engine lua scripting. Am I correct that I can not call GetNextSignalState() from an Engine Script, I did not see it listed as an available function call. I did find it when referencing "Signal Scripting" development though. So, If I call my "signal script" first and then call the original signal script, just like I am doing with the Engine Scipt, would that be a valid approach? This means that I would have to find out what signal script the scenario is using to be able to frontend my script in first, correct ? Thank you again for you help and any pointer that you might deem helpful. --Gary
Another thought... Would changing the Career Scenario to a Standard Scenario bring back the 2DMap signals ? Is RW Tools the thing to use in making this conversion ? ( I have never used this program). Thanks, --Gary
Gary Yes, it does work with RWTools now TSTools, ie you can convert career to standard scenarios at the click of a button. You can also open the appropriate scenarioproperties.xml file and change all "Career" mentions to "Standard".
