Hi,
We're trying to get PDG going on the farm. Some early success was a pleasant surprise, but results are inconsistent.
Tasks often error with:
Timed out waiting for MQ connection file at //location.xyz/pdgmq_server.txt
Absolutely, that file isn't being written to disk. At least not consistently, sometimes it appears and the task completes successfully. So the same config yields varied results. We've also tried limiting new submissions to boxes that have been previously been successful, no dice.
On the deadline side the job reports feature:
Task rendering stopped due to external cancellation.
Something along the lines of a timeout being too short? All speculation at this point.
Any information about where to look next would be well received!
Cheers,
H19.5.435 and DL 10.1.21.6.
Found 5 posts.
Search results Show results as topic list.
PDG/TOPs » Deadline Farm. "Timed out waiting for MQ connection file"
- FridayMarch27th
- 5 posts
- Offline
Technical Discussion » Vellum cloth attach and orientation
- FridayMarch27th
- 5 posts
- Offline
I've had a few occasions recently where I've attached Vellum cloth pieces to hair curves.
The typical distance constraints for attaching the cloth haven't been quite right, leaving it with an obvious tendency to rotate or spin around the curve.
The problem I've broadly solved with additional geometry. Branches from the main curve maintain their orientation while giving the cloth something to attach to. This works, but it strikes me that there are likely less convoluted methods of achieving the same result.
I've attached a clip of a spinning constraint, versus not spinning branches.
How wrong am I?
Cheers,
Edit
I should qualify that the “Yes” label in the video implies yes that you're looking at the “good one”, not the one with the spinning constraints.
The typical distance constraints for attaching the cloth haven't been quite right, leaving it with an obvious tendency to rotate or spin around the curve.
The problem I've broadly solved with additional geometry. Branches from the main curve maintain their orientation while giving the cloth something to attach to. This works, but it strikes me that there are likely less convoluted methods of achieving the same result.
I've attached a clip of a spinning constraint, versus not spinning branches.
How wrong am I?
Cheers,
Edit
I should qualify that the “Yes” label in the video implies yes that you're looking at the “good one”, not the one with the spinning constraints.
Edited by FridayMarch27th - Dec. 10, 2020 19:19:48
PDG/TOPs » Geometry pieces to FBX
- FridayMarch27th
- 5 posts
- Offline
Wowzers. @pdg_output in a file parm I'd clocked, so of all the things to miss!
Thank you so much.
Thank you so much.
Edited by FridayMarch27th - Jan. 9, 2020 14:28:49
PDG/TOPs » Geometry pieces to FBX
- FridayMarch27th
- 5 posts
- Offline
Hi,
A question appeared on the Think Procedural Discord channel that felt as though it would easily be covered by TOPs (of which, admittedly, I've extremely limited experience):
“How to export different pieces of a model to individual FBX files?”
The separation of pieces was very straightforward, creating a group per piece allows TOPs to create comparable work items. One geometryInputTOP later, and we have our separated .bgeo files.
Onto writing FBX files. Given that the journey up to this point was trouble free and largely predictable, it felt as though format conversion would follow a similar pattern, but no joy so far.
All signs point toward a ROP_fetchTOP; though the relationship between this and the subsequent filmboxfbxROP is my point of failure, in a way that makes me feels as though I'm missing a fundamental piece of puzzle. The fbxROP's Export parm is what would select the geometry network to write, but in the case of Export parm vs TOPs, what's required?
I've spotted a few similar discussions around the web, including one here [www.sidefx.com], but none reach closure.
So, geometry pieces to separate FBX files. What am I missing?
Cheers.
A question appeared on the Think Procedural Discord channel that felt as though it would easily be covered by TOPs (of which, admittedly, I've extremely limited experience):
“How to export different pieces of a model to individual FBX files?”
The separation of pieces was very straightforward, creating a group per piece allows TOPs to create comparable work items. One geometryInputTOP later, and we have our separated .bgeo files.
Onto writing FBX files. Given that the journey up to this point was trouble free and largely predictable, it felt as though format conversion would follow a similar pattern, but no joy so far.
All signs point toward a ROP_fetchTOP; though the relationship between this and the subsequent filmboxfbxROP is my point of failure, in a way that makes me feels as though I'm missing a fundamental piece of puzzle. The fbxROP's Export parm is what would select the geometry network to write, but in the case of Export parm vs TOPs, what's required?
I've spotted a few similar discussions around the web, including one here [www.sidefx.com], but none reach closure.
So, geometry pieces to separate FBX files. What am I missing?
Cheers.
Houdini Lounge » Path Deform HDK Plugin
- FridayMarch27th
- 5 posts
- Offline
-
- Quick Links