Groups keyboard shortcuts have been updated
Dismiss
See shortcuts

Problem in resolving wedge variables in gaffer 1.4

41 views
Skip to first unread message

Sudarshan Havale

unread,
Oct 3, 2024, 7:09:16 AM10/3/24
to gaffer-dev
Hi,

We heavily rely on wedging in our workflow, and to generate Deadline job names for wedges, we tag a custom variable "Name" with the value "${wedge:shot}_Arnold" on the Render task node. This setup worked flawlessly in Gaffer 1.3. However, after upgrading to Gaffer 1.4, it seems that the "Name" variable is no longer resolving the wedge variables as expected.

I've attached a snapshot and a sample scene for clarity. I'm not sure if this is a bug, but could you please provide guidance on how to resolve this issue within the node graph?


gaffer-1.3.x
gaffer13_wedging.PNG

gaffer-1.4.x
gaffer14_wedging.PNG

Thanks,
Sudarshan

z999_shavale_lgt_multiShotGaffer14_v003.gfr
z999_shavale_lgt_multiShotGaffer13_v003.gfr

John Haddon

unread,
Oct 3, 2024, 8:17:46 AM10/3/24
to gaffe...@googlegroups.com
Hi Sudarshan,

Thanks for the clear description of the problem and the example files. We did refactor the Dispatchers significantly in 1.4, but I'm having difficulty picturing how that could have caused this problem. I'm wondering if perhaps something has changed in GafferDeadline instead. Could you share which versions of GafferDeadline you used for each test please? I'll ask Eric - Mr GafferDeadline himself - if he could take a quick look, and if it looks like a Gaffer problem after all, I'll take a look too.

Cheers...
John

--
You received this message because you are subscribed to the Google Groups "gaffer-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gaffer-dev+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gaffer-dev/cb8b5837-2724-4e5e-abd1-e3bf0b8f09edn%40googlegroups.com.

eric...@gmail.com

unread,
Oct 3, 2024, 9:21:20 AM10/3/24
to gaffer-dev
Hi Sudarshan,
What version of GafferDeadline are you using? This sounds a lot like a bug that was fixed in 0.58.0.0, so if you haven't upgraded to at least that version, give it a try. The latest is 0.59.0.0, so I recommend that : https://github.com/hypothetical-inc/GafferDeadline/releases/tag/0.59.0.0.

If you are up to date, let me know and we can figure out what's going on. It's definitely something that should be working with all Gaffer versions.

- Eric

Sudarshan Havale

unread,
Oct 3, 2024, 9:50:33 AM10/3/24
to gaffer-dev

Hi John and Eric,

Thanks for the quick response.

@Eric, this is a bit embarrassing, but you were right, we were using an older version. The latest version does indeed have the fixes. :|

Thanks again :)

eric...@gmail.com

unread,
Oct 3, 2024, 11:26:39 AM10/3/24
to gaffer-dev
No reason to be embarrassed! I'm glad it was an easy fix :)
Reply all
Reply to author
Forward
0 new messages