Bug In 2022.1.b11, lost subgraph if I open vfx.

Hi @shibiUNITY ,

This shouldn't be happening; can you please log a bug with the vfx and subgraph(s) in question so we can take a look? Also, are there any console errors?

Thanks!

 

Are the two issues you mentioned related?
I just tried renaming a subgraph and did not reproduce the same issue. (the link is though the file's ID, not its name, so renaming it should not affect it).

If you can file a bug with the assets causing you issues we can take a look, otherwise I'm afraid it's a bit hard to say what's going on.

 

Output Events are a way to pass the initial values set in the Spawn context over to C#.
In the VFXOutputEventRigidbody example, here's how the script maps to the VFX attributes:

In the same example, it is simply using the velocity attribute you set in the VFX Graph to add force to the rigidbody:

Code (CSharp):

1.          switch (eventType)
2.             {
3.                 case RigidBodyEventType.Impulse:
4.                     rigidBody.AddForce(velocity, ForceMode.Impulse);
5.                     break;
6.                 case RigidBodyEventType.Explosion:
7.                     rigidBody.AddExplosionForce(velocity.magnitude,  position, size);
8.                     break;
9.                 case RigidBodyEventType.VelocityChange:
10.                     rigidBody.AddForce(velocity, ForceMode.VelocityChange);
11.                     break;
12.                 default:
13.                     break;
14.             }

You are just inheriting any attributes set in the Spawn context with SetSpawnEvent [Attribute] for the specific effect you are referencing:


And this bit is for optimization only, as it's faster to look for an int that do string comparison:

Code (CSharp):

1. static readonly int k_Position = Shader.PropertyToID("position");
2. var position = eventAttribute.GetVector3(k_Position);

You can also directly do this:

Code (CSharp):

1. var position = eventAttribute.GetVector3("position");

("position" can be replaced with anything else you want to inherit, "age", "color", etc.)

You can view in the Inspector the names of all attributes used for a context by selecting a context. In this case, all attributes available in Initialize:

These are the names you can refer to in your code, and as long as they are set in the SpawnContext, you can grab them in C# and then create your custom logic on what you'd want to do with them (like in the rigibody example, add physics force based on the velocity attribute value, or in the AddExplosionForce option, add a directional explosion based on the velocity, position, and size attributes)

Important to note, you can only get the initial values with Output Events when the particle first spawns, this will not allow you to continue tracking its values over the particle's lifetime.

Hope this helps!

 

I can see the same issue on my side! We'll take a look, thanks for raising this!
You can track the resolution here (it may take a few hours for the link to go live)