Found 12 posts.
Search results Show results as topic list.
3rd Party » [SOLVED] Redshift :: Missing Shader Kernel
- ChazS
- 12 posts
- Offline
Updating my Nvidia driver to v.452.06 fixed it.
Edited by ChazS - Aug. 30, 2020 20:55:14
3rd Party » [SOLVED] Redshift :: Missing Shader Kernel
- ChazS
- 12 posts
- Offline
While going through Entagma's rendering tutorials, everything was working fine until I realized the RS MAXON NOISE node wasn't available in the version being used, so Redshift and Houdini were upgraded to v.3.0.26 and v18.0.532 respectively. The tutorial was restarted from the beginning but the renders are now entirely black.
Digging into the Program Data folder exposes the GPUKernels folder and its subsequent content are missing. Uninstalling and reinstalling Redshift hasn't helped; nor has rebooting my workstation.
I'll certainly reach out to Redshift, but since it's a Sunday, figured too see if anyone here knows how to remedy this in the interim. Thoughts?
Houdini 18.0.532
Redshift 3.0.26
Win10 Pro
Titan X GPU
Bunches of RAM
Lots of HDD
Ikea Desk: Effectiv
Subaru Crosstrek '18
Digging into the Program Data folder exposes the GPUKernels folder and its subsequent content are missing. Uninstalling and reinstalling Redshift hasn't helped; nor has rebooting my workstation.
I'll certainly reach out to Redshift, but since it's a Sunday, figured too see if anyone here knows how to remedy this in the interim. Thoughts?
Houdini 18.0.532
Redshift 3.0.26
Win10 Pro
Titan X GPU
Bunches of RAM
Lots of HDD
Ikea Desk: Effectiv
Subaru Crosstrek '18
Edited by ChazS - Aug. 30, 2020 20:54:14
Technical Discussion » Error message
- ChazS
- 12 posts
- Offline
It's December 2019 and Edward's suggestion still works
The only difference is there isn't a way to turn off the AA (at least in my control panel) but changing the setting to “application specified” worked for me.
The only difference is there isn't a way to turn off the AA (at least in my control panel) but changing the setting to “application specified” worked for me.
Technical Discussion » Object rendering as black in viewport when first opening houdini scene
- ChazS
- 12 posts
- Offline
Houdini Indie and Apprentice » Display mode affected by display type of connectadjacentpieces node
- ChazS
- 12 posts
- Offline
I don't know if the two are related, but another issue reared its ugly head, so I'm linking it here in case the two are somehow connected: https://www.sidefx.com/forum/topic/57056/?page=1#post-255542 [www.sidefx.com]
I'm also including the file so if you're inclined to open it up, I"d be greatly obliged. ~Cheers
I'm also including the file so if you're inclined to open it up, I"d be greatly obliged. ~Cheers
Houdini Indie and Apprentice » Constraints are activating/breaking
- ChazS
- 12 posts
- Offline
Houdini Indie and Apprentice » Constraints are activating/breaking
- ChazS
- 12 posts
- Offline
I'm following a tutorial where the constraint network for the tutor remains intact where mine begins to immediately crumble. In the tutorial, the model remains whole and doesn't break at all and the constraint strength is set to zero.
However, the model in mine begins to crumble at the base as soon as the sim begins.
He's using an older version of Houdini, so maybe my newer version requires a different setting somewhere.
The other issue might be due to a naming error that is appearing in the connectadjacentpieces node of the SOP network (I haven't figured out how to fix that one either).
I'm cross linking these two issues in case one is the result of the other. The other topic https://www.sidefx.com/forum/topic/56988/ [www.sidefx.com]
Thanks in advance.
However, the model in mine begins to crumble at the base as soon as the sim begins.
He's using an older version of Houdini, so maybe my newer version requires a different setting somewhere.
The other issue might be due to a naming error that is appearing in the connectadjacentpieces node of the SOP network (I haven't figured out how to fix that one either).
I'm cross linking these two issues in case one is the result of the other. The other topic https://www.sidefx.com/forum/topic/56988/ [www.sidefx.com]
Thanks in advance.
Edited by ChazS - July 24, 2018 18:58:21
Houdini Indie and Apprentice » [SOLVED... well, kinda] Prefractured objects are a jumbled mess.
- ChazS
- 12 posts
- Offline
tamte
it's the Initial State Rotation on your rbdpackedobject, it's rotating each piece around it's pivot, hence the mess
move and rotate the geo before going to DOPs
Sounds like a plan. Thank you.
Houdini Indie and Apprentice » Display mode affected by display type of connectadjacentpieces node
- ChazS
- 12 posts
- Offline
I'm getting a peculiar display issue when building a constraint network. In the SOP network is a connectadjacentpieces node that (with the display type of "adjacent pieces from points“) will only display the wire connections. The flat shaded mode, among all the others, will not work.
However, if the display type is changed to ”adjacent pieces", the flat shaded mode will display.
I wouldn't be concerned with this, but there is a warning message on the node, Invalid attribute specification: “attribute name either not used or unrecognized”, so I'd like to fix it.
Knowing just enough, my best guess is that pieces (that have been renamed further upstream) is somehow borking this node. But I'm just new enough to Houdini to not know how to fix it. Would it have something to do with the VEX in Attribute Wrangle?
I didn't want to inundate this initial topic with unnecessary info, so just tell me what's needed and I'll be happy to supply any other info about the file.
Thanks in advance.
However, if the display type is changed to ”adjacent pieces", the flat shaded mode will display.
I wouldn't be concerned with this, but there is a warning message on the node, Invalid attribute specification: “attribute name either not used or unrecognized”, so I'd like to fix it.
Knowing just enough, my best guess is that pieces (that have been renamed further upstream) is somehow borking this node. But I'm just new enough to Houdini to not know how to fix it. Would it have something to do with the VEX in Attribute Wrangle?
- s@name_orig = s@name;
- s@name = sprintf(“inst%d”, @ptnum);
I didn't want to inundate this initial topic with unnecessary info, so just tell me what's needed and I'll be happy to supply any other info about the file.
Thanks in advance.
Houdini Indie and Apprentice » [SOLVED... well, kinda] Prefractured objects are a jumbled mess.
- ChazS
- 12 posts
- Offline
Once the issue of Houdini constantly crashing was resolved, I was able to spend some time reviewing the file. The pivot location in the ASSEMBLE node (for the voronoi fracturing network) was set to centroid. Setting it to origin resolved the issue. ~Cheers
UPDATE: So changing the pivot location to origin will collapse all the points into one spot. This creates a new issue when using constraints (i.e. connectadjacentpieces), so another solution or work-around for either the jumbled pieces or the constraint needs to be found.
UPDATE: So changing the pivot location to origin will collapse all the points into one spot. This creates a new issue when using constraints (i.e. connectadjacentpieces), so another solution or work-around for either the jumbled pieces or the constraint needs to be found.
Edited by ChazS - July 12, 2018 21:40:48
Houdini Indie and Apprentice » [SOLVED... well, kinda] Prefractured objects are a jumbled mess.
- ChazS
- 12 posts
- Offline
I'm attempting to complete Steven Knipping's Rigid I tutorial, but an hour into the video my prefractured object is a jumbled mess.
Steve was kind enough to load up the file to discover it's working fine on his machine. Aside from some unknown diffs with our workstation specs, the obvious one is that he's using build 378 and I'm on 496 (v16.5).
Plans are to revert my copy to 378 to see what happens, but before doing so I was hoping someone running 496 would be willing to open my file and report the result. Please?
I've attached the hip file, as well as a txt file of my machine spec (generated by Houdini) and some screens of both results from mine and Steve's machine.
Any other comments and suggestions are greatly welcomed.
Many thanks.
Steve was kind enough to load up the file to discover it's working fine on his machine. Aside from some unknown diffs with our workstation specs, the obvious one is that he's using build 378 and I'm on 496 (v16.5).
Plans are to revert my copy to 378 to see what happens, but before doing so I was hoping someone running 496 would be willing to open my file and report the result. Please?
I've attached the hip file, as well as a txt file of my machine spec (generated by Houdini) and some screens of both results from mine and Steve's machine.
Any other comments and suggestions are greatly welcomed.
Many thanks.
Edited by ChazS - July 12, 2018 21:37:40
Technical Discussion » houdini 16 crashes on start up
- ChazS
- 12 posts
- Offline
I'm using Apprentice v16.5.496 (GPU drivers: v388.59 & v391.35) and it still crashes within minutes when the work begins. If I leave it alone after launching, it doesn't crash. The moment I add a color node though, the program simply disappears.
Reinstallation didn't fix it. This included cleaning out my hard drive of any remnant v15 stuff.
Firewall permissions are already allowed for everything Houdini.
From tmdag
Where is this file? SOLVED= *> Documents > houdini16.5 …
Where is the crash log or stack trace? SOLVED= From the help desk…
Thanks in advance.
Reinstallation didn't fix it. This included cleaning out my hard drive of any remnant v15 stuff.
Firewall permissions are already allowed for everything Houdini.
From tmdag
Sidefx helped with solution:
add ‘HOUDINI_USE_HFS_PYTHON=1’ to houdini.env file and that fixed my problems.
Where is this file? SOLVED= *> Documents > houdini16.5 …
Where is the crash log or stack trace? SOLVED= From the help desk…
- Help -> About Houdini -> click on “Show Details” -> Save
- or…
- …users > YOU > AppData > Local > Temp > houdini_temp > crash.untitled.YOU.hipnc
Thanks in advance.
Edited by ChazS - July 9, 2018 18:07:53
-
- Quick Links