[SOLVED] Commands Which Require video_restart/render_restart/render_reload

[taylormorris]

On the documentation page for Console Commands, there are notes on the use of various display settings, that indicate some might require different restart and reload commands. But it is not specified which settings require which commands, so it is very unhelpful for us in creating a user interface which will need to run specific commands when a player changes their settings. 

 

 

Here are the notes: 

 

Notice (Video Settings)

 

To come to effect, the commands below require either video_restart or render_reload commands to be run after them.

 

Notice (Rendering Settings)

Many of the following options require the render_reload command to be run after them to take effect.

 

There are two settings, render_filter and render_anisotropy which mention they do not require render_restart but it says nothing about render_reload. What we need is another column for all video and render settings that details exactly which reload or restart commands are required for each setting to take effect. 

 

I assume render_restart will have the same effect as render_reload, but how about video_restart? Does that restart the renderer as well? Clarity would be much appreciated!

[sebastianbah]

Hi,

 

render_reload - reloads all shaders, but does not update shader variables.

render_restart - reloads all shaders and update shader variables.

video_restart - restart application window. Renderer is also reloaded. You need this command for video_* commands.

 

Also, we've added task to TODO list, to add required restart/reload commands for the console commands.

[taylormorris]

Hello, looks like some big changes in this area with 2.0!

 

Our new problem is that some rendering commands automatically run "shader_reload" after changing values. This is causing problems with our Video Settings page, where we are potentially changing multiple settings before running "shader_reload". With the way things are now, a loading screen pops up every time you change certain settings through the ui (without hitting the confirm button). Not good.

 

The commands that we see trigger this reload: render_ssao, render_anisotropy, render_shaders_quality, render_filter, render_textures_quality

 

And the commands we're using that don't trigger: render_dof, render_motion_blur, render_shadow_shafts

 

Is this an intentional feature that's not documented or just a bug?

[binstream]

You can apply changes in batches like that:

render_ssao 1 && render_shaders_quality 2 && render_textures_quality 1

[sebastianbah]

Hi Taylor,

 

I'm afraid that documentation for some of the features included to Unigine 2.0 are in progress for the present moment.

For now render_* commands automatically calls shaders_reload command if required.

 

If you use multiple render_* commands in console with "&&" shaders will be reloaded only once at the end of all commands.

 

Sorry for the inconvenience.

[taylormorris]

OK, good to know. This forced us to change how we are doing our settings but it is actually much cleaner and shorter now!

 

The shader_reload command does run multiple times if multiple commands are entered though. I see the progress bar on the splash screen fill up twice after entering two required commands on the same line, but only once if one required command is entered.

[sebastianbah]

Hi,

 

I'm afraid it was a bug with some console commands and it's fixed already. Fix will be available in next SDK update. 
 

Sorry for the inconvenience caused.