Priority 1
Some of cvars declared using DeclareConstIntCVar contains uninitialized value in release build. This fix sets such cvars to its default value.
For example cvar: e_MemoryProfiling. For release there is only declaration but initialization is excluded by RELEASE define as result we have random cases when such cvar is not zero and memory profiling info is displayed on the screen
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Priority 1 Some of cvars declared using DeclareConstIntCVar contains uninitialized value in release build. This fix sets such cvars to its default value. For example cvar: e_MemoryProfiling. For release there is only declaration but initialization is excluded by RELEASE define as result we have random cases when such cvar is not zero and memory profiling info is displayed on the screen
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.