[Nuke 8 0v1 98
Luther Lazaro
This seems to work locally as OCIO is set in nuke, however when I use shotgrid > file open > new file. The colour managment resets to nuke and doesnt use ocio. Is it possible that there are some default settings in shotgrid that are overriding my settings set in nuke?
I think it might be Nuke that is resetting the config.
We have a hook that runs on file open/save/new which sets the OCIO environment variable before opening the new scene. This affords us per-project OCIO configs. It works well currently (there were issues with resetting OCIO on older Nukes).
You can also set the variables SHOT, SEQ, if you have per-shot looks and such.
Yes, it is. Unfortunately there is no way to set this value in python or any other way (and believe me, we searched far and wide). You can only set it manually for each artist. The Foundry needs to add that in. It is kind off odd, because it feels like Nuke is going out of its way to NOT use OCIO. Pretty annoying issue.
If I do a full machine restart it will usually (although not always) work for a few submissions, but then at some point it will fail and Nuke will hang. once its hung once, it will normally hang everytime I try a submission, untill i do a full restart.
We are running a few custom tools and scripts but nothing particularly clever, and nothing that I can imagine would cause this issue. Everything seems to be working completely normally from a user/tools point of view, its just the submissions thats failing. I can send you the menu.py and init.py if you want to check what were doing?
The crashes were indeed in the cases where jobs are submitted in threads.
I debugged this for a while today, and found that the crash happens around line 1435, where
get_filename(node) is called.
This might be because the nuke api is called concurrently in this function from multiple callers.
First tried acquiring the semaphore before this call, which did not help.
A sleep(0.5) before the call seems to fix it as far as I have tested. This solution relies on luck though, so not that good.
The user right "nuke" is automatically granted to the "sysop" user group.To decouple this and assign this right to a dedicated new user group such as "nuke" add the following to your "LocalSettings.php" file:
I started playing eve early in 2016 right before the citadel update hit. My first few months I was flying with Signal Cartel doing exploration to make my isk and dipping my toes into WHs living in their wormhole campus (living out of a pos, imagine that). I left when I wanted to get into pvp and I moved in with Rapid Withdrawal in galmil and started playing in FW. I flew with them for a few years being a generally useful-ish line member until WANGS died and I managed to finagle my way into Snuff which is where I am now.
If you want to ask me any questions feel free to ask here in the forum post, you can also reach me on discord, either by messaging me directly @nukelear or on the server for my CSM campaign here: Nuke4CSM
You can also contact me in game by mailing Nuke Michael but it will take longer to get any answer
In that way I am no bigger of a risk of a CSM leak than any other candidate from an Alliance that could use that info. CCP is very strict about that sort of behavior and bluntly, there is no advantage to be gained from leaking CSM info, which not only gets me banned from the game of course, but also opens me to irl litigation, that would be worth those costs.
That is just wrong and I wont apologize for having told you it was a bad idea, and joking about how Id have a fast response. I also never said your questions were dumb, I just said you wouldnt like my answers, it was a different user who called them dumb.
As we can see with little screenshot, the problem is not how much the Snuffed Out alliance would profit, but the door it would open to some special kind of characters in the game (that Nada in the screenshot, for example) as in the elitist, irascible, drama-fueled, and vindictive people that Nuke has surrounded himself with (in my opinion), and give them an access to the ear of a CSM.
One of the suggestions in this very thread to nerf unbonused ewar is nerfing something that we utilize way more than most other groups and in more doctrines than others, it is strange to accuse me of not wanting any changes that might hurt snuff while being right below that.
Although the majority of my gameplay has been LS focused, I have enough experience in other areas of the game in WH/NS/poch to at the very least be able to stop the negative changes going their way, which is the biggest job of the CSM, coming before pushing for specific changes.
Is this actually what the CSM do? My understanding -based on the experiences shared by past and present CSM representatives- is that the CSM is best characterised as a consumer consultancy group and their greatest successes in representing the player base have been when presenting studied, well-documented, well-produced and analytical presentations.
How can we expect that you will also defend the interests of people who do not have the same general knowledge or mastery of the game as you? Can you genuinely tell me that your first instinct will be to advocate for them too?
domain will default to your-username.pythonanywhere.com (with "your-username" replaced by your username of course), so if you already have a web appon different domain and you want it nuked, you need to explicitly specify itwith --domain=your-custom-domain.com flag.
I rendered a sequence in UE and now that I have the erxs I want to use the camera move from sequencer in Nuke. Its easy enough to export the camera from sequencer as an FBX but I cant seem to find orientation options. UE is Z-up (correct me if Im wrong) and Nuke is Y-up. When I import the camera into nuke I have options such as transform order and rotation order but no combination seems to match.
795a8134c1