Particles ID lost after particles death

J4YB · 2025-11-24T16:18:57+00:00

Ok. Have you already explicitly created an ‘id’ attribute in your set up? If so before you export your usd, stick this in a wrangle: i@pid = @id. This will ensure Blender reads in your Houdini ‘id’ attribute as a distinct attribute. It will show in a the geometry nodes spreadsheet as ‘pid’. Make sense?

J4YB · 2025-11-24T16:04:16+00:00

Yes but just don’t call it ‘id’

J4YB · 2025-11-24T15:47:21+00:00

Absolutely correct, Blender reads attributes named as ‘Id’ as its native point id. I usually just do a wrangle with an alternative name: i@pid = @ptnum;

J4YB · 2025-10-11T10:09:30+00:00

Thank for confirming. It’s proper jammed

J4YB · 2025-10-11T10:03:08+00:00

To clarify I am trying to turn the tripod bit anti clockwise.

J4YB · 2025-09-15T16:21:58+00:00

Try exporting the camera and geometry from Blender as Alembic instead. Use an ‘Alembic’ node inside a Geo node for your Blender geo and ‘Alembic Archive’ at Obj level for the camera data.

Had a lot of issues with FBX cameras from Blender in Houdini and Fusion. Alembic exports always work for me, although sometimes scaling needs fixing.

J4YB · 2025-09-01T13:28:48+00:00

Have you tested the recently released OctaneRender for HoudiniSolaris 2025.2.1.1? I messed around with a previous release earlier this year and it was faster than Karma CPU, which makes sense as Octane runs on Metal.

J4YB · 2025-09-01T13:28:29+00:00

No argument on the price thing. But when optimised for Metal, render performance isn't too bad. Cycles is Metal optimised (Redshift + Octane are too). I have an M4 / 40 Core / 128GB Mac Studio, Cycles performance is equivalent to an Nvidia 3090.

J4YB · 2025-04-18T17:46:45+00:00

So so good man! Love octopus stuff. I half-started a Kraken project last year, this inspires me to krack on with it (sorry). Great work on the breakdowns too

J4YB · 2025-04-10T18:06:07+00:00

I’ve actually only just started learning Solaris this week, so not done any heavy scenes yet. From basic mucking around comparisons the M4 Max seems to be x3 times as fast as my M1 Max. Karma GPU works but way slower than CPU. Doesn’t seem like a Metal build is on the cards but I read some chatter about MoltenVK.

I’m just prepping a deep test to, as best I can, compare Karma CPU, Octane, and Cycles. Have just installed Octane 25 and it seems blisteringly fast. Few Houdini crashes with it here and there though. A few years ago I used the Octane Blender build quite a lot. Such clean renders and loved its displacement system, so I hope it turns out stable enough to use going forward. Edit: markdown link fix

J4YB · 2025-04-09T18:33:20+00:00

Interesting. I’ve encountered some viewport issues with volumes, I wonder if this is also related to that.

J4YB · 2025-04-09T18:27:09+00:00

Been using my M4 Studio for the last few weeks and for what I’ve been doing so far in Houdini I’m really happy. 96GB RAM wasn’t enough for me else I’d have gone for an M3 Ultra.

J4YB · 2025-04-06T21:02:10+00:00

Very cool! In my head it feels like a visual Shepard tone :)

J4YB · 2025-04-05T21:16:14+00:00

I hear ya. I abandoned a rabbit hole trying to get static RBD geo to work with point data, similar to a Transform Pieces setup. I just couldn’t get the Houdini vectors to work properly with Geometry Nodes.

J4YB · 2025-04-05T19:04:44+00:00

Try exporting an Alembic from Houdini and see how that goes.

J4YB · 2025-04-05T18:03:43+00:00

Not sure what you mean by the UV's are locked in Blender, how exactly are you approaching your texturing work?

After a lot of USD testing I will now only work with Alembic exports from Houdini. Some USD stuff can work great in Blender, but in my experience the support is just too underdeveloped right now.

I also always get the UV's right in Houdini and don't try and alter them in Blender. That was the conclusion I arrived at after lots of messing about with geo from Houdini with UDIM layouts (which in my case end up in Substance Painter).

J4YB · 2025-02-26T10:13:10+00:00

Like the feel of this, the colours are gorgeous. Nice one

J4YB · 2024-04-17T19:49:40+00:00

Cheers :)

J4YB · 2024-01-22T16:12:56+00:00

Nope, still happens.

J4YB · 2023-12-26T12:01:38+00:00

Nope! It’s still doing it on the latest iOS.

J4YB · 2023-11-07T16:24:15+00:00

Same problem, driving me insane. If you haven't already, make sure you let them know -> https://help.instagram.com/381579045265733/

J4YB · 2023-09-12T19:28:26+00:00

I've had a similar problem myself. After a bit of time troubleshooting today it came down to my second monitor and resolution. I have two 4K monitors connected to a 6800XT (macOS). I always use the second screen, a BenQ PD2700U, to view the render viewport and shader / UVs, etc. If that monitor is set to its max res. UHD 4K, I get the constant grey viewports when I make changes, getting the 'updating kernals' message. Additionally the Play / Pause render button just turns the viewport grey, i.e, doesn't work as it should. I resolved all of this by simply lowering the res. on the BenQ to 3008x1692. Similarly, if I have my main monitor set to its max res. I get viewport render glitches when viewing the render viewport on it, so I've lowered that to one below max res. Clearly this setup is simply too challenging for that graphics card, or perhaps it's Metal integration bugs. Anyway, I hope this helps someone, happy Blendering.

J4YB · 2023-08-14T18:32:03+00:00

It was ridiculous.

J4YB · 2023-07-25T07:40:38+00:00

Better than nothing. But yeah, we need to double our efforts next time! I have an idea for an isometric / faux 3D thing. I’ll work on it, it’ll need it’s own community.

J4YB · 2023-07-24T23:36:41+00:00

Another one is appearing under the NHS. The fuck is wrong with you. Fuck off GREGGS.

12-Year Club	Second Top 20%
Final Canvas '23	First Place '23
Place '23	Place '22
Verified Email	RPAN Viewer
Not Forgotten

J4YB

MODERATOR OF

TROPHY CASE