CINEMA 4D R10.1 - free update for all R10 owners


#192

Is this described anywhere, or are you making news here?

This sounds good. As an architectural user, I’m interested. I really hope you are putting in a translator from DXF/DWG to turn symbol/blocks into their counterpart in Cinema–Insance object. And yes, I’ve talked to Maxon about this, many times. It should be on your user wishlist, at least in English.

Anyway, despite any concern over whining about no fix-list, I think everyone who posted was happy for the update. Somehow that got overlooked.


#193

I fear you will have to wait for the announcement. It’s not my job to pre-announce stuff and also i don’t know what exactly will be part of that offer since i’m not into sales or product management.
I only provided the info to give a context to the already available help information on this tool.
Cheers
Björn


#194

You little teaser…

On another note… The viewport speed/laggin issue is gone with 10.1. But I just witnessed after working for 10 minutes with 10.1 that again, it grabbed a cpu and locked it to 100% with ‘some’ task. Al is running fine. Just one CPU is gone on vacation to the loooi loop islands. C4D is the only app doing this and I have pretty much everything on the box from Adobe to ZBrush… Any idea how to find out what this dreaded CPU is doing??? Of course… rendering is loosing one of it’s render buddies.
Cheers
Rainer


#195

If anyone else is having trouble with the downloads I think the link for the downloads is just busy.

I always use Downshift for these big downloads - it keeps at it until you get the file - saves a lot of hassle.
http://www.rosecitysoftware.com/Downshift/

re. 10.1 generally, early days but it seems to have fixed my constant crashing when editing materials on cad models imported from Allplan. Phew :thumbsup:


#196

The updated IRR is a big improvement. It doesn’t clear your last render when you make a change. Much more useful now.

However, I can’t get it to work with the inbuilt DOF post effect. I can’t even really figure out what it’s doing, but it seems to render the whole region, then clear the image around the DOF target.


#197

has the selection mirror functionality been changed in R10.1? cause now when i hide some polygons on one side of the object, they still remain visible on the mirrored side. is there a way to turn it off?


#198

I also want to add my “polite request” for a fix-list for future updates.

While sure I can try each and every thing to find out if it works now, it makes way more sense for ONE person in the know to sit down and do that list than each and every user finding out on his/her own.
Other companies are able to do it, so maxon should be no different. The request is very reasonable, equal how many maxon employees tell us something different. :wink:

I find myself having workarounds built very deep into my working habits so I don’t even remember how it was supposed to work originally :wink: It helps a LOT to read such a list in my experience with other software!

Well, my main problem with C4D - the net renderer not supporting .rpf files - is still there in 10.1 - and support told me “it isn’t a bug”… :rolleyes: :shrug: :banghead:

Cheers and thanks for the update anyway! :thumbsup:

Over and out :bowdown:


#199

Hi dude, so you went back to c4d :thumbsup: In what way can´t you get them to work?
Just tried both reading and saving to .rpf trough NET render with no problem:shrug:


#200

Hi AAAron :wink:

Well, seems to be my software-roundtrip year… :hmm:
“Still haven’t found what I’m looking for”…
Maybe if C4D 11 will have shader-nodes… or Blender 2.5 got it’s UI overhaul… or Lightwave 12 shows up with an integrated modeler with history or… :wink:

Back on topic:
Yes, you can render .rpf files with the net renderer - but they contain no depth channel. :sad:

.rpf makes working so much cleaner for the current project, since you can have most needed channels in one file, get a non-antialiased continuous camera-setting-independent 16bit depth channel in a 8bit render and AfterEffects and some plugins we use can extract the depth directly…

Right now I am unable to use the net renderer at all because of this “non-bug”… Feels like the old version 4 or 5 days working with the batch feature again… :rolleyes:

The “reason” for this seems to be that the netrenderer renders to b3d files first which then get converted to the selected file format - and those don’t support a z buffer.
Well, I as a customer sure don’t give a damn about what clever reason exists for this weirdness, I just want to be able to render the same formats with net as with standalone… :shrug:

Isn’t 3D software fun?

Cheers!


#201

Aha nnoying:rolleyes: I feel your pain. It´s always something… So far I been stuck in a Sketch & Toon (which is great:thumbsup:) project so I haven´t used the regular renderer so much yet…


#202

Oh yes you’re right. I hope there is a way to turn this off (other than switching of the symmetry object).
Cheers
Boxy


#203

I won’t be downloading the update till I finish my current project, but am delighted to hear that the IRR now works as should…I will actually be able to use it without cursing :scream:

Looking forward to checking to see if any of my other pet hate bugs have been exterminated.

Btw , Skymatter are another company that lists it’s major bug fixes with each release. All people are really after are a list of the the major bug fixes/“feature enhancements” of each release. Not every single obscure fix that has ocurred.

Anyway , if that is Maxon’s policy then bitching about it aint gonna help change it . Thank goD for CGtalk, as this thread has a few enlightening posts :thumbsup:


#204

very very happy about focus on fixing stability for R10 imo was most unstable i’ve seen it in years so any more towards resolving this is big news for me…stability is top most in my mind. so thanks for this one maxon theres rarely any glamour in this sort of release but its big smile from this customer. jury is out on how stable its likely to be but given input it sounds very promising. c4d is very stable compared to other softwares anyways but was starting to look a little wobbly for a bit which was a bit of a surprise good to see this has been faced.
thanks again keep up the good work guys.:thumbsup:


#205

i totally recommend using PSD as the file format - it is internally lossless compressed and holds any and all channels you ever want including higher bit depths.

dann


#206

I run psd as default but rpf/rla are so much faster and easier to work with when you are doing depth stuff in AE. It is just a pity that it doesn’t make it with NET.

Cheers
Lennart


#207

The updated IRR is a big improvement. It doesn’t clear your last render when you make a change. Much more useful now.

I tested it on 2 PCs now and it DOES clear when i make a change. It would indeed be much more useful if it wouldn’t clear the last render, this would make a direct comparison possible. I also sent a request to Maxon for this a few months ago… but did they really address it?

Hmm, i also stated it on the german forum and it seems that for some people it gets cleared and for others not.

A statement from one of the Maxon-guys could maybe clarify if there has been a change…

Anyways, thanks for the update!!
cheers,
Günter


#208

It clears for me too, so still not really useful to me until it doesn’t :slight_smile: - on a PPC mac.
Cheers
Boxy


#209

It clears for me too, so still not really useful to me until it doesn’t - on a PPC mac.
Cheers
Boxy

Also for me on a PPC Mac!

Bye


#210

This sounds like the difference between radeon and geforce gfx cards. Its not a change as far as I know. Check the smart refresh option in the prefs. some cards will correctly keep the image and only overlay the changes, other cards dont support this and the refresh will flush the image. Try toggling this option on or off.


#211

Well on further inspection, it seems it DOES still clear the last render. My scene must have been rendering to quick to notice the blanking out.

Smart refresh doesn’t make a difference on my Geforce card.

It would be great if this could be fixed. I can’t imagine it would be that hard to implement.

And the DOF effect definately doesn’t work with IRR. As soon you activate “front blur” it clears the render after the camera target.