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

Pages: [1]
1
Oh, sorry ! In VFB - all fine. Problem occurs only in "Corona Image Editor". My mistake.
I use autosave function, it saves ".cxr" Files, when i open them "CMasking_ID" linked to Exposure/LUT/Curves/etc...

On - https://puu.sh/xTNTX/ef854c3aff.png
Off - https://puu.sh/xTNUN/812adb00e7.png

2
Why "CMasking_ID / CMasking_WireColor" affected by VFB-Settings like "Expusure/Highlight Compress/Contrast/Saturation/etc" ?
Can i disable this ? To save manually this Render Elements i need turn-off all VFB-Features, reset all to default, than save Masks.
Not sure, maybe its bug ? I use 1.7 RC7 Version on 3Ds Max 2017.

3
No, everything it's okay. Thank you.
<3 Corona, you are doing a good job !

4
Maybe it's strange question... But :
If i first time buy 1-Month FairSaaS — license period starts immediately after payment / OR / day count starts only after i activate and run licence first time ?

For example (to be sure) :
I buy 1-Month FairSaaS (6 October). But i only buy it, not activate or even run this.
And, for example first time i activate this and run (~26 October) - I will have 10 days left or 30 ?

5
News / Re: Corona Renderer 1.7 for 3ds Max Daily Build
« on: 2017-10-05, 22:59:28 »
IMPORTANT NOTE BEFORE YOU TEST:
Due to the significant changes in 1.7, scenes saved with 1.7 are NOT backwards compatible with 1.6.1 - if you save a scene using the 1.7 daily builds, you will not be able to open it with 1.6 or 1.6.1 installed.
This is only about "Daily Builds and Release Candidate" ? I mean - after "Stable Release" Corona 1.7 will it be compatible with 1.5-1.6 ?

P.S. Sorry if someone already asked about it.

UPD Haha, unbelievable timing, really. RC7 Version what i need.

Pages: [1]