Thanks for the file, but I am confused why the docs shows something that is not working, so what you are saying is that the docs are not correct, so I should ignore them or it should work as demonstrated, as the scene you sent has removed the Apex Edit Graph SOP which was in the docs, and I think I followed it precisely?
I think again example files for us to test that is a clone of what the docs is showing would be great, if its not working then it should be removed
And I learned that there is strict naming convention, which would be good to document for us who needs to understand the lower level of this, just like VEX, python etc.
E.g naming inputs to get an attribute from the skeleton, how dose that work, Base vs base, why is that a convention, for people who developed it it make sense, for someone just reading the docs, its not clear at all what the naming conventions are.
Cheers
Found 68 posts.
Search results Show results as topic list.
Rigging » Apex Graphs docs
- jens_martensson
- 341 posts
- Offline
Rigging » Apex Graphs docs
- jens_martensson
- 341 posts
- Offline
Hi Again
I am stuck at the APEX geometry deformation part in the docs, doesn't seam to get my transforms from my skeleton.
Also in the docs its says
I am stuck at the APEX geometry deformation part in the docs, doesn't seam to get my transforms from my skeleton.
Also in the docs its says
the skeleton joint names are set to joint_0, joint_1, and joint_2 in the Skeleton SOPI tried, I get point_0, point_1 etc
Image Not Found
Rigging » Apex Graphs docs
- jens_martensson
- 341 posts
- Offline
Hi
I had same issue as above, can we update the docs and maybe ship it with working example scenes?
Thanks
I had same issue as above, can we update the docs and maybe ship it with working example scenes?
Thanks
Edited by jens_martensson - Nov. 15, 2023 14:13:36
PDG/TOPs » Labeled Workitems in the Dropdown Menu
- jens_martensson
- 341 posts
- Offline
Hi
I have been searching and trying to use this
But it's not persistent or not working, and I think it would be great to add a label to a work item so when switching work item in the dropdown menu you have labels and not some random names based on the node+ work item index
Any solutions would be great
Cheers
I have been searching and trying to use this
pdg.WorkItem.setLabel()
But it's not persistent or not working, and I think it would be great to add a label to a work item so when switching work item in the dropdown menu you have labels and not some random names based on the node+ work item index
Any solutions would be great
Cheers
Solaris and Karma » Anamorphic workflows in Solaris
- jens_martensson
- 341 posts
- Offline
Thanks
That works, I would hope it can be transferred more easily with an updated Scene Import, to add those properties, at least the aperture settings on the camera
Cheers
That works, I would hope it can be transferred more easily with an updated Scene Import, to add those properties, at least the aperture settings on the camera
Cheers
Solaris and Karma » Anamorphic workflows in Solaris
- jens_martensson
- 341 posts
- Offline
Hi
So I need to render non square pixels in Karma, and I have a camera that is anamorphic.
First thing, loading a camera from OBJ that works as intended (viewport is not squeezed in OBJ level) does not translate into LOP's with the those settings, is it because a USD Camera doesn't have a pixel aspect ratio ?
Second thing is I make a LOP's camera, and add a rendersettings node after and set aspect ratio to 2, so now my hydra viewport in Houdini GL is drawing a mask like its a x2 Pixel aspect ratio, but all things drawn as square pixels, while Karma at least does the correct squeeze on all objects.
So last thing when viewing in Karma with an aspect ratio of 2 as in this example, is there something that stretches it out so I can view it correctly like the normal Render Viewer or Mplay does, and still renders an image to disk with an non-square pixel aspect ratio
Cheers
So I need to render non square pixels in Karma, and I have a camera that is anamorphic.
First thing, loading a camera from OBJ that works as intended (viewport is not squeezed in OBJ level) does not translate into LOP's with the those settings, is it because a USD Camera doesn't have a pixel aspect ratio ?
Second thing is I make a LOP's camera, and add a rendersettings node after and set aspect ratio to 2, so now my hydra viewport in Houdini GL is drawing a mask like its a x2 Pixel aspect ratio, but all things drawn as square pixels, while Karma at least does the correct squeeze on all objects.
So last thing when viewing in Karma with an aspect ratio of 2 as in this example, is there something that stretches it out so I can view it correctly like the normal Render Viewer or Mplay does, and still renders an image to disk with an non-square pixel aspect ratio
Cheers
Solaris and Karma » Toggle background image on and off
- jens_martensson
- 341 posts
- Offline
Hi, is there a reason why there is no toggle for showing a background image in the Solaris Viewport ?
Right now I have to open display settings and toggle background image on an off.
Would help if we had the same button as in the viewer in obj level "Display Background"
Cheers
Right now I have to open display settings and toggle background image on an off.
Would help if we had the same button as in the viewer in obj level "Display Background"
Cheers
Solaris and Karma » Physical Lens Exposure slider
- jens_martensson
- 341 posts
- Offline
Solaris and Karma » Physical Lens Exposure slider
- jens_martensson
- 341 posts
- Offline
And, there seams that the Lens Shader only works on LOP Cameras, imported one from OBJ and added the properties under Karma Lens Properties , but the "karma:camera:lensshader" is not being set correctly
Cheers
Cheers
Solaris and Karma » Physical Lens Exposure slider
- jens_martensson
- 341 posts
- Offline
Hi
I wonder if its just me, but I tried the exposure slider on the Physical Lens, and it seams to do nothing, the intensity slider works
Tried 19.0.546 and 19.0.531, same behaviour
Cheers
I wonder if its just me, but I tried the exposure slider on the Physical Lens, and it seams to do nothing, the intensity slider works
Tried 19.0.546 and 19.0.531, same behaviour
Cheers
PDG/TOPs » Function/Class that moves dependencies into working dir
- jens_martensson
- 341 posts
- Offline
Hi
Something changed in v19, in v18.5 files, e.g rop.py was copied to a working dir specified in the scheduler, can't get that to work anymore in v19, what changed and except for the file dependencies parms in on the TOP nodes
Any examples what needs to be implemented in v19 to copy ?
I tried to use self.transferfile() but I don't know where that is implemented so cant find where its transfering the file
Cheers
Something changed in v19, in v18.5 files, e.g rop.py was copied to a working dir specified in the scheduler, can't get that to work anymore in v19, what changed and except for the file dependencies parms in on the TOP nodes
Any examples what needs to be implemented in v19 to copy ?
I tried to use self.transferfile() but I don't know where that is implemented so cant find where its transfering the file
Cheers
Houdini for Realtime » unreal engine Niagara 2.0 git plugin for 4.26
- jens_martensson
- 341 posts
- Offline
Solaris and Karma » Rotating USD UVs with VEX/VOP ?
- jens_martensson
- 341 posts
- Offline
Hi
The idea here is to move uv's to origin, so its assuming no UDIM's
But this will rotate the uv's by 90 degrees
Hope that helps
Cheers
The idea here is to move uv's to origin, so its assuming no UDIM's
But this will rotate the uv's by 90 degrees
// move original uv's (st) to origin vector2 uv = u@primvars:st - 0.5; matrix UV = ident(); //rotate 90 degrees rotate(UV,radians(90),{0,0,1}); //rotate the uvs with matrix multi uv *= matrix2(UV); //assign to uv's again u@primvars:st = uv + 0.5;
Hope that helps
Cheers
Edited by jens_martensson - March 1, 2020 17:58:28
Solaris and Karma » How to access a USD stage from SOP's in a wrangler
- jens_martensson
- 341 posts
- Offline
Solaris and Karma » How to access a USD stage from SOP's in a wrangler
- jens_martensson
- 341 posts
- Offline
Hi
So I am trying to access a USD stage from a SOP wrangler, been trying everything but no luck, the other way around works fine with the “op:/” syntax in a LOP wrangler, is it not possible or do I need to use something as my stage instead of the “op:/” syntax ?
And maybe if its not working in SOP:s, the functions needs be hidden in any SOP wrangler context?
Cheers
So I am trying to access a USD stage from a SOP wrangler, been trying everything but no luck, the other way around works fine with the “op:/” syntax in a LOP wrangler, is it not possible or do I need to use something as my stage instead of the “op:/” syntax ?
And maybe if its not working in SOP:s, the functions needs be hidden in any SOP wrangler context?
Cheers
Edited by jens_martensson - Jan. 24, 2020 21:48:48
Solaris and Karma » SOP Import and Point Instancer Examples
- jens_martensson
- 341 posts
- Offline
Hi Chris
Thanks, I do wanna have a deeper dive then just that
Sop Import is the point of failure in many cases when asset brought into Lops from Houdini and not some external usd library
So having a lot of examples helps, and more technical documentation where attributes end up in Lops is crucial for most Houdini artist to learn how to use Lops. I hope this makes it more clear, when I mean more docs and examples
Thanks, I do wanna have a deeper dive then just that
Sop Import is the point of failure in many cases when asset brought into Lops from Houdini and not some external usd library
So having a lot of examples helps, and more technical documentation where attributes end up in Lops is crucial for most Houdini artist to learn how to use Lops. I hope this makes it more clear, when I mean more docs and examples
Solaris and Karma » SOP Import and Point Instancer Examples
- jens_martensson
- 341 posts
- Offline
And, how to hide an instance in USD using point attributes, tried ‘hidden’, “visibility”
Can do it with a LOP Wrangler, based on some arbitrary attribute from SOP, but it seams like
something somebody would do a lot
Cheers
Can do it with a LOP Wrangler, based on some arbitrary attribute from SOP, but it seams like
something somebody would do a lot
Cheers
Solaris and Karma » SOP Import and Point Instancer Examples
- jens_martensson
- 341 posts
- Offline
Hi
So these nodes are doing a lot of work, and documentation is very basic.
Great examples would describes the connection between choices a user does and the result of those choices.
Feels like we should have example files of how to
- Import Geometry, how does attributes travel from SOP's to USD (LOP's)
- Packed Geometry, different ways of getting them in, as a lot of content is coming from there
How to prepare your packed geometry vs geometry to retain Name and Path from SOP's
Where do my attributes end up?
- Point Instancer, different examples of the three main modes, first input, second input (all prims) and second input (selection)
- How to hide exemplars?
- How to use name attribute to copy exemplars on to specific points
So what I am asking for is more examples how to use it, beyond copying a pigheads to points
Examples I would love to see
ForEach loading from SOP's and generating Exemplars
A layout that moves and changes number of Exemplars
And all the examples we had during the beta period, they where great
Thanks
So these nodes are doing a lot of work, and documentation is very basic.
Great examples would describes the connection between choices a user does and the result of those choices.
Feels like we should have example files of how to
- Import Geometry, how does attributes travel from SOP's to USD (LOP's)
- Packed Geometry, different ways of getting them in, as a lot of content is coming from there
How to prepare your packed geometry vs geometry to retain Name and Path from SOP's
Where do my attributes end up?
- Point Instancer, different examples of the three main modes, first input, second input (all prims) and second input (selection)
- How to hide exemplars?
- How to use name attribute to copy exemplars on to specific points
So what I am asking for is more examples how to use it, beyond copying a pigheads to points
Examples I would love to see
ForEach loading from SOP's and generating Exemplars
A layout that moves and changes number of Exemplars
And all the examples we had during the beta period, they where great
Thanks
PDG/TOPs » Setting attributes with pdgcmd.writeAttribute()
- jens_martensson
- 341 posts
- Offline
Thanks Chris
I will send the stacktrace in a separate post
The result server env exist when running on the farm
Cheers
I will send the stacktrace in a separate post
The result server env exist when running on the farm
Cheers
PDG/TOPs » Setting attributes with pdgcmd.writeAttribute()
- jens_martensson
- 341 posts
- Offline
Hi
So we have an out of process running both on the farm and locally, using pdgcmd.reportResultData()
works fine both local and on the farm
When I am trying to write back an attribute using pdgcmd.writeAttribute() I get a bunch of errors on the farm
related to the server address, which by default seams to be 127.0.0.1
- What do we need to get the proxy server up and running? Our in-house scheduler is built upon the Tractor one
- Is there a way to return the non-local IP using self.scheduler.workItemResultServerAddr(), is that something that needs to be implemented in the scheduler ?
- Why is pdgcmd.reportResultData() working and not pdgcmd.writeAttribute()? I understand the difference, but it would be great if both of them had the std_out option, only pdgcmd.reportResultData() has it at the moment
Cheers
So we have an out of process running both on the farm and locally, using pdgcmd.reportResultData()
works fine both local and on the farm
When I am trying to write back an attribute using pdgcmd.writeAttribute() I get a bunch of errors on the farm
related to the server address, which by default seams to be 127.0.0.1
- What do we need to get the proxy server up and running? Our in-house scheduler is built upon the Tractor one
- Is there a way to return the non-local IP using self.scheduler.workItemResultServerAddr(), is that something that needs to be implemented in the scheduler ?
- Why is pdgcmd.reportResultData() working and not pdgcmd.writeAttribute()? I understand the difference, but it would be great if both of them had the std_out option, only pdgcmd.reportResultData() has it at the moment
Cheers
-
- Quick Links