A Few Suggestions and Bugs on WC as Discussed with Greythane on Google

[WhiteCoreWebUI]

[FEATURE REQUEST]

Setting time in .ini for Display Name Update Time with option to enable and disable it.

Loading a OAR or Heightmap on a newly created Region by Prompt.

Ability to set WebUI to "none" when using the PHP Webui
[BUGS]
On a KVM Host Setup WC Can cause a CPU Softlock this mostly happens on multi core systems when there are more than 6 Cores assigned.

[fine77]

KVM had always issues with opensimulator based applications.
i would suggest to not support KVM anymore in this case.
Some peoples have Problems and some are not.
sorry about.

[emperorstarfinder]

It really doesn't come down to whether WC should support KVM. Ideally if your going to run WC in a production environment you shouldn't run it in a KVM environment but some people do choose to do so.

The key here is how the KVM and its host environment are configured. If configured correctly then WC should work just fine (what the correct configuration of the KVM and the Host Environment are though is a whole separate story in itself as I don't personally use KVM for testing or for production level architectures).

I suspect he was doing some tests here which is likely to see errors. As for the WebUI (builtin) being set to none when replaced by the PHP WebUI this can be done by commenting out the Builtin module. However it might be worth looking at a better configuration switch method here.

[greythane]

An update on these...

• The DisplayNames update will be available in the 0.9.4 release
• Loading an OAR or terrain on creation
  Some work has been done on this but it is not yet complete. This should be available in the dev updates soon.
• The default (builtin0 WebUI can be disabled by setting the 'Module = BuiltIn' in the config folders,
  Grid/ServerConfiguration/Modules/WebInterface.ini or Sim/Standalone/WebInterface.ini to anything but 'BuiltIn'
  e.g. to Use the add-on WebUI >> Module = WebUI or Module = None/Disabled/Etc
• The KVM issue is a bit harder as the OS and the thread implementation is out of our control somewhat. Further testing and debug needs to be done on this.