KSO
KSO mode
The KSO Mode is a special render mode: "Keep Scene Open"
The scene is kept open in memory and the clients sends new render commands via python or a text file.
It requires
- a commandline block with a header that includes KSO: ############ [someOS] [KSO] ##########
- a block with KSO commands and log outputs that tell RR that the app is in a special state.
The KSO commands and settings are defined as:
|
KSO_Type |
Can be either TCP or File.
The client starts a TCP cleint and sends all commands to the TCP server running in the render application.
The client writes all commands into a file. The render application has to read and delete the file. |
|
KSO_NewFrame |
After the render application has done the assigned frames, it has to wait. If there are new frames, the client sends these lines to the render application (via TCP or file). |
|
KSO_Close |
After the render application has done the assigned frames, it has to wait. If the job is done, the client sends these lines to the render application (via TCP or file). |
|
KSOlog_AppStarted |
(The client checks the log output of the render application. ) If it received this text, then the client knows the application is started. This setting is currently not used. |
|
KSOlog_Running |
(The client checks the log output of the render application. ) If it received this text, then the client knows the application is in KSO mode. If the application takes more than 20 minutes to display this message, the render is aborted. (20 minutes as the application startup could require need to load the scene as well) |
|
KSOlog_FrameDone |
(The client checks the log output of the render application. ) If this text is received, then the client knows the frames assigned have been finished and the render application is waiting for a new command. |
|
KSOlog_Quit |
(The client checks the log output of the render application. ) If it received this text, then the client knows the KSO mode is down and the application is closing. This setting is currently not used. |