kbar

Hi everyone, I am working on a fluid simulation system called Jet Fluids. It is based on the open source Jet Framework by Doyub Kim. This is a very early Alpha plugin and I work on it every now and then to add new features and workflows. But it will keep changing and being updated. It is available for R20, R21, S22, R23 and S24 for both OSX and Windows. If you use it and create anything cool, or find any bugs then just post it up here and let me know. You can also visit: https://www.plugins4d.com/jet-fluids for more information.

I had to go through the signup process again to find it. Here is the link for those interested. https://www.c4dcafe.com/ipb/terms/

How can we read it again? I can't find any link to it anywhere on the website.

Recently when logging in I was presented with a Terms and Conditions agreement that I had to accept. Could you please add this to the bottom of the website. It should be accessible at all times. Also you should probably add a Privacy Policy as well. Thanks, Kent

I think 3D-Kiwi lives quite a few hours away so I wouldn't expect him to make the trip for the first meet. Maybe next year if we have a few people and I can run some presentations. I am mainly curious to see if I can build a little community for people near Wellington. But I think the number of C4D users in NZ is very small. They all use Maya around here (WetaFX).

Hi all, I have started a meetup here in Wellington New Zealand to see if there are any other C4D users near me that want to get together. You can find the meetup at: So if there is anyone here from the Cafe that wants to catchup then please join the group and I hope to see you there! The venue is yet to be decided, but it will be in the Wellington CBD. Cheers, Kent

The C4D SDK is very stable and efficient. And it has its own forum with dedicated sdk support team to help you with any questions you have.

There was actually a very huge update in R19 in regards to BodyPaint. The 3D painting is now done entirely in OpenGL. In R18 and below it was all done in a software renderer and only switched back to OpenGL if you rotated the model. Also curious as to what you would do if the SDK did have access to the nodal material system? Since for all 3rd Party render engines they would just bake these all to textures anyway. For a fully procedural node based workflow in a 3rd party engine it would be preferable to use their own node based materials. Unless you are talking about UI tools? IE allowing 3rd Party devs an easier way to make the UI for their node system? This part would be beneficial.

This is from there V100 Volta range. They are aimed at high performance computing, in particular machine learning and AI. https://www.nvidia.com/en-us/data-center/tesla-v100/ Not required for C4D users at all.

For those people reading this thread the problem is actually Adobe Acrobat Reader DC. For some reason Adobe Acrobat Reader DC is only rendering scenes in Software rendering mode on a PC. Which makes them slow, have less rendering features, and can also be unresponsive. The exact same PDF file when viewed in Adobe Acrobat Pro DC on the other hand renders perfectly with Direct X 9 hardware acceleration. This is of course really annoying. I will be logging bugs with Adobe to see what is going on. Lastly the scenes Burnsilver created look incredible in Adobe Acrobat Pro DC.

