Messages

16

[C4D] Daily Builds / Re: V12 RC1 - New VFB UI / UX

« on: 2024-06-23, 02:17:16 »

Smooth zooming and for me a fit to window button. The way it is now is a hassle.

I always have the VFB open for the settings and the C4D picture viewer for having a look at the image. Clumsy but the only way regretfully.
OSX

17

[C4D] Daily Builds / Re: Daily Build June 12 on Mac Studio

« on: 2024-06-20, 16:55:29 »

Indeed.  The zooming is impossible, way too fast. I am still hoping for a fit to window button. Would be so much easier than going to the C4D picture viewer.

18

[C4D] Daily Builds / Re: Daily Build June 12 on Mac Studio

« on: 2024-06-20, 12:12:52 »

Since 11 works fine there must be a problem with 12.

19

[C4D] Daily Builds / Re: C4D scenes dont open with new Daily Build from Corona 12 March 11.

« on: 2024-06-20, 12:12:05 »

There must be a difference between 11 and 12 that causes this huge problem.
Even very large files took just seconds to open. Which is important since I open many files every hour. Release of 12 without solving this problem is not an option.

20

[C4D] Daily Builds / Re: C4D scenes dont open with new Daily Build from Corona 12 March 11.

« on: 2024-06-19, 15:39:40 »

About the C4D asset browser, this is not the only cause. I had the problem with Maxtree assets that I opened just by clicking the file. That problem seems to be resolved even when I leave the File path prefs as they are.

I will start a new project soon and see how and if there are still problems opening files. Maybe it's an idea to set Coronarender not to look for maps and link the maps after the file is open through the asset inspector. I used to open very big files in seconds. One of the things I like about C4D is fast opening of the app and files.

21

[C4D] Daily Builds / Re: Daily Build June 12 on Mac Studio

« on: 2024-06-18, 11:35:23 »

Stefan-L is right. Playing a bit with the file assets paths in C4D prefs does make all the difference. Files open instantly if you delete all paths and set them again.

Other things not working yet for me:
-C4D crash at C4D quit after render.
-New VFB 2.0 zooms in and out centering the image to the upper left corner. A hassle to move the image back in view. I would love to see the Corona VFB has a fit to window option. As in the C4D picture viewer.

I hope the RC of version 12 is all about making Coronarender a breeze to use. Not having to point to texture maps, easy viewing of the image in progress, more straightforward camera/rendersettings. A little more AI in the UI might help too.

22

[C4D] Daily Builds / Re: Daily Build June 12 on Mac Studio

« on: 2024-06-18, 10:57:07 »

It's not the C4D asset browser. Even with a single 9Mb Maxtree resource with all maps in place in the same folder the problem persists.

23

[C4D] Daily Builds / Re: Daily Build June 12 on Mac Studio

« on: 2024-06-17, 10:25:13 »

Usually the daily builds were very reliable so it's a bit frustrating those days are over. But I do understand daily builds are meant for a few hobbyists who love to try stuff to see if it works.

I am sure the Corona team will solve this issue otherwise it's the end for Corona for Cinema4D. Wonder if this is just a OSX problem.

24

[C4D] Daily Builds / Re: Daily Build June 12 on Mac Studio

« on: 2024-06-16, 00:18:10 »

Just tried to import a Maxtree asset (legacy meterials) with the daily build 12, a 9 Mb file with a few rather small jpg maps as textures.
Took about half a minute to open. The C4D project asset inspector could find all the maps. No need to relink. The maps are within a subfolder in the same folder as the file itself.

Then installed CR 11. The same Maxtree asset opened instantly. Less than a second. But the C4D project asset inspector could not link the maps even as I pointed to the exact location. Although all corona materials looked fine including the maps. Rendered fine too.

With the daily build 12 I can no longer use my assets. Importing a bunch of plants will probably take hours and eventually might even crash my system.

The problem has most likely nothing to do with the C4D asset browser. It's probably just a problem with the path to the right location of the texture maps at opening a file. It seems to me very simple to solve.

The attachment is the instantly opened file with CR11 installed with the broken links (C4D project asset inspector) that are not actually broken.

I have decided to stop using daily builds. I am getting the feeling things are going backwards.

Mac Studio M1
OSX 14.5
C4D 2024.4.1

25

[C4D] Daily Builds / Re: Daily Build June 12 on Mac Studio

« on: 2024-06-14, 00:08:55 »

I am getting a bit worried the issue with older files or files with C4D assets gets solved or not.

26

[C4D] Bug Reporting / Re: crash after rendering a lot of passes

« on: 2024-06-13, 12:13:36 »

I haven't had this problem anymore. But I no longer work with the daily builds 12 since I can't open files with it.
I will let you know when it happens again. I do get a crash every time I quit C4D after rendering (CR11).

27

[C4D] Daily Builds / Daily Build June 12 on Mac Studio

« on: 2024-06-12, 19:08:12 »

I did a quick test with the latest build June 12:
• Files don't open made with 11 or so slow that I decided to force quit. This problem remains.
• New VFB 2.0  looks better but does not work ( well ) on a Mac Studio Ultra. Zooming in and out is a hassle to keep the image properly within the window. C4D picture viewer works well though.
• C4D crashes after quit. Not sure if this is related to CR. It also crashes after quit with 11.

Build 12 is not functional yet on a Mac Studio OSX Sonoma 14.5 and a fully updated C4D.
Downgraded back to release 11.

28

Gallery / sketch for a small apartment building

« on: 2024-05-18, 01:31:42 »

I got a basic 2D layout for an apartment building and a budget of a days work to design the exterior materials, build the 3D model and some terrain and provide for two renders.
I used Chaos Cosmos 3D humans and was surprised how good some of them are. Some are very bad though but some are really very good. Zoom in on the old man reading.

Something was a bit weird. Even though the CR-camera lens was not all that wide angle (50 to70mm) I thought the camera view seemed still very wide, much wider than I expected. Some setting must be wrong or I am just imagining this.

29

[C4D] Daily Builds / Re: C4D scenes dont open with new Daily Build from Corona 12 March 11.

« on: 2024-05-17, 10:55:50 »

Just tried the current daily build (15 05). Had to go back to 11 though.
I could not open the test file or the original on my Mac Studio harddrive with the current build 12. Regardless of missing textures, with CR11 the same files open instantly. The testfile is not an older file but a project I just started a week or so ago.

30

[C4D] Daily Builds / Re: C4D scenes dont open with new Daily Build from Corona 12 March 11.

« on: 2024-05-17, 01:18:58 »

Treid the 15 may build.
I could open my testfile with the 15 may build, the one I send to Benjamin, in about 7 seconds on my Macbook air m1. On my Mac Studio it opened instantly with CR 11. Will try at the office how the latest build does with my Mac Studio.

I did notice that the testfile I send to Benjamin (saved project with assets) had lots of mappings missing in the exported tex folder. See attachment. On my Macbook these materials render black. I only noticed because I open this test file on my home MacBook Air. At the office on my Mac Studio I did not notice jpeg maps where missing in the export file.

Somehow Coronarender materials with a certain bitmap path don't export at saving a project with assets. That might explain as well the long opening times.