How would I see all the environment variables that a deadline “session” has. I mean I am loading some varialbes with the JobPreLoad.py (for husk) and I see that working before it constructs the husk render command. what is really weird is that all this just works in 20.0
Just add somewhere in the Houdini plugin
print(os.environ["PYTHONPATH"])
and/or
print(sys.path)
By the way when you say you execute the command, do you run the full command? Meaning the one with hrender_dl.py in it?
1 Like
Sorry, I need to clarify. I am rendering through husk (with husk standalone). So this is already a husk standalone job. So actually husk is crashing not hython.
Oh alright, I overlooked it.
You can print the subprocess’s environment by
plugin.GetProcessEnvironmentVariable("PATH")
(it is possibly the library include path, and not PYTHONPATH)
https://docs.thinkboxsoftware.com/products/deadline/10.1/2_Scripting%20Reference/class_deadline_1_1_plugins_1_1_deadline_plugin.html#ac233247e900b1e80fef4f6edfbdf72a3
I don’t see any issues with what env vars are set (they are the same for 20 and 20.5). Another thing I do suspect is some sort of access restriction that has not mattered until now or some python version issues. But this is what you get from using an unsupported tool like Deadline…
Anyways, just out of curiosity: have you run renderjobs (with Karma) from H20.5? And if so, did you have any issues?
@Ronald_Anzenberger we recently started to using karma from H20.5 without any issues so far. Is it failing just one particular job or all of them?
EDIT: could you provide whole log with that SEGFAULT?
EDIT2: is it xpu or cpu? Wouldn’t be it caused by graphic drivers in case of XPU?
Every job, every machine. we are trying to render with XPU. XPU in H20.5 itself works, it also works when running husk from within houdini (hitting render on a usd render rop) or executing the command the submission creates for each task in a command prompt. But once it is submitted and a task is executed (by a deadline worker) it has the seg-fault.
I shall see to provide more of the log, but as far as I can remember, the additional info was rather cryptic.
Are you using the same user? I’m hitting an issue where if Deadline runs as ‘root’ then Redshift bombs out (another thread on this forum). Someone mentioned this could be something from logs generated.
If Deadline is running as the same user, or you’re running deadline directly on the machine you’re submitting from this should point the issue more at deadline
when you say “deadline runs as root” you mean the worker, right?
As we are on windows, there is no root user, so the worker runs with the user of the machine if it’s a workstation and in case of renderfarms with a special renderfarm user. But no matter the combination, it does not work. And again, this is all not a problem with 20.0. I can literally submit a job out of 20.0 which works and submit the same thing out of 20.5 (without changing anything in deadline) and it will crash husk. the only difference is which houdini/husk version is used.
I do in fact suspect something beeing wrong with deadline and I am glad that people seem to have it working with 20.5. But with the current evidence I have, its hard to track down what is wrong.
1 Like
Ok, just in case anyone is having similar issues we found out what the problem was. It appears, that husk (as well as houdini) loads any available OFX plugins (for the new COPs). This lead to the crashes when running husk through deadline (not when running it from a command prompt interestingly enough). We also had some rather random houdini 20.5 startup crashes (also with segmentation fault) which is also fixed by not loading the OFX plugins. SideFX also suggested to remove system paths for python versions that do not match the houdini version or use a houdini version that matches python version on your system. I can not be sure if this really did anything, but this was part of the process. Thanks to everybody jumping in very quickly and giving suggestions!
2 Likes
Since switching to 20.5 I have a weird problem when submitting husk jobs. it would create the usd file for rendering (with the usdrender rop) but then when actually rendering the frames it would always write to the last frame of the sequence (it does render the correct frame it just overwrites it to the framename with the last frame in the name). So all frames of a 100 frame sequence would be written to filename.100.exr. mind that this is not caused by an incorrect command for every frame, but the actual usd file is incorrect. the intesting thing is, that when I don’t use the deadline rop to create the usd file (locally) it is correct. Has anybody seen this kind of behaviour?
what is your chunkSize of the export job? If you need 1 usd file to be used for all frames, you should have chunkSize >= frame range.
Deadline 10.4.0.8 released 14/10/2024, includes support for Houdini & Mantra 20.0 & 20.5, and also Karma but only for version 20.0?
https://docs.thinkboxsoftware.com/products/deadline/10.4/1_User%20Manual/manual/release-notes.html
Interested to see how this is implemented, backwards compatibility means it’ll be safer to create a test environment
ok, I don’t see anything in the plugin options, or under the ‘Submit’ menu, the docs show it’s a standalone app
https://docs.thinkboxsoftware.com/products/deadline/10.4/1_User%20Manual/manual/app-karma.html
It’s not in the submit menu
or the Plugin Config
or the submission scripts
or the Houdini integrated submitter
There’s nothing in the repo itself…
I’m using 10.4.0.8
Also the installer for the plugin doesn’t include py3.11 option (just install 3.10 and copy to 3.11 and it runs anyway)
I got confirmation Karma was missing from the release and have a copy of the plugin. I’ll let some official share that though.
EDIT: I grabbed the wrong commit - Zain’s got the proper stuff here.
1 Like
A quick mod will get 20.5 on there too, was there any reason to skip Karma when Houdini got this?
[Karma20_5_Executable]
Label=Karma 20 Executable
Category=Render Executables
CategoryOrder=0
Type=multilinemultifilename
Index=1
Default=C:\Program Files\Side Effects Software\Houdini 20.5.332\bin\karma.exe;/opt/hfs20.5/bin/karma
Description=The path to the Karma executable used for rendering.
Also needs “20.5” in the submission script, I’ve attached an icon too to help differentiate renders
Karma_ico.zip (709 Bytes)
What’s the status of the Husk submitter?
“We can’t share the roapmap”
wait, there is a karma.exe? I always thought that rendering karma was always handled through husk. Will this do everything that husk can do (but limited to only karma cpu/xpu)? Could you already test if/how that works? what would be the submitter input? Is the submitter a ROP or a LOP? it will be some time until we can upgrade to this i’m afraid.
I got a response from SideFX about this, karma.exe and husk.exe are aliases of the same program, if you check the file size they are identical, and work identically. So you can render redshift USD with karma.exe the same way you would Husk.
It makes more sense to me (for clarity) to go with Husk as the tool to do this, as Karma sounds like it only does Karma.
I got a response from Thinkbox you could rename the Karma plugin to husk and it would function the same. but this seems pointless as the one on this thread is a working solution, and the new Thinkbox Karma(husk)Plugin only works through the Monitor for submission.
@MikeOwen @eamsler @Justin_B @zainali If you read through this thread you’ll see how this works, I’m sure anyone on this thread would help out develop this plugin also. I’d be more than happy to jump on a call to demo
1 Like
just to add my 2cents: @anthonygelatka is right. While it is really great that we now have official support for solaris/husk/karma it is important to note that the workflow should be similar to the “old” way of rendering using the deadline rop. This is because you often have situation where you want to submit muliple renders from within one houdini scene and you don’t want to do that by hand with every iteration. Also with Solaris, the chance that there is a multishot workflow going on makes this even more important. Also as far as I can tell from the 10.4 documenation, there seems to be no way to do the USD export locally.
1 Like
@Ronald_Anzenberger @anthonygelatka
We are generally using the ROP for submissions for all the reasons mentioned above. It would be great to be able to use an “official” deadline rop if/when that is released.
2 Likes
06 Nov 2024 - 10.4.0.10 released
Is there anyway of finding out the differences from the plugin development without doing a comparison?
It sounds like the Deadline Karma (Husk) plugin now includes an integrated submitter
IGNORE THIS, it’s just including the standalone karma plugin that missed the boat on the last release…