Hi Burnsilver, I believe I just emailed you directly via the 4D Publish support page. But I will ask here again as well. Could you please let me know what version of Adobe Acrobat Reader your clients are using? There is no malicious code included in any published PDF documents using 4D Publish. The document does include 3D content as well as javascript. If this is an older version of Adobe Acrobat Reader, and not the latest Adobe Acrobat Reader DC (https://get.adobe.com/uk/reader/) then it may give different warnings. I just found another thread from you on the Adobe forums as well. Is this you? I will contact you again via the support email regarding this issue. Best Regards. Kent

I am experiencing this issue today. It happens on the main forums page. Definitely something dodgy going on there. I am running Chrome. I am seeing 99% CPU usage.

The best way is to just start messing with examples in the C++ SDK. I made a couple of tutorials last year that will help you get started with the python and C++ examples.

I have created a new topic in the Sculpting and Texturing club where I will post all the new videos for this tutorial series.

No problem at all. I just think Katana is a really interesting workflow and thought others might like to know what it is.

I made the video since people may not know what Katana is or how its actually used. And I do not expect anyone here will actually have a copy of Katana, or even want to have a copy at all. Mostly this is used in large studio pipelines, although some smaller studios are also now using it. The videos are just to show what it is and how it can be used. This post has absolutely nothing to do with the film project post. But to answer your questions, the idea for the film project is that it can look different for different shots. I don't actually expect anyone to have Katana, or even want to use it. But I personally am interested in creating a scene with it, so that is my direction of interest. Different shots can use different renderers and different workflows to help cater to those c4d users who have Octane, while others might have Arnold or Redshift or even use the Standard and Physical renderers. We could even make the movie a montage of different pieces. I think you are jumping the gun a bit since at the moment I am just looking to see who is interested. We are a long way off actually getting started. But for now there are some people interested in the idea, and thats good enough for me personally to start thinking and planning. No one else needs to do anything at all at this stage.

I am going to be creating a bunch of tutorials to explain how Katana can be used for Look Dev. I will be using Cinema 4D to create all the 3d content in the tutorials and I will be using Pixar's Renderman for the renders (non-commercial version). This first video is a basic introduction to Katana that uses C4D to create an Alembic file. Then all materials, lights and cameras are applied in Katana. It is then rendered using Pixar's Renderman. In future videos I will go over texturing and how to do look dev for large scale scenes. If you have any questions then just ask. If you would like any specific tutorial videos then also just let me know.

To give people an idea of the timeline involved in such a project I had a look around for an existing article that tries to describe it. Interestingly this was one of the first ones I found and captures the process really nicely. Even though the movie that we intend to make may not contain live action or real life location shoots, the same process still needs to be considered in the overall production pipeline. http://www.andrew-whitehurst.net/pipeline.html

By 'showcase C4D' I am mean the later. To have a high-production quality movie where C4D is the primary tool for its creation. Its not about features in C4D. Its about using C4D to create as much of the content, animation and vfx as possible. The story comes first. This is also about the idea of making a movie. Which comes with a lot of different challenges. We can start with shorts, and need to in-fact to sort out the pipeline. But a short could be a single shot from a particular scene in the overall story. When creating a movie, C4D is a tool. It's like a toaster. It's our toaster, it's the toaster we like to use and it makes really good toast. I keep hearing people say that Maya makes better movie toast, and thats wrong, they both just toast bread so it's brown. And we still need the bread, toppings, knives and people to put it all together. What I am saying is that C4D is part of the solution, and we use it everywhere we can, but its not all going to be done in C4D. For instance someone might like to use Katana for a shot and render it using PRMan. All you need from C4D in that case is Alembic files of the assets. All of which can be created in C4D. This is going to be a slow process. It will take a long time. I will start gathering up more information in the coming months and flesh out the website with more information and content. Nothing will 'start' until early next year. But its good to get this idea out so we can start thinking about it.

Really great to see people are interested in the idea. At the moment there is no story. I am just gauging the interest level here on the cafe to see if people might be interested in such an idea. This will take a long time, as mentioned on the website it could take a couple of years. During that time I expect people to drop out of the project. In fact I expect people may pop in for a day/week and then leave. That is also fine. For now there is enough interest that I will go ahead and put together a website to help deal with the project. Since it's the project management and organisation part that I am most interested in creating. A place that allows for indie film makers to connect and collaborate on projects together. Trello will not work for this project since it is going to get very large and complicated, Trello is fine for smaller projects, but I have found for anything bigger it gets very messy. I will start planning things out and will look to have more information about how this would work next year. To begin with I will create a place that lets people say who they are, what interests they have in the project (writer, director, editor, 3d modeler, sound designer, look dev, animator etc...), what software they have or know (C4D, Katana, Renderman, Octane, X-Particles). We then need to define a story, design the visual look, break the story down into shots, define sets/props/characters etc... and only then can we start to actually do any work in C4D itself. Each scene could potentially use a different renderer, to utilise the existing hardware/software we each have. So teams working on a group of shots for a scene could have their own look. Or we may settle of a standard renderer such as Renderman, since the non-commercial version could be used for this project. I could also ask Pixar for some licences for this project. We need previz assets and final assets. So even if someone is only learning modelling, we can still use their creations for previz and look-dev, swapping out assets later on for the final high quality versions. So everyone is welcome to contribute. I personally am also interested in lookdev and would like to see how many people have, and know how to use, Katana. Particularly with a Renderman pipeline. We could then look at handling a few very large scale scenes. The Foundry may also be able to offer us a couple of licences when we get to the point that we need it. I can also handle setting up renderfarms on AWS and write custom software, tools, applications and setup a good pipeline. Thank you to everyone for your interest. More information will come next year. But if people have ideas for scripts then feel free to post here, or start a topic in the new Film Makers Club.

Would everyone at the Cafe be interested in collaborating to create a movie using primarily just C4D? To start with I have created a website called http://www.indie4d.com to explain the idea. I would like to have a nice showcase for what C4D can do, similar to how the Blender crowd have created their tech demo movies. For myself, I would like to create the website that helps everyone collaborate and streamline the process for creating a film. It would allow people to connect, upload ideas for scripts, models, sound, character design etc... create lists of tasks and jobs for all the shot breakdowns, let people put their names to a job, basically keep track of everything including all the assets used for the creation of the movie. I also have a plugin that will allow everyone involved to be connected directly in C4D (like Skype), allowing you to directly communicate as well as drag and drop anything in c4d to your fellow movie maker friend (images, models, presets, stamps, objects from the OM...). This would also be hooked into the website to allow everyone to download content from the website directly into their scenes (model, textures, full scenes, music, light setups, layouts, presets etc...) If people would be interested in this idea then just let me know and I can start building the full website. This may work in well with the new Filmmakers club. Were everyone can discuss techniques about how to make films, and apply those skills to an actual film in the process.

Yeah, a stand up desk. Much better for the back and posture.

I think its a fun way to experiment and play with ideas. It will also give people, who previously have never created anything in 3D before, an easy entry point into being able to create their own models. Once they reach their limits in VR they will then move to a DCC app, so its a good stepping stone. There are things you can do in VR that are a lot more intuitive and very easy to do. Grab a model scale it, move it, rotate, duplicate, all with a single hand movement. Draw geometry just by clicking a controller and dragging out the polygons. Walk into your model and draw things exactly where they should be without having to zoom cameras around. Use pre-built geometry to quickly build up a scene. Its a great workflow for concept sketching. Including working collaboratively with people all around the world. Its a different form of creation. It will not replace sitting with a mouse or tablet (or standing as I do), the same way we will never be doing Minority Report style video editing on a giant screen in front of us waving our arms around for 8 hours at our day job. But it is fun, easy and very captivating when you are in VR. I am working in this area myself at the moment, and its a lot of fun.

I believe Craig has been busy recently with other projects. Also I advised him to wait until 1.6 was released, which was today. This allows him to talk about any of the new features as well as the current ones.

You might want to ask over on the official MAXON SDK Support site: http://www.plugincafe.com/forum Or post up your code so we can see what your doing and what might be wrong.