Corona Bitmap Shade/Wireframe switch super slow

[rombo]

Hello, I have been having the problem of using max 2016 for a couple of weeks already and noticed that the viewport is slowing down to switch from shaded to wireframe to the point of having to wait a few seconds (20-30s sometimes, depending on the number of Corona Bitmaps used on the scene) for it to switch. It was ok before because it was just a little, but now with the whole scene assembled it is unbearable to switch for a simple edit.

I tried moving the textures to the good old max bitmap reader and the VP is switching in the blink of an eye.
Any idea why? I can provide an example scene if needed.

Regards,

PS:

Using July 21st daily, but the 1.1 version is the exact same.

[agentdark45]

I've noticed a similar issue when using high res bitmaps. Viewport switching / editing materials is much slower compared to using the native bitmap loader.

[rombo]

Yup, indeed, after installing the new converter script with the new daily, I converted everything back to regular max bitmaps and things are a lot smoother regarding viewport shade/wire switching.
Thanks, I thought I was the only one with the issue and it took me a while to figure out what was going on, I even downsized the resolution of 300 bitmaps in my scene because I thought it was due to their high res.

[atelieryork]

Can confirm! As soon as any coronabitmaps are visible in the viewport the scene becomes unusable. Switching between shaded and wireframe can take up to 30 seconds or so. I have set my viewport to show texture maps at 2048 or 1024 but no difference.

The Corona Scene Converter script also doesn't pick up maps that are in any slots other than Diffuse, so if you have maps visible that are in the reflection slot or buried within a multi-sub or within a colorcorrect node then they don't get turned off/on by the script.

I'm struggling to find a reason to use coronabitmap, really, since it's causing this major issue. Any real reasons to use it over standard max bitmap?

edit: i should note that it also takes a fraction of the time for a large scene to load and be usable in max with these maps not visible in the viewport.

[racoonart]

The Corona Scene Converter script also doesn't pick up maps that are in any slots other than Diffuse, so if you have maps visible that are in the reflection slot or buried within a multi-sub or within a colorcorrect node then they don't get turned off/on by the script.

Well, if no one reports it, it sure won't get fixed ;) I tried it here and it seems to work fine. Could you provide a simple scene where this issue happens?

[atelieryork]

Sorry only just noticed it :)

I can't share this scene, sorry. In my case it was maps inside a colorcorrect node and maps in any other slot than Diffuse. So, reflection, bump etc. In all cases it turned off the Diffuse slot map, but nothing else.

[hubrobin]

Hi guys,

could you try with the latest daily build? I believe this issue has been addressed.

Thanks,

Robin

[atelieryork]

Good stuff!

I might jump on the dailies but right now on 1.2.

How can I get access to the dailies?

[romullus]

How to use daily builds: https://coronarenderer.freshdesk.com/support/solutions/articles/5000570015-daily-builds

[atelieryork]

Installed and can confirm that you fixed the issue, as far as I can tell. Good work!