Particle-System | Particle System experiment designed to benchmark | Binary Executable Format library

When you want to select some objects to be fused (or clicked) and exclude others, you do this with the raycaster component, which works with the cursor (or can work without it, but for fusing, use with the cursor component).

Then on every entity that you want to include in the raycasting, add the attribute class="clickable"

Here is the documentation on raycasting and cursors:

https://aframe.io/docs/0.9.0/components/cursor.html#fuse-based-cursor

I am very surprised that particles would participate in raycasting, as they are gpu instances only. They are not actually 3D entities in the scene, but generated and rendered as geometry shaders on the graphics card. Ray casting occurs before all the geometry is sent to the graphics card. Have you tested turning the raycasting on and off while particles are visible to see if that is causing the slowdown?

Your code does not show the cursor or raycasting so I don't know if you are filtering entities, but it does not appear that you are using the class filter on your entities, so it appears that you are not filtering the raycaster.

I was in the process of typing up a response, suggesting the use of the animation component (included in 0.9.0 core) rather than a-animation (deprecated, and removed in 0.9.0), which I would still recommend in general practice, but I realized that the animations still do in fact fall out of sync.

I'm assuming this is due to any of the following:

• The extremely short interval (dur). The higher you set this, the less noticeable the timing issue.
• A difference in overhead due to how the animated properties are targeted, e.g., raw property vs. attribute (using setAttribute under the hood).
• IIRC, loops are set with either setTimeout or setInterval under the hood. Rather than rely on this, you may want to disable looping and trigger these animations by emitting a timed event so you can guarantee that they're executed simultaneously. You can create a custom component that does this using a throttled tick handler, setTimeout or setInterval.

I also suggest using either linear or easeInOutQuad for the easing as the default setting only eases in one direction, which can cause an undesirable effect.

Either way, you may want to submit this as a bug to the A-Frame repo: https://github.com/aframevr/aframe/issues/new

As suggested:

The answer to my particular problem: "How to get an existing Unity ParticleSystem to play through script" (slightly more descriptive title). Has been solved. Please note further research is required to understand why the answer worked.

One setting in the ParticleSystem is called Prewarm. Enabling that setting allowed the system.Play and system.Stop code to start and stop the particlesystem. As previously stated, I as yet do not know why changing that setting to true (enabled) allowed the code to work.

No proper research was done. I was simply playing with settings, one at a time.

confetti.object3D.visible = false or confetti.removeAttribute('particle-system')

This fairly normal, considering Color uses floating point colors, taking values ranging from 0 to 1.

As your values are rounded, they all end up at 1, which in your case leads to pure white.

If you wish to use 0-255 ranged colors, you should use Color32 instead.

I've used the following code in some of my projects:

This example should help: https://glitch.com/edit/#!/a-frame-mouse-click-example?path=index.html:1:0

For the hover, you could use the event_set component (though outline is a bit harder, perhaps there's an outline component out there) and then use js for click handlers to navigate to another url:

Hover example:

At the moment, we can't read the MinMaxCurve from scripts, as per here: https://blogs.unity3d.com/2016/04/20/particle-system-modules-faq/ (scroll down to the Easing the Pain section).

However, your code returns not a MinMaxCurve, but the Start Color of type Color that you can set via inspector or via script.

For example, if you create a Particle System game object in a scene, and you attach to it this simple script:

It's important to understand that A-Frame doesn't work with React out of the box.

Whenever you include a tag like in your JSX, React will expect it to match to an existing component. That's because all of the tags in JSX map to components (either built-in ones like or custom ones).

So what you'll need to do is use a lib that wraps React component logic over these new vr tags like aframe-react