Page 1 of 2

AI Shunting

Posted: Wed Aug 20, 2008 6:01 pm
by peterdore
Not sure if this subject has been covered or not....

I have tried to get an AI loco to shunt from one siding to another then attach wagons and move them to another siding.
I used the Consist Operations Instructions, seemed to work but then whack thud! wagons on olde England.

Is this not posssible yet given that the commands are part of the Dev tools?

Pete Doré

Re: AI Shunting

Posted: Wed Aug 20, 2008 7:07 pm
by CaptScarlet
Unfortunately not at the moment.

John

Re: AI Shunting

Posted: Wed Aug 20, 2008 7:35 pm
by TheTazman
I think this would be very cool. But I am not sure if its dooable in RS.

Re: AI Shunting

Posted: Wed Aug 20, 2008 8:34 pm
by jamespetts
AI consist operations are definitely not possible. There is no official word on when or whether they ever will be, even though it is apparent that it was originally designed to be possible.

Re: AI Shunting

Posted: Thu Aug 21, 2008 12:21 am
by AndiS
With the new freedom in jumping around, with the trains going on as AI as you leave then, you should have the option to just take control for the short phase before the coupling. Not ideal, and certainly not an option for background activity while you pass the station driving another train, but maybe worth an experiment in some cases.

Re: AI Shunting

Posted: Thu Aug 21, 2008 7:00 pm
by jamespetts
AndiS wrote:With the new freedom in jumping around, with the trains going on as AI as you leave then, you should have the option to just take control for the short phase before the coupling. Not ideal, and certainly not an option for background activity while you pass the station driving another train, but maybe worth an experiment in some cases.
This isn't new: this has always been possible.

Re: AI Shunting

Posted: Thu Aug 21, 2008 7:40 pm
by AndiS
I might get confused, but there must be something that this -allowJump option allows that is not allowed otherwise. Of course, you are technically right, it was always possible, we just did not know the option existed.

Re: AI Shunting

Posted: Thu Aug 21, 2008 11:10 pm
by jamespetts
AndiS wrote:I might get confused, but there must be something that this -allowJump option allows that is not allowed otherwise. Of course, you are technically right, it was always possible, we just did not know the option existed.
I did.

Re: AI Shunting

Posted: Fri Aug 22, 2008 12:07 am
by phat2003uk
Is there list of various commands that can be put in the shortcut to allow/enable certain things?

Re: AI Shunting

Posted: Fri Aug 22, 2008 12:24 am
by jamespetts
phat2003uk wrote:Is there list of various commands that can be put in the shortcut to allow/enable certain things?
It always worked, even without the shortcut.

Re: AI Shunting

Posted: Fri Aug 22, 2008 9:43 am
by AndiS
So you are saying that -allowJump does nothing?

Re: AI Shunting

Posted: Fri Aug 22, 2008 12:52 pm
by t1metraveller
You have always been able to jump trains in free-roam, but not in scenarios. At least I've not been able to do so on the route I work with, Cajon.

-allowJump allows this now in scenarios.

Bill

Re: AI Shunting

Posted: Fri Aug 22, 2008 2:34 pm
by AndiS
That's the way I remembered it, but it is quite a while that I touched the scenario editor, so I was not at all sure (I have reason not to trust my memory :crazyeyes: ).

Re: AI Shunting

Posted: Fri Aug 22, 2008 3:47 pm
by jamespetts
I have never tried -allowjump, but jumping has always been possible in free roam and timetabled scenarios. It is not possible in standard scenarios - perhaps "-allowjump" makes it possible in standard scenarios, too.

Re: AI Shunting

Posted: Fri Aug 22, 2008 4:53 pm
by t1metraveller
Okay boys, maybe I'm sticking my neck out here, but here goes.

This is what I have found in terms of command line code possibilities using a hex editor and looking through the game files since the MK2 update.

KRS Command Line Codes
------------------------------------
All codes below have been gathered with a hex editor.

Codes are defined in the file GameManager.rsp, found in the \plugins folder.

NOTE: Some may not be valid now or even work, but these codes do exist in GameManager.rsp.

NOTE: Only a few of those shown below have been checked.

NOTE: A few from this first set may instead be LogMate codes.

-fs ....Game uses smaller fonts for certain narrative text and menus
-allowJump ....Allows jumping AI trains in scenarios
-ShowDriverList ....Adds a 'Driver' button inside the Driver Properties window (MK2?)
-ShowControlStateDialog ....Expanded HUD
-nvperfhud ....Create NVIDIA performance HUD (not confirmed)
-NoSplashScreens ....Disable intro splash screens
-ShowSoundDeviceSelector ....Allows choice of system sound device
-DisableSignals
-ShowTrackLinks
-Show3DPaths
-DisableDump
-DontUseBlueprintCache ....Possibly rebuilds blueprint .pak's each time???
-UseFastBlueprintCache
-DontBakeDistances
-SaveDistances
-DisableAWS
-ShowAudioConsists
-VerboseAudioDebug
-ForceSWMix
-EnableSoundDebugDialogs
-DisableEAX
-EnableEAX
-UseSoundDevice
-EnableSound
-DisableSound
-DisplayLocMe
-LeipzigDemo
-ShowDestinationMarkerList
-enable-backups
-enable-perforce
-EnableFullEditor
-NASKU
-Language
-updateRVNumbers
-IgnoreCoupling
-ManualCoupling
-generateDetailLevels
-blocking
-UseStreamCache
-UseFastStreamCache
-NoClearType
-ConvertDistanceData
-FilterForDirectionality
-FilterForManualJcts
-QuickStartStream
-NoWagonBraking
-EndTrackCheck
-TakeADump
-relaunchmce
-oogbb_noh ????
-FlashStrings
-SetDefaultButtonSound
-TrackPatternEntityFixup
-ignoreTrackTypes
-BlockingPhysics
-NoPlayerTrain
-followaitrain



LogMate Stuff
------------------------------------
-LogMate
-SetLogFilters
-RemoveLogFilters

Other LogMate Codes?
------------------------------------
-ValidateSignals (confirmed)
-WhereIs
-UnitTestPathing
-show-time-of-day
-show-lat-long-position

Some or all of these below may be usable parameters (filters) for LogMate. I have only tried "Script Manager" for use in analysing signals.

Known Examples:

-LogMate -SetLogFilters="Pathing"
-LogMate -SetLogFilters="Script Manager" -lua-debug-messages
-LogMate -SetLogFilters="Script Manager,Signals,Pathing" -lua-debug-messages

UnitTests
GhostAI
Signals
Shutdown
Update
Initialise
Camera
Physics
Pathing
Platforms
Streaming
Sound
Windows Manager
Driver Manager
Scenario Manager
Route Manager
Script Manager
Data Management
Rail Vehicle Manager
Track Manager
Scheduler
Input
Engine
Components
Singleton
Game Manager
Core