Mesh issues

[Ana-Green]

Load the OAR file on a region - shutdown region then restart the region again Mesh looks good, was editing the build due that I did fall through the floor, looked at the build but the mesh was a mess, corrupted? logged out and removed the region with the command delete-region then used a new OAR file same build after that it was reloaded I did restart the region |console shutdown/restart. That did not work same as before see attachments, I used the same procedure 4 times on Opensim or you like to hear it or not no issues at all

Seems most bug s get not fixed.

Best regards,
Ana Green

[Ana-Green]

As reference I used the same OAR on Halcyon where it was first good 3 days later corrupt re-load from the original OAR did not help on Opensim I did not see any issues of course one would say the compressed OAR from Opensim is broken and therefore it doesn't load correctly on Halcyon. That might be so in case the compatibility is gone, meaning someone broke the compression method or at least to say changed it (for no known reason) so that it can not load from OS - > Halcyon, well done. Don't give me that, fix first known bugs before even thinking about changing stuff.

Regards,
Ana Green

[mdickson]

Its not clear from your report but if you're trying to move OAR's containing mesh from Halcyon to OpenSim and likely in the other direction as well its very possibly going to get errors. If the OAR is generated from Halcyon the protobuf serialization thats used for assets won't be readable by OpenSim at all. Matrerials will also not be preserved. Going in the other direction Halcyon will likely not restore a physics shape correctly, OARS in Halcyon are really only useful for backing up regions in the same grid, The work was never done to make it truly portable to OpenSim or any other platform.

I'm also not aware of any current active development. I just wanted to respond to this because I am very familiar with the Mesh implementation in Halcyon and now also OpenSim.

[Ana-Green]

@mdickson

With some random snips code still from Opensim:

if this is true then all work Dad did on Opensim, all his builds are useless on Halcyon then it is not only a script replacement that needs to be corrected but Dad can re-build all over again and he is not going to do that. The OAR compression format exist already for a long long time and the code Halcyon vs code Open-Sim did change that includes not excludes others parts in Halcyon not only the OAR Import/Export, he can't use it, same if I look in the source "section IAR" Please do not use this but the whole Open-sim code is still in it only disabled or should I say destroyed? I see so many old Open-sim code still in Halcyon why was they're no clean up in the first place Mike? No idea what you mean with "the protobuf serialization"? And yes I am aware not that nobody works on Halcyon, Someone told me this "Jim did do extensive work on correcting the Halcyon Oar handling errors with a lot of improvements. I have noticed some cases where the materials set in OpenSim oars do not import into Halcyon. Usually, that has very little effect and is easily edited for correction on the few items that are missing a set material entry. Only the OpenSim scripts will not work from an OpenSim oar import" Duh yes the scripting engine is also not the same I can also say NPC code inworld does not work in world at Halcyon of course not it has no support for NPC's. And so I think the mesh decoding process is different in Halcyon, better or worse? Well, we will never find out, will we? If this statement is correct " Figure it out! We do not have any developers on Halcyon right now." Why is some Grid even try to create a business Grid from it?

Like this part in Halcyon:

using System;
using System.Collections;
using System.Collections.Generic;
using System.IO;
using System.Reflection;
using System.Text;
using System.Text.RegularExpressions;
using System.Timers;
using log4net;
using Nini.Config;
using OpenMetaverse;
using OpenSim.Framework;
using OpenSim.Framework.Servers;
using OpenSim.Framework.Console;
using OpenSim.Framework.Statistics;
using OpenSim.Region.Framework.Interfaces;
using OpenSim.Region.Framework.Scenes;
using OpenSim.Region.Framework;
using System.Runtime;

All opensim next Opensim Base:

        m_console.Commands.AddCommand("region", false, "load oar",
                                      "load oar [--ignore-errors] <oar name>",
                                      "Load a region's data from OAR archive", LoadOar);

Used in Halcyon as a leftover from Opensim:

And why is this still in Halcyon like so many Opoensim parts?
/// Disabled right?
///

/// The file to load and save inventory if no filename has been specified
///

