Daily builds version 3

[Dung (Ivan)]

For example: if i set bump map 0.05 via keyboard and press enter i get only 0.1. with all others numeric setting's the same problem. You can try it by youself:))

I have newest DB from 19/9/2018 and both Material editor and VFB works

[cecofuli]

Hi Iva,

BSDF exposed? =) 
I have DB 20 September, 3ds Max 2015 and I don't see this menu in my CoronaMtl.

[sevecek]

Hi Iva,

BSDF exposed? =) 
I have DB 20 September, 3ds Max 2015 and I don't see this menu in my CoronaMtl.

Little perks of being a member of Corona team :)

[Fluss]

At all numbers spinners in VFB not working with values higher than 2 digits/
For example i can't set value 0,05 or -0,05 or 0,15 / 0,25  for saturation spinner, only 0,1  0,2 
or -0,1 - 0.2  -0.3  and etc.
Same thing for other's  settings :)

Also in all settings /Corona Sun,Corona Sky,Corona Light and even in materials /for example impossible to set bump map 0.05 /--exist same problem---very uncomfortable/ I'am going back to Db 08/16g

Some new's about this problem?!!:))
In last DB is the same and also arrow's near the numbers not working as expected on mouse one click, only on drag :(((

It already happened to me some time ago (was on 1.6 and max 2017 at that time). Closing 3ds max and reopen the scene solved the issue most of the time except once where i had to completely merge the old scene into a fresh new one. I'm pretty sure it was a max issue as the bug happened in every single spiner in the scene, not only corona's ones. Never encountered the issue again since i'm on max 2018 tho.

[denisgo22]

At all numbers spinners in VFB not working with values higher than 2 digits/
For example i can't set value 0,05 or -0,05 or 0,15 / 0,25  for saturation spinner, only 0,1  0,2 
or -0,1 - 0.2  -0.3  and etc.
Same thing for other's  settings :)

Also in all settings /Corona Sun,Corona Sky,Corona Light and even in materials /for example impossible to set bump map 0.05 /--exist same problem---very uncomfortable/ I'am going back to Db 08/16g

Some new's about this problem?!!:))
In last DB is the same and also arrow's near the numbers not working as expected on mouse one click, only on drag :(((

It already happened to me some time ago (was on 1.6 and max 2017 at that time). Closing 3ds max and reopen the scene solved the issue most of the time except once where i had to completely merge the old scene into a fresh new one. I'm pretty sure it was a max issue as the bug happened in every single spiner in the scene, not only corona's ones. Never encountered the issue again since i'm on max 2018 tho.

Don't matter which scene or max file, even in new opened file after several restart's -- result is the same, impossible set 0.05 and etc. numbers /max2017/ :)

[Fluss]

removing 3DSmax.ini sometimes help too but you'll lose all your UI customization

[denisgo22]

removing 3DSmax.ini sometimes help too but you'll lose all your UI customization

Thanks a lot :)
I'ts working!!

[Njen]

removing 3DSmax.ini sometimes help too but you'll lose all your UI customization

Thanks a lot :)
I'ts working!!

It was probably the precision setting in the Max preferences. You can tell Max how many decimal places to use: 'Customize -> Preferences -> Spinners [group] -> Precision'. You might have accidentally set your value to '1', and the default is '3'.

[ihabkal]

I'm facing some instability issues after update 2 3dsmax 2019, please guys take this update into consideration when you do your programming it seems Autodesk has pulled a fas one and made some changes in the code.

[ihabkal]

I'm facing some instability issues after update 2 3dsmax 2019, please guys take this update into consideration when you do your programming it seems Autodesk has pulled a fas one and made some changes in the code.

Believe it or not, turned out Anima 3.5 was crashing max every 5 minutes, I removed it and max was stable all night. they just released it yesterday. This was hard to figure out as I had installed max 2019 update 2, new Nvidia drivers, new Corona build, new anima, and new 10GB card same week so took me the whole day to figure it out.

[Juraj]

@Romullus, tiny off-topic, but true 32bit displacement maps would look smooth to eye (when looking at the texture itself) but the detail would actually still be there.
For example if the total depth of the map is 10cm let's say but it also has ultra rough micro-noise at 1mm, the map would still look super smooth to human eye.

It's not possible to judge detail of true disp map, it always looks blurry and smooth. You can though, high-pass it to reveal more&more micro detail or alter the ratio between low & high frequency detail.

Just thought I would say since you used screeenshot of the disp map as proof, but it doesn't work that way :- ).

[romullus]

That displacement map is 8 bit, it has only 256 shades of grey. As bad as my sight is, i think i can still see that this map has no micro details in it :]

[ihabkal]

That displacement map is 8 bit, it has only 256 shades of grey. As bad as my sight is, i think i can still see that this map has no micro details in it :]

this reminded me where I read that for hollywood level stuff they only use 16bits for bump and displacement maps.

[pokoy]

That displacement map is 8 bit, it has only 256 shades of grey. As bad as my sight is, i think i can still see that this map has no micro details in it :]

this reminded me where I read that for hollywood level stuff they only use 16bits for bump and displacement maps.

Funny, I've been at places where they use Jpegs for almost anything and no one understands why it's a bad idea. Naming convention - almost never, too. Hollywood level can also mean it's done in a rush and as long as it's not a hero asset in slow motion right in front of the camera no one will notice it ;)

[Juraj]

Guys with Threadrippers, can you check what is your CPU usage during UHD Cache ?

Set it for something longer (Precision 4,etc..) and let me know please. I only get 33perc. on 2990WX.