So Ive followed the standard steps to creating an explosion sequence but the actual visuals are set far out into the distance with nothing telling it to be that far. All items are spawned are by default spawned in the center of the scene.
In the C4D viewports the effects show it centered.
Xparticles VDB Offset in Live Viewer
Moderators: ChrisHekman, aoktar
how do you use volume?
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
I have a rather simple setup, just spawning it in a default position in the middle of the grid with using D:\XP_Cache\xpExplosiaFX\xpExplosiaFX_000001.vdb
Position X,Y,Z ARE AT 0,0,0 meters.
VDB Loader
0 offset
0 start
90 end
6 digits
The volume seems to be the only thing affecting its position because when I move it the whole particle effect moves with it unlike the other things in the scene (xpCache, epExplosiaFX, Sphere w/ exEFX Source Tag.)
Position X,Y,Z ARE AT 0,0,0 meters.
VDB Loader
0 offset
0 start
90 end
6 digits
The volume seems to be the only thing affecting its position because when I move it the whole particle effect moves with it unlike the other things in the scene (xpCache, epExplosiaFX, Sphere w/ exEFX Source Tag.)
You need to reverse the z scale for xp
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
I already have looked through that thread, even changing the Z axis.
Is there a version of Octane and Xparticles versions I should be using?
I am using the most current Xparticles 4 plugin and Octane 4 with Cinema 4D Studio R19.
I am using the latest Studio Driver from Nvidia.
I still feel like Im missing something.
Is there a version of Octane and Xparticles versions I should be using?
I am using the most current Xparticles 4 plugin and Octane 4 with Cinema 4D Studio R19.
I am using the latest Studio Driver from Nvidia.
I still feel like Im missing something.
When I was at NAB talking to the Insydium team, I brought up this issue. I was told to nest the volume underneath a null, as that can, along with the negating of the Z axis, can help. In some cases, nesting under a null and negating the Z on the null instead of the volume might be a better solution. I wish I could recall the discussion more precisely, but it was with either Bob Walmsley, Jon Bosley or Mike Batchelor. If you ask on the Discord channel, I am sure one of them can jump in and offer guidance.
CaseLabs Mercury S8 / ASUS Z10PE-D8 WS / Crucial 64GB 2133 DDR4 / 2 XEON E5-2687W v3 3.1 GHz / EVGA 1600 P2 / 2 EVGA RTX 2080Ti FTW3 Hybrid/ Cinema 4D
Is it fast? Oh, yeah!
Is it fast? Oh, yeah!
You can get to it through the Insydium website.
CaseLabs Mercury S8 / ASUS Z10PE-D8 WS / Crucial 64GB 2133 DDR4 / 2 XEON E5-2687W v3 3.1 GHz / EVGA 1600 P2 / 2 EVGA RTX 2080Ti FTW3 Hybrid/ Cinema 4D
Is it fast? Oh, yeah!
Is it fast? Oh, yeah!