RailWorks command line options

[davveb]

I'm having trouble getting some usefull command line options to work with RailWorks. These are all things
that work fine with Railsimulator. Specifically I can't get the "lua debug messages" (which is a tick box
option on the wrapper screen) and the "set log filter" options to work in order to display information
in log mate on signal and consist script behaviour. Maybe I'm just missing something, but can anyone
else get basic lua Print() to work?

Cheers
Dave B

[Sly401]

Hi Dave

No help I'm afraid , I have tried and I can't get them to work either... just confirming

Sly

[markpullinger]

The grab screenshot seems to have gone as well - had to take screenshots with me camera for my upload!

[AndiS]

I have the same problem. I only have success with:
-LogMate -SetLogFilters="All" -lua-debug-messages

This brings up a load of tabs, one of them being the Script Manager tab, i.e., the output from Print().

Of course, with so much stuff, you need to click "clear logs" more often.

I still use KRS for signal script debugging.

P.S.: For screenshots, I always used IrfanView.

[markpullinger]

Screenshot worked till last update as had to do a fault pic in RW but was first time I'd needed it since the update - so hadn't noticed it not working!

[davveb]

I have the same problem. I only have success with:
-LogMate -SetLogFilters="All" -lua-debug-messages

Cheers Andi, that did the trick! You are very helpfull as always. As you say, you do get all the extraneous reporting, which tends to make my old computer struggle, but trying to debug script without any diagnostic output is very slow work.

Now I can finish off my dynamic engine exhaust with matching trailing engine sound operation scripting.

Dave B

[Acorncomputer]

The grab screenshot seems to have gone as well - had to take screenshots with me camera for my upload!

Screenshot = Print Screen Key on Keyboard or Alt+Print Screen Key on Keyboard if you just want the active window.
Open in Paint or other image editor.

[markpullinger]

Hi Geoff, it used to work like that but tried taking some screen shots at the weekend & it wouldn't play ball.

[scefhwil]

Cheers Andi, that did the trick! You are very helpfull as always. As you say, you do get all the extraneous reporting, which tends to make my old computer struggle, but trying to debug script without any diagnostic output is very slow work.

Now I can finish off my dynamic engine exhaust with matching trailing engine sound operation scripting. Dave B

Dave, are you now able to get Print() debugging info out of Script Manager? If so can you detail how please?

Cheers

Stuart

[AndyUK]

Hi Geoff, it used to work like that but tried taking some screen shots at the weekend & it wouldn't play ball.

The usual Windows method of using the 'PrintScreen' key and pasting from the clipboard into Paint or similar still works for me. However the current version of RW has its own built-in screenshot capability, press 'Ctrl+S' and an image in .png format will be saved (under WinXP 32 bit anyway) in your 'My Documents\My Pictures' folder. The file will have the Route name and lat & long as part of the filename.

Andy L

[markpullinger]

Thanks - forgot that shortcut

[davveb]

Cheers Andi, that did the trick! You are very helpfull as always. As you say, you do get all the extraneous reporting, which tends to make my old computer struggle, but trying to debug script without any diagnostic output is very slow work.

Now I can finish off my dynamic engine exhaust with matching trailing engine sound operation scripting. Dave B

Dave, are you now able to get Print() debugging info out of Script Manager? If so can you detail how please?

Cheers

Stuart

Stuart
As Andi said above you need the -SetLogFilters="All" included in the Steam command line options. You do get all the status reporting, which is an allful lot (but a good insight into how complex the program is!) so it's best to select the Script Manager tab rather than leave logmate on the All tab. In Railsimulator you used to be able to use -SetLogFilters="Script Manager", but that doesn't seem to work anymore.

Dave

[scefhwil]

Thanks Dave, got it working now.

I copied the DebugPrint code from the signal scripts and, whoopy! now have output in logmate. However, it all seems to grind to a halt after 20secs or so, with RW window going black and "not responding".

Any ideas, anyone?

Cheers

Stuart

[AndiS]

You need to click "clear logs" in the leftmost menu quite often. Or switch back to KRS until they fix it.

It is a known problem of LogMate that it grinds to a halt when the shown log is too big.

In the setting with "All" tabs, it may help to use the simplest possible route for testing. I would not want to try starting RW with a default route and a complex scenario. With all these tabs, LogMate will die within seconds, logging minute details about the inner workings of the dispatcher and other parts of the programme.