For Karma rendersettings there is a MetaData tab for Artist/Comment/Hostname.
The docs seem to indicate exr supports such meta data.
But I'm guessing not being able to see such data in Windows when using File Explorer is a limitation of File Explorer Itself?
Perhaps get a 'better' file manager app for windows.
Found 2075 posts.
Search results Show results as topic list.
Houdini Lounge » EXR - Including MetaData
-
- BabaJ
- 2077 posts
- Offline
Houdini Indie and Apprentice » can't view previewmaterial in cop network
-
- BabaJ
- 2077 posts
- Offline
metaclay2Perhaps it is a bug for osx...I'm using windows
osx version
Post your hip...I'll open the file using windows and if I don't get your 'error', then definitely it's a bug for osx.( could be related to the viewport as I see a long discussion about that for mac on the forums here).
Otherwise it's possible you may have made a parameter change and forgot about it?
Edited by BabaJ - July 22, 2024 12:49:43
Houdini Indie and Apprentice » can't view previewmaterial in cop network
-
- BabaJ
- 2077 posts
- Offline
What is your height scale set on the preview materail.
For me, using all the default settings I actually have to reduce that scale(initially set to one) to bring down the displacement to more pleasing levels.
For me, using all the default settings I actually have to reduce that scale(initially set to one) to bring down the displacement to more pleasing levels.
Edited by BabaJ - July 22, 2024 11:54:56
Houdini Lounge » Why does Karma restart under those silly circumstances?
-
- BabaJ
- 2077 posts
- Offline
LukeP
Thank you. This helps but in my opinion the software should just know not to restart the renderer.
Why? For how some work, having the software do that is a boon - e.g. working and adjusting in other contexts that affect the outcome of rendering, i.e. less clicking to get the render update changes.
The opposite could be said if your preference was the default - The software should know I'm still making changes in many different places - it should update 'automatically'.
Houdini Lounge » Why is the UI Design of Houdini So Inconsistent?
-
- BabaJ
- 2077 posts
- Offline
kodra
The fact that even the most basic functionalities like viewport and hotkeys can break is insane. It's like releasing a new car model whose steering wheel isn't 100% reliable but cheered for its in-car entertainment system.
It's more like people use different aspects of Houdini and in different ways....it's not an entertainment system vs. steering wheel(That's because you are assuming how and what you like to use is the same for everyone else);
But more like everyone has a favorite radio staion/s on that cars entertainment system - some are disgruntled that their tunes are not getting the air play on their station, while others like myself are finding their station is doing quit well.
No matter what, no one can argue that refining existing features in terms of functionality, interactivity and stability is a good thing.
However, Houdini with it's breadth and depth - makes it impossible to address in a short go to satisfy everyone.
There would be many features I would like to see attention given to aka - developer time spent on, but it's highly likely you could care less of those features that matter to me.
SideFX could do what you suggest - and take 2-3 years and halt development of all new features and just do refinement of existing features. Except for stability issues though, that could never happen - what and how one person prefers something to be set up is guaranteed to be different from the next person.
I for one who has been using Houdini since 14.0 or so have found personally, overall, Houdini has gotten 'better' much more so than it has raised 'annoyances'(which have been in the minority).
It's unfortunate judging by your comments, that it seems your experience has been the opposite - more annoyance than anything else.
Hopefully, as you already know - keep putting those RFEs and Bug reports in - I'm pretty sure it's a numbers game in the regard that if many people share your view on those RFEs/bugs - attention will definitely be given to them and resolved/changed.
Edited by BabaJ - July 22, 2024 08:48:38
Houdini Indie and Apprentice » 20.5: How to have a "default" recipe for a node?
-
- BabaJ
- 2077 posts
- Offline
Technical Discussion » Capernicus - Wrangling
-
- BabaJ
- 2077 posts
- Offline
Edit:
Just deleted my ramble.
The basic question was does the number of pixels('image' resolution set) get represented by the same represent the number of voxels in a cop net(Copernicus).
While I was in the cop net, I couldn't find any reference where that info got exposed.
However, bringing up the info panel on the cop network node itself answered my question as it lists the number of voxels.
Just deleted my ramble.
The basic question was does the number of pixels('image' resolution set) get represented by the same represent the number of voxels in a cop net(Copernicus).
While I was in the cop net, I couldn't find any reference where that info got exposed.
However, bringing up the info panel on the cop network node itself answered my question as it lists the number of voxels.
Edited by BabaJ - July 21, 2024 18:38:35
Technical Discussion » Node Permanent Defaults with Recipes
-
- BabaJ
- 2077 posts
- Offline
Ok, I see...but I guess it's a matter of perception - I would consider it not misleading but rather usefull if one has never used presets before.
'Because what you are about to use is legacy...why don't you go over here and use this instead...you might like how it works...'
Just helps differentiates to indicate two different systems rather than one with improved features.
'Because what you are about to use is legacy...why don't you go over here and use this instead...you might like how it works...'
Just helps differentiates to indicate two different systems rather than one with improved features.
Edited by BabaJ - July 21, 2024 13:40:36
Technical Discussion » Node Permanent Defaults with Recipes
-
- BabaJ
- 2077 posts
- Offline
Dawid Wizor
Under "Legacy Presets" is still option to "Save as Permanent Defaults" but is it correct to use it, since it is an outdated system?
What do you mean by 'correct'?
You could say have a recipe and apply it - then also go to Legacy Presets and Save as Permanent Defaults.
Or just set up your desired preset and save as permanent default.
Technical Discussion » Object Merge Node for Copernicus COPs
-
- BabaJ
- 2077 posts
- Offline
netlander
Yes the dot can make the wires look a little more organised but no way to avoid criss-crossing wires which is what, on large networks, hurts my brain
That's why I suggested what I did originally.
But I do like your suggestion that you provided ref. information on the dots.
There has been times when just working in an object context where I have a very complex structure going on, and a number of times I don't simply want to make an 'invisible' reference to other nodes i.e. I want to have a wire connection instead;
Having desired information to be able to be exposed on the dot connectors can be very useful; similar to having the group names one setups in a group node show themselves along with the group node name.
I've just been 'lazy' to put in a request for such a feature as I get by without it anyways.
I'm sure you're not alone with others coming from 'Designer' , go ahead and put an RFE in with a description and image like you did. There may be enough of the same RFEs that they put some time into it.
Edited by BabaJ - July 21, 2024 10:38:01
Houdini Lounge » The hotkey system is broken in Houdini 20.5
-
- BabaJ
- 2077 posts
- Offline
kodra
I wonder this too. I think H20.5 doesn't change much how we switch between contexts.
You no longer have to change to composite view - You can stay in scene view.
Technical Discussion » Object Merge Node for Copernicus COPs
-
- BabaJ
- 2077 posts
- Offline
netlander
the attachments below show how the Dot node in Designer works, which is what I'm after.
Also, if it's not just for organizing(what I was suggesting), and you just want the information to be able to be exposed.....
You know you can already create a 'dot' on a wire anywhere with 'Alt' + click?
Then you could possibly put in an RFE that information (like what you seem to suggest) could be exposed/available on those created dot connectors.
Technical Discussion » Object Merge Node for Copernicus COPs
-
- BabaJ
- 2077 posts
- Offline
netlander
Thanks for the reply: Something of a workaround albeit a bit combersome.
It's actually not a workaround.
If you want to have wire connections too then just encapsulate the copnet nodes, object nodes, etc. with a subnet.
Or if you want more 'functionality' of the subnet itself, just turn it into an asset.
Edited by BabaJ - July 21, 2024 09:48:44
Technical Discussion » Object Merge Node for Copernicus COPs
-
- BabaJ
- 2077 posts
- Offline
If you work in object context, you can set up orgainzed networks of networks and use referencing like op: or rel/abs referencing.
And you can make use of both object merge nodes and cop network nodes
And you can make use of both object merge nodes and cop network nodes
Houdini Lounge » The hotkey system is broken in Houdini 20.5
-
- BabaJ
- 2077 posts
- Offline
timurproko
To save recipes, they created new API calls to capture all the parameters, which was not possible before......
.....Regarding the UX, they lack a coherent strategy and make strange decisions that result in an interface that looks worse than one from 20 years ago, which they haven't updated in ages
Don't you mean UI(appearance)in this case? The save recipes is an example UX - which for myself has been a boon, and a improvement in the UX.
Because it's so much quicker to create/edit and manage - I'm finding I'm using it more often rather than making presets before less ofter. It's improving my workflow, efficiency and enjoyment.
timurprokoI'm tempted to screenshot my recent version of SolidWorks - Compared to that Houdini looks like something from the future while SolidWorks something from an 8-bit game in the 70's.
that result in an interface that looks worse than one from 20 years ago, which they haven't updated in ages.
But SolidWorks has great nurb tools and it's good that they didn't sacrifice development time on UI eye candy but kept it on functionality.
Hope SideFX keeps giving under the hood emphasis rather than appearance.
Photoshop is a good example...UI has become really 'sexy' over the years. Just had a look from my old copy that was in CS2 compared to 2024 - Like night and day. Yet under the hood there is still lots that hasn't changed since CS2, which is unfortunate but an example of a company that emphasises what looks good instead of functionality.
LukePCore functionality has improved for me in 20.5
This has been a common complaint from many people after looking at 20.5. And core functionality of the software
Like the already mentioned recipes - Copernicus has many elements to it that allows greater flexibility in making your own 'tools' and workflows - which imo is the Hallmark of Houdini.
Being able to reference/switch between and each geo/lop/cop contexts much more easily is a real joy.
I don't normally do much render work - but the ease of use now (UX Improvement) has gotten me experimenting and thinking how I can use it in ways I couldn't as easily before.
Solaris and Karma » High Aspect Ratio Factors for Orthographic Cameras
-
- BabaJ
- 2077 posts
- Offline
jsmackSort of...checking out Copernicus, making terrain maps, etc....seeing how it renders different scales, tiling, etc.etc.
Then you must have changed it to work in 10 meter units. Doing city-scale modelling maybe?
Solaris and Karma » High Aspect Ratio Factors for Orthographic Cameras
-
- BabaJ
- 2077 posts
- Offline
jsmack
The hip file default unit size is 1, not 10.
Mine shows 10
jsmackOk...now this makes sense then. Thanks for the insight on that.
The horizontal and vertical apertures are entered in mm, and encoded following the USD spec....is 100000mm.
Solaris and Karma » High Aspect Ratio Factors for Orthographic Cameras
-
- BabaJ
- 2077 posts
- Offline
Does anyone know why the default parameters for aspect ratios require a very high input number?
For example in the hip file, a grid of 10x10 scene units (hip file preference set to default of 10 units) for top view.
When in Solaris, in order to have that fit the camera view for either approach of using horizontal aperture controlling the ratio or both horizontal and vertical aperture directly - in each case, a value of 1 million is needed.
I would think that SideFX would make default values according to what they think is typical use scenarios - but if that is the case, I am clearly not in that category.
Personally I would put in an RFE to have the aspect ratio number requirements reduced 100k times so that orthographic view aperture setting values match scene grid values. It also has the added benefit of adjusting values more in line with numbers found on the value ladder adjustments.
But then again, there must be some 'industry' need for how it is?
For example in the hip file, a grid of 10x10 scene units (hip file preference set to default of 10 units) for top view.
When in Solaris, in order to have that fit the camera view for either approach of using horizontal aperture controlling the ratio or both horizontal and vertical aperture directly - in each case, a value of 1 million is needed.
I would think that SideFX would make default values according to what they think is typical use scenarios - but if that is the case, I am clearly not in that category.
Personally I would put in an RFE to have the aspect ratio number requirements reduced 100k times so that orthographic view aperture setting values match scene grid values. It also has the added benefit of adjusting values more in line with numbers found on the value ladder adjustments.
But then again, there must be some 'industry' need for how it is?
Edited by BabaJ - July 18, 2024 12:33:04
Houdini Lounge » Why is the UI Design of Houdini So Inconsistent?
-
- BabaJ
- 2077 posts
- Offline
kodraIt's not that SideFX thinks it's super important.
I honestly can't remember the last time when I need to check these timestamps. But for SideFX they must be super important.
It's just that you haven't worked on a scene with 30+ attributes present,
to 'appreciate' the insignificance( in terms of screen space ) of the two timestamps Modified/Created.
Edited by BabaJ - July 18, 2024 08:36:00
Technical Discussion » preferences and plugins for houdini upgrade
-
- BabaJ
- 2077 posts
- Offline
Thought I would revive this thread with an 'extension' question.
As jsmack suggested this is what I have actually been doing for as long as I can remember, since the number of preference files I transfer to new releases is small and an easy and quick task.
However, as an excercise in python I'm thinking of writting a python script file in which I think if I 'drop' in a new release preference folder and run the script from there, could reach back to specified folders and transfer those files; And also modify contents if need be as well,e.g.,
open houdini.env file and insert lines like:
OCIO = "C:......\aces_version\config.ocio"
MAPBOX_API = pk.eugus239Addsoekr9322.zgkdsie
etc.
etc.
Wondering if this is the type of approach studios take or is there some 'app' that a studio might use to do such things and 'more'?
As jsmack suggested this is what I have actually been doing for as long as I can remember, since the number of preference files I transfer to new releases is small and an easy and quick task.
However, as an excercise in python I'm thinking of writting a python script file in which I think if I 'drop' in a new release preference folder and run the script from there, could reach back to specified folders and transfer those files; And also modify contents if need be as well,e.g.,
open houdini.env file and insert lines like:
OCIO = "C:......\aces_version\config.ocio"
MAPBOX_API = pk.eugus239Addsoekr9322.zgkdsie
etc.
etc.
Wondering if this is the type of approach studios take or is there some 'app' that a studio might use to do such things and 'more'?
Edited by BabaJ - July 16, 2024 10:06:53
-
- Quick Links