Technically, the artist needs to (and does) credit the author of the artwork he referenced and only mention what and where from the character is. Given that, this is a 3d/gaming/technical thingie-ma-jibs website that does not (and probably shouldn't really) reflect on the circumstance of the character itself, but concentrate on creation and techniques used in creation. The name of the character is referenced, but nowhere on the original art the name Sam Riegel is mentioned. As much as critter community is nice and welcoming, this part of "CREDIT THIS OR CREDIT THAT" irritates me. IMHO, Credit is given where credit is due. This 3d model was made with learning purposes only, whereas the original art is being sold. Instead of commenting "GIVE CREDIT" comment "COOL ART OF SAM'S CHARACTER" or "GREAT CRITICAL ROLE ART". All that said, this is an amazing rendition of the original artwork of the character of critical role. As a critter, I love both this piece and the idea of other critter being so talented! Peace, a member of the wonderful critter family.
You need to make it clear that this is an interpretation of someone else’s character and credit them (Sam Reigel, from Critical Role).
As great as this is, it’s not actually “your character” so you should really credit Sam Reigel of Critical Role who created this character, and make it clear this is your interpretation of it, because you make it sound like it was all your idea.
Visual Script Diagnostics
The new Profile node makes Nuke’s performance profiling system easily accessible through the UI. These tools can be used to help identify possible areas for optimisation in a script. A Profile node can be inserted at any point in a script, allowing performance data including CPU time, wall time, number of ops and memory usage, to be captured for all upstream nodes. The resulting data is viewed in a new Profile panel that allows you to display the data in a bar chart, pie chart, as a list of nodes, or across a timeline and filter the data shown using a variety of options. Profile data can be easily exported and viewed in another session of Nuke without the need to load the script or reprofile.
Localization system improvements
Nuke and Nuke Studio’s file localisation system has been updated to provide more granular control over when and which files are localised; while also introducing more visual cues to showcase the status of localised files, for a more intuitive experience. A new “Manual” mode and “On Demand” policy introduce the ability to localise files, or a subset of files, only when prompted by a user. Manual mode is saved as a preference, allowing you to maintain this setting when opening scripts made by other users which may have different localisation policies. The Python API has been extended to allow developers to set system modes and localization policies programmatically. The API also provides the ability to set localization priority, apply policies based on read node type, and find and remove localised files according to specific criteria.
Nuke Studio: Expanded source clip properties
Properties for source clips in the Nuke Studio and Hiero timeline have been extended to offer more consistent properties with Read nodes in Nuke and create more efficient workflows across the Nuke Family. Source clip properties are now shown in a Nuke style Properties panel. This consolidates existing options into a single location, providing faster access and greater control. A new Project root directory allows source footage file paths to be relative, making the sharing of projects between locations or artists easier and more efficient. In addition, source clip properties are accessible through the same Python API as Nuke, improving scripting capabilities and the ability to integrate Nuke Studio into existing pipelines.
You can find more details on the update and get the tool here.