The big thing your missing out on 7.0v6 is the extra Assist seats for any
NukeX lics you have. I'm not sure if that matters much to you guys though.
-deke
On Monday, April 22, 2013, wrote:
so we saying 7.0v5 is the latest 'dependable' version ?
anyone have a particular issue with 7.0v5 ?
hey Deke,
refresh my memory on the assist seats ? might that help such a large
group when we already have such a large base of licenses ?
and what say you regarding any prominent 7.0v6 issues ?
Lastly, do you know if the file browser issue with displaying numbered
files as sequences is still,
Assist us the Roto/paint version of nuke you get 2 copies of with NukeX.
Though as you said you may have so many lics it doesn't matter.
http://www.thefoundry.co.uk/articles/2013/03/18/496/assist-tool-for-nukex-available-now/
Easier to see what nodes are enabled in the release notes.
yes, I have. especially the gamma option will screw up your image in a
way that may cause NANs. bit m in the bum big time on a recent show.
it's a great new node though, I just hope the polish it a bit to avoid
these things
On 23/04/13 11:17, Howard Jones wrote:
Has anyone noticed that the
Hi
Does anyone know the (environment) variable for the default font path? - there
used to be something on Nukepedia but I cant find it there or in the manual.
I want a gizmo to load with the systems default path.
Thanks
Howard
___
Nuke-users
Anyone have the bug number for that regression or the file browser issue?
Sounds very similar to Bug ID 30168, with the file browser not identifying
sequences of certain file types (like dtex).
That one got resolved during the beta, but it sounds like having no file
extension at all leads to
Actually nuke.defaultFontPathname() brakes in most linux systems I have and
I've seen it failing under OSX too. So I ended up re-assigning it to my own
version that points to a default font on a central repository instead.
But I have a second version that handles Linux, Windows and OSX using
