Very nice tool Jonathan, I can see its utility!
Unfortunately I've never managed to make the external editor work with Houdini.
(it doesn't always launch from shortcut, and when it does, it won't save the code back to Houdini.)
Found 900 posts.
Search results Show results as topic list.
Houdini Lounge » Houdini 20 Rumors
- Andr
- 900 posts
- Offline
Houdini Lounge » Houdini 20 Rumors
- Andr
- 900 posts
- Offline
Maybe this is the dumbest idea ever:
Why not integrating VSCode inside Houdini, instead of implementing new features from scratch for the Houdini editors?
I have no idea if it's even possible (technically and commercially), but I've seen some web apps for coding that seem to be using VSCode engine, so I was wondering..
Also I'd like the idea that such integration could open up the possibility for further customization by the community, thanks to VSCode extensions.
Why not integrating VSCode inside Houdini, instead of implementing new features from scratch for the Houdini editors?
I have no idea if it's even possible (technically and commercially), but I've seen some web apps for coding that seem to be using VSCode engine, so I was wondering..
Also I'd like the idea that such integration could open up the possibility for further customization by the community, thanks to VSCode extensions.
Edited by Andr - June 8, 2023 08:22:52
Technical Discussion » Can really VEX save so much memory?
- Andr
- 900 posts
- Offline
thanks for bringing this up.
Regarding the matter, I've also always wanted to know what "instanced" means
Regarding the matter, I've also always wanted to know what "instanced" means
Edited by Andr - June 4, 2023 04:28:19
Houdini Lounge » Local vs SideFX.com help
- Andr
- 900 posts
- Offline
Ah, now I see what you mean.
Yes I experience the same issue of 404.
Might be worth to fill a bug report with the Support
Yes I experience the same issue of 404.
Might be worth to fill a bug report with the Support
Houdini Lounge » Local vs SideFX.com help
- Andr
- 900 posts
- Offline
I actually prefer sidefx.com as the local help tends to be slower than the remote help - quite the laugh, right? Besides, on my machine, the local help has a habit of triggering session crashes.
Slightly ot:
I've noticed that few companies have now integrated chatbots that are specifically fine-tuned for their services. Unlike the first generation of chatbots, which merely redirected users to specific pages of documentation or FAQs, these modern chatbots provide meaningful responses based on user inquiries.
Can you imagine how useful a well-integrated, fine-tuned chatbot could be for newcomers to Houdini? I'm pretty sure this could significantly increase Houdini's adoption among a larger user base
Slightly ot:
I've noticed that few companies have now integrated chatbots that are specifically fine-tuned for their services. Unlike the first generation of chatbots, which merely redirected users to specific pages of documentation or FAQs, these modern chatbots provide meaningful responses based on user inquiries.
Can you imagine how useful a well-integrated, fine-tuned chatbot could be for newcomers to Houdini? I'm pretty sure this could significantly increase Houdini's adoption among a larger user base
Edited by Andr - May 18, 2023 16:37:45
Technical Discussion » Need advices to estabilish better workflow for HDA developing
- Andr
- 900 posts
- Offline
OK, I recently discussed with Chat-GPT and devised a GitHub workflow for developing and publishing a collection of HDAs.
Key points include:
Any feedback or suggestions for this new-to-GitHub approach are appreciated.
1. Public Main Branch: This branch contains the stable versions of HDAs, with versioning in the format x.x.
2. Hidden Develop Branch: This branch is where new minor versions of HDAs are developed. Add the suffix -dev to the HDA file names while working on them in this branch.
Example: If the stable release for a particular HDA is 1.0, the development version would be named my_hda.1.1-dev.
3. Development and Merging Process:
a. Develop new minor versions of HDAs in the hidden develop branch.
b. Once a milestone for the new minor version is reached, rename the HDA file to remove the -dev suffix and update the minor version number.
Example: Rename my_hda.1.1-dev to my_hda.1.1.
c. Merge the updated HDA file into the main branch using the git checkout method. This ensures that only the specific HDA file is merged, without affecting other files in the main branch.
4. Hotfixes for Current Minor Versions:
a. For maintenance updates or hotfixes, create a new branch from the main branch, with a descriptive name like hotfix/hda_name.
b. Apply the hotfix or maintenance update to the specific HDA in the new branch.
c. Test the changes to ensure they work as expected and do not introduce new issues.
d. Commit the changes in the hotfix branch with a descriptive commit message, such as "Hotfix for HDA_name: description of the fix".
e. Switch back to the main branch and merge the hotfix branch into it.
f. Push the updated main branch to the remote repository and delete the local hotfix branch.
5. Repository Releases, Hotfixes, and Versioning: When ready to release a new version of the entire HDA collection, create a new repository release that includes the updated HDAs and any hotfixes applied to them. Note that a hotfixed HDA may maintain the same version number, and it is important to refer to the repository release version to understand which specific hotfixes have been applied.
Key points include:
- Adopting major-minor versioning for HDAs, like 1.4, nothing more granular.
- Hotfixes and maintenance updates won't change minor version numbers. Users should refer to the repository release changelog
Any feedback or suggestions for this new-to-GitHub approach are appreciated.
Managing Houdini HDAs Repository: Guidelines for Development and Hotfixes
1. Public Main Branch: This branch contains the stable versions of HDAs, with versioning in the format x.x.
2. Hidden Develop Branch: This branch is where new minor versions of HDAs are developed. Add the suffix -dev to the HDA file names while working on them in this branch.
Example: If the stable release for a particular HDA is 1.0, the development version would be named my_hda.1.1-dev.
3. Development and Merging Process:
a. Develop new minor versions of HDAs in the hidden develop branch.
b. Once a milestone for the new minor version is reached, rename the HDA file to remove the -dev suffix and update the minor version number.
Example: Rename my_hda.1.1-dev to my_hda.1.1.
c. Merge the updated HDA file into the main branch using the git checkout method. This ensures that only the specific HDA file is merged, without affecting other files in the main branch.
4. Hotfixes for Current Minor Versions:
a. For maintenance updates or hotfixes, create a new branch from the main branch, with a descriptive name like hotfix/hda_name.
b. Apply the hotfix or maintenance update to the specific HDA in the new branch.
c. Test the changes to ensure they work as expected and do not introduce new issues.
d. Commit the changes in the hotfix branch with a descriptive commit message, such as "Hotfix for HDA_name: description of the fix".
e. Switch back to the main branch and merge the hotfix branch into it.
f. Push the updated main branch to the remote repository and delete the local hotfix branch.
5. Repository Releases, Hotfixes, and Versioning: When ready to release a new version of the entire HDA collection, create a new repository release that includes the updated HDAs and any hotfixes applied to them. Note that a hotfixed HDA may maintain the same version number, and it is important to refer to the repository release version to understand which specific hotfixes have been applied.
Edited by Andr - May 13, 2023 16:02:06
Houdini Indie and Apprentice » Set external script editor not working
- Andr
- 900 posts
- Offline
I managed to use VSCode as external editor for python scripting but I'm experiencing few issues:
Regarding 2, I tried to add the following line in the settings.json of VSCode, but it didn't work:
- The hotkey ALT+E does not work because it launches the internal Houdini editor. To properly launch VSCode, I must right-click (RMB) on the Python Code parameter, select 'Expression', and then click on "Edit in External Editor."
- When editing a Python SOP, I must include "import hou" in the code to enable autocompletion in VSCode, which is redundant for a Python Sop.
- Additionally, autocompletion is not instantly available; there is a significant delay of at least 15 seconds before it becomes accessible in VSCode.
Regarding 2, I tried to add the following line in the settings.json of VSCode, but it didn't work:
"python.autoComplete.extraPaths": [ "C:\\Program Files\\Side Effects Software\\Houdini 19.5.569\\houdini\\python3.9libs" ]
Technical Discussion » Need advices to estabilish better workflow for HDA developing
- Andr
- 900 posts
- Offline
Hello wizards,
I'd like to understand your workflow and practices for developing new tools and updating them.
Additionally, I need advice in these areas where I struggle:
VERSIONING:
https://www.youtube.com/watch?v=pLM0LESO_kA [www.youtube.com]
EMBED INTERNAL ASSETS:
How do you handle the updating of a HDA that uses internal assets?
My HDAs often use internal service HDAs (not available to users in the TAB menu).
I use the "embed internal assets" function, but when saving the main HDA to a new version, the instances of sub-HDAs used in the MAIN HDA network are replaced with a "Merge Sop" node, which breaks the whole network.
This could be due to the main HDA's different namespace in the new version. When I use the embed function, the new installed internal asset has adn::Sop/Main_HDA::1.0::adn::Sop/Internal_HDA::1.0, so it's only available to Main_HDA::1.0.
Then when updating the Main_HDA to a new version, the internal_HDA isn't available to adn::Sop/Main_HDA::1.1, even if installed in the same library file, and thus the instances inside the network of main_HDA::1.1 are automatically replaced with a Merge Sop node.
It is such a struggle every time I save to a new version, because I have to manually update every instance of any internal hda used in the network. I believe I'm not using a the correct workflow here.
GITHUB REPOSITORY:
I'm new to GitHub and like the idea of an online public repository for my HDAs.
What's your workflow with GitHub used for Houdini development.
ROADMAP, FEATURE LIST, TASKS, TODOs, REQUESTS, CHANGELOG:
What's your approach to these aspects? Do you use any service? I'm interested in tracking my HDAs, organizing them in a database, maybe using Notion. It might be overkill or time-consuming for a solo dev like I am, so I'm open to learning from your experience.
I'd like to understand your workflow and practices for developing new tools and updating them.
Additionally, I need advice in these areas where I struggle:
VERSIONING:
- Why does Houdini's built-in HDA creation tool force versioning to start at 1.0, not 0.1? I believe "1.0" should represent the first milestone, not the starting point for a new tool.
- The built-in tool doesn't allow granular versioning like 1.0.3, leading to a premature 2.0 milestone. It increases by 0.1 with each save, permitting only 10 saves before a new x.0 milestone. Established HDA libraries (e.g., MOPs) use the x.x convention, so I wonder how they handle more granular saves during development.
https://www.youtube.com/watch?v=pLM0LESO_kA [www.youtube.com]
EMBED INTERNAL ASSETS:
How do you handle the updating of a HDA that uses internal assets?
My HDAs often use internal service HDAs (not available to users in the TAB menu).
I use the "embed internal assets" function, but when saving the main HDA to a new version, the instances of sub-HDAs used in the MAIN HDA network are replaced with a "Merge Sop" node, which breaks the whole network.
This could be due to the main HDA's different namespace in the new version. When I use the embed function, the new installed internal asset has adn::Sop/Main_HDA::1.0::adn::Sop/Internal_HDA::1.0, so it's only available to Main_HDA::1.0.
Then when updating the Main_HDA to a new version, the internal_HDA isn't available to adn::Sop/Main_HDA::1.1, even if installed in the same library file, and thus the instances inside the network of main_HDA::1.1 are automatically replaced with a Merge Sop node.
It is such a struggle every time I save to a new version, because I have to manually update every instance of any internal hda used in the network. I believe I'm not using a the correct workflow here.
GITHUB REPOSITORY:
I'm new to GitHub and like the idea of an online public repository for my HDAs.
What's your workflow with GitHub used for Houdini development.
ROADMAP, FEATURE LIST, TASKS, TODOs, REQUESTS, CHANGELOG:
What's your approach to these aspects? Do you use any service? I'm interested in tracking my HDAs, organizing them in a database, maybe using Notion. It might be overkill or time-consuming for a solo dev like I am, so I'm open to learning from your experience.
Edited by Andr - May 12, 2023 09:45:12
Technical Discussion » Normalize @P with an SOP to get a sphere out of a box?
- Andr
- 900 posts
- Offline
Soothsayer
Woah, what's this?geo: hou.Geometry = node.geometry()
I believe it just declares the datatype of the variable.
It's called "variable annotations"
Not necessary, but might be better for reviewing and understanding the code.
Also new to me, I'm watching this video about it
https://www.youtube.com/watch?v=QORvB-_mbZ0 [www.youtube.com]
Technical Discussion » Normalize @P with an SOP to get a sphere out of a box?
- Andr
- 900 posts
- Offline
Technical Discussion » Normalize @P with an SOP to get a sphere out of a box?
- Andr
- 900 posts
- Offline
elovikov
You can use compiled graphs in this context. Check the example, you just need Invoke Compiled Graph verb and the graph itself which is basically geometry. With that you can use any compilable networks and hdas.
You just need to bring geometry to the script, but you can even embed it in .py file as byte sequence as I did here: https://www.sidefx.com/forum/topic/86736/ [www.sidefx.com]
==
I've created once a "verbifier" for such a thing, but right now with invokable graphs it doesn't make much sense
https://github.com/igor-elovikov/hipie/blob/main/help/verbifier.md [github.com]
I'm not the op, but thanks a lot anyway!
that's a great showcase of more advanced stuff that I might need in the near future.
cheers
Edited by Andr - May 10, 2023 11:12:40
Houdini Lounge » Houdini design update
- Andr
- 900 posts
- Offline
toadstorm
having designed plenty of interfaces myself, i can tell you that simply saying "ux bad, make it better" is entirely worthless and a waste of everyone's time.
In my opinion, it's not a complete waste of time.
Writing and communicating UI/UX RFEs can be more challenging for various reasons,
and I can imagine one may opt to use the limited time allocated for RFEs to address urgent matters, such as production-critical bugs, instead of focusing on UI/UX improvements.
Although it's not ideal, I'm ok if users simply express their complaints regarding UI/UX.
SideFX could take a tiny bit more proactive approach to improving UI/UX, as they already do in other departments.
Houdini for Realtime » Labs Building Generator
- Andr
- 900 posts
- Offline
ps.
To be fair, in the specific case of the Labs Building Generator, what is also daunting (at least for me) is the overall complexity of the network.
In fact, I can see myself still struggling a bit, even if the naming of the nodes were more established.
I must say, it is still very tempting to invest time studying and attempting to refactor it for better cleanliness.
I suppose it's one of those challenging and annoying tasks that improve your expertise as a Technical Artist?
To be fair, in the specific case of the Labs Building Generator, what is also daunting (at least for me) is the overall complexity of the network.
In fact, I can see myself still struggling a bit, even if the naming of the nodes were more established.
I must say, it is still very tempting to invest time studying and attempting to refactor it for better cleanliness.
I suppose it's one of those challenging and annoying tasks that improve your expertise as a Technical Artist?
Houdini for Realtime » Labs Building Generator
- Andr
- 900 posts
- Offline
Vinnyvince, I now remember I've experienced the very same thing.
I started with a very confident thought: "OK, today I'm going to improve and expand the functionality of the Labs Building Generator."
I dove into the HDA, assessed the situation, and exited 30 seconds later.
I started with a very confident thought: "OK, today I'm going to improve and expand the functionality of the Labs Building Generator."
I dove into the HDA, assessed the situation, and exited 30 seconds later.
Houdini Lounge » Houdini design update
- Andr
- 900 posts
- Offline
paolorava.freelance
actually I find it very smart and functional
Am I the only one struggling with the design and functionality of the Edit Type Properties Window?
For me it's just a constant frustration of mouse dragging and resizing.
Houdini Lounge » Tragic news about Ben Mears
- Andr
- 900 posts
- Offline
Houdini Lounge » How To Change Avatar Image?
- Andr
- 900 posts
- Offline
Houdini Lounge » Debate question - why would we want SideFX to upgrade COPS?
- Andr
- 900 posts
- Offline
LukeP
Healthy debate question…
Why would we want SideFX to invest money into revamping COPS?
I believe the primary reason for wanting a revamp is that COPs is highly unstable and slow. These reasons alone are significant enough to justify a revamp, to me.
Additionally, when considering the other valid points mentioned earlier, it becomes clear that something needs to be done about this situation.
Houdini Lounge » Chat GPT and Houdini
- Andr
- 900 posts
- Offline
I've submitted an RFE for Chat-GPT tailored for Houdini, fine-tuned for the documentation, VEX language, and Python HOU.
The RFE number is #128111."
Can you imagine?
The RFE number is #128111."
Can you imagine?
Edited by Andr - April 6, 2023 15:10:55
Technical Discussion » Visualize attribs from PCloud on Pieces?
- Andr
- 900 posts
- Offline
Andr
I suppose I need to dynamically create a visualizer in Python using the hou.viewportVisualizers module, right?
As far as I understand, even if I use Python to create a Visualizer for a specific node inside a subnet, I would still encounter the same problem. This is because the Visualizer would have a limited "Scope" set to the child node, which means it wouldn't show up in the parent network?
-
- Quick Links