Author Topic: Corona Material/Lights Converter (legacy)  (Read 923759 times)

2018-01-26, 12:13:22
Reply #1095

faust

  • Primary Certified Instructor
  • Active Users
  • ***
  • Posts: 20
    • View Profile
I've just caught this message

>>> SCENE Info: <<<
Corona version: 1.7 (hotfix 2), build timestamp: Nov 29 2017 16:10:25
Converter version: 1.39
Max version: 19000
Installed Vray plugins: V_Ray_RT_3_40_03  V_Ray_Adv_3_40_03 
# Material conversion took 1.413 seconds
# Iterations: 96, converted: 94
# Map conversion took 0.645 seconds
# Iterations: 275, converted: 4
# Light conversion took 0.051 seconds
# Iterations: 1

Error occured in VRayFastSSS2 : Material #2100440743:VRayFastSSS2
-- Unknown property: "texmapOnDisplacement" in Material #2100440743:CoronaSkinMtl

Error occured in VRayFastSSS2 : sahar pesok:VRayFastSSS2
-- Unknown property: "texmapOnDisplacement" in sahar pesok:CoronaSkinMtl


2018-01-26, 12:18:19
Reply #1096

DeadClown

  • Active Users
  • **
  • Posts: 1445
    • View Profile
    • racoon-artworks
This error is caused by the old vray version you have installed. The converter uses a property that has been introduced in a more recent version of vray. I can't keep track of all the little changes everywhere in vray or any other renderer all the time.
I'll fix this issue in the next converter version but I'm quite busy atm, so this may take a while. The easiest way to get rid of it is updating your vray ;)
Any sufficiently advanced bug is indistinguishable from a feature.

2018-01-30, 15:25:11
Reply #1097

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 9040
  • Turning coffee to features since 2009
    • View Profile
Hello, I can send you the free public version.

I am very interested in this conversion, I want to leave Fstorm at once and go to Corona. Memory problems on the GPU, a burning of video card. Lack of resources, etc.

https://drive.google.com/drive/folders/1L-oLHHginYHWpqsixqJsO09uBjIRbsvW?usp=sharing

It has the free version and the last version that can be used with watermark.
Problems with those is that anyone could have snuck in some trojan/virus/keylogger/bitcoin miner. We saw corona "cracks" in the wild that made the computer mine bitcoins while corona was rendering. Installing anything like this is a big no-no for anyone taking security seriously... unless the binary is signed (which is not the case AFAIK)
Rendering is magic.
Private scene uploader | How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)

2018-01-30, 16:59:32
Reply #1098

sbrusse

  • Active Users
  • **
  • Posts: 26
    • View Profile
Hey guys, any way you could add the deletion of the VrayColor2Bump?
I have to go through all the materials manually to delete the VrayColor2Bump and it's a pain.

Thanks!

2018-01-30, 17:10:54
Reply #1099

viscorbel

  • Active Users
  • **
  • Posts: 8
    • View Profile
Would it be possible to add an option that removes any VrayBumpMtl nodes and replaces them with whatever is inside the base mtl slot?
Right now it converts the base material to Corona mat and leaves it inside the VrayBumpMtl. For someone like me who uses this Vray feature often, this creates a lot of glowing red 'unsupported' objects in the renders after a conversion. So there's a need to manually go over all the relevant materials and fix this.

Some small objects sometimes get away and are only found out in the full res render which results in some unpleasant language.

2018-01-30, 17:24:19
Reply #1100

DeadClown

  • Active Users
  • **
  • Posts: 1445
    • View Profile
    • racoon-artworks
Hey guys, any way you could add the deletion of the VrayColor2Bump?
I have to go through all the materials manually to delete the VrayColor2Bump and it's a pain.
Not going to happen! ... but how about substituting the VrayColor2Bump for an CoronaBumpConverter map instead :P . Will do that for the next version, good pointer. I missed that new map.

Would it be possible to add an option that removes any VrayBumpMtl nodes and replaces them with whatever is inside the base mtl slot?
Sure thing! Good pointer as well. Will be done in the next version.
Any sufficiently advanced bug is indistinguishable from a feature.

2018-01-30, 20:14:04
Reply #1101

DeadClown

  • Active Users
  • **
  • Posts: 1445
    • View Profile
    • racoon-artworks
Ok, here are the two small additions (which didn't take long to make). I know, I still have some other things on my todo list but I don't have much time for it right now.

Get it here: http://www.racoon-artworks.de/CoronaConverter/CoronaConverter.html

changelog:
v1.41 - [2018/01/30]
  • added support for VRayColor2Bump
  • added simple VrayBumpMtl conversion
Any sufficiently advanced bug is indistinguishable from a feature.

2018-01-30, 22:41:40
Reply #1102

viscorbel

  • Active Users
  • **
  • Posts: 8
    • View Profile
Wow, that was fast!
Many thanks, works great :)

2018-02-02, 16:37:51
Reply #1103

sbrusse

  • Active Users
  • **
  • Posts: 26
    • View Profile

2018-03-15, 09:31:35
Reply #1104

daliaahmed

  • Users
  • *
  • Posts: 1
    • View Profile
Hey I just got this message:

>>> SCENE Info: <<<
Corona version: 1.7 (hotfix 2), build timestamp: Nov 29 2017 16:08:17
Converter version: 1.39
Max version: 17000
Installed Vray plugins: V_Ray_RT_3_00_07  V_Ray_Adv_3_00_07 
# Material conversion took 6.741 seconds
# Iterations: 1019, converted: 1018
# Map conversion took 2.895 seconds
# Iterations: 1335, converted: 183
# Light conversion took 0.838 seconds
# Iterations: 289

Error occured in VRayFastSSS2 : Material #2146934348:VRayFastSSS2
-- Unknown property: "texmap_opacity" in Material #2146934348:VRayFastSSS2

Error occured in VRayFastSSS2 : wax_top:VRayFastSSS2
-- Unknown property: "texmap_opacity" in wax_top:VRayFastSSS2


2018-03-27, 23:03:05
Reply #1105

ecaterinatache

  • Users
  • *
  • Posts: 3
    • View Profile
Hello
I`ve just got this message

>>> SCENE Info: <<<
Corona version: 1.7 (hotfix 3), build timestamp: Feb  8 2018 13:06:46
Converter version: 1.39
Max version: 18000
Installed Vray plugins: V_Ray_RT_3_20_02  V_Ray_Adv_3_20_02 
# Material conversion took 0.298 seconds
# Iterations: 12, converted: 11
# Map conversion took 0.573 seconds
# Iterations: 194, converted: 0
# Light conversion took 0.067 seconds
# Iterations: 18

Error occured in VRayFastSSS2 : veiny_marble:VRayFastSSS2
-- Unknown property: "texmapOnDisplacement" in veiny_marble:CoronaSkinMtl

P.S. I`m using the demo version

2018-03-28, 10:56:57
Reply #1106

DeadClown

  • Active Users
  • **
  • Posts: 1445
    • View Profile
    • racoon-artworks
New minor version.

Get it here: http://www.racoon-artworks.de/CoronaConverter/CoronaConverter.html

changelog:
v1.42 - [2018/03/28]
  • fixed errors in VraySSS2 material conversion with old vray versions
Any sufficiently advanced bug is indistinguishable from a feature.

2018-03-30, 06:51:48
Reply #1107

Hozkr Mejia

  • Active Users
  • **
  • Posts: 8
    • View Profile

2018-04-21, 01:47:55
Reply #1108

Prazno

  • Users
  • *
  • Posts: 3
    • View Profile
I got this error and the request to post this here...

>>> SCENE Info: <<<
Corona version: 1.7 (hotfix 4), build timestamp: Mar 23 2018 11:50:59
Converter version: 1.42
Max version: 18000
Installed Vray plugins: V_Ray_RT_3_60_03  V_Ray_Adv_3_60_03 
# Material conversion took 8.025 seconds
# Iterations: 188, converted: 190
# Map conversion took 1.143 seconds
# Iterations: 172, converted: 172
# Light conversion took 14.078 seconds
# Iterations: 58

Error occured in TargetDirectionallight : $Target_Directional_Light:Direct01 @ [608313.500000,-206687.796875,196261.968750]
-- Unknown property: "AreaShadow" in $Target_Directional_Light:Direct01 @ [608313.500000,-206687.796875,196261.968750]

Error occured in Omnilight : $Omni_Light:Omni04 @ [-3005.970215,-2684.351074,179.892059]
-- Unknown property: "AreaShadow" in $Omni_Light:Omni04 @ [-3005.970215,-2684.351074,179.892059]

Error occured in Omnilight : $Omni_Light:Omni05 @ [-3005.970215,526.738281,179.892059]
-- Unknown property: "AreaShadow" in $Omni_Light:Omni05 @ [-3005.970215,526.738281,179.892059]

Error occured in Omnilight : $Omni_Light:Omni06 @ [-3005.970215,3737.827637,179.892059]
-- Unknown property: "AreaShadow" in $Omni_Light:Omni06 @ [-3005.970215,3737.827637,179.892059]

Error occured in Omnilight : $Omni_Light:Omni07 @ [-3005.970215,8309.910156,179.892059]
-- Unknown property: "AreaShadow" in $Omni_Light:Omni07 @ [-3005.970215,8309.910156,179.892059]

Error occured in Omnilight : $Omni_Light:Omni01 @ [-8881.720703,2267.581055,2666.993896]
-- Unknown property: "AreaShadow" in $Omni_Light:Omni01 @ [-8881.720703,2267.581055,2666.993896]

Error occured in Omnilight : $Omni_Light:Omni08 @ [-10387.004883,2267.581055,2666.993896]
-- Unknown property: "AreaShadow" in $Omni_Light:Omni08 @ [-10387.004883,2267.581055,2666.993896]

Error occured in Omnilight : $Omni_Light:Omni09 @ [-11878.650391,2267.581055,2666.993896]
-- Unknown property: "AreaShadow" in $Omni_Light:Omni09 @ [-11878.650391,2267.581055,2666.993896]


2018-04-24, 10:00:57
Reply #1109

DeadClown

  • Active Users
  • **
  • Posts: 1445
    • View Profile
    • racoon-artworks
Thanks for the report. Unfortunately I can't reproduce it here. Can you send me a scene with one of those lights which cause this error?
Any sufficiently advanced bug is indistinguishable from a feature.