Search the Community
Showing results for tags 'versioning'.
Found 3 results
Hi everyone! I am looking for a way for multiple people to work on the same .hip file. Since .hip files can be exported as text, I assumed it would be possible to simply use git for versioning (and merging the edits made by multiple people). However, it does not seem to be that straightforward. To test this approach, I created a very simple network (first attachment). Now I made two edits (second and third attachment), each adding a transform node to the network. I assumed these changes could be merged, creating a new network containing both transform nodes. However, attempting to merge the .hip files using git resulted in several conflicts. Some of these could be solved trivially, (like changes to the viewport or the last edit timestamp) but there are several conflicts (last attachment) for which I could not find a way of resolving which produces my expected result. Does anybody have experience with this approach? How do you handle multiple people working on the same .hip file? Any help would be appreciated!
Hi guys, I hope I can pick your brain a little bit. I would like to know how you guys manage your effects versions. My concrete scenario is a couple of strung effects. It starts with a RBD explosion sim, then a pyro sim off of that and finally advecting particles along the sim. I like to hold all these in the same geo which poses a bit of a problem. How do I correlate the cache version to the hip file version? My approach is to use this in the filecache node: $HIP/geo/$HIPNAME.`opname("..")`.$OS/$HIPNAME.`opname("..")`.$OS.$F.bgeo.sc (windows guy, so I like to keep all sequences in separate folders). This complicates if I don't want to redo the RBD sim for example, then I have to replace the $HIPNAME with the absolute name of the file which simulated the RBD version. I know it would be much cleaner if every sim would reside in its own file, but that is a little too small of a granulation for single person workflow. If you could shed some light/share your practices, it would benefit me immensely
Hey. Did anyone experience problems with HOUDINI_OPNAMESPACE_HIERARCHY ? I used this variable before and don't remember that i had any problems with it, however i can't make it work in latest build: https://www.sidefx.com/forum/topic/37903/ Having op::0.1 and op::0.2 and HOUDINI_OPNAMESPACE_HIERARCHY = "op::0.1" i always get op::0.2 created by default. https://www.sidefx.com/docs/houdini/assets/namespaces Does the behavior of HOUDINI_OPNAMESPACE_HIERARCHY changed recently?