WhiteCore Version of OpenSim – Initial WhiteVue Grid Tests


The WhiteCore branch of AuroraSim, itself a development of OpenSim, has reached its first release 0.9.1. It includes a number of developments including a built in web interface for account creation and other facilities. It does not yet support the HyperGrid.


A trial Virtual University of Edinburgh (Vue) grid was built to test out this release and give feedback to the developers. Import of an avatar Inventory Archive (IAR) and region OpenSim Archive (OAR) was also tested.

2014-05-02-WhiteCore-Tests-1 2014-05-02-WhiteCore-Tests-2


Initially I ran with the configuration set to use SQLite, Grid Mode, No-auto Avatar Registration and using the initially recommended WhiteCore.Server plus four secondary servers plus the WhiteCore region server. It turns out that using a single instance for the WhiteCore.Server rather than starting the four secondary servers is recommended, and the build instructions will be changed.


The three red errors showing on the region server console on startup indicate a few minor LSL script problems, likely because of use of osFunctions in the OpenVCE OAR that was loaded.

This entry was posted in OpenSim, Virtual World and tagged , , . Bookmark the permalink.

1 Response to WhiteCore Version of OpenSim – Initial WhiteVue Grid Tests

  1. bat says:

    Noting here some errors and issues as they arose in testing… when things settle down these may be reported via the proper channels when the issue reporting mechanism is established.

    Running with initial configuration selected as SQLite, Grid Mode, No automatic registration of avatars, Server port 8002, Region port 9000. using WhiteCore.Server.exe, four secondary servers and WhiteCore.exe.

    Initial Avatar Setup Issues

    Error thrown when using initial run of WhiteCore.exe console when creating initial region when the avatar does not exist…

    Exception: System.NullReferenceException: Object reference not set to an instance of an object. at WhiteCore.Services.DataService.LocalUserAccountConnector.Store(UserAccount data) at WhiteCore.Services.SQLServices.UserAccountService.UserAccountService.StoreUserAccount(UserAccount data) at WhiteCore.Services.SQLServices.UserAccountService.UserAccountService.CreateUser(UserAccount newAccount, String password) at WhiteCore.Services.SQLServices.UserAccountService.UserAccountService.CreateUser(UUID userID, UUID scopeID, String name, String password, String email) at WhiteCore.Services.SQLServices.UserAccountService.UserAccountService.CreateUser(String name, String password, String email) at WhiteCore.Modules.Estate.EstateInitializer.CreateEstateInfo(IScene scene) at WhiteCore.Modules.Estate.EstateInitializer.FinishStartup(IScene scene, IConfigSource source, ISimulationBase openSimBase) at WhiteCore.Region.SceneManager.StartModules(IScene scene) at WhiteCore.Region.SceneManager.StartRegion(ISimulationDataStore simData, RegionInfo regionInfo) at WhiteCore.Region.SceneManager.StartRegions(Boolean& newRegion) at WhiteCore.Region.SceneManager.PostStart() at WhiteCore.Simulation.Base.SimulationBase.StartModules() at WhiteCore.Simulation.Base.SimulationBase.Startup() at WhiteCore.Simulation.Base.BaseApplication.Startup(IConfigSource originalConfigSource, IConfigSource configSource, ISimulationBase simBase, String[] cmdParameters)

    Attempt to create an avatar also via the WhiteCore.AvatarServer.exe console using create user appears to work, but the avatar seems not to be set up correctly, and cannot be selected as the owner of a region when the initial region setup is done.

    The command create avatar appears not to accept parameters. When the parameters were given on the command line, it still asked for input for all the entries via the console prompts.

    Creating avatar via the web interface worked. Then I could rereun WhiteCore.exe and set up the initial region and point it at the precreated avatar.

    .NET Issue perhaps needing loadFromRemoteSources

    WhiteCore.exe console threw this error message, indicating that “loadFromRemoteSources” must be set in the relevant config files. This is an issue relating to the change from .NET 3.5 to .NET 4.0 and addressed in the recent OpenSim 0.8.0 dev core. See http://opensimulator.org/mantis/view.php?id=6846:

    [ConsoleThread] WARN – Unrecognized rendering plugin D:\VW\Whitecore\bin\OpenMetaverse.Rendering.Meshmerizer.dll: Could not load file or assembly ‘file:///D
    :\VW\Whitecore\bin\OpenMetaverse.Rendering.Meshmerizer.dll’ or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)
    System.IO.FileLoadException: Could not load file or assembly ‘file:///D:\VW\Whitecore\bin\OpenMetaverse.Rendering.Meshmerizer.dll’ or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)
    File name: ‘file:///D:\VW\Whitecore\bin\OpenMetaverse.Rendering.Meshmerizer.dll’
    —> System.NotSupportedException: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information.
    at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark&
    stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
    System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMar
    k& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIn
    trospection, Boolean suppressSecurityChecks)
    at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
    at System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark& stackMark)
    at System.Reflection.Assembly.LoadFrom(String assemblyFile)
    at OpenMetaverse.Rendering.RenderingLoader.ListRenderers(String path)

    WhiteCore Web UI Issues

    Avatar registration pages shows {ErrorMessage}
    WhiteVue: Avatar registration

    The * indicates which entries are compulsory I assume. Can all rest be omitted? Including e-mail which I would think was necessary for password recovery? Maybe add a note at bottom to say so?

    * Required entries. Others are optional.

    Reference to address zip code and city is very US centric. Better just to include address and country?

    Date of birth also is in the odd US centric Month Day Year order which will throw some people especially as all are selectable via a numbers drop down list. Maybe make month be the words to clarify that or allow a simpler dd-Mon-yyyy format?

    The web interface avatar profile page uses the US centric, and internationally confusing, mm/dd/yyyy format which is badly ambiguous for days 01..12.

    The date format in the consoles uses dd/mm/yyyy which is not useful internationally… and is badly confusing since US centric mm/dd/yyyy is used elsewhere. I suggest dd-Mon-yyyy be used throughout as internationally unambiguous.

    On the web page related to regions, and the welcome pages, etc… the link given is to a secondlife://region/x/y/z link to launch the viewer. A hop://gridname:port/region/x/y/z would be ore useful.. and allow for proper grid selection in modern OpenSim capable viewers.

    The Viewer help page does not include Firestorm.

    The language options appear not to work yet.


    Administrator Validatiion of Avatar Creation Requests

    I selected not to allow automatic creation of avatars on viewer login. But it seems that the web interface allows for avatar creation and has no option to have these held for administrator approval. This would be needed in a range of production and closed grid environments, typical of university usage. is this already configurable by manual configuration file change somewhere (I looked and could not find it at the moment). if not, please treat this as an important feature request.

    OpenSim OAR Compatibility and LSL Compile Errors

    On loading the OpenVCE OAR there are a few script compile errors, indicating some difference to standard OpenSim…

    [02/05/2014] 11:50:53: Error compiling script:
    (51,54) syntax error prim name: Teleport to OpenVCE Central Plaza@ item name: Show on Map, CompiledFile: ScriptEngines\569\5695252c-3f47-445c-b304-f11b0ea6d65b.dll

    [02/05/2014] 11:50:54: Error compiling script:
    (0,0) Invalid argument in ‘on_rez’ prim name: Give Region Xloc and Yloc@ item name: Region Xloc and Yloc, CompiledFile: ScriptEngines\cab\cab6789e-1076-4076-92fe-e8f862886134.dll

    [02/05/2014] 11:51:10: Error compiling script:
    (230,34) syntax error prim name: Federated window system@ item name: Dialog module, CompiledFile: ScriptEngines\f49\f494f2c7-ff8b-4373-a616-eae926a15b4b.dll

    [02/05/2014] 11:51:10: [WDNE]: Found bad version ID in queue, resetting, 0 to 1
    [02/05/2014] 11:51:10: [WDNE]: Function: ‘unknown’ in region WhiteVue
    …Repeats of these…

Comments are closed.