Chaos Corona Forum
General Category => Porting and API => Chaos Corona for Blender => Topic started by: blanchg on 2018-06-23, 23:14:43
-
Hey guys, what do you want first?
Support for Blender 2.8
Support for Corona 2.0
Doing 2.80 will get 2.0 compatibility only in 2.80, doing 2.0 now might mean losing support for Corona 1.7 and the Mac version requiring a early version.
However Blender has changed their render engine completely which means it will take me several months to get it working.
This work is for you all so let me know what you need.
-
I think making support for corona 2.0 in blender 2.8 now doesn't make much sense.
Who knows what will change until 2.8 releases so I guess development of plugin/exporter would be even slower now.
So support for latest existing corona for latest official blender release would make more sense.
Anyway, do you think it would be possible to convert blender 2.8 principled shader to corona material? So that it would be possible to create materials in realtime viewport and then auto-convert them when switching to corona?
-
That is a different topic entirely 😁 with some community help we might be able to get close but not exact
-
Hi Blanchg and thanks for your productive dedication! I would prefer a stable Corona 1.7, otherwise you would risk losing everything ...
-
What is making 1.7 unstable? Apart from the preview with images.
-
I was wrong to use the term stable. I prefer a fully functional release, even if not current.
The "export object" does not work for "only selected", it exports everything.
Sometimes it creates errors in the file.mtl the "hue saturations value".
-
Support for Blender 2.8 would be my choice.
-
I was wrong to use the term stable. I prefer a fully functional release, even if not current.
The "export object" does not work for "only selected", it exports everything.
Sometimes it creates errors in the file.mtl the "hue saturations value".
If you could provide small .blend files that demonstrate the last issue it would help.
-
Error "Hue saturation value"
-
thank you for your time to make this good thing. personaly for me, i will stay on 2.79 maybe for a half of year because i got its workflow in my hands already. but i would like of course corona 2 for 2.79 for it's speed. however i'm very happy with the old 1.6 because all is working good. i would prefer more the interactive integration instead of newer versions. but it's just my point.
-
Error "Hue saturation value"
it's a very known thing already. a hue/saturation is a tonemapping operation. so you have to use a "tone mapping" node alongside "hue/saturation" node.
-
thank you for your time to make this good thing. personaly for me, i will stay on 2.79 maybe for a half of year because i got its workflow in my hands already. but i would like of course corona 2 for 2.79 for it's speed. however i'm very happy with the old 1.6 because all is working good. i would prefer more the interactive integration instead of newer versions. but it's just my point.
That level of integration won't be possible until it is added to the standalone which won't be in any current release. Of course I could do it now but the performance would be unbearable and it is a lot of work for something that won't be usable.
-
thank you for your time to make this good thing. personaly for me, i will stay on 2.79 maybe for a half of year because i got its workflow in my hands already. but i would like of course corona 2 for 2.79 for it's speed. however i'm very happy with the old 1.6 because all is working good. i would prefer more the interactive integration instead of newer versions. but it's just my point.
That level of integration won't be possible until it is added to the standalone which won't be in any current release. Of course I could do it now but the performance would be unbearable and it is a lot of work for something that won't be usable.
sad... maybe in the next life :) ok. then i would stay on 2.79 with new corona. :) thanks
-
it's a very known thing already. a hue/saturation is a tonemapping operation. so you have to use a "tone mapping" node alongside "hue/saturation" node.
Perfect! Thank you!
-
it's a very known thing already. a hue/saturation is a tonemapping operation. so you have to use a "tone mapping" node alongside "hue/saturation" node.
Perfect! Thank you!
glad to help
-
2.8 definitely
2.8 will attract a lot more users to Blender, and likely, many of them will be looking for something better than Cycles, at least for achviz. Therefore it makes a lot more sense :)
By the way thank you very much for all the effort put into the exporter! :)
-
i'm coming with a little sugestion. since the exporter works with corona v2 while rendering it's a "solution" to make the exporter working with two different binaries. one for material with old corona and another one for final rendering. what do you think? a temporary solution for using v2 of corona with actual exporter.
-
While its understandable that people want 2.8 support, as it stands developing addons for blender 2.8 is being actively discouraged due to upcoming changes in the python api. https://code.blender.org/2018/06/beyond-the-code-quest/ (https://code.blender.org/2018/06/beyond-the-code-quest/)
it might be more worthwhile to focus on getting to know corona 2.0 better.
-
Personally I think that if I can get my hands on Corona 2.0 first then i'll be happy. Because I use Blender and Corona, half of the cycles features are unusable anyway. Plus 2.79 has been good to me for the past (year?), so 2.8 isn't so important to me right now. The features for Corona 2.0 though... they look amazzinggg
-
So how does this look atm? With 2.8 being finalized can we expect Corona addon? Is there someone actively working on this?
-
When I first started this thread I tried blender 3 but the add-ons weren't possible. I will revisit that as blender gets closer to a release. One thing we will lose is change detection. So using proxies will be the only way to speed up the export process.
-
Addon's have been told to wait until the first beta release where the blender python api will be stabilised. That will be in the next week or two so I will start back on it then.
This is a massive change though so don't expect a working plugin this year, likely sometime in Jan/Feb.
-
The BETA is out and the devs have given the go-ahead to start addon development!
-
On it
-
On it
Actualy even though they stated it is now in beta, according to the post at blender.org API is still being finished, so I guess it could still break the addon.
-
First of all, thanks for the work already done.
Since the beta has already reached the state in which it is possible to work in it, is there any progress in the work of the 2.8 plugin?
We will be happy to do a beta test. :D
Because now I am standing at a crossroads, stay at 2.79 with corona or study 2.8 without it.
-
There is a massive change getting it ready for 2.8
Basically none of it will work without rewriting the exporter which is about 50% of it.
I very rough estimate 200-300 hours work. Combine that with Corona doing a new file format I will wait and do them together.
-
Sounds good to me, worth the wait.
And another question, is there Corona Distance Map shader awailable in Standalone 3 ?
-
I haven't seen it documented anywhere does it export from Max?
-
It works in Max since 1.5 version I guess
-
It works in Max since 1.5 version I guess
Yes, but does it get exported for rendering with Standalone (ie. like on a client, over network)?
How to render using Corona Standalone? (https://coronarenderer.freshdesk.com/support/solutions/articles/5000547357-how-to-render-using-corona-standalone-) @HelpDesk
-
It works in Max since 1.5 version I guess
Yes, but does it get exported for rendering with Standalone (ie. like on a client, over network)?
How to render using Corona Standalone? (https://coronarenderer.freshdesk.com/support/solutions/articles/5000547357-how-to-render-using-corona-standalone-) @HelpDesk
Unfortunately I can not reproduce it, I do not work in Max
-
Just tested with latest build - Corona can't export distance map to standalone.