New version impedes PCX importer to work: v0.4.0: URP/HDRP support, easier PLY workflow, smaller chunk info Latest about unitygaussiansplatting HOT 10 CLOSED

Ah! I guess I could make it so that people have to rename their gaussian splat point clouds to some other extension, e.g. .gply. Would that work?

from unitygaussiansplatting.

Not the original poster but I think it would. However I think this points to a flaw somewhere. On one level - the Splatting community should probably settle on their own extension. These are regular .ply files only in the loosest sense so a new extension makes a lot of sense and would ideally be adopted widely.

But another aspect is that Unity's scripted importers are really annoying! This isn't the first time the tight coupling between importer and file extension has caused problems.

from unitygaussiansplatting.

@andybak looks like Unity scripted importers do have some functionality where multiple importers could co-exist. I'll investigate https://docs.unity3d.com/ScriptReference/AssetDatabase.SetImporterOverride.html and friends and will report back. Thanks for notifying me, I was not aware that other packages also want to import PLY files!

from unitygaussiansplatting.

Ah! I guess I could make it so that people have to rename their gaussian splat point clouds to some other extension, e.g. .gply. Would that work?

Thanks, I imagine that might work. PCX is very established for PLY, it has a lot of functionalities and works with VFX. I’m eager to produce visuals using both packages. I was able to add the GaussianSplatURPFeature to an asset renderer on version 3, but it only worked by replacing the GaussianSplatRenderer and deleting the GaussianAssetCreator, but my previous created assets still don’t visualize. The GaussianSplatRenderer panel even shows a message that say the asset was created in a previous version. Thank you for considering this issue!

from unitygaussiansplatting.

I was hoping that using ScriptedImporterAttribute.overrideFileExtensions would work nicely, as in I'd register no "primary" extension, only the ply as an override extension. And then indeed it works nicely, if both GaussianSplat and PCX are in the project - PCX is used by default, but you can override the asset to be imported as GaussianSplat instead.

But! Then it does not work at all if PCX is not in the project; the asset just is not imported at all. Oooof!

I guess I'll get back to not using a custom importer afterall, i.e. back to the "create asset" window thingy.

from unitygaussiansplatting.

Thank you for trying that! Yes, the create asset window, prior to the URP/HDRP update, worked great with PCX.

from unitygaussiansplatting.

Should be fixed now in v0.5.0

from unitygaussiansplatting.

Should be fixed now in v0.5.0

Thank you so much for implementing this, @aras-p . It works!

Sometimes I've had some memory leakage alerts when selecting ply files on the project window, but I've been able to ignore them. Runtime works normally.

[00:07:17] [Worker1] Internal: There are remaining Allocations on the JobTempAlloc. This is a leak, and will impact performance
[00:07:17] [Worker1] To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
[00:07:26] [Worker4] Internal: There are remaining Allocations on the JobTempAlloc. This is a leak, and will impact performance
[00:07:26] [Worker4] To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
[Worker4] To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
A [Worker4] To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.

from unitygaussiansplatting.

One thing I did so the various glTF importers could happily co-exist was to make a scripting define to specify if the „fileExtension“ should be used (default) or if „overrideFileExtension“ is used.

This allows for both, the nice import workflow and coexisting importers. People that have both pcx and splats have to set the scripting define manually (can also be automatic with a version define in an AsmDef).

from unitygaussiansplatting.

@hybridherbst yeah that might work, but also a step that someone has to actually do :/ Right now I'll probably keep on not using a scripted importer, given that it has other issues (namely: there's no way to efficiently store the imported "bunch of bytes" without making either inspector slow, or domain reload slow -- waiting for Unity to add TextAsset constructor that takes byte array as input).

from unitygaussiansplatting.