That darned evil capy is at it again - this is a viewport flipbook btw, not Karma
Found 16 posts.
Search results Show results as topic list.
Mardini 2024 » Day 24 | Character | Crowd Motion Path | Animation
- Drewzee
- 16 posts
- Offline
Houdini Indie and Apprentice » Can no longer open Indie files in Indie version
- Drewzee
- 16 posts
- Offline
For anyone wondering I had some packages that were .hdanc in my packages folder. Getting rid of those solved it.
Mardini 2023 » Day 27 | Worlds | Ancient | Animation
- Drewzee
- 16 posts
- Offline
Houdini Indie and Apprentice » Can no longer open Indie files in Indie version
- Drewzee
- 16 posts
- Offline
I'm having the same issue. I didn't add any HDAs to the file, just default Houdini nodes. Is there a solution for this?
Technical Discussion » Parsec and virtual displays
- Drewzee
- 16 posts
- Offline
I get this same problem every time using virtual display driver.
Try adding this to ENV file in your documents folder under Houdini , it worked for me.
HOUDINI_USE_HFS_OCL = 0
Try adding this to ENV file in your documents folder under Houdini , it worked for me.
HOUDINI_USE_HFS_OCL = 0
Houdini Indie and Apprentice » how do you export a hard surface model into photoshop
- Drewzee
- 16 posts
- Offline
Technical Discussion » Karma MPlay cannot export EXR only PNG
- Drewzee
- 16 posts
- Offline
Would it make a difference if Karma XPU was being rendered inside of a LOPnet instead of using the Stage context?
Technical Discussion » Houdini Launcher Keeps Asking to Update / Breaks License Svr
- Drewzee
- 16 posts
- Offline
Hi sesi
Houdini launcher keeps asking me to update it, even though I already have. I'm on the latest prod build for License Server and Houdini, 19.5.435. If I update, the install seems like it breaks the license server because when I try to launch H after the update I get the error "Host Header Not Accepted".
I didn't know what to do so I just uninstalled the license server inside of the Launcher and reinstalled it, downloaded and installed my license from the sidefx website, and Houdini was working again.
For a second day in a row I still get the pop up to install an update to the launcher, but I don't feel I can trust it now. The launcher seems delicate.
Is there a way to see what version of the launcher I have? I've decided to skip whatever update it wants me to install for now.
Houdini launcher keeps asking me to update it, even though I already have. I'm on the latest prod build for License Server and Houdini, 19.5.435. If I update, the install seems like it breaks the license server because when I try to launch H after the update I get the error "Host Header Not Accepted".
I didn't know what to do so I just uninstalled the license server inside of the Launcher and reinstalled it, downloaded and installed my license from the sidefx website, and Houdini was working again.
For a second day in a row I still get the pop up to install an update to the launcher, but I don't feel I can trust it now. The launcher seems delicate.
Is there a way to see what version of the launcher I have? I've decided to skip whatever update it wants me to install for now.
Technical Discussion » Karma MPlay cannot export EXR only PNG
- Drewzee
- 16 posts
- Offline
Hi Enivob
Half of the render was already done and rendered in the way you describe without using MPlay. But the render failed mid way through. I decided to use MPlay instead to hopefully prevent whatever halted Karma from continuing to render, thinking it could export EXRs, but it seems that MPlay has either been broken and there's no plans to fix it, or failing to export EXRs will simply remain an undocumented limitation.
Someone with as many posts as you would have mentioned a solution by now or some work around if there were such a thing; to capture the EXR format from MPlay.
There is a tick box that I didn't see that will allow me to monitor the frames in MPlay as they render. I will use that whenever I decide to use XPU again, but I dont think that will be for a long time.
Half of the render was already done and rendered in the way you describe without using MPlay. But the render failed mid way through. I decided to use MPlay instead to hopefully prevent whatever halted Karma from continuing to render, thinking it could export EXRs, but it seems that MPlay has either been broken and there's no plans to fix it, or failing to export EXRs will simply remain an undocumented limitation.
Someone with as many posts as you would have mentioned a solution by now or some work around if there were such a thing; to capture the EXR format from MPlay.
There is a tick box that I didn't see that will allow me to monitor the frames in MPlay as they render. I will use that whenever I decide to use XPU again, but I dont think that will be for a long time.
Edited by Drewzee - Nov. 16, 2023 12:19:20
Technical Discussion » Karma MPlay cannot export EXR only PNG
- Drewzee
- 16 posts
- Offline
Hi gang
Getting this error for the first time when trying to save a sequence rendered to MPlay as EXR from a Karma XPU render. PNG/TIFF/JPG is fine but with EXR I get this error:
“Cannot write file
Please check that the destination path exists and is not write-protected, and there is sufficient space on the drive”
Whether I create the folder with the Houdini save prompt window, or choose an existing folder this error comes up. There’s also 2TB of free space. Ive right clicked the folder and ticked off “Read Only”. Tried saving on a separate drive, on desktop, on other external drives to no avail.
Is there something wrong with saving EXR format from MPlay after using Karma (XPU)? Should I avoid Karma XPU for now?
I hope I won’t need to re-render this whole 18hr render again. Is there a check box I missed when rendering?
Getting this error for the first time when trying to save a sequence rendered to MPlay as EXR from a Karma XPU render. PNG/TIFF/JPG is fine but with EXR I get this error:
“Cannot write file
Please check that the destination path exists and is not write-protected, and there is sufficient space on the drive”
Whether I create the folder with the Houdini save prompt window, or choose an existing folder this error comes up. There’s also 2TB of free space. Ive right clicked the folder and ticked off “Read Only”. Tried saving on a separate drive, on desktop, on other external drives to no avail.
Is there something wrong with saving EXR format from MPlay after using Karma (XPU)? Should I avoid Karma XPU for now?
I hope I won’t need to re-render this whole 18hr render again. Is there a check box I missed when rendering?
Edited by Drewzee - Dec. 31, 2022 17:29:39
Houdini Lounge » Houdini 20 Rumors
- Drewzee
- 16 posts
- Offline
wouldnt it be cool if the shelves re-ordered their contents based on how often you used one of its items?
Technical Discussion » Houdini and Redshift freezing system
- Drewzee
- 16 posts
- Offline
Technical Discussion » Launcher does not work
- Drewzee
- 16 posts
- Offline
toonafish
2nd attempt today to use the Launcher to update Houdini. 1st time a while ago I got a "corrupt install" error when trying to run the Launcher after install. SO I gave up.
This time it seems the Launcher was installed, but I get a "Error while extracting from houdini_19.tar.xz: Can't unlink already-existing object" error when trying to update from 19.0.561 to the latest 19.0.589.
Then after a while it installed a 19.0.589 after all, but a version that "NEEDS REPAIR", but repairing doesn't work :-/
So it seems this time I have to manually un- and reinstall 19.0.589.
Nice, "the preferred method of installing houdini".....
Getting the same.. "Waiting for 0 other actions" .. after waiting for about 5 minutes it finally uninstalled the version I wanted to remove and is working normally, but it would be nice if the user was informed to wait instead of having to guess as to how long something like this would take.
Houdini for Realtime » Houdini Niagara Updates
- Drewzee
- 16 posts
- Offline
Houdini Lounge » Request to have CAD import surface in Houdini
- Drewzee
- 16 posts
- Offline
Hi all - also adding my voice here to be able to import files from Inventor! Inventor is becoming really popular with younger engineers these days. I'm going to try the UE4 route and see if that works; I've seen it suggested before.
3rd Party » Octane Installation errors
- Drewzee
- 16 posts
- Offline
ayanm
I also have the same issue. I'm trying to run the demo version.
First of all I tried the packages and wrote the json file which mr.dyts said above here
but it didn't recognize
so I wrote the json file like this referencing the axiom's json file which is already recognized and runs well
{
"env" :[
{"OCTANE_ROOT":"C:\HoudiniSetting\Houdini18.5\packages\Octane_2020.1.5.3_Houdini_18.5.351_demo_Win64"},
{"HOUDINI_PATH":"$OCTANE_ROOT"},
{"PATH":"$OCTANE_ROOT/bin"}
]
}
it is recognized but once I try to put geo node at first, it crashes.
it says "17272: fatal error : Segmentation fault"
What should I do ?
I'm new to these kind of things so any help would be appreciated..
Thanks in advance !
(April 11, 2021)
The post I'm quoting was deleted for some reason (thanks google cache).
I had the same exact problem. You absolutely have to use the version of Octane that supports the Houdini version that you're using. I was using Houdini 18.5.561 but my Octane was "Octane_2020.2.3.1_Houdini_18.5.351" - so if a new Houdini version drops you gotta just be patient. It worked only a few times until it broke when I installed SideFX labs. Now it all works fine even with SideFX Labs because the versions match.
-
- Quick Links