Drag&drop broken after Corona instal

[pOOLa]

Hi, I usually use V-ray. But I wanted to try Corona. After installing Corona on max 2024, unfortunately the drag&drop bitmap broke. The thing is that with V-ray mtl, the drag&drop bitmap always created a V-rayBitmap in the slot. After installing Corona, a standard 3dsmaxBitmap is created. Is there somewhere to change this? It's quite annoying and even uninstalling Corona didn't help :-(
THX

[pOOLa]

I also tried reinstalling (uninstalling and installing) V-ray. Also did not help. :-(

[romullus]

3ds Max bitmap on drag and drop is standard behaviour, so i don't think that Corona broke something. Maybe you were using some custom configuration, or it's Vray, that changed default behaviour to enhance user experience, but Corona install somehow overwrite that. Anyway, i suggest you to try this script by Changsoo Eun: https://cganimator.com/cs_sme_drop/ It creates native bitmaps for every supported renderer, including V-Ray and Corona. Just be aware that it requires 3ds Max 2024.1 or later to work.

[pOOLa]

Unfortunately, that's only addressed in Slate. In the classic editor, Corona just broke it somehow :-(
I installed Corona just for max 2024 and it stopped working. I did not uninstall Corona for max 2022 and it still works OK.

[Avi]

You can use Corona converter to quickly convert standard 3ds Max bitmaps to CoronaBitmaps.

[dj_buckley]

You can use Corona converter to quickly convert standard 3ds Max bitmaps to CoronaBitmaps.

Does this now work safely with all image formats?  There were issues previously with tiff files

[Avi]

You can use Corona converter to quickly convert standard 3ds Max bitmaps to CoronaBitmaps.

Does this now work safely with all image formats?  There were issues previously with tiff files

I quickly tested converting a standard bitmap containing a tiff file to Corona bitmap, it seems to be working fine but I will look up for any issues regarding this which was reported before and update you.


Edit- This was reported to Autodesk as this is a 3ds Max issue not Corona and I quickly tested with 3ds Max 2024.2 and Corona 11 HF 1. It is not yet fixed.

[pOOLa]

Well, I'm sorry. It seems to be a bug in V-ray + max 2024. It still works in max 2022. I mean, I'll post it on the other Chaos forum :-) Thanks and sorry for the confusion.