Jump to content
Cinema 4D Plugins

blutz

Regular Member
  • Content count

    9
  • Joined

  • Last visited

  • Days Won

    2

blutz last won the day on July 18 2017

blutz had the most liked content!

Community Reputation

24 Noble Beginner

About blutz

  • Rank
    MAXON Computer GmbH
  • Birthday October 3

Profile Information

  • First Name
    Bernd
  • Last Name
    Lutz
  • C4D Ver
    19.024 Demo
  • Location
    Germany

Recent Profile Visitors

447 profile views
  1. C4D forward backward compatibility

    We try to be as forward/backward compatible as possible with our file format. Normally, you can open CINEMA 4D files in newer and older versions. New functionality will be ignored, when you open a file in an older version. This could change the look and behavior of your scene and is not recommended. But even then, CINEMA 4D will try to keep the unknown data for new functionality, even when you are editing the scene. There is a chance, that you can open a actual scene in a older version, edit it and open it back again in the new version and everything works. There is also a huge chance that your edits changed the scene in a way, that information about new functions can't be preserved and you ruin your scene. R12 is a barrier, as we switched to double precision back then. Up to R19, there is a special importer for scenes older than R12. This importer will be removed with R20, so make sure to load old (<R12) scenes with R19 and save them again, as you won't be able to load them in R20.
  2. MAXON Labs is GO !!!!

    Yes, there is something on the horizon. But our highest priority will always be to finish CINEMA 4D features and to make them as easy to use and as stable as possible. This can always push the Lab projects a bit into the future.
  3. Cinema 4D R19 discussion!

    Free software doesn't integrate itself for free into a product. It doesn't automagically connect itself to the object system, animation system, material system, ... It also doesn't test itself or designs it own User Interfaces and workflows!
  4. Cinema 4D R19 discussion!

    We never (at least since I am working for MAXON) distinguished between a .5 and a full release during planning and development. Which is also the reason, why we ditched the .5 versions.
  5. Cinema 4D R19 discussion!

    You can be sure, that our programmers mainly focus on programming and not on UX Design, testing or Productmanagement. Which doesn't mean, that they don't support the Designers, Testers, ... Creating such a complex software as CINEMA 4D is a team effort. You don't have to wait until you win a job at MAXON, you just can apply for one: Assist me in Productmanagement: https://www.MAXON.net/en/header-meta-navigation/about-MAXON/jobs/description/junior-product-manager-mf/ Help Quality Assurance to make CINEMA 4D as stable as possible: https://www.MAXON.net/en/header-meta-navigation/about-MAXON/jobs/description/quality-assurance-engineer-mf/ Support us in making CINEMA 4D fun to use: https://www.MAXON.net/en/header-meta-navigation/about-MAXON/jobs/description/user-experience-designer-mf/ And much more: https://www.MAXON.net/en/header-meta-navigation/about-MAXON/jobs/
  6. Cinema 4D R19 discussion!

    CINEMA 4Ds SDK (Software Development Kit) is changing constantly. This has to be done to reflect new functionality and changes under the hood. While we try to keep the SDK as stable as possible, from time to time, we have to introduce bigger changes. Sometimes, even smaller things can cause bigger changes for the 3rd Party Developers. With R12 we switched from single to double precision. This isn't a huge change by itself, just adding some digits to make numerical calculations more precise. But this also meant, that no old Plugin would run anymore and each Developer had to adapt and recompile his plugins. So changes in the SDK are happening all the time, sometimes they are bigger or can have a bigger impact. We've announced some time ago, that we are working on new foundations for CINEMA 4Ds future. A project, which we have been working before this announcement and which we are constantly working on. As you can imagine, such internal changes will also influence plugin developers. In fact, they already did. The changes developers will have to face (our developers, as well as external developers) will have sometimes more impact, sometimes they won't have that much impact. Thus you can expect Releases with a huge impact for Developers and Releases, with just a minor impact. We will try to balance our development in such a way, that we don't hurt 3rd Party Developers too often and too much, but to proceed, we will need to put an end to old functionalities and introduce new functions and behaviors. So there is a high probability that future releases will have a bigger impact on our SDK, as more and more of the core functionality will get replaced in a way that we can't make a very smooth transition for developers. I won't give any information about R20 here, so please don't start asking. We will announce news, when it is time to announce them.

×