This is how professional compositors do it. This is why most 3d rendering is done in separate passes with the DOF applied to each layer separately. The software has to 'make up' what it thinks is behind the subject. This creates an unnatural halo effect around objects where the information has to be interpolated by the blurring software. The first major issue is that you cannot achieve an accurately natural background blur as your image will not have the information behind the foreground elements which occlude them. There are many caveats of doing DOF as a post process using plugins like frischluft LensCare. Now lets say even by some voodoo magic you are able to obtain a z depth image for each frame of video you shoot on your humble DSLR. Even in CGI, This is not trivial to do well. I have spent a great deal of time trying to perfect the process of adding DOF to a single beauty pass render in conjunction with a z depth pass. I too am a 3d artist who has been working in games and VFX for the last 15 years. It’s up to you which flavour you like best.When i read the first post on this thread i actually laughed. This time around I have taken a bit different route when detecting the OS type, by using the Python “sys” library. In order to make a whole lot of custom stuff work, we need to detect the current operating system. For some reason, their sample code snipplet does not work with Nuke 6.3 as of writing this. If you wish to specify file paths for Linux systems, simply check out nuke.env, like in their sample code on that page. You can read more about the filenameFilter in The Foundry’s Python docs. replace ( '/Volumes/Assets', 'Y:' ) return filename # Use the filenameFilter(s) replace ( '/Volumes/Projects', 'X:' ) filename = filename. replace ( 'Y:', '/Volumes/Assets' ) if nuke. replace ( 'X:', '/Volumes/Projects' ) filename = filename. # Make all filepaths load without errors regardless of OS (No Linux support and no C: support)ĭef myFilenameFilter ( filename ): if nuke. Examples of this below…Ĭontents of launch_nuke.py (works on Windows with Python installed): Nuke will then look for this environment variable and intialize any customizations defined with init.py and menu.py, which we will create inside this directory.Īn alternative to setting the environment variable is to run Nuke from a Python script or a bash script for the Mac, which will launch Nuke with the environment variable loaded for the particular shell it is running in. Let me know if there are any specific Windows/Mac switching woes that you are experiencing, which are not covered here.įirst off, create the environment variable NUKE_PATH and point it to a centralized server location, in my case Y:/include/nuke on Windows or /Volumes/Assets/include/nuke on Mac OS X. In this article, I will explain how to set up Nuke with a few handy extras that will make it fly even smoother across Windows and Mac computers, and with custom menus. Since I jump between my Mac laptop and a Windows based workstation, I used to mess around with broken file read nodes in The Foundry’s Nuke and other stuff related to file paths being different on Windows and Mac OS X. This is a quick guide to setting Nuke 6.3 up with a custom menu and make it work more seamlessly across operating systems. Nuke 6.3 small studio setup for Windows/OS X #Nuke #Python
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |