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

Pages: 1 ... 119 120 [121] 122 123 ... 127
1801
Hi,

Apologies that it has taken quite a while to get back to you regarding this one.

I have done some tests without forestpack in the scene and it renders quicker on our dual xeon machine. Which leads me to believe that the issue lies within forestpack.

If it is still an issue I'd suggest contacting iToo to further assist you.

Thanks,

Rowan

1802
  • Environment direct visibility, reflections and refractions overrides were moved to the new advanced setup mode

But why??? Now, it's horribly inconvenient :[
Hi,

I'll relay the feedback to the dev team regarding this and see what can be done :)

Thanks,

Rowan

(Internal ID = 353183604)

1803
Hi,

I'm glad you managed to solve it! :)

Thanks,

Rowan

1804
Hi,

This looks very similar to: https://forum.corona-renderer.com/index.php?topic=23462.0

Can you try the steps that Maru recommended on that thread please?

Thanks,

Rowan

1805
hi, I cannot show the proxy object with full mesh method after updating the latest daily build.

Hi,

Full mesh mode is only supported when the keep in memory checkbox is ticked.

Thanks,

Rowan

1806
[Max] Bug Reporting / Re: Corona DR using all of disk space
« on: 2019-05-13, 18:19:15 »
Hi,

Can I ask for some more information please?

Can you provide me with the version of Windows and Corona that you are using, are you also using any 3rd party software to launch the DR nodes?

Thanks,

Rowan

1807
[Max] Daily Builds / Re: Caustics playground!
« on: 2019-05-10, 10:57:35 »
Build 2019-05-09 (sorry, it took us a bit longer than expected to test this build)
  • Fixes and improvements of the fast caustics solver
    • Fixed issue when caustics disappear after adding new light sources
    • Fixed issue when caustics disappear after adding large geometry
    • Caustics are now influenced by bump mapping
    • Caustics now work with rayswitch material
  • Added fisheye projection type to CoronaCamera

Caustics fixes are in the latest daily. Looking forward to your feedback :)

Cheers,

Rowan

1808
[Max] Daily Builds / Re: Caustics playground!
« on: 2019-05-09, 14:27:42 »
was the fix for larger scenes included in the daily build on the 7th? dont see anything about it in the changelog

Hi,

It was not in that build (7th), it will be coming soon though.

Thanks,

Rowan

1809
thanks for the tip I am starting to think it's the high quality filtering, I turned it off and it seems to not turn black randomly anymore. it seems to be it. I rendered all I needed for my work with CXR so I am ok except for the photoshop all nighter I might have to do to please a client.
CXR is great if we can have an adobe photoshop reader so we can open that one file and have all layers just like EXR, but it takes an extra 10 to 15 minutes for me to export the layers and reassemble them. other than that it seems to be much better in system responsiveness but the file is 7 to 9 times bigger than EXR so my renders are up to 5.6GB per view now from a few hundred MB.

Hi,

When rendering with the high quality filtering did you by chance have the AI denoiser enabled?

If you could provide your scene I will be able to investigate this further.

Thanks,

Rowan


1810
I just saw this line in the Trello for Corona 4 bugfixes: "Fix CoronaProxy bad performance, memory usage in some situations"

Does "in some situations" have anything to do with loading proxies over 10Gb Ethernet? We've been troubleshooting a slow to open max file where removing the proxies (held on a server via 10GBe) seems to remedy the problem.

Sorry to bump this but I feel that it got snowed under by other posts.

Hi,

Sorry we missed this one earlier. We would genernally expect that the system caches the files intelligently, but this might not always be the case.

So in order for us to investigate, it would be really helpful for us to get a copy of your scene and assets if possible?

Instructions on how to do this are in my signiture, please don't forget to let me know the name of the file which you have uploaded.

Thanks,

Rowan

1811
Hi!
Found a problem. I can't make a black and white image.
3ds max 2016, "dailyBuild May 3 2019"
I was planning to post the same thing tomorrow as a problem. Additionally, I found another problem, which made me delay my project submission with 2 weeks until I realised where was the problem.
2 Images attached.
The image where I used Corona 3.2 three months ago to render an animation the pool water was looking like on the attached.
A round of revision came in and I had to update some parts of that animation, but I updated already to the latest daily build (at that time). The result of the pool water was not expected while nothing else was changed for that part of the sequence. Two days ago I have tried to render the only 1 frame with the latest daily - the results as obvious.

Hi,

So the saturation bug has been noted quite a few times already in this thread. A fix is coming soon for it.

I'm not quite sure I understand your description of the second issue. You say that you already realised where the problem was, is this correct?
If not, please can you provide your scene to me? Instructions on how to do this are in my signiture, please don't forget to let me know the name of the scene.

Thanks,

Rowan

1812
I can send you a scene tomorrow. I had the exact same issue happen today on a completely new scene without using DR. I already sent an email and video to Corona as there is a ticket open already for 2 other issues.
Where should I send the file? New ticket or one that open?

Hi,

Can you either submit a new support ticket, or create a post in the bug reporting section and we'll continue there as to not flood this discussion.

Thanks,

Rowan

1813
I've had this issue for the latest 2 builds, when i render using DR, the frame buffer Beauty pass will go black randomly after a few minutes, then if I cycle between the elements and back to beauty it will show up again, then go black after some minutes. When render ends it is randomly either saving or not saving the beauty (black layer) depending on if it shows or not at the time. In some cases the other elements also would have the alpha wrong as in a big blag square of the element missing or added. Anyone having same issue? could it be a memory leak when it receives data from the render nodes?

+1 exactly the same issue. Haven’t had any loss when saving out (to Cxr) but the black VFB during DR is identical. I agree that it happens with the DR machines send their data back to the workstation - I played with how many passes it takes between sending the data back and got less frequent black screen. Flicking back and forth to other elements gives the same behaviour too (returning VFB back to normal).

Hi,

Would you both be able to provide me with your scenes? I am currently trying to reproduce this, but so far I have been unsucessful.

Thanks,

Rowan

1814
I get this too - but the file doesn't need to be that big - working on a 75mb file it's just frozen...

If 3ds max autosaves whilst using interactive rendering, it crashes...

this has happened numerous times for me.

max 2019, corona 3...

Hi,

If Max is crashing/freezing can you please generate a minidump? Instructions on how to do this are in my signiture.

So far I have been unable to reproduce this issue. Are you also able to provide me with the scene that you are experiencing the crash with, and provide me with your system specification?

Thanks,

Rowan

1815
Okay, thanks.

As Ryuu said here: https://forum.corona-renderer.com/index.php?topic=22530.msg148170#msg148170 the calculated noise level can vary and be bit off, however I agree it shouldn't change this drastically just by enabling the HQ denoising.

Testing with a pass limit ensured that the HQ denoiser was not having a general effect on the speed of the renders, and that it seems to be limited to rendering with a noise limit.
With my tests using a pass limit I found that the reported noise level was roughly the same after the 30 passes, whether the HQ denoising was enabled/disabled which was not the case when using a noise limit.

Please find my results below:

Code: [Select]
Test 1: HQ Filtering, HQ denoising 5% noise limit
Render time: 5.43 minutes
Passes: 110
Reported Noise: 4.90%

Test 2: HQ Filtering, No denoising 5% noise limit
Render time: 29 seconds
Passes: 15
Reported Noise: 4.79%

Test 3: Normal Filtering, HQ denoising 5% noise limit
Render time: 1.11 minutes
Passes: 30
Reported Noise: 4.90%

Test 4: Normal Filtering, No denoising 5% noise limit
Render time: 18 seconds
Passes: 10
Reported Noise: 3.58%

Test 5: HQ Filtering, HQ denoising 30 pass limit
Render time: 1.14 minutes
Noise Level: 3.44%

Test 6: HQ Filtering, No denoising 30 pass limit
Render time: 1.10 minutes
Noise Level: 3.40

Test 7: Normal Filtering, HQ denoising 30 pass limit
Render time: 1.11 minutes
Noise Level: 1.82

Test 8: Normal Filtering, No denoising 30 pass limit
Render time: 1.08 minutes
Noise Level: 1.84

We will continue to look into this.

Cheers,

Rowan

(Internal ID=347673267)

Pages: 1 ... 119 120 [121] 122 123 ... 127