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

Pages: 1 ... 33 34 [35] 36 37
511
Question for the guys with a mixed OS setup.
When using the UHD Cache “load from file” in a animation render, where do you save the cache file, so both systems have access to this file?
TR can’t find the UHD Cache in the “tex” folder or any other default project folder.
Tom G’s UHD Cache video on the help page, mentions to use “a networked drive” but doesn’t give any detail about how to setup a networked drive so the UHD cache lives in the exact same location on Mac and PC.
In the Render settings/ UHD Cache, the filename field does not take a URL.
On macs I can setup a WebDAV on all my Macs from my nextcloud server, and all my nodes have the exact same mount point. /Volumes/Frank/UHD_CACHE/Cache.hdc. (See screenshot)
That mount point would of course be different on a PC and TR wouldn’t be able to find the cache file.
Any advise on how to get this to work?




Hey JOJORENDER,

despite this post & topic being older... but I have the same problem with the UHD cache not being read by the client computer.

It is happening even on a simple network consisting only two Macs (wired by Thunderbolt).

All other assets are recognized like a charm, even the Laubwerk plants plugin. But the Corona UHD-cache constantly gets an error message: "UHD cache cannot be opened / read".
This results in visible differences of those frames rendered by the client computer - especially flickering GI splotches in corners (yes, flicker-feee is activeated).

Have you been successful by placing the UHD cache on a networked external drive?

Thanks in advance for any tip!


This thing drives me nuts. Need to render an animation and not being able to profit from team render.

As mentioned in https://forum.corona-renderer.com/index.php?topic=30816.0, for anyone wondering this as well, the UHD cached can be placed to a network drive which is mapped from both computers, and the secondary GI will be loaded correctly.

512
[C4D] Bug Reporting / Re: Team Render - cannot read UHD
« on: 2020-09-11, 12:14:09 »
Hello,

no worries, that's what I'm here for :).
As for having only one file on the client's side.. I don't know whether that will work and how the file path structure works with networked computers. You can try it and tell me how it went.

As you say it, I just copied it there. I tried desktops but on windows the path differs from usernames to usernames as the name of the user is in the file path, I'm not sure about Mac right now.

Once you are ready to try this solution, please, let me know. I hope it does work.
Jan

513
[C4D] Bug Reporting / Re: Team Render - cannot read UHD
« on: 2020-09-11, 11:43:27 »
Additionally, if you have a shared network drive, it becomes easier. I've just mapped a drive on both computers and created a folder (which therefore has common file path for both computers) - UHD cache file properly loaded and render was without an error.

514
[C4D] Bug Reporting / Re: Team Render - cannot read UHD
« on: 2020-09-11, 11:17:17 »
Hello Designerman77,

sorry for the inconvenience! I have managed to reproduce your issue while running Team Render and I can see how this is frustrating.
The issue in this seems to be in the way the UHD load file is stored, as the client computer is scanning itself for a path, which is relevant for the main computer.
Example: I saved my UHD cache file as C:\Users\me\Desktop\UHD and the client server is looking for the same path in that computer. There is no user called me and therefore it fails.

I will talk to the dev team if there is something that can be done with this issue. In the meantime, a temporary workaround that worked for me was to copy the UHD file to the client computer and have identical paths on both.
Example: I saved my UHD cache file as D:\UHD on both main and client computers (as both have a drive D:\). No error received afterwards.

Try the workaround if it works for you and let me know, please.

Thanks,
Jan

EDIT: This is relevant for Windows users, but I believe that the logic stands also for Mac

515
[C4D] Bug Reporting / Re: Tonemapping automaticly disables
« on: 2020-09-11, 09:55:52 »
Hello,

sorry that you are experiencing issues. I am not following the issue, could you please elaborate the steps on how to encounter this issue? My tone mapping does not seem to "constantly disable".

Attaching a video, please let me know more in order for us to help you.

Thanks,
Jan

516
Hello Chris,

sorry for the late-ish reply.
I am unable to reproduce this issue on my side. Would it be possible to send over a scene and textures, with steps to reproduce?
Also does this happen if you choose to store them with the scene? (in a tex folder next to the .c4d file)
As usual, versions of corona and c4d are always helpful to disclose.

Thanks,
Jan

EDIT:
I just somehow managed to encounter the issue, even with a bit different approach. Will investigate and then report to the devs. Thank you for reporting!

517
[C4D] General Discussion / Re: Corona 6 for C4D R23
« on: 2020-09-10, 09:21:50 »
Hello everyone,

as we have received information (and a build) of R23 very late, it takes some time to integrate. We are tirelessly working on delivering a daily build which supports R23, with a hotfix version of V6 a bit further down the line.

Thank you for patience,
Jan

518
Apparently, there is an issue with distance scale input for MoGraph objects. Thank you for letting us know!

Jan

519
Hello Mike,

there is something going on with the distance shaders as effectors, so thank you for pointing that out, we will try to investigate.
Anyway, I don't know what your aim was with this scene, but in my opinion, it would be better to assign the noise shader to the colors, rather than the distance scale (or the combination of these two). I will attach some snapshots of results with different settings.

Thanks,
Jan


520
[C4D] General Discussion / Re: Corona v6 New Features
« on: 2020-09-09, 09:06:30 »
corona is really developing fast lately...
i just wish it would be more stable, it crashes from time to time and that makes me hesitate to fully switch over...

Hey,
we are sorry to hear that you are having issues! Please, as burnin said, don't hesitate to create a ticket whenever some crash or freeze occurs. It is our number 1 priority to deliver a stable product.

Thanks,
Jan

521
[C4D] Daily Builds / Re: C4d Always frozing
« on: 2020-09-07, 11:30:20 »
Hello,

does this happen for every scene?
what version of C4D are you using?

Please, after you get a freeze, try to press LeftShift, RightShift, Delete simultaneously to force quit C4D and get a log file. That log will be located in %appdata%\Maxon\Maxon Cinema 4D R21_64C2B3BD(this changes based on the C4D version)\_bugreports
Please, attach it here.

Thank you,
Jan

522
Hello,

thank you for reporting! I have created a task (internal id=560936787) for the developers to look into.

Have a nice day,
Jan

523
[C4D] Bug Reporting / Re: Multi Instance
« on: 2020-09-04, 15:38:50 »
Hello,

we are aware that this is a highly requested feature, however, due to its difficulty, it's taking a lot of time to properly implement. It is something that we are definitely looking into and want to implement in the future, but do not have an ETA just yet.

Thank you for understanding,
Jan

524
I have a minor issue with the Corona VFB...Mainly it won't go away, meaning I cannot close it. I can only minimize (or maximize). Also the image will not fill the VFB (see image below). I can zoom in and out as before but the window pane stays the same size.

Same here. I cannot resize the VFB or the Error Reporting windows. The content will not resize to match the window. I have attached examples below.
Thank you!

Same issue. I can not operate Corona V6 with the released build. Using Cinema 4D R18.

Hello,
can you please share your MacOS version? We are unable to reproduce it at our local machine and would really appreciate any bit of information about this issue.

Thanks,
Jan

525
Hello fabrica,

I do not seem to encounter this issue, do you mind sending your scene over?
Please, try the following:
1. Locate your material in node material editor
2. Click on the material
3. Double click on the material preview picture (above "Basic Properties")
Please, let me know if this fixed your issue with a black preview.

Thanks,
Jan

Pages: 1 ... 33 34 [35] 36 37