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.


Messages - John_Do

Pages: [1] 2 3
1
[C4D] Bug Reporting / Re: Object preview in asset browser
« on: 2023-02-04, 16:32:09 »
Hi,

The bug is still here in the latest daillybuild (Version • 10 (Daily Build Jan 23 2023)).



The model is the same in both objects. only the left one have Corona materials applied. So it seems indeed related to Corona. Can you fix it ?

2
Hi Beck,

I have this issue too, it is here since Corona 9. There is a workaround, you have to set the C4D Picture Viewer as the default Framebuffer in Corona settings, like this :




3
Hi, Speaking of speculation ;) ''There are a number of things C4D users have asked for again and again over the years that just got forgotten/ ignored.'' - This is not the case at all. There are limitations to how much of the API we can access. So if something hasn't been implemented after it has been requested, please consider something other than ''forgotten/ignored''. ;)

Come on Bengamin, you can't say that when some of the bugs are known for years and are still not fixed.

- Like the random bump behavior with Layered / Triplanar / Noise shaders
- or the motion blur issue with render instances
- or the anisotropy mapping
- or the many issues the Shared shader has
- or the way the Layered Material is handled in the Asset Browser ( introduced in S24, but I don't know if the API was available. Works flawlessly in Octane though )
- or the IPR less responsive than on 3dsMax ?

And the API ? Let's talk about the Corona UVW Randomizer which still doesn't support the Corona Bitmap ? And the Override UVW which does nothing ? Even the Corona shaders are not working properly.

I understand that development is hard and you can only do so much in the amount of time you have between two releases, we all understand that bugs are to be expected and it's part of software development, but come on, relying on workaround for years is really what is expected from your customers ? I think many of us would appreciate to have the basics work flawlessly before implementing fancy features like Chaos Scans.

4
[C4D] Bug Reporting / Re: More bump issues
« on: 2023-01-17, 15:59:23 »
Hi Bengamin, it was with the latest daily build.

5
[C4D] Bug Reporting / More bump issues
« on: 2023-01-11, 15:02:11 »
hi,

Few other issues I'm noticing with the bump channel in Corona Materials :

1. Colorizer doesn't work in bump channel, even if the source map is a Corona Bitmap. Worse than that, it disable the bump effect.
2. Corona Color Correct also doesn't affect the bump channel. The texture is affected in the Node Preview, but it doesn't reflect in the render.

Base image


with Colorizer shader


with Corona Color Correct ( I tested Contrast and Curves )




6
[C4D] General Discussion / Re: Refresh Button?
« on: 2022-12-17, 21:08:36 »
Also - what about the PICK button?

Pick allow you to select the object under the cursor or adjust the focus target. You have to enable Pick and right click to use it. Look for the context menu, it has a tendency to pop outside of the VFB window.



For refresh I don't know, never used it and from a quick test it doesn't seem to have any effect ?

7
Hi Tom, thanks for answering so quickly

duplicated nodes from Corona Shared shader - afaik this no longer happens. If there is a workflow that makes it happen still, does it have a ticket or a thread on the forum about it?

It is still here. For example import "Fabric Cotton" from the Corona Material Library and drop it into the Node Editor. Happens also randomly with my own materials, usually when copy pasting materials between scenes. Unfortunaterly it's hard to track.

Also the Corona Shared shader leads to another limitation I've discovered today which is happening when you transform a shared C4D Bitmap to a Corona Bitmap. The bitmap path is lost during the "conversion" and you have to relink the nodes. Example below.



Quote
Motion blur - what does Max do that C4D does not here? Remember that Max has limitations on what can be moblurred too. Just wanting to know the specifics of any particular complaint, thanks!

Motion blur doesn't work with Render Instances, it was reported again last week, it's on the Trello board for 3 years. It works with instances but it's not a real workaround since C4D "Instance" mode eats as much memory as if it was a regular object.

Quote
UVW Support, can you be specific again? Just wondering, since Max and C4D handle UVs very differently, and not sure if the problem you are running into is a Corona one, or a C4D one.

Corona Bitmap's Override UVW parameter is a nice addition to overcome the way UVs are handled in C4D ( poorly yes ) , unfortunately it doesn't work at all. In the same way, the UVW channel setting for Anisotropy Orientation doesn't work.
( Request #63528 )

Quote
As for paying the same price, well there are things done for C4D that are not done for Max, the Node Material Editor, support for totally different hardware in the form of Macs (with several different types of those now), and other things that C4D gets/needs that Max does not.

Fair enough, I hadn't thought about that and the Apple Silicon support is really nice since I guess it was not an easy thing to tackle.

8
It's way better with the Corona Bitmap shader ( default shader settings, haven't touched the bump strength )

Unfortunately not a solution in some cases like on a wooden floor where a Corona UVW Randomizer shader is used. I had forgotten that Corona Bitmap and UVW Randomizer don't work together. Time for a rant !

Could you guys please fix once and for all all these inconsistencies in the C4D plugin ? Triplanar and Layer in Bump channel, proper UVW support, proper render instances support, motion blur, duplicated nodes from Corona Shared shader and the list goes on.
Some are known for YEARS, and are sometimes even reported by several users on the forum in the span of a few years, and it doesn't get better with each new version, still we are asked to pay the same price as the Max guys. I would gladly trade new features for a bug-free Corona 10 ( heck, some are not even bug but rather non-working features / settings ).

9
I don't know if it is considered as a bug but this annoying behavior is still here yes.



Video

It's way better with the Corona Bitmap shader ( default shader settings, haven't touched the bump strength )


