Give parameters to start Zusi

[SevenThunders]

In Windows shortcuts you can avoid the Steam-Message by using the Steam.exe as the target with the parameter “-applaunch [Game-ID]” instead of linking the game.exe directly, followed by the other required parameters.

For example the OMSI-Mapeditor: "C:\Program Files (x86)\Steam\Steam.exe" -applaunch 252530 -editor

Zusi has the ID 1040730.

That indeed, does work, (my steam was here though: C:\Steam\steam.exe) if i choose an option like this then that would be the Steam users covered so then its just a case of the non steam Zusi users.

Cheers
Neil

[hlinke]

Dear Neil,

I can offer you to start the Zusi-Trains via ZusiStart.
ZusiStart handles the different cases of Zusi-Versions, but the main advantage is that it creates a temporary optimised schedule that includes only the trains interacting with the starting train that reduces the waiting time for a train to start dramtically especially in big schedules and a train that starts late in the schedule.

If you are interested we can discuss the interface via PM.

You can find ZusiStart here (unfortunately still in german only- I am working on international support:
https://www.hlinke.de/ZUSItools/zusistart.html

Kind regards
Harold

[SevenThunders]

Dear Neil,

I can offer you to start the Zusi-Trains via ZusiStart.
ZusiStart handles the different cases of Zusi-Versions, but the main advantage is that it creates a temporary optimised schedule that includes only the trains interacting with the starting train that reduces the waiting time for a train to start dramtically especially in big schedules and a train that starts late in the schedule.

If you are interested we can discuss the interface via PM.

You can find ZusiStart here (unfortunately still in german only- I am working on international support:
https://www.hlinke.de/ZUSItools/zusistart.html

Kind regards
Harold

Hi Harold, thanks for your message... i have looked at the TCP stuff stored in the _Docu folder that Carsten mentioned however its all stored in german and i think in pascal files as well so is too much for me to decipher at the moment.

So i have decided to try and call the Zusi.exe directly with parameters similar to what has been suggested in this thread... i think its a good compromise rather than going down any sort of TCP connection for now.

Best regards
Neil

[SevenThunders]

Initial tests are good, i now have Zusi (steam version) fully starting up (without no Continue dialog appearing) with a selected route from within Zusi Route Finder

[SevenThunders]

Initial tests were good, however i have now discovered that when Zusi is started via Steam (like with the line given below)... most of the Function Keys (F3, F11, F12 etc.) do not work (it is possible to select them off the right click menu but that's not the same as pressing a key), does anyone know why?

C:\Steam\steam.exe -applaunch 1040730 "C:\Steam\steamapps\common\ZUSI 3 - Aerosoft Edition\_ZusiData\Timetables\Deutschland\Hamburg_Kassel\Hannover_Paderborn-Kassel_1991_00Uhr-12Uhr\Az88611.trn"

[Carsten Hölscher]

Maybe Zusi doesn't have the focus then? The F keys need the focus while the keys for train operation don't.

Carsten

[SevenThunders]

Maybe Zusi doesn't have the focus then? The F keys need the focus while the keys for train operation don't.

Carsten

I have looked at all possible parameters including ones i found for steam that did not even work (-windowed and -force_focus) as using them after the appid followed by the .trn filepath just caused Zusi to start but not with the given route.

I also looked at the Windows side including extra commands to give focus after Zusi has started but these did not work either.

Its as though the steam.exe app does not give focus to Zusi when a route is initially started from the command line with a .trn file

However if the route is stopped with Simulation > Restart Timetable... and then another timetable is started, then focus (plus the Function keys with it) is regained

Very strange

Cheers
Neil

[SevenThunders]

After further investigation... it looks like its something to do with the Train Data window in Zusi

Ill maybe know more tomorrow after more tests

Cheers
Neil

[SevenThunders]

Yes, it is the Train Data window in Zusi that is grabbing focus or at least interfering with the focus, doing this gives focus back to Zusi...

If the Train Data window is not open then open it using the right click menu.... focus is now fully restored to Zusi.

Or

Uncheck the option... Hide train data window under Configuration > Settings > Simulation.... then each time Zusi starts the Train Data window will already be open, user then needs to just click on that window
to give full focus back to Zusi.

I could possibly automate that 2nd option if the user leaves the option unchecked so that the Train Data window will always appear, i could maybe automate the selecting of it which would then give full focus back to Zusi.

Cheers
Neil

[SevenThunders]

Okay, after my previous posts about Zusi having focus and losing/regaining use of certain keys such as the Function Keys (F3, F4, F11, F12 etc) i have discovered this:

After Zusi starts (via Zusi Route Finder) if at any time you give focus to another app (whether it is Zusi Route Finder or anything else you have running in windows it does not matter) then you return to your route in Zusi, you may find you do not have use of the keys again (F3, F4, F11, F12 etc), to get use of the keys back you can do either of these:

In the windows taskbar click the Zusi icon again to give it focus... try the keys again, you may need to do this a couple of times to regain focus to Zusi.

However, if you have the Train Data window open in Zusi (usually its in the bottom left of the screen, F7 switches it on/off) then you should regain focus of Zusi including use of the keys again as soon as you give focus back to Zusi on the Taskbar.

I haven't got a clue what's happening to be honest but definitely some sort of focus issue.

Cheers
Neil

[SevenThunders]

Anyway, i have decided to go with what i have for now in the latest version of Zusi Route Finder as i need to move onto other projects.

I will update the manual with anything i think the user needs to know as far as the use of the keys after starting Zusi via ZRF

Cheers
Neil

[SevenThunders]

Unfortunately after more testing i am not going to put the start Zusi with the selected route into Zusi Route Finder, there are too many things not working.... for example i have now found that the mouse does not work, sure the mouse moves and allows you to pick items off menus however it does not allow you to click on buttons on the data displays etc. and i do not know how to correct that, its again some sort of focusing issue but not one that can be sorted out simply by clicking on the train data window or the zusi window.

Neil

[Johannes]

Don't worry, people have been complaining about this focus issue for years: viewtopic.php?t=14712

[SevenThunders]

Don't worry, people have been complaining about this focus issue for years: viewtopic.php?t=14712

Ahhh, if only i had seen that earlier!

[Carsten Hölscher]

On my development computer the mouse works so it's difficult to find this issue. sorry

Carsten

[SevenThunders]

On my development computer the mouse works so it's difficult to find this issue. sorry

Carsten

It is what it is... i am incorporating connections with Zusi Start now, hopefully... get to it Harold

Neil

[yxyx]

For me the F keys and Esc also don't work when I start Zusi using a .trn file.

Best regards
yxyx

[SevenThunders]

For me the F keys and Esc also don't work when I start Zusi using a .trn file.

Best regards
yxyx

You can get use of the F keys back by opening the Train data window (using the main menu or right click menu)... each time you lose the F keys just click on the Train Data window again... however its the mouse that is the main problem, sure you can move it around and select off menus... but you will find you cannot click on buttons (such as those on built in cab data monitors) or when viewing the train from outside the cab use the mouse to move around the viewpoint.

Neil

[yxyx]

however its the mouse that is the main problem, sure you can move it around and select off menus... but you will find you cannot click on buttons (such as those on built in cab data monitors) or when viewing the train from outside the cab use the mouse to move around the viewpoint.

Oh sorry, I forgot to test that as well.

Best regards
yxyx

[Michael Springer]

This topic was already discussed years ago.

viewtopic.php?p=290255
viewtopic.php?f=55&t=14712

But I have no idea what the result or output was