Limitations on the use of `atom.json` model in open source projects

[GitHubDragonFly]

This is actually a question but could serve as a suggestion on adding additional info to the description in the repository (info related to any limitations).

I am considering adding this atom to my Cube Shading example but would need to know of what limitations are there.

I can see that the atom is featured on the official Quarks VFX website page but is also available to be downloaded from the Sandbox Example.

My intention would be to include the atom within the box being shaded and reveal it when it gets transparent, like the attached picture shows.

[Alchemist0823]

Hi @GitHubDragonFly, thanks for posting. Can you talk a little bit more about what you are trying to achieve here? I don't fully understand the question here.

If the material of the box doesn't write depth buffer, it will render as the picture you attached. you can set the any material's depthWrite to false new BasicMeshMaterial({depthWrite: false}), then the particle system will show up in your view.

[GitHubDragonFly]

@Alchemist0823 thank you for the reply.

My question is about using the atom.json file itself:

• Does it have any specific license attached to it?
• Can I include it in my repository?
• I could not find it available in this repository, otherwise I could just try using GitHub URL to it

The picture that I posted shows pretty much how I would use it in my example. The atom would be hiding within the box and only show when the box sides become transparent.

This is already working on my end and the only question is whether this file is off limits for public use.

[Alchemist0823]

Yeah it's free to use in any projects. I should add more information regarding to the license of those assets. Thanks for asking.

[GitHubDragonFly]

Thank you for letting me know.

I have just included it and you can see how it works in my Cube Shading example.

It appears to be working properly in Firefox / Chrome / Safari browsers on both Windows and Mac OS.