10
[C4D] Bug Reporting / Re: Motion Blur & Instances
« on: 2022-12-08, 09:15:33 »
Hey there, still (or again?) got this Motion Blur Bug. I guess it comes with Instances, but not sure about this. I could go through the hassle of testing it thoroughly, but this bug exists since the introduction of Motion Blur to Corona. So you propably know it very well. Just a little reminder.

Yep this bug is still here, it's on the roadmap for years.

You can switch the instancing mode from Render Instance to Instance if you have enough memory ( and patience to handle the added viewport lag ).


11
Hi Bengamin, that's the issue, I don't always use a Corona Camera Tag and in any case it should work without it. I want to handle the post processing at the scene level and parent the various format output to this setting. If Camera tag are used it's only for exposure adjustment.

12
Hi,

I think that with the new Tonemapping stack and the way it's implemented in the C4D Render Settings ( in Camera/Postprocessing tab ), the native C4D settings inheritance doesn't work anymore. I would like someone else to confirm but on my side it is the case, and it even seems logical since the Tonemapping settings are now contained in their own "space" and not visible in the tab itself.

If it is confirmed, is it fixable ? This feature is quite useful to manage engine settings and output size / format in a granular way, yet easy.

Thanks

13
[C4D] Bug Reporting / Re: v9 Stability
« on: 2022-11-22, 17:54:56 »
once again, as this seem all the same problem, to specify it more:

in my experience since weeks, it is in special when i copy a corona light (or cam, or instance , or other generator object) and then move it while ipr is on,
almost in 100% of the cases i get a crash due Corona render, and c4dfreezes (i need for force quit it).

it doesnt happen in small scenes, but in any realistic production normal arch scene we have here, on any PC, and seems quite reproducible.
alone today like 15 crashes so far

Thanks for the explanation, it's exactly what happens on my side too, so there must be some sort of regression in the Corona plugin. I'm keeping my fingers crossed for a hotfix.

14
[C4D] Bug Reporting / Re: v9 Stability
« on: 2022-11-22, 13:12:44 »
Hi there, can you share a short vid of this happening? I tried to recreate it here but failed. Thx :)

Are you able to test this with Corona 10 daily and let me know if the issue persists?
https://forum.corona-renderer.com/index.php?topic=38328.0

(Internal ID=1010200894)

Hey Bengamin, I've sent you a DM with some screen recording.

Indeed in a new scene, Corona doesn't freeze when I drag-copy objects and lights, no matter how hard I try it's rock solid. However it freezes in no time when I do the same on a real objects hierarchy with textured null, mesh and sds objects.

I don't know if it's specific to the meshes, the objects types, the materials, the textures used or a combination of all of these, but unfortunately I don't have the time to test all the scenarios nor the dailybuild. I'm rather thinking of going back to v8 where IR is less prone to crash while waiting for a fix.

"Had to quit and restart C4D at least ten times today"

if you mean IPR instability, here r25 and v9 win10,
 I and others also reported this already, i already did send also reports with crash dumnps etc (daily 10 didnt change any):

https://forum.corona-renderer.com/index.php?topic=38371.0


Yep IPR instability exactly. Did you notice any pattern in the way IR freezes / crash ? Does it happen in all your scenes ?

15
[C4D] Bug Reporting / v9 Stability
« on: 2022-11-21, 18:05:57 »
Hey guys,

Does anyone else have stability issues with Corona 9 on C4D R26.107 and Windows 10 ? Particularly when adjusting lights and playing with Decals ? Had to quit and restart C4D at least ten times today, it's really starting to get on my nerves.

EDIT : It happens often when I drag-copy an object ( with Move Tool + Ctrl pressed ), whether it's a light or a mesh item.

EDIT 2 : Toggling Replace base bump and Replace Base Displacement in a Corona Decal settings freezes C4D too.



Pages: [1] 2 3