Jops

I am not so into subscription, and planing to purchase one or two licenses of octane 2020 perpetual (the last perpetual of any GPU renderer that I can find) On paper it look great, Noise reduction, Aces and RTX3000 support. Even though I have worked with octane I have no deeper insight If this version is really worth it. Could someone help me out? - Is ist stable? - how far is it behind the newest version? - is any netrender ability included? How is the licensing? Do I need a new license for any node, or do they offer render nodes? I am planing to work with it in R20 thanks a lot Jops

[I] After This Video I feel so uplifted! I feel so connected to this Company. Stuff like this is what makes the customers happy. Everything is going to be fantastic.[/I]

Oh man, again? Sorry. Just flying over it, otherwise I would not have the time to post anything 🙂 It wasn't on purpose, sorry.

check if the instances that get created are set to renderinstances or regular ones. Renderinstances might not work.

R25 just is a mess. I don't want to reduce the work of the developers, as I think it is a result of a change in development principles. I am shure they are doing what they can. Today it is quite common to develop parallel not sequential anymore. R25 and the "secret" and retracted 25.016 feel more like a build of the current development instead of a finished product. I personally do not care how they develop, but I think the customer has a right to get a product that feels finished. I wanted to write, that R25 is not suitable as a perpetual version (who wants to pay >3000€ for this without the hope to ever get a finished product) but as I see it it doesn't matter if you are on subscription or on perpetual. People have to work with this software every day and for this price point they are entitled to get at least a cohesive software that is stable and complete. As a perpetual customer you are stuck with a expensive "beta" version of a software, but as a subscriber you also never get a finished product just a new "beta" version. Don't understand me wrong. C4D still is acceptable to work with (I had to work with S24 wich was much better than R23) but R25 with its unfinished and unnecessary UI overhaul new bugs and clumsy updates really feels like a unnecessary release to me. If they can not produce a finished product every half year, they should skip the S releases. No one is helped with new but over and over unfinished releases. People have to work with this software, it is not a computer game or something.

Tgis looks great, thanks a lot!

my information is, that if take the offer to "convert" the license then you loose your perpetual. If you just start a new subscription you keep it.

Thanks you so much for your thoughts on this. It's nice to get a detailed assessment from someone who has obviously put some thought into this, or had to 🙂 I really wish that the customer communication would be as open and clear as your statement. Blender clearly shows how far people are willing to carry a project if they feel they are being taken seriously. But equally they are adamant when they feel screwed. The discussions about Zbrush have surprised me. That so many people outside this forum have the same impression about the development of Maxon and communicate it so harshly shocked me. Even if I knew it in principle. Many of these harsh statements here and elsewhere are the expression of disappointment. And for many it is not about the speed of development (which, if properly communicated, is not a problem for a long time, see star citizen) but about the simultaneous hard, almost boldly displayed business decisions. I don't think this incredibly expensive loss in customer satisfaction would have been necessary. However, you didn't want to be drawn into the communication discussion. Nevertheless, thank you very much for this contribution! p.s. I also would prefer to live in a country that can count vaccinations 😄

There is no r22, only s22. That means 22 was a subscription release and therefor there unfortunately is no perpetual version of it that you could buy.

I made a bold statement in a thread here in the forum that people who have been using c4d for a long time tend to stick with R20 or R21. While agencies and users who are newer to C4D more likely use the newer versions. That is my personal experience. To check this thesis I make this survey. I want to make it clear that there is no right or wrong, and that I have absolutely nothing against „noobs“ or „old farts“ 🙂 It is a complex question to fit into the polling tool, but I hope it is ok as it is now.

Because mainly bigger agencies and Beginners are on subscription. The guys that are in business for a longer while stayed or switched back to R20 or R21. These are my personal findings anyway.

It will be of little use to users. C4D and Zbrush simply have too few connection points. Also, Maxon is primarily interested in growing, so it is not practical for them to integrate features from one program into the other. Sure a little bridge here a little bridge there, but no real integration. They haven't even integrated redshift yet. So it's about increasing the portfolio to become a big player. That means owning as many tools as possible and getting money from as many people as possible, even from the people who only use a small part of the tools.

ok, so no R25 for me then. Man they really lost their mojo. Its a bummer ... and sad.

did anything change regarding the icon situation? I didn't see anything while quickly flying over the release notes.

Oh wow, yes reading is not my strength 🙂

did you setup the scene with the same c4d version you are working with now? maybe something in the new.c4d scene is referenced, that is not part of c4d anymore. Just a guess though. good luck!

