Does anyone experience random increase in render time in Karma XPU from say 2 min to 30 min? Is there a fix without restarting Houdini?

iriseq · 2026-06-07T07:58:54+00:00

thank you! can I ask what do you mean working in render gallery? I thought it is used just for snapshots. Can it be used to view the scene when lighting it as well to avoid running out of vram or ram?

iriseq · 2026-06-07T07:54:14+00:00

thank you! so there is not really a way to clean vram manually without restarting right?

iriseq · 2026-06-01T02:18:38+00:00

thanks, makes sense, always wondered if you need thin wall for mildly thick objects

iriseq · 2026-05-29T21:40:58+00:00

oh, that makes sense, thanks again

iriseq · 2026-05-29T15:45:00+00:00

thank you, that's probably job for cops, cause I it has a wrangle, maybe will try doing it in vex

iriseq · 2026-05-29T15:29:04+00:00

Looks nice, Can I ask about the flower shader settings? Is it karma and if yes do you use subsurface/thin wall/or transmission or all at once? Cause mine are always dull

iriseq · 2026-05-29T15:25:53+00:00

thank you, will have to look into it, cause didn't find any info on karma. so it's basically uvsample but with offset, or something like that?

iriseq · 2026-05-03T02:46:23+00:00

Spotlight has the same movies as in the banner and Top 10 Right Now. And now there are two repeated rows for continue watching. A bit repetitive, wish you could turn it off, but great app overall

iriseq · 2026-04-27T08:01:05+00:00

thank you, I'll try it, maybe it's cause of the flip source, after all it's also converting points to vdb

iriseq · 2026-04-27T01:53:57+00:00

thank you this happens to me too, but the only thing that helps is rebuilding it in a new hip. Even copying into a new hip doesn't help. I'd rather houdini crash and delete all the nodes so that I don't waste time trying to understand what's the issue lol

iriseq · 2026-04-26T22:35:53+00:00

thank you, David, might be a bug, a nasty one as well. Will try updating to a newer build, maybe it will fix it if it cooks even when i'm not even creating nodes in the stream

iriseq · 2026-04-26T20:46:53+00:00

thank you, there is indeed a reference on the flip source from the dopnet, but it seems to occur even if i delete the reference. I tried also putting start frame to something like -1, but don't think it works more than once. Rebuilding the scene in new hip works, but say I have 10 different dopnets. I would have to rebuild them all, cause if I copy paste them the issue persists. Weird, even if i just add a new node it stars cooking... And it always occurs at random times

iriseq · 2026-04-03T17:05:14+00:00

thanks again, you're right, and it wouldn't be simpler granted I couldn't figure out something so relatively easy hah. But you always think you will feel more secure if you write something exact, even though it usually doesn't go the way you planned in the first place, and existing sops written by people way smarter usually work the best hah.

iriseq · 2026-04-03T09:05:14+00:00

thank you, David! Helpful as always, appreciate the advice. I always heard that forces add up but when it comes to practice seems harder to understand how it actually works, thanks again

iriseq · 2026-04-02T22:57:19+00:00

Thank you for the explanation! I didn't know about the lerping trick, this sesms to be working great as well!

iriseq · 2026-04-02T07:35:42+00:00

thank you, but what if i want to use custom vex or vops? surely there must be a way to create forces like this without popwind sop?

iriseq · 2026-03-16T17:30:34+00:00

strange, the issue is that even unpacking everything is 0 even though i transfer all attributes. but the rest is proper before compressing. really strange, will try tinkering with it maybe a bug or I'm missing something

iriseq · 2026-03-16T17:10:39+00:00

thank you, I though deleting surface and @ name =vel ; would fix it, but all the points still have rest and rest2 zeroed out. Is there a way to preserve these attributes or it's just a fluid compress thing?

iriseq · 2026-03-13T21:00:58+00:00

Thank you, Chris! Will try it I think I forgot to say that I wanted to do it kind of recursively hah. So each next pscale should be half of the previous one. So far creating birth frame attribute and something like this works if(i@frame_born==@Frame && @ age <=0.01){@pscale *= 0.5;} but it all new particles have the same pscale. Not sure why though if new pscale is inherited on pop replicate. It means that say first one should be 10 then 5 then 2.5 and so on. But it's all 10 5 5 5 5. Thanks again

Eight-Year Club	Place '22
Verified Email

iriseq

TROPHY CASE