render_dof is being reset on application start / not matching config file

[taylormorris]

We noticed some inconsistencies with our depth of field settings (we have a toggle set up on a 'video settings' page) and created a sample project and were able to reproduce.

 

1. Create a new project and launch

2. Enter the following commands in the console

'render_dof 1'

'config_readonly 0'

'config_save'

3. Close program - config file now reads render_dof 1

4. Open program again

5. Enter 'render_dof' to check status

'render_dof 0' is returned, contradicting the config file (which does not change when closed)

 

We actually have the opposite problem, where render_dof always returns to 1 on opening (and does change the config file when the application is closed).

Hopefully clearing whatever bug is causing the one shown above will fix our problem as well!

 

Edit: Just checked with render_motion_blur and found the same behavior, not sure how wide spread the problem is but it's not just render_dof

[silent]

Hi Taylor,

 

Please, check the *.world file. Starting with Unigine 2.0 render-specific options are loaded directly from the <render> section of the *.world file (ignoring the *.cfg file).

 

Thanks!

[taylormorris]

Wow, that's a really strange decision and it makes it very hard for us to have "video settings" for the application. How do you save the changes to the .world file? Console commands still work but they don't change the .world file, even after quitting. I don't see a "save" function like there is with engine.config, so how are we supposed to make changes to the file from the application?

 

(You can move this out of bug reports!)

[dred]

Yes this really doesn't work for us, we don't want to be able to save the world files on a packaged release.  We need users will need to have access to any of the quality settings so they can tune the application to run on their hardware. Also being able to turn off things like motion blur, dof, taa, is nice for a user and those settings need to persist, changing them every time they start up won't work.  I don't have a problem with the defaults being in the world file, but you should still be able to override them at a user level. 

[taylormorris]

Is there any update? We are fleshing out our video settings in the ui and it makes a huge difference if Unigine will continue to have render settings set per world instead of application wide. Please let us know if there is an update coming to fix this.

 

If not, we will have to create a separate xml for Video Settings and update every world with that info when it loads. Any alternative solutions are welcome!

[silent]

Hi Taylor,

 

I'm afraid, there is no major changes planned for 2.3, so it is better to create separate XML with rendering settings for that.

 

Sorry for the inconvenience caused.