Whats with the red shadows when using quicksilver renderer.
when colour ink rendering level is set and lighting and shadows quality slider is a few notches up the shadows get red, unusable. I think some of quicksilvers other render levels are affected too.
I like to use this feature a lot 
I can reproduce that on my end. Might be a new bug in 2014, I'll see what I can do.
Can you tell me what graphics card you run?
No problem. I'll talk about this with the devs and try to get a fix for this. Can't give an ETA at this moment though, apologies.
@Anonymous wrote:I dont think it is a graphics card problem as this problem was present with my last graphics card (now blown up) nv 570
The problem has existed since the release of 2014. I was hoping it would be fixed on release of SP1 but no.
Thanks for your reply.
I would tend to agree that it seems like it isn't a graphics card problem but one of my colleagues didn't seem to get the issue with a Quadro 4000. That being said it could be some other difference on that system.
In any case I always like to gather as much detail as possible. I've overlooked things in the past and it has on the rare occasion come back to bite me in the butt. 😉
@Anonymous.sz wrote:Iam having a problem too, when i check Indirect Ilumination, my scene doesnt render.
I am using mr photographic exposure control, daylight system with mr sun and mr sky, and the materials are standard.
Can you help me?
I can certainly try. A couple of questions though:
-What exactly do you mean by your scene not rendering? (red colours, no output, etc...)
-Just to confirm, you're using quicksilver as the renderer?
I have just tried with indirect lighting setting to see if I get same result as wagner.sz and.....
i had no crash but a whole lotta red.
Ben, I hope this may throw some light on the prob..ahem
Hey everyone. Sorry for the delay. I was away due to travel.
Just want you to know that I've submitted this issue (the red tint) to the devs. They're taking a look at it now.
I can't you any kind of ETA for a fix unfortunately.
wagner.sz wrote:
Yes, iam using Quicksilver as the renderer.
After press Render button, the progress remains at 0% forever until I click on the screen and force the program to close.
I am animating some objects using slice modifier to "show" the objects.
My pc: i7 3770 3,5ghz, 16gb ram, nvidia gtx 650 ti.
Hmmm...never seen that one before. Could be your Hardware Shader Cache contains a corrupted file.
A few questions first:
-What version of Max are you using?
-Does this happen with any scene?
-Was Quicksilver working before and this issue was a recent development?
At the moment I would try a reset of Max. Perform the following:
-Ensure that 3ds Max is not running.
-For Windows 7/8 navigate to the following path (These paths include hidden folders, so be sure to enable the ability to see hidden folders in Windows).
-C:\Users\%username%\AppData\Local\Autodesk\3dsMax(or 3dsMaxDesign)\201X – 64(or 32)bit\enu
-rename the “enu” folder to “enu.old”
-When 3ds Max is restarted a new “enu” folder with its associated contents will be created.
Keep in mind that this will return Max to its "just installed" freshness so you'll lose any customization that you may have done. If this doesn't get Quicksilver working you can undo this procedure by deleting the new ENU folder and renaming the old one back to what it was.
Just wanted to give an update. Setting the Viewport driver to "Nitrous Direct3D 9" gives correct results. At least with the testing I've done so far. The two other Nitrous options gives the wierdness.
Also the legacy drivers (Direct 3D/Open GL) freeze Max on my main system (Quadro 4000). I'm in the middle of testing on my 3 other systems.
wagner.sz, this may be the freezing that you're getting. Try what I mentioned above.
@Anonymous wrote:
post SP2 install, and I still have these red shadows.
For sure you'll still have them at this point. The defect I logged was submitted too late for a possible fix to be included in SP2.
The current workaround is to set your Viewport Driver to "Nitrous Direct3D 9"
-Customize > Preferences.... > Viewports > Display Drivers > Choose Driver...
So far that worked for all test systems I tried, and the same for one of my colleagues. Tell me if this doesn't work for you.
Jamma247 wrote:
This problem still exists, does it mean it will never be fixed for 2014 version? (if i stop paying subscription, will I be left with this feature broken)
Will it be fixed in 2015 version?
I took a look and it's still open. Without talking to the devs I can't give you a specific reason as to what the status is. Based on expereince I can guess that since it's not a showstopper kind of defect, it may have been superceeded by those defects that have been deemed more important. It's disapointing I know but that's the nature of the beast.
I'll try to get some info and will keep you updated.