protected const string DEFAULT_INV_BACKUP_FILENAME = "user-inventory_iar.tar.gz";

    /// <value>
    /// All scenes that this module knows about
    /// </value>
    private Dictionary<UUID, Scene> m_scenes = new Dictionary<UUID, Scene>();
    
    /// <value>
    /// The comms manager we will use for all comms requests
    /// </value>
    protected internal CommunicationsManager CommsManager;

    public void Initialize(Scene scene, IConfigSource source)
    {            
        if (m_scenes.Count == 0)
        {
            scene.RegisterModuleInterface<IInventoryArchiverModule>(this);
            CommsManager = scene.CommsManager;
            OnInventoryArchiveSaved += SaveInvConsoleCommandCompleted;
            
            scene.AddCommand(
                this, "load iar",
                "load iar <first> <last> <inventory path> [<archive path>]",
                "Load user inventory archive.  EXPERIMENTAL, PLEASE DO NOT USE YET", HandleLoadInvConsoleCommand); 
            
            scene.AddCommand(
                this, "save iar",
                "save iar <first> <last> <inventory path> [<archive path>]",
                "Save user inventory archive.  EXPERIMENTAL, PLEASE DO NOT USE YET", HandleSaveInvConsoleCommand);           
        }
                    
        m_scenes[scene.RegionInfo.RegionID] = scene;            
    }
    
    public void PostInitialize() {}

I Responded to this:

-------- Forwarded Message --------
Subject: Re: [HalcyonGrid/halcyon] Mesh issues (#111)
Date: Tue, 08 Sep 2020 05:16:30 -0700
From: Mike Dickson [email protected]
Reply-To: HalcyonGrid/halcyon reply+ait3kzrq3snrux7r42qi6kv5mnlr5evbnhhcsykpiq@reply.github.com
To: HalcyonGrid/halcyon [email protected]
CC: Ana Green [email protected], Author [email protected]

It's not clear from your report but if you're trying to move OAR's containing mesh from Halcyon to OpenSim and likely in the other direction as well it's very possibly going to get errors. If the OAR is generated from Halcyon the protobuf serialization that's used for assets won't be readable by OpenSim at all. Materials will also not be preserved. Going in the other direction Halcyon will likely not restore a physics shape correctly, OARS in Halcyon are really only useful for backing up regions in the same grid, The work was never done to make it truly portable to OpenSim or any other platform.

I'm also not aware of any current-active development. I just wanted to respond to this because I am very familiar with the Mesh implementation in Halcyon and now also OpenSim.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Regards,
Ana Green

[Ana-Green]

The results below are not only from the OAR imports but also howe Opensim handles mesh and how Halcyon currently handles mesh.

Halcyon Mesh Decoding - DreamCastle Grid
https://user-images.githubusercontent.com/36156774/92318020-fc34a500-f006-11ea-8c25-2334a89c8871.png

https://user-images.githubusercontent.com/36156774/92318024-048ce000-f007-11ea-8d0f-f4051147948f.png
Opensim mesh Decoding from DreamScape Grid

Regards,
Ana Green

[sonjamichelle]

Halcyon, well done. Don't give me that, fix first known bugs before even thinking about changing stuff.

No wonder why there are no active developers for Halcyon, with facing an attitude like that I wouldn't want to be involved in a project where I was DONATING my FREE time on a product you DO NOT PAY FOR and you are FREELY allowed to take up the mantle and develop the "deficiencies" you see that are so glaring to you yourself. If you are NOT WILLING to contribute then back off. I've watched you post for quite some time now and the majority of your posts are filled with vitriol and negativity and are composed as if they were written by a kindergartner. And you say you are a NASA engineer if I recall correctly?

Please, contribute something POSITIVE to the project or just BACK OFF.

Halcyon has some promise, it has features like the physics engine that work much better than OpenSim, handles a few things in the scripting engine better, but it does have it's shortcomings like it's dependence on Windows. But if all the potential developers get are negativity, headaches and backlash then I don't blame them for not wanting to touch the project with a ten foot pole. We HAD two really good developers, they were both basically run off because of the BS and decided to get back to their day jobs, I don't blame them. I even took a major step back from the project as a user and tester. I lurk and watch, but I today I just had to speak my two cents.

[Ana-Green]

Sure, wait till my daughter is back. Have a nice day.

Frank Orbis

[Vinhold]

Most of the oars Frank has loaded into his Halcyon world have had no problems. There has been a couple of them that did not load all of the content - some parts were mesh and some not. This could be due to whatever version of OpenSim oar was the source and not all was read by the Halcyon importer.
Jim had done a rewrite of the oar save and load process to correct several issues discovered after the collapse of InWorldz. That has been a big improvement especially with Halcyon oar exports to load into OpenSim or other Halcyon worlds. They work perfectly Halcyon to Halcyon as I have done a lot of those transfers in the last year.
OpenSim oars into Halcyon is a general roll of the dice for what will work OK and what will not.