1
[C4D] Bug Reporting / Re: Proxy renders differently
« on: 2021-02-04, 13:22:20 »
For completeness, I attached a stripped down example file for easy repro.
2022-06-25, 19:43:26
News:
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2
[C4D] Bug Reporting / Physical material wrong UI behavior
« on: 2021-01-08, 00:18:51 »
When setting the Metalness mode to metal and after that assigning a bitmap to that slot, SSS and Refraction are still greyed out. That is not correct.
3
[C4D] Bug Reporting / Re: team render resolution
« on: 2020-11-24, 10:22:07 »
By the way, the simplest workaround:
Set your desired physical size (e.g. 40x30cm)
Choose the desired DPI
Switch back to pixels.
Cinema automatically does the conversion for you.
Set your desired physical size (e.g. 40x30cm)
Choose the desired DPI
Switch back to pixels.
Cinema automatically does the conversion for you.
4
[C4D] Bug Reporting / Re: Team Render Object ID
« on: 2020-11-23, 15:18:14 »
Do you have a fixed amount of scene entities?
That excludes things like particle systems, Cloners with varying amounts, animated "Enabled" parameters and so on.
So basically all that would alter the scene's object-count.
That excludes things like particle systems, Cloners with varying amounts, animated "Enabled" parameters and so on.
So basically all that would alter the scene's object-count.
5
[C4D] General Discussion / Re: Team Render, “Error – Saving Image”
« on: 2020-11-23, 12:58:00 »
It might help to disable "Abort rendering on Client error" and "Exclude client on loading error" in TR prefs to prevent this behavior. This also helps if plugins are missing that are referenced in the scene ffle.
6
[C4D] Feature Requests / Re: Vector Displacement
« on: 2020-11-22, 17:03:12 »
Here's your yearly reminder again. ;)
7
[C4D] Bug Reporting / Re: team render resolution
« on: 2020-11-22, 16:58:00 »
@TomG:
It depends. When you assign a physical rendersize + DPI within Cinema 4D, the resulting render resolution is indeed DPI-dependent.
If TR assumes default 72dpi when a physical measurement is set, the render resolution becomes wrong.
However, this needs further information.
Like:
Is he using physical measurement in output?
Does this also apply to Standard-Renderer?
Does this only occur with TR?
But honestly, this smells more like a C4D-bug.
It depends. When you assign a physical rendersize + DPI within Cinema 4D, the resulting render resolution is indeed DPI-dependent.
If TR assumes default 72dpi when a physical measurement is set, the render resolution becomes wrong.
However, this needs further information.
Like:
Is he using physical measurement in output?
Does this also apply to Standard-Renderer?
Does this only occur with TR?
But honestly, this smells more like a C4D-bug.
8
[C4D] Bug Reporting / Vertex Maps in Hair-Material are ignored
« on: 2020-11-22, 16:52:57 »
In the file attached, the HairMtl's Clump-Parameter is driven by a Vertex-map.
In AR/PR, hairs render fine.
Corona ignores the vertex map.
In AR/PR, hairs render fine.
Corona ignores the vertex map.
9
[C4D] General Discussion / Re: Cinema 4D Corona Scene Converter
« on: 2020-09-14, 12:16:55 »This plugin sounds amazing, but I can't get it to work in R23.
Is this correct, drag the content to ../plugins/ folder and start C4D?
Where should I se it?
There's no plugin for R20+ available yet.
10
[C4D] General Discussion / Re: Cinema 4D Corona Scene Converter
« on: 2020-09-01, 15:01:32 »Good to hear. The devs don't seem to think this is a useful tool. Will your tool hand materials with Reflectance correctly?
It's a bit complicated to calculate reflectance correctly because there's always differences in the rendering equations. So at least, there's an approximation.
There's definitely going some research into that, I assume a sample-based lookup table might give nice results. :)
Will see how it works out.
11
[C4D] General Discussion / Re: [DISCONTINUED] Cinema 4D Corona Scene Converter
« on: 2020-09-01, 09:25:58 »
Good news everyone. Recovered the source files and will start updating the tool again soon. :)
12
[C4D] Feature Requests / Re: Vector Displacement
« on: 2019-10-08, 11:31:35 »
Got lost again, huh? ;)
13
[C4D] Resolved Feature Requests / Re: Relative IES paths still broken when working on network shares.
« on: 2018-11-14, 20:51:20 »
Great! Thanks guys. Invaluable developers! :)
14
[C4D] Bug Reporting / Re: bugs with B2
« on: 2018-11-12, 14:51:38 »Regarding plugins: The sole purpose of bug reporting is to make sure that it works on an unaltered environment. Using plugins, you can never make sure what breaks what.
Still, we'd like to support reasonably-written plugins, so bug reports like this are still very useful to us!
Sure, I understand that - but shouldn't this then be in a completely new category? Like 3rd Party issues/bugs?
I can imagine that testing any sort of plugin with Corona may be a nightmare and probably has effect of finding bugs solely related to Corona ?
15
[C4D] Bug Reporting / Re: bugs with B2
« on: 2018-11-12, 12:15:41 »
Regarding plugins: The sole purpose of bug reporting is to make sure that it works on an unaltered environment. Using plugins, you can never make sure what breaks what.