Scalability settings will not override project defaults on Linux

Development Platform & Builds
, , , , ,
1

When selecting a different setting in the quick scalability menu in the editor, the associated console variable will not apply. The UI changes to reflect the new setting, but unfortunately the change is not applied, and instead a short warning is shown in the console.

[2016.01.05-17.42.30:969][948]LogConsoleManager:Warning: Console variable 'r.MSAA.CompositingSampleCount' wasn't set ('Scalability' has a lower priority than 'ProjectSetting')

73027-scalability.png
73027-scalability.png1920×1055 287 KB

Since the viewport is still black when running on OpenGL 4+ with hih or better antialiasing on Linux, this presents a rather annoying blocking issue for certain projects x)

I’m running the editor from the terminal, using the -opengl4 switch. The default memory allocator (binned) is used.

The engine is a direct-from-github compilation of the Release branch.

System information:
Linux Mint 17.3 Rosa (64-bit)
Nvida GeForce GTX 660Ti, 2048MB
Engine Version: 4.10.1-0+++depot+UE4-Releases+4.1

2

Hey -

When you mention the console, are you referring to the Editor’s output window or the Linux Terminal? What scalability settings are you changing when you notice this warning message. If possible, please list the steps used so that I can ensure that I am seeing the same results that you’re referring to.

Cheers

3

Sure thing - it’s in the Linux terminal, and it’s for all of the scalability settings.

Steps to reproduce:

  1. Create a new project using maximum quality Desktop settings.
  2. Run the editor with the -opengl4 switch.
  3. Press the “Settings” button in the toolbar, and go to “Scalability”
  4. Select “Medium” or lower.
  5. The setting should now take effect, but will not and instead a warning is shown in the active terminal window.
4

I’ve set the scalability as you described in your steps however my terminal is not reporting any warning. When switching from Epic settings to Medium settings, my terminal shows the following:

[2016.01.11-21.41.59:325][116]LogContentStreaming: Texture pool size now 400 MB
[2016.01.11-21.41.59:337][118]LogRenderer: Reallocating scene render targets to support 1168x664 (Frame:14707).

Switching back from Medium to Epic has a similar message but with an increased texture pool size:

[2016.01.11-21.42.11:699][436]LogRenderer: Reallocating scene render targets to support 1168x664 (Frame:15217).
[2016.01.11-21.42.11:729][436]LogContentStreaming: Texture pool size now 1000 MB

Again, switching back and forth printed these sets of output to the terminal. This was tested in 4.10.1 as well as the current 4.11 available on GitHub. Can you let me know if you still see the same message when using the latest 4.10 or the 4.11 branch?

5

Turns out this was due to old leftover settings in DefaultEngine.ini, since the project had been converted sequentially up from 4.8 a couple of times. I had forgotten I was reusing some parts for new projects as well, and thus the issue carried over. Completely fresh projects do not display this problem.

Thanks for the help!