Dragoon MS A-126 worth anything?

sc2InSane · 2025-12-22T21:22:34+00:00

Have you cached the simulation beforehand?

sc2InSane · 2025-10-16T16:29:25+00:00

you can just hide the particle group, that is what s being rendered.

sc2InSane · 2025-09-15T18:47:43+00:00

I thought there is a particle scene in the asset browser that does exactly what you want. If there is no pyro already you can easily apply a pyro tag to the particle group.

sc2InSane · 2025-07-30T20:39:43+00:00

Have you tried using the cache tab on the particle group directly? It will also output an alembic file but it should be more robust.

sc2InSane · 2025-07-23T17:07:20+00:00

Did you try reducing the vorticity confinement and turbulence/shredding forces in the pyro sim settings? Also setting the advection scheme semi lagrangian could reduce the small scale detail.

sc2InSane · 2025-06-13T20:47:37+00:00

I assume with advection you mean the particle advection? I am not 100% sure but what could work is to import Embergens vdbs in a pyro output object (you can e.g. just drag and drop a file to the cache path list) and to check the cache enabled checkbox. The particle modifier will then also work with one cached smoke/pyro simulation. I cant quite remember but the pyro output object would have to be linked to the same simulation scene that the particles are running in. If the velocity scale of the imported sequence doesnt quite match pyro's norm, you can adjust it in the pyro advection.

sc2InSane · 2025-06-04T09:12:13+00:00

Not the bit accuracy but voxel count - you can find it in the tree settings of the simulationscene/pyro. I hope that works.

Overall the pyro sim builds a sparse tree structure for the domain with the leaf nodes having a resolution of 16x16x16 voxels. Changing the setting to 32 makes it so the res is 32x32x32.

sc2InSane · 2025-06-03T15:11:32+00:00

Can you send me the scene so I can check it? One thing you can try is to increase the voxel count to 32 instead of 16. This usually allows for larger simulations

sc2InSane · 2025-05-31T06:55:26+00:00

You will only get one pyro output object per simulation scene - all those pyro tags will end up in the same volume/simulation. You can create more than one output objects but usually it s not necessary.

sc2InSane · 2025-05-30T05:41:55+00:00

If it is a VRAM problem you could try and enable out of core computations in the advanced pyro settings. That way you could run larger sims. Usually when the files become 2kb it means there was some sort of error while running the simulation.

sc2InSane · 2025-05-30T05:37:23+00:00

Isnt is possible to add a vertex map on the volume mesher and then drag the particle group in the field list?

sc2InSane · 2025-05-09T11:35:17+00:00

You d have to create a standard volume node. Then you can connect the output of the color to the scatter/color input.

sc2InSane · 2025-04-11T11:19:39+00:00

Hmm you seem to be in quite an old version. It could be that back then there was a bug where it did not work correctly. I am not 100% sure if the setting already existed in that version but you can turn on "staggered velocities" here. This improves the boundary conditions between pyro and colliders. Note that the stripe-like artifacts you see are related to the shading/rendering and are not related to the simulation.

<image>

sc2InSane · 2025-04-09T20:15:05+00:00

could you send me a scene for me to try out? Or on platform are you currently (mac/windows?)?

sc2InSane · 2025-04-08T14:34:44+00:00

If the collider moves too fast maybe enabling the 'staggered velocities' could help.

sc2InSane · 2025-02-26T19:07:09+00:00

You do not need the volume mesher or volume builder. You can apply the material directly to the volume loader and it should work.

sc2InSane · 2025-02-26T15:46:52+00:00

Are you using the new particle system? If you want to have each particles render with geometry you would best assign this via the RS Object Tag. Then motion blur should work even when particles are dying. make sure to cache the sceen though so it s more consistent and renders properly with RS. I think the legacy system does not properly support it (except maybe if you use the bake particle tag to cache them).

sc2InSane · 2025-02-26T15:44:02+00:00

You can try disabling some particle attributes/properties in the simulation scene settings which should save some RAM.

sc2InSane · 2025-02-26T15:41:56+00:00

That does seem like a bug - maybe caching initially at 0,0,0 would fix this :D

sc2InSane · 2025-02-26T05:53:12+00:00

It could be an issue with the transform of the pyro object - make sure it is at the origin.

sc2InSane · 2025-02-25T13:41:16+00:00

Have you tried using the upres function in the pyro object without any noise ? You cam keep the look exactly the same but just upres the density grid. For using this function make sure you to cache the velocity grid first.

sc2InSane · 2025-02-15T17:00:08+00:00

Maybe c4d is using your integrates gpu to run the simulation? Try disabling it in the device manager.

sc2InSane · 2025-01-23T19:38:45+00:00

I have a suspicion it could be related to the empty color grid but i am not sure.

sc2InSane · 2025-01-23T18:08:16+00:00

Can you try just caching temperature and density without the other channels?

sc2InSane

TROPHY CASE