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 - jojorender

Pages: 1 2 [3] 4 5 ... 17
31
I wanted to prepare a scene for you to test - “Save Project with Assets” and lots of assets are now missing in the newly created project. My original file renders fine in TR and doesn’t show any issues with missing textures. The usual shared shader / Corona bitmap issue.
I wouldn’t normally use the C-bitmap but unfortunately many cosmos assets use this shader... knowing it has issues.
I think fixing the many C-bitmap problems is more important than this region render issue.
Thanks anyway!

32
Thanks for posting a pic of the Chaos Corona team at work.
So, it’s just 1 guy in that "team"? That explains a lot…

33
[C4D] Resolved Bugs / Re: Possible Bug
« on: 2023-05-08, 16:11:51 »
don't worry, we haven't forgotten about it ;)
Damn, that’s usually code for “we’ll never fix it”… :-(

34
It’s one known issue of many, but the c-bitmap shader still gets “forced” onto us with cosmos assets. The screenshot is just 1 example…
 
As BigAl said, perform a thorough exorcism or kill it before it kills us.

35
[C4D] Resolved Bugs / Re: Possible Bug
« on: 2023-05-08, 15:04:33 »
Thanks for the quick response.
If the c-bitmap shader finally gets the long awaited overhaul, please send devs a reminder for this issue - Internal ID=487235911

36
[C4D] Resolved Bugs / Re: Possible Bug
« on: 2023-05-08, 14:27:43 »
Why was this moved to “resolved bugs”? Doesn’t seem resolved…
I only found this when searching for “Save Project with Assets” because on 2 recent jobs, that I had to send to a farm, I ran into the same issue.
I render most of my projects in-house with TR on 3 nodes and know that all textures are linked correctly. When preparing a scene to send to a farm, shared shaders and Corona Bitmap shaders textures go missing.

How was this issue resolved?

37
So basically no easy switching… Thanks for letting me know.

I just ran into the region render noise limit bug again. TR stops early, single machine renders till 3%. See screenshots.
Will send a scene when I have a min.

38
Don't have time now to test this or prepare scene. Will do later.

- ONLY noise level set
- it stops while region is still very noisy - not reporting error.
- Did not test these scenes in V9, but I don't think V9 had this issue.

Current workaround, set high pass limit and let it run...

BTW, is it possible to have release version and daily both installed and easily switch between them without always complete reinstall?
If so, please let me know how this works. MacOs if that matters.

39
Version • 10 (Daily Build Jan 23 2023) / macOS 10.15.7 / R24

When render region is set, noise limit (5%) is ignored and render stops early around 20%
This happens when team rendering on 3 nodes. Noticed this on several different jobs.
It used to work as expected before.

40
I would say that’s a feature, not a bug. The B&G constantly recalculates, taking CPU resources from the actual rendering. That’s a real problem while rendering animations.
If the corona team considers a fix, please look into the possibility to trigger B&G after render and before saving.

41
[C4D] Daily Builds / Re: Cosmos asset features
« on: 2023-03-22, 15:13:51 »
Cool, thanks!

42
How is your Mac studio “attached”? While WIFI might work, make sure to use a wired lan setup.
Did you do what the error message asked? Look at the TR console on the Mac studio to get an idea what went wrong.
It might be a licensing issue on the Mac studio…

43
Any update to this?
How can you get a .cxr file from a renderfarm?

44
Yes, that works. Thank you!
Still think devs should look at it. Why these 3 decimals when scrubbing. 0.1 jump in scale / density happen in higher values too.   

45
Are you able to right-click instead of double clicking to input?
Left or right click, scrubber just jumps to cursor position.

Pages: 1 2 [3] 4 5 ... 17