Jim Scott
1
COW Coin
Forum Replies Created
-
Glad I could help.
-
Make sure the “Edge Angle” is set to 0°. If the angle is set to 90° that will cause the behavior you describe. You may have inadvertently held the shift key after starting to drag, which allows that angle to be changed.
-
[dorota sloma] “What I don’t know is what is Redshift, when it’s needed and if I need it at the very start of learning?”
Redshift is a third-party GPU-accelerated renderer which was recently purchased by Maxon. It is one of many options available for 3D artists looking for faster rendering and more control over rendering. Since C4D has built-in rendering you do not need it, or any other third-party renderer, while you are learning C4D. Once you get proficient with C4D in general you can then decide if Redshift, another third-party renderer, or C4D’s built-in options best fit your needs and budget.
For a comparison of most of the renderers available, see the link below. Octane is another very popular renderer which isn’t included in the article.
https://www.toolfarm.com/tutorial/in_depth_3d_renderers/
-
[Brian Jones] “Can’t view it at the moment but I’m guessing inverse the box falloff to do it with one wind”
Well, that would work as well, but I just enlarged and positioned the box falloff so that it enclosed the emitter while the cube was to the side and then moved clear of the emitter as the cube moved.
-
Very clever Brian. That got me thinking about using a falloff on the original wind object and parenting it to the cube. Something like this:
-
By virtue of its symbology in the viewport, the Wind object tends to give the impression that it is “blowing” air from a certain position. But like other similar modifiers (“gravity” and “turbulence,” for example) it is simply applying a force to the particles in the scene regardless of where its icon happens to be located. Unless it has a falloff applied its position is completely irrelevant, which means that moving an object “between” it and the emitter isn’t really doing anything. Its force is being applied everywhere, and not from one position (the “fan,” so to speak) to another. If you want it to look like wind is being “blocked” by the cube simply keyframe the “Wind Speed” or the “Enabled” parameter to coincide with the movement of the cube.
-
In a quick test with a MoText object I was able to stop the leaking by slightly increasing the collider tag’s collision distance, as well as increasing the resolution of the fluid and mesher (and lowering its radius).
-
[Fabio Apelbaum] “I wonder if there is a different way to add thickness to a parametric object?”
https://www.youtube.com/watch?v=GwWhOpnUXw0&pbjreload=10
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
This may be a C4D version issue, and if so I’m afraid I won’t be able to offer any more help. In R19 and later (the only versions I have access to) C4D doesn’t append any numbers unless there is more than one image being rendered. It may be that R15 always adds the frame number. Perhaps someone else with earlier versions of C4D will chime in. Good luck.
-
Our messages crossed but I got the screenshot.
Click on the three dots at the end of the file window, select the desktop and then just give your file a simple name and see what happens.