- RELOADING ERROR IN NUKE 10 SERIAL KEY
- RELOADING ERROR IN NUKE 10 INSTALL
- RELOADING ERROR IN NUKE 10 DRIVERS
- RELOADING ERROR IN NUKE 10 UPDATE
- RELOADING ERROR IN NUKE 10 FULL
Then I set up both computers on windows 11 pro for personal use with Microsoft accounts and added my work account in as a secondary just for apps.įor whatever weird reason Chief does not like if computer is governed by work account (azure ad). First time I had azure ad as computer admin on both computers and got this error. Then installation asks you for your Microsoft account (personal) and this account becomes administrator. After windows 11 home I tried to reinstall windows again and this time I installed windows 11 pro and chose "set up computer for personal use". When I was installing windows 11 pro then I chose an option to "set up windows for work or school" and logged in with my business account (azure ad) and this account became administrator of operating system. When you set up windows 11 home then setup asks you to log in to your Microsoft account (personal).
RELOADING ERROR IN NUKE 10 FULL
While searching for an answer tried as a last resort to do a full windows reinstall again, but this time windows 11 home not pro. And the only reason for this is because Chief Architect is weird as hell. Had to nuke about 2 days worth of work trying to set up my old PC and new laptop on windows 11 pro. Even the message log in appdata is a generic one and tells absolutely nothing.Īny suggestions from Windows 11 pro users? Because right now it is the only logical thing that is in common with both computers. If Chief software finds that something is wrong then It should at least point in a direction of the issue.
This error message is completely useless. I do not understand what to look for or even try.
RELOADING ERROR IN NUKE 10 DRIVERS
But drivers are different for both computers. It is like something is wrong with Windows 11, drivers or my licence key.
RELOADING ERROR IN NUKE 10 UPDATE
And after clean windows reinstall, full update and clean Chief install. But I get the exact same message on both of them. It is weird as both computers are completely different and seem to be supported all the way through. Intel Iris XE is on Chiefs "Intel supported chipsets" list. So should not be a problem with the laptop either. As I have seen in forums then people are using Chief even on Microsoft surface pros and on Inter Iris XE laptops just fine. RX 6800 XT is a stronger version of RX 6800 which is in recommended system requirements. Also I updated BIOS for TPM 2.0 support and compatibility with Windows 11. If I look around Chief forums then some users are using Chief already for a long time with Windows 11. The only difference is that before I was using a Windows 10 home and now Windows 11 pro. I have been working with Chief for about 4 months now on the same PC. As I wrote that PC is the same as it was before. And yes I did unassign my key from another computer before trying on a second computer.
RELOADING ERROR IN NUKE 10 SERIAL KEY
Error comes just after I insert serial key for activation. On laptop graphics drivers are from windows update and on PC I installed AMD pro drivers from a manufacturer website.Ĭhief did not open even once on both of them.
RELOADING ERROR IN NUKE 10 INSTALL
All windows updates are done, graphic drivers are new, Chief Architect is a clean install and even BIOS is up to date. I bought a new laptop and made a clean reinstall of Windows 11 pro.Īlso did a clean reinstall on my PC to Windows 11 pro.īoth computers are fully up to date. I am not sure how long support answers on these cases and I really need this issue sorted fast. I already opened a new case about this to technical support, but maybe someone here knows something about that. How do set up my scene so that it renders the render layers correctly while also displaying correctly in the viewport?Īttached is the passes from my latest render.I thought I post my issue here also. Is there a recommended way of doing renderlayers in max? For example, if I create a daylight system, the image is completely blown out unless I use the exposure control. Am I doing something wrong or is this a bug?Ģ. Also, when rendering AO for example, the output is unusable unless I render to layers, which is kind of unnecessary.ġ. This isn't a huge problem huge problem since I'm comping together the passes to make a new RGB anyway, but I'd like to have the alpha, and also the thumbnail displays the messed up RGB so it makes it harder to orient oneself in the comp tree. However, with the release of 2014, the default RGB-channel - the beaty pass if you like - is completely messed up when I render to exr. It usually turns out reasonably well, as long as I leave the mr Photographic exposure control to 0 or disable it altogether and dim my lights accordingly.
I've been trying to render passes from 3ds Max in the diffuse-indirect-reflections-spec-style with mental ray.
0 kommentar(er)