two observations in that regard. 1. for editor view the first lights (from top to bottom) get used for preview up to the number defined in the preferences. the rest gets ignored. 2. nodes get evaluated from top to bottom from left to right. But many of them have a priority setting. It is advisable to get used to define the priorities of tags, that are dependend of each other properly. ( I use steps of 10, so I have room to put something between later). More information can most probably be found in the Help. Sorry, right now I have no more time. best luck Jops

Everfresh's post is absolutely on point. Show, what you want to get jobs for. But also consider what kind of jobs are more common and which are absolutely niche. What can help is to give yourself imaginary Jobs. for example a technical animation for the function of coffee machines. or a super hip advert for a lifestyle product. Use imaginary products, so that you don't get problems, but make them feel real so that any viewer can belief it. Give yourself a time budget and define the wished outcome. just like with any regular job. And while you make it just think about the result and do not hesitate. Be harsh to yourself don't be happy with the result to easily. And take your time. A show reel from scratch takes month. The better it is the better jobs you will get. best luck Jops

I find that highly interesting. Not just how many different usecases there are for blender, but also what kind of different users and cases seem worthy for the blender foundation to get featured in such a video. This really gives the impression, that everyone in welcomed no matter where she/he is coming from Nation, profession and skill wise. I really like that. it is basically the opposite of the alienation we have seen in other areas of the industry. No wonder that a lot of customers who feel excluded look if they can find a new home with Blender.

I think I can remember, that it was removed. I am not shure when though. But It is not long ago. maybe R23?!

Wow. They really have a fair licensing. Incredible.

As I understand it they don't give away "predictable" deals anymore (as the summer deal in the past). and if they do most likely just temporary offers for subscription.

Thanks. We will see how it is received by the users. For me personally, this system tries way too much to anticipate what I want, and in my experience, that backfires more often than it helps. I would prefer a more conservative approach (the asset is stored in the scene) until I promote the asset to be a global one. In some companies I am working for the use of this asset browser would produce a meltdown.

Thank you. Is there a way to make assets lokal? Because It might not always be wanted, that a change of the asset changes it in all scenes it is used in. I understand the benefit and could imagine, that this is of use for a very limited amount of users, but it also has its downfalls and I could imagine that it is worse for most of the users. I Personally would prefer to have every asset lokal and only some selected globally connected. While it is quite common to instance certain types of nodes for example (it would be great in xpresso by the way) I know no program, that is doing it in a way to instance over different sceene files. This also explanes why it is not good usable for textures for example. How many alpha.png did you see in projects, and every time you change it, it would change this alpha.png in all your Projects. If it is like this it would be basically unusable for me. As I said. I understand that you have to invent new strategies for the new tech that you are doing (I also believe in capsules) but I really have my problems with complicated setups like this, that connect different jobs of different customers without my interaction. Maybe the new asset browser should have been a pure capsules library with the old asset browser besides it for all the rest. I don't think that people are aware of the complicated nature of it.

Thanks srek for explaining all this to us (even on a sunday evening). In principle I don't think it would be your job to do that, but since we otherwise get a bit little information about new features I am very grateful for it. Please forgive me if I use this opportunity not only to ask questions but also to give some feedback. So a c4d installation has one database and every c4d file has also one database. and you can transfer (or better copy) assets from one to another. Until now it was for example like this: Example1: I have a customer project that I want to pass on. for this there was save with assets and everything was copied to one folder. however it was still single files. I can understand that it might make sense to integrate all files into a C4D, but why do we have to go the detour via the asset manager. That is quite cumbersome and I have then gradually a mass of possibly unwanted data corpses of various customers in my database. If I used it I would then also like to integrate textures, because what exactly does the integration of a few parts of a scene help me, if I then still have to make a zip. Example2: I have a xpresso script (the closest thing we have to caps at the moment). The expresso was automatically included in the scene. So this is not an improvement basically. and if i wanted to reuse this xpresso i could save a c4d file and view it in the old asset browser. I don't see any advantage there with the new structure. That this database makes sense internally for your new system, I can imagine, but I find it all unnecessarily complicated from the user side. A simple button to integrate all assets into a C4D scene as an alternative to save with assets would have interested me. There are several places in new features from the last 3 to 4 years that are harder to use, or more complicated, or with more klicks then necessary (or like the features they replaced). It would be nice, during the revision of the program, if maxon first would try to recreate the existing functions at least on the same easy to use level, before they introduce new functions.