Leaderboard

Yup, I felt the same way too. Then business dropped off and I realized how expensive it really was.

Feeling charitable. UnMute Layers: import c4d from c4d import gui def walkLayers(): treeWalker = doc.GetLayerObjectRoot().GetDown() while treeWalker != None : yield treeWalker if treeWalker.GetDown() != None : treeWalker = treeWalker.GetDown() elif treeWalker.GetNext() != None : treeWalker = treeWalker.GetNext() else : while treeWalker.GetUp() != None : if treeWalker.GetUp().GetNext() != None : treeWalker = treeWalker.GetUp().GetNext() break treeWalker = treeWalker.GetUp() else : treeWalker = None def UnMuteLayers(): for currentLayer in walkLayers(): if currentLayer.GetBit(c4d.BIT_ACTIVE) : currentLayer[c4d.ID_LAYER_VIEW] = True currentLayer[c4d.ID_LAYER_RENDER] = True currentLayer[c4d.ID_LAYER_MANAGER] = True currentLayer[c4d.ID_LAYER_ANIMATION] = True currentLayer[c4d.ID_LAYER_GENERATORS] = True currentLayer[c4d.ID_LAYER_DEFORMERS] = True currentLayer[c4d.ID_LAYER_EXPRESSIONS] = True currentLayer[c4d.ID_LAYER_LOCKED] = False currentLayer[c4d.ID_LAYER_XREF] = True if __name__=='__main__': UnMuteLayers() c4d.EventAdd() Mute Layers: import c4d from c4d import gui def walkLayers(): treeWalker = doc.GetLayerObjectRoot().GetDown() while treeWalker != None : yield treeWalker if treeWalker.GetDown() != None : treeWalker = treeWalker.GetDown() elif treeWalker.GetNext() != None : treeWalker = treeWalker.GetNext() else : while treeWalker.GetUp() != None : if treeWalker.GetUp().GetNext() != None : treeWalker = treeWalker.GetUp().GetNext() break treeWalker = treeWalker.GetUp() else : treeWalker = None def MuteLayers(): for currentLayer in walkLayers(): if currentLayer.GetBit(c4d.BIT_ACTIVE) : currentLayer[c4d.ID_LAYER_VIEW] = False currentLayer[c4d.ID_LAYER_RENDER] = False currentLayer[c4d.ID_LAYER_MANAGER] = False currentLayer[c4d.ID_LAYER_ANIMATION] = False currentLayer[c4d.ID_LAYER_GENERATORS] = False currentLayer[c4d.ID_LAYER_DEFORMERS] = False currentLayer[c4d.ID_LAYER_EXPRESSIONS] = False currentLayer[c4d.ID_LAYER_LOCKED] = True currentLayer[c4d.ID_LAYER_XREF] = False if __name__=='__main__': MuteLayers() c4d.EventAdd() Both scripts work on all selected layers at once, including sublayers. ---------- Learn more about Python for C4D scripting: https://www.patreon.com/cairyn (I do have the feeling I should rather link my Amazon wishlist as no new subscribers ever come from these posts. Duh.)

One thing people need to keep in mind, is that different parts of the world have taken different paths. It may very well be that you're in industry X, and all your friends use the same software in industry X, but jump over to europe, Japan, China, south america and you may suddenly find you're a fish out of water and very few people use the same software you do.

The majority of my work is through C4D, I'm the only one in our very small business using it, It is too expensive for me. I feel I'm stuck with it as I have many C4D project file over the last 10 years that I repeatedly go back to to update or use parts of in newer projects. Plus I don't fancy learning Blender again.

Oh good you've done it and saved me making a video 🙂 Not sure what you're using for that texture, but do you mean to have the little unaliased pixelated edges to the dots ? You can do this procedurally and resolutionless vector-style if you use the tile shader in circles 3 mode instead ! That's what I did, and look how smooth mine are ! CBR

XD noted, I've put a disclaimer in the original post 😛

Ah I TOTALLY get it! Thank you so much for your in-depth answer. As always, I appreciate you taking the time and helping me! My little guy isn't perfect, but I'm a heck of a lot closer thanks to your help! I'll keep practicing! Or "practising" in your case 😉

I'm not bothered with the price because 3d work is my source income. My only frustration with this pricing model is that I can not use Cinema on a other computer while rendering.

If you just want to see where they are couldn't you just enable any mode that shows you the lines ?! Or disable transparency in the view filter so you get the legacy version of it, which is sh1tter to look at, but might be more visible at lower transparencies ? CBR

For a general guide on pcs, my advice would be, with a range of budgets: AMD Ryzen CPU, 3800X, 3900x or 3950x GPU would be best with nvidia, 2070 or higher RAM 16gb absolute minimum, 32gb low-mid end, 64gb plenty for most people, 128gb if you do a lot of heavy after effects pcie gen 3 or 4 M.2 SSD, 2gb or higher, sabrent do a nice range

There are a couple of things to note before deciding whether to build Redshift materials in the 'old' Xpresso based 'shader graph' - or as new 'Node materials'. Redshift have said they will continue to support the shadergraph system for the foreseeable future. 1. Old style 'C4D shaders' are not available in the new window. That's a C4D limitation, not an RS one. I have some specialist plugins with associated C4D shaders - so I need to incorporate them into my RS materials via the older Shadergraph system. 2. Watch out for shaderball rendering in the new Nodes interface. All those previews need to be rendered - so I'd collapse them if you have complex materials. Redshift can create materials in both systems - via the old shadergraph, or as new node materials. The materials can be mixed and matched in scenes, but the materials themselves are not interchangeable.

Redshift does support the new node materials. 3rd partys do not yet since this API is not yet available, but we are working on that of course.

I use the Node Material Editor for Redshift, not the XPresso interface. Thus far no issues and it's WAY less finnicky. I don't remember where I saw that, but I think I read something along the lines of some nodes not being in the Node Editor. This might be patched at this point or I simply misremember.

Do not post duplicate threads please. I have removed your other one. No it has just moved, next to SDS under the (Green) generators menu, which makes sense, given that it is not a simulation in and of itself. CBR