Jump to content

EricNS

Limited Member
  • Posts

    34
  • Joined

  • Last visited

Profile Information

  • First Name
    Eric
  • Last Name
    Smit
  • Company
    Eric Nicolas Smit

HW | SW Information

  • OS
    Win10
  • CPU
    AMD Ryzen 5 5600X
  • GPU
    RTX 3060 Ti

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

EricNS's Achievements

  1. In the Bitmap Shader attributes, you can change the Color Profile (Embedded, Linear, sRGB or Custom) To access it, just click on the texture and go to the Shader Properties tab.
  2. EricNS

    Important Notice

    it seems fair. But to be really successful, you might want to consider exclusive contents like assets, scripts, plugins, deals, ...
  3. Hi Petematul, A very late answer. Cinema 4D doesn't read DNxHR and GoPro. You should render your Resolve project in TIFF or EXR image sequence. Make sure the "Export Alpha" is active.
  4. Follow up: Uninstalling and re-installing wasn't enough to fix the issue. I had to remove first all traces of S26 from the PC then re-install, as suggested by Sandro from MAXON.
  5. I know the drill 🙂 I'll have to contact MAXON anyway since re-installing and re-starting the PC, doesn't solve the issue. It's the first time in 22 years that Cinema 4D is totally blocked. I had all sort of issues with public releases, alpha and betas, but never a permanent freeze. It's quite scary...
  6. S26 now simply doesn't work. Everytime I start it, it's locked in a "Speedup Asset Search" process. I have to force quit from the Task Manager. I'll see if re-installing solve this issue...
  7. Thanks for investigating! So the iterations parameter from the Simulation Scene does the trick. At 3 it's already producing decent results. On a side note, I find the default value of the parameters quite strange. The Bendiness for example. At the default 0.1, the cloth surface behaves like rubber. With 2 or 3 it feels more like textile.
  8. I'm having issue with the cloth intercollision. A single cloth simulation generates accurate results, the cloth surface interacts correctly with the collider objects. If I use multiple cloth objects, the collision between the cloth objects is accurate, but the collision with the collider objects fails. It seems the first take priority. In the attached scene, there are 3 cloth objects - blue, red and green, and a few collider shapes - all using the default cloth and collider tag settings. If I run only the "Cloth 01" simulation in blue, it works as expected. If I run all the simulations together, "Cloth 01, 02 and 03", I get bad results. -See this capture: The blue cloth object penetrates inside the collider object (as indicated by the light gray boxes). I would expect some inaccuracy, caused by the low density of the geometries and/or insufficient thickness values, but not something as bad. I have to increase the cloth tag thickness value to 10 cm to improve the result and it's way too much. It creates a huge gap between all the objects. I have searched for an accuracy setting (something similar to the old Cloth "Sampling" and "EPS" settings), but I couldn't find one... Test the attached scene "Cloth-InterCollision-Test-02. c4d": Try the simulation only with Cloth 01, then with Cloth 01, 02, 03. Cloth-InterCollision-Test-02.c4d
  9. I found your description about the coding process and what it involves extremely interesting. Thanks. Keep writing interesting stuff 🙂
  10. I have to agree with you Dessta. There is still no sign of fundamental improvements, nothing that could be the starting point of a "new" revolutionnary Cinema 4D. Concerning RedShift CPU: there seems to be an issue with Memory management. On my PC (AMD Ryzen 5 5600X with 48GB of RAM, WIN10), rendering a simple primitive require already 15GB of ram. Give it a try: -Switch to the Redshift Renderer -Load a Sphere -Assign to it a default RS Material -Load a RedShift Sun and Sky Rig Render the scene in the Picture Viewer. ... and Cinema 4D will go from 2GB used RAM to 15GB, without reasons...
  11. Did you add a Hair Collider Tag on your Deer ? I don't see one...
  12. If Mash, as a beta tester, gives it a solid 9/10, I think we can expect something decent 😉 I've lost contact with the MAXON team since 2018. I have no inside information about the recent development but I like to speculate. It's fun. So here's my hypothetical list of "new" features and updates: 1. RENDERING : Something will happen in the rendering department. Cinema 4D's render engines are outdated. The Physical renderer was not seriously developed since 2014. The "external" alternatives proposed by MAXON since then were either mediocre (ProRender) or not fully integrated (RedShift). A new solution will appear. It will be an integrated version of Redshift or a brand new renderer. 2. PARTICLES : I expect a nodal particle engine to replace the old Thinking Particles. This year we celebrate it's 20iest anniversary ! I don't see how MAXON could rely on the expensive X-Particles for any longer. A powerful particle engine is an indispensable tool, it should be included in every modern 2D/3D CG software. 3. DYNAMICS : A new system will appear. It will replace the previous one based on Bullet engine. I don't expect a high end system like Houdini, but the foundation of a new powerful set of tools. It might use the same approach as Mograph, with effectors and fields. 4. SAMPLING / PHOTOGRAMETRY / MOTION CAPTURE: Assets creation is now all about sampling the world - capturing geometries, textures and motions. I predict that Cinema 4D S26 will include solutions for this. 5. VOXELS : Handling complex geometries (generated by photogrammetry, fluid simulations, particles, sculpting, volumes, etc...) requires a reliable grain/voxel system. I hope to see one in S26. I also wish for direct voxel rendering, without the need to generate polygonal data. 6. 3D PAINTING : Not sure about this one, but anyways... I hope MAXON will improve and simplify the texture painting tools. 7. PRIMITIVES : A lot could be done to improve the primitives generators - more shapes, more controllers, more HUD tools, recursive / fractal structures, etc... That's about it.
  13. It's no longer an issue. There are many way to circumvent memory limitations, as Mash mentioned. UNREAL 5, for example, can run massive scenes on basic GPU gaming cards. It uses "virtualized" geometry and textures: data is fragmented in clusters, then streamed on demand based on the camera view and the necessary level of details. It's what they call "Nanite". https://docs.unrealengine.com/5.0/en-US/RenderingFeatures/Nanite/ The sequences in this video, for example, were rendered in real time on a Playstation 5 with only 16GB :
  14. Thanks for taking the time to answer this question ! It's extremely reassuring since I have the same opinion about R21 to R25.
  15. Hi Mash, Out of curiosity, and to put things in perspectives, how would you rate R21, R23 and R25 ?

About Us

We are a community of passionate 3D artists, hobbyists and professionals. We welcome everyone, and encourage artists of any level willing to share, discuss, learn, and generally contribute positively to the community. If you are a Cinema 4D, Blender, Houdini or Unreal Engine 5 artist then our Core 4D community is the best place to hang out and meet like-minded people! :cowboypistol:

×
×
  • Create New...

Copyright Core 4D © 2022 Powered by Invision Community