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

Pages: 1 [2] 3
16
Will the updated material converter convert 3dsmax's Physical Material to Corona?
Models that I bring in from other Architectural apps default to that. It's such a pain to manually convert them all. Even if it just copied the bitmap paths over to the diffuse channel, I can set the rest of the settings.

thanks

Hello Javadevil, thank you very much for your feedback. Conversion of 3ds Max's Physical Material is very high on our "what to do next list", however before adding support for another material to Corona Converter, first we want to make sure conversion of already supported materials works as expected. So currently we mostly focus on simplifying the shading networks, since this is something which troubles lots of early adopters of Corona 7. If everything goes well and we'll manage to address all the issues with currently supported materials, hopefully we would be able to start working on support for Physical Material soon :)

17
A material made with Corona 6 consists of 1) after conversion with the latest converted, the newly created material contains many maps and nodes 1) + 2); That's so frustrating; Is there any workaround?

tallbox, romullus, thank you very much for your feedback, we're already working on changes which should result in simpler shading networks being generated.

18
Hi guys, i just start trying Corona 7 last daily. One thing i have noticed is that in some models specifically on archmodels collection 171, when converting from CoronaLegacyMtl to the new CoronaPhysical material i have an issue with the refraction.  For some reason the guy that made the models had the refraction level 1 but the color black so even if in the legacy material that's not a problem and won't translate as glass, after the conversion to physical material it is a problem since the leaf looks like glass. As far as I can understand in the conversion takes into account only the refraction amount and not the legacy material refraction color. I hope that makes sense!

Hello annkos, please could you provide us some of these models with the corresponding materials or create for us some reproduction case we might investigate?

19
...
I uploaded the scene in question. Initial parsing time was around 30 seconds, seems it is due to the Rhino geometry, but switching between viewports IR was ok. Every now and again it slows down a little though. Still, hitting render instead of IR parsing was 4-5 seconds.

Hello steyin, please may I also ask you if you have some plug-ins installed? And what version of Microsoft Windows and what hardware do you use?

20
...
Hi.
Did you guys receive the scene? I was wondering if you got the same outcome.

Hello lupaz, yes we received it, thank you very much. We are currently investigating it but we are unable to reproduce the slowdown in Corona 4. My colleague even stated that: "(for me) it was the other way around - when I tried IR on the included scene with Corona 1.5 it was very laggy and sometimes it didn't even show anything in the VFB. When I tried the same scene, but with Corona 4 everything worked well and smoothly."

Please what hardware do you use? Do you have some plug-ins installed? We want to test it with the same plug-ins installed to try to find out, if they could cause this slowdown.

21
...

I uploaded the scene in question. Initial parsing time was around 30 seconds, seems it is due to the Rhino geometry, but switching between viewports IR was ok. Every now and again it slows down a little though. Still, hitting render instead of IR parsing was 4-5 seconds.

Steyin, thank you very much for the scene. We are going to have a look at it. :)

22
Forestpack and railclone (itoo software plugin for 3dsmax) slow down deeply the iR.

Hello Alexandre,  thank you very much for your feedback. We are aware of this problem and currently we are still investigating whether it is some fault on our side or if the slowdowns are caused by aforementioned plug-ins. Also if you could provide us some scene which manifests this issue, it would help us a lot. :)

23
...
You can bet that I will do that. :) I would also give you the scene.
Until now I could only notice that IR sometimes crashes, if I made a lot of changes in the scene very quickly - like every few seconds a change.

Regarding parsing time, I noticed that some scenes are simply parsing quicker than others.
Tried erasing parts of the scene... until it remained literally almost empty. Still the same long parsing...

In other scenes that are much bigger, parsing is much quicker...
Strange phenomenon that I had noticed also in previous Corona versions.

I´ll continue testing.

Designerman77, if you had some empty scene which parses for a long time, please could you send it to us? This indeed should not happen and we would like to investigate what could be the cause of this issue.

24
Here's a video:

I can send you the scene tomorrow, but honestly I believe the issue is scene independent.
...

Hello lupaz, thank you very much for your feedback and for dedicating your time and energy into recording the video - the slowdown is indeed visible in this case. Since you mentioned that you get "Fault tolerant heap" warning, it is highly probable that this could be the cause of the slowdown. "Fault tolerant heap" is a feature of Microsoft Windows OS, which can get automatically turned on if OS detected multiple crashes of some specific application (in this case 3DS Max). This feature may have severe performance impact on rendering speed. It is not possible to turn off this feature from Corona Renderer, we can only warn our users that it is turned on (as you can see in 0:28), but you can turn it off it manually, as described on our Freshdesk:

https://coronarenderer.freshdesk.com/support/solutions/articles/5000678431-windows-enabled-fault-tolerant-heap-for-3dsmax-or-dependent-processes-this-may-have-severe-perform

I recommend you to turn it off and try the Interactive Rendering again, hopefully it will be much better now. Please let us know if turning off this feature helps.

Anyway, if you could send us the scene you used for this comparison, it would really help us a lot, since we don't have enough "real-world" examples (scenes) where we could reproduce these kind of issues. :)

25
Hello Steyin, thank you very much for your feedback. Please could you provide us such scene so we could investigate the cause of this issue?

You can use either our Private Uploader: https://corona-renderer.com/upload or you can send it to me as a private message. No uploaded files will be shared with anybody else or used for purposes other than debugging Corona without explicit permission.
I'll try to get you the scene along with a former one with a different Rhino export. The one I'm currently using might be heavier due to the modeling of the import...since its from the city of NY and who knows if they know what they're doing. I finally rendered the scene however for final renders and noticed the parsing times were only a few seconds compared to nearly 20-30 for IR.

Steyin, the difference between parsing times for IR and final renders should definitely not be so big - there is certainly some problem (maybe on our side). If you could provide us the scene so we could have a look at it, it would help us a lot with finding the potential issues.

26
Yes i was think about it, but without light material it is also add about ~5s for parsing scene what slowing response from IR

I asked about this issue my colleague and he agreed that in this case, the slowdown is currently expected, since as romullus mentioned:
Quote
when you assign lights to particles, then it breaks instancing of those lights

27
Hey Ondra,

in C4D, iMac Pro 2018, OS High Sierra, I sometimes also experience Corona crashing after using IR.
Seems to happen in big scenes... not often... but two-three times it occured.

I´ll keep an eye on it... maybe there is a pattern in the cause.

Thanks for your constant optimization of Corona.

Hello Designerman77, thank you very much for your feedback. If you would discover some case where the crashes are repeatedly occuring, please let us know and we will try to reproduce and investigate the problem. :)

28
I've noticed that as of late, any exports I get from coworkers from Rhino 5 (mainly OBJ) are creating long parsing times and slow IR at the beginning. It seems to balance off after a few mins, but I've never had the issue before. I'm running Max 2017 and Corona 4 HF1.

Hello Steyin, thank you very much for your feedback. Please could you provide us such scene so we could investigate the cause of this issue?

You can use either our Private Uploader: https://corona-renderer.com/upload or you can send it to me as a private message. No uploaded files will be shared with anybody else or used for purposes other than debugging Corona without explicit permission.

29
Hi selene, thx for the interest, IR is the most important tool for us, so yes i have a report of IR restarting with some forest, i have filled a bug report, the support ticket of the fresh desk is the #177229, developers say the manage to reproduce the bug but we havent heard of it since. its happening for us on almost every scene now, and the only solution for us is to hide this objects to work on the scene and unhide them and make a real render of it just to see how its looking (very time consmuing process, and if the ir is launched with the forest active we need to forece close the 3dsmax and loose the changes again)

thx again!

Hello Arqrenderz, thank you very much for your feedback. I'll have a look on the issue.

30
Since I think this topic is related to the issue we are currently investigating, I'm going to pin here a link to the poll and topic dedicated to solving this problem: https://forum.corona-renderer.com/index.php?topic=26333.0

As TomG and Maru already mentioned, please report us any specific case, ideally a 3DS Max scene, which you think is relevant to solving the issues with Interactive Rendering slowdowns - it would really help us a lot :). We would really like to deeply investigate it, but we struggle to reproduce it ourselves. Most of the time we get such feedback, our users don't provide us with needed information or example scenes, so it is really hard to find cause of this problem.

Thank you very much for any information which could lead to solving this issue :)

Have a nice day,
s.

Pages: 1 [2] 3