bumping this, as I've again stumbled upon that.
Raising refraction limit is the brute force option that I do not have the budget for . . .
Found 226 posts.
Search results Show results as topic list.
Solaris and Karma » exit color om refraction
-
- sekow
- 239 posts
- Offline
Solaris and Karma » Geometry Clip Sequence Lop or how to handle large data
-
- sekow
- 239 posts
- Offline
mtucker
Indeed. Please give it a try and let me know if the performance has gotten to where you want it to be. Thanks!
Pretty sure that our need for performance will never be satisfied..and as soon things get faster, the workload gets bigger.
But this is very appreciated and I am going to test it today
Solaris and Karma » exit color om refraction
-
- sekow
- 239 posts
- Offline
Hey is there any way to color the exit color when teh refraction limit is reached?
Instead of just being black?
Could have sworn to be able to that in Karma
Thanks
Instead of just being black?
Could have sworn to be able to that in Karma
Thanks
Solaris and Karma » Geometry Light in LOPs
-
- sekow
- 239 posts
- Offline
tamtesekowyou can tag geometry with LPE tag and then isolate in your AOVs
bump, LPE tags for geo lights still a no no?
it works for geometry light contributions
the main limitation seems to be that the Split Per LPE Tag checkboxes don't parse geometry marked as lights, only light schemas and therefore they will not detect and create the AOVs for current workaroundish incarnation of geometry lights
so you have to create additional AOVs yourself with corresponding LPE that filters lights by LPE tag of the geometry light object
thanks Tomas, should have come up with that on my own, here is the hip for everybody that is interested. But not sure if my LPEs are correct, even if they look alright.
Solaris and Karma » Geometry Light in LOPs
-
- sekow
- 239 posts
- Offline
Technical Discussion » Give Me Some Ideas Please
-
- sekow
- 239 posts
- Offline
Technical Discussion » Flip simulation inside a Geometry with FLIP Solver SOP
-
- sekow
- 239 posts
- Offline
Usually its enough to load in the collision sdf into the sim and inverse it.
do not know how to do it with flip sop solver though.
Have a look at the hip
do not know how to do it with flip sop solver though.
Have a look at the hip
Houdini Lounge » Karma XPU (H20) vs Redshift
-
- sekow
- 239 posts
- Offline
jerry7
I want to know why the bubble warp example is so slow in karma (about 30 mins). It only takes several minutes in RS.
https://www.sidefx.com/forum/topic/92976/ [www.sidefx.com]
https://www.sidefx.com/forum/topic/93004/ [www.sidefx.com]
Solaris and Karma » Geometry Clip Sequence Lop or how to handle large data
-
- sekow
- 239 posts
- Offline
mtucker
The other option (which already exists as an RFE) is to provide a checkbox on the Geo Clip Sequence LOP that says "trust me, my scene graph hierarchy doesn't change from file to file, just generate the manifest from the first BGEO file". This will make the "multi frame" cooking mode of the Geo Clip Sequence very fast even for BGEO sequences as it will only need to load one BGEO file to create the manifest. Of course depending on your BGEO sequence, turning on this check box may generate an incorrect manifest file, but at least you'll be able to control this tradeoff between speed and "correctness". We don't have a timeline for this change, but this issue does keep coming up.
btw I would be totally fine with this extra control
Solaris and Karma » Geometry Clip Sequence Lop or how to handle large data
-
- sekow
- 239 posts
- Offline
mtucker
And yes, we definitely need to put out more information about this process.
Please do. Seriously that is so crucial and I am a bit puzzled that it did not come up yet.
Solaris and Karma » Geometry Clip Sequence Lop or how to handle large data
-
- sekow
- 239 posts
- Offline
robp_sidefx
If you have "Flatten Clip Files" disabled (which I appreciate I left enabled in the screenshot & example above), then there shouldn't be any BGEO->USD conversion. You'll end up with a direct link back to the BGEO in your scene.def Xform "geoclipsequence_noTimeDep" (
clips = {
dictionary default = {
double2[] active = [(1, 0), (2, 1), ...]
asset[] assetPaths = [@../geo/sphere.0001.bgeo@, @../geo/sphere.0002.bgeo@, ...]
thanks, getting closer to understand what is going on here.
But I still need to cache all time samples into memory first (setting the geo clip seq lop to a framerange). So the whole framerange.
Other than writing a python script is there a way to avoid loading those time samples into the stage beforehand?
I am just trying to avoid sitting here and waiting for 500 frames of heavy geometry getting loaded into ram just to be written down into a dictionary inside the usd.
I guess I could come up with and hda/top network where the manifest, topology and reference usd will be written out immediatley after caching out the bgeo files.
Solaris and Karma » Geometry Clip Sequence Lop or how to handle large data
-
- sekow
- 239 posts
- Offline
robp_sidefxsekow
in the presentation you can see the lop went time dependent
Yes, one of the things I didn't show (but really should have) is that, as with many of our other LOPs, we can generate a range of time samples directly from this LOP and avoid introducing the time dependency.
Its just that usually those geo caches are several Gb big, and in my case its a fairly long shot. In that case I wont be going around the fact that I need to cache those timesamples out as USD (via the geometry clip seq lop).
Just making sure there is not an other way of handling that.
Solaris and Karma » Geometry Clip Sequence Lop or how to handle large data
-
- sekow
- 239 posts
- Offline
Solaris and Karma » Geometry Clip Sequence Lop or how to handle large data
-
- sekow
- 239 posts
- Offline
tamte
2. Geometry Clip Sequence LOP seems to be able to reference .bgeo* files directly and I'd assume probably other like .vdb, so I'd assume there should be no need to recache them again as .usd, but I haven't tried
https://youtu.be/R4SLw5EdzQ8?si=NZ4F9U2zwDvISC0s&t=1815 [youtu.be]
Hey Tomas, hope you good!
yeah, in the presentation you can see the lop went time dependent. Which will recook the whole graph later on.
Geometry Clip Sequence Lop makes it a bit more convenient to prep the cache out to usd though.
Solaris and Karma » Geometry Clip Sequence Lop or how to handle large data
-
- sekow
- 239 posts
- Offline
Hey.
I am interested in good practice of handling large caches.
Love the way how fast it is to work in Lops but as soon as there are time dependencies involved all that gets slow really fast ...
I understand the way time is handled in Solaris and I am using the "cache lop/ write usd to disk" quite frequent.
Now I am usually working with heavy fx caches. Massive Rbds, surface meshing, volumes , insane point counts etc.
And as those are already cached out as bgeo/vdb sequences I thought that the Geometry Clip Sequence could handle that.
But I've learned that I need to sample a frame range to get rid of time dependencies again, so I need to write out those caches as usd anyway. .
Now I can reference those back into the stage... Sounds redundant to me and disk space is sacred.
Have a look at the example hip file where I explore that a bit.
I am interested in good practice of handling large caches.
Love the way how fast it is to work in Lops but as soon as there are time dependencies involved all that gets slow really fast ...
I understand the way time is handled in Solaris and I am using the "cache lop/ write usd to disk" quite frequent.
Now I am usually working with heavy fx caches. Massive Rbds, surface meshing, volumes , insane point counts etc.
And as those are already cached out as bgeo/vdb sequences I thought that the Geometry Clip Sequence could handle that.
But I've learned that I need to sample a frame range to get rid of time dependencies again, so I need to write out those caches as usd anyway. .
Now I can reference those back into the stage... Sounds redundant to me and disk space is sacred.
Have a look at the example hip file where I explore that a bit.
Edited by sekow - Dec. 7, 2023 11:58:16
Solaris and Karma » Thoughts on manipulating geometry in LOPs?
-
- sekow
- 239 posts
- Offline
apologies for my possible ignorance, but as soon as you want to do any kind of geo manipulation you have to dive into sops right?
Sop modify lop is just a subnet with a sop network inside.
Just asking as I am getting familiar with lops myself right now and trying to set up everything in lops, with the occasionally diving into sops for exactly that, geo manipulation, generation.
Sop modify lop is just a subnet with a sop network inside.
Just asking as I am getting familiar with lops myself right now and trying to set up everything in lops, with the occasionally diving into sops for exactly that, geo manipulation, generation.
Technical Discussion » Hey guys, I have a problem with switching Alembic cameras.
-
- sekow
- 239 posts
- Offline
Never tried that and to be honest I think this is a limitation.
Try this: Copy the cameras out of the alembicarchive objs. Get rid of those transform and use a fetch obj to read the transforms from the cameras inside that archives. Plug the fetch outputs into the cameras
Try this: Copy the cameras out of the alembicarchive objs. Get rid of those transform and use a fetch obj to read the transforms from the cameras inside that archives. Plug the fetch outputs into the cameras
Edited by sekow - Dec. 4, 2023 03:21:16
Technical Discussion » Particles Emit only once when reach a condition?
-
- sekow
- 239 posts
- Offline
Technical Discussion » Particles Emit only once when reach a condition?
-
- sekow
- 239 posts
- Offline
have a look at pop replictate dop and use the reference stream input (2nd), set Kill Original Particle.
When particles hit something the popsolver set some hit attributes: i@hitnum, i@hittotal i@hitprim . . .
When particles hit something the popsolver set some hit attributes: i@hitnum, i@hittotal i@hitprim . . .
Technical Discussion » Right way to convert simulation outputs to static geometry? [[SOLVED]]
-
- sekow
- 239 posts
- Offline
-
- Quick Links