Poll

3 features you want the most:

PBR Style material (Disney, Unreal Engine, etc..)
98 (9.8%)
Refraction/Reflection working with masking render elements (CMasking_Mask,CTexmap, etc...)
65 (6.5%)
Render-time booleans (cut/slice objects)
59 (5.9%)
Dedicated CarPaint Shader
22 (2.2%)
Memory optimization (lower memory usage in 3ds Max; not out-of-core)
77 (7.7%)
GPU/Hybrid rendering
135 (13.5%)
Displacement improvements (2D displacement, autobump, memory efficiency, ...)
64 (6.4%)
Speed improvements
109 (10.9%)
Cryptomatte
35 (3.5%)
Geopattern
106 (10.6%)
Toon shader
38 (3.8%)
Reworking tone mapping (DSLR-style tonemapping)
112 (11.2%)
Interactive rendering in 3ds max viewport (with gizmos, object selection, manipulation, ...)
34 (3.4%)
Adding own materials to Corona Material Library
46 (4.6%)

Total Members Voted: 412

Author Topic: The most wanted feature?  (Read 219066 times)

2018-11-26, 12:02:22
Reply #585

romullus

  • Global Moderator
  • Active Users
  • ****
  • Posts: 5802
  • Let's move this topic, shall we?
    • View Profile
    • My Models
I don't know, since i discovered Connecter, Corona library lost its appeal for me.
I'm not Corona Team member. Everything i say, is my personal opinion only.

2018-11-26, 12:17:14
Reply #586

Juraj Talcik

  • Active Users
  • **
  • Posts: 3629
  • Tinkering away
    • View Profile
    • studio website
I also hope much resources won't be wasted on this. Connecter (free) or SigerLibrary (the empty one without materials is super cheap) are million years more advanced already right now.
talcikdemovicova.com  Website and blog
be.net/jurajtalcik   Our studio Behance portfolio
Instagram   Our studio Instagram, managed by Veronika

2018-11-30, 04:01:28
Reply #587

paulosamsam

  • Active Users
  • **
  • Posts: 6
    • View Profile
Ornatrix hair motion blur is essencial... its currently not working...

2018-12-03, 16:43:07
Reply #588

Otuama

  • Active Users
  • **
  • Posts: 22
    • View Profile
Coming from using Vray for years we're starting to bend towards Corona more and more.

What I love about Vray - and HATE in Corona is the way the Corona VFB handles renders.

If you store an image in the Corona VFB history you can only save out the base image.

Render elements aren't saved into the history so you can't save out any render elements.

In Vray - If you double click a render in the history, it opens up in the VFB (and loads elements in too).  You can then 'Save All'

In Corona I don't think you can do it.

Is there a fix/workaround for that?


2018-12-05, 17:52:16
Reply #589

oddvisionary

  • Active Users
  • **
  • Posts: 194
    • View Profile
    • Behance | Artstation : artstation.com/oddvisionary
Coming from using Vray for years we're starting to bend towards Corona more and more.

What I love about Vray - and HATE in Corona is the way the Corona VFB handles renders.

If you store an image in the Corona VFB history you can only save out the base image.

Render elements aren't saved into the history so you can't save out any render elements.

In Vray - If you double click a render in the history, it opens up in the VFB (and loads elements in too).  You can then 'Save All'

In Corona I don't think you can do it.

Is there a fix/workaround for that?

I don't want to be mean but you cannot say you hate it if you haven't learn it yet. Yes you can, actually Corona VFB is very flexible and easy.

How to : Corona VFB Window > Save Icon > Put the mouse OVER and HOLD > Save as CXR = Corona own format for saving all the elements you added.

Now you can close Max or C4D, and open the CXR file using Corona Image Editor, you have all your render elements + post FX + light mix.

Let me know if you need more help.
- Jin
Freelance Post-Prod / Lighting & Look Dev 3D Generalist | VFX Designer | Sound Effect Recordist & Sound Designer

Corona Discord server : https://discord.gg/2uxq8EA

2018-12-31, 00:12:49
Reply #590

zokni

  • Active Users
  • **
  • Posts: 8
    • View Profile
I really hope this whole poll means the first three goes to the next release (v4), at least this one:
Reworking tone mapping (DSLR-style tonemapping)

Am I right?

2018-12-31, 10:39:36
Reply #591

romullus

  • Global Moderator
  • Active Users
  • ****
  • Posts: 5802
  • Let's move this topic, shall we?
    • View Profile
    • My Models
If you want to see better picture of what to expect in upcoming release, then look at the roadmap: https://trello.com/b/EfPE4kPx/corona-road-map-3ds-max

The poll in this topic is just a guide for devs to see what features are on demand by the users, but it's not an indicator of whether those features will be implemented and when.
I'm not Corona Team member. Everything i say, is my personal opinion only.

2019-01-01, 14:59:06
Reply #592

bluebox

  • Active Users
  • **
  • Posts: 174
    • View Profile
If you want to see better picture of what to expect in upcoming release, then look at the roadmap: https://trello.com/b/EfPE4kPx/corona-road-map-3ds-max


Don't want to be mean, but is this the case :) ? Slicer-clipper was postponed at least for 4 major releases now.

We got into this trap of starting an ongoing project in Corona because clipper was due to be released in the next upcoming version and now we have to resolve to cumbersome workarounds with distance maps...

If you can't really fully trust trello, nor this topic then what is the sense of both ?

2019-01-01, 15:51:01
Reply #593

romullus

  • Global Moderator
  • Active Users
  • ****
  • Posts: 5802
  • Let's move this topic, shall we?
    • View Profile
    • My Models
I believe i don't have to remind you, that there are only two certain things in life... ;] I think team has firm reasons to postpone some features in favor of another ones. Maybe they decided that ROI of those features would be too low at this moment, maybe they got instructions from above, maybe... i will just shut up.
I'm not Corona Team member. Everything i say, is my personal opinion only.

2019-01-01, 16:35:20
Reply #594

bluebox

  • Active Users
  • **
  • Posts: 174
    • View Profile
This was more of a rhetorical question but thank you Romullus.

Just wanted to point out that people working on a specific rendering engine try to streamline their work and optimize it (yeah capt. obvious :] ). Switching from for example Vray is a huge commitment of time and therefore money investment.

I of course understand that huge amount of people want huge amount of features and having limited resources (developers) the company has to choose which ones to implement at a given time taking into consideration all the factors that you mentioned.

But telling people that something will be done and not doing it for over a year (I think clipper was due to be released in 1.6) is not entirely Fair in accordance to FairSaaS in all of its glorious aspects ;)

And clipper is just an example here. Just trying to figure out what is the key factor that pushes any given feature into production. For example Disney material is at the top of the poll in this topic for a looong time. And it just sits there :)

2019-01-01, 22:58:58
Reply #595

lolec

  • Active Users
  • **
  • Posts: 81
    • View Profile
I've been on both sides of product development and let me assure you a few things.

-Decisions are unimaginably more complex for the corona team that what you think
-They spend 100x more time thinking about these issues than any customer ever will.
-And based on what I've seen, the Corona team is also working very very hard and they have absolutely no reason not to build the best product they can.

I know, as a customer, there is a small set of features that are disproportionately more important because of your specific use case, and it can be very frustrating when the product priorities don't align with yours.

Just remember that there are hundreds of use cases and hundreds of "hidden" complexities in running a business and building a product.

This is not to say that we as customers should shut our mouths and just wait for the dev team to do their best, but I find that complaining is not the most useful thing we can do, here is what I think it's better:


- Understand WHY a feature is not here, sometimes it's not used by enough people, sometimes it's too complex to build, and in some rare cases, the feature is being overlooked by the dev team.
- Build a strong case on why a certain feature is important and try to get more people to support the idea and help the dev team see something they might be missing (like a market trend, new tools, new workflows etc.)

In the end, I don't think neither this poll nor the trello should be used to inform future jobs we take, we should use them as tools that reflect vision and trajectory, as I currently interpret both of these are:

The poll: People are liking the results from Fstorm and other GPU renders and would want to have those goodies in Corona too. (geo pattern, tone mapping, gpu) Second, the industry seems to be moving to PBR and people are starting to miss proper PBR support in Corona.  Most of the other items seem to have niche support and not general support.

The Trello: Seems like the Corona team is focusing on closing on "essential" features before jumping to new features: stable light solver, caustics, clearcoat, volumetrics. These are MUST have features for any production-grade render. This is a sign of maturity for the product. 
 
I don't expect they will focus in too many new features until Corona is stable and robust as a production render, something a studio can pick up knowing that it will work for them 99% of the time and they won't need to hack or fake stuff out, or switch renders in a few years. Once that is solid as a rock, I would expect they would start exploring things.

Exploring things means breaking things, and when client's livelihood depends on your product, you can't be as aggressive with new features. Fstorm can get away with whatever they do because pretty much no one is using it for "serious" work.





2019-01-02, 10:09:01
Reply #596

karnak

  • Primary Certified Instructor
  • Active Users
  • ***
  • Posts: 66
    • View Profile
Thank you lolec, I think your message has very good insights and is very respectful of both consumers and the development team.
Corona Academy (May 2017)

2019-01-04, 11:29:59
Reply #597

Jpjapers

  • Active Users
  • **
  • Posts: 1206
    • View Profile
Really good response there and it makes sense to do whats best for the company. I think a fair bit of frustration from what ive seen comes from the development fstorm has in some areas and its just one man doing the dev. It seems fstorm has stuff corona doesnt but corona has more necessary and production ready stuff than fstorm.

I agree that it seems ridiculous that some features get pushed back release after release. I originally asked for the clipper in 2014 i think. But there are some features like a proper PBR material and like Geopattern or Reworked tone mapping that make larger parts of the production pipeline easier and id rather have those completed first. Clipper would make a very specific part of the workflow easier yes. But it wouldnt make as much difference as a proper PBR material would.

2019-01-04, 15:54:12
Reply #598

bluebox

  • Active Users
  • **
  • Posts: 174
    • View Profile
Really good response there and it makes sense to do whats best for the company.

I agree that the company must do what is best for itself. We as companies or freelancers do the same. What I do not understand is why from one point of view people say that we as the users should not keep our mouths shut about the development and on the other hand each time someone decides to speak up some other person appears arguing that there should be no complains because the corona team does super job providing us this great plugin.

I agree that Corona is great. I love working using it. I respect the developers. But we are all buing a product here, and doing so in SaaS way part of what we pay goes to fund the development.
So the everlasting narrative of being eternally gratefull to the Devs for doing their job that some people present is getting irritating.

I would love to meet Ondra some day for example in Venice and talk about ponies and stuff over a beer or something and make friends. But I firmly believe this kind of stuff should be done off the forums ;)

If a feature was promissed and it doesn't get delivered I do not see a point why users should not talk about it.

I agree that it seems ridiculous that some features get pushed back release after release. I originally asked for the clipper in 2014 i think. But there are some features like a proper PBR material and like Geopattern or Reworked tone mapping that make larger parts of the production pipeline easier and id rather have those completed first. Clipper would make a very specific part of the workflow easier yes. But it wouldnt make as much difference as a proper PBR material would.

I completeley agree. I asked a question about this in the daily build section but it wasn't answered. I also believe that the product should be built logically from the ground up. If proper PBR shading is a standard these days such shader should be IMHO one of the first things to implement so users building their material library won't be forced to rebuild it as a whole and reshade all their assets, and instead build them with correct shaders from the beginning.
Same goes for tone mapping.

I also would have those features paired with mentioned geopattern sooner than even mentioned clipper. Clipper was just an example here.

2019-01-04, 16:11:09
Reply #599

TomG

  • Corona Team
  • Active Users
  • ****
  • Posts: 2564
    • View Profile
Just a quick note, no-one should keep their mouths shut :) We do always welcome hearing requests, whether that is for something never asked for before, or a request that someone notes "I first asked for this back in 2017". We don't take that as criticism, just as a reminder.

That said, we do ask that people understand that their request is a request, and while we do listen to and consider every request, that won't always mean we implement every request; and that people keep in mind that prioritizing development is a balancing act between a lot of different considerations, so if we do implement something, when that happens may be quick or may take a long time, or even may change (we think we can do it, but other things come up in priority and it gets pushed back). So, feel free to remind us it's a long standing request, but please don't yell at us :) Which I don't think anyone has been doing, to be honest, it's all been respectful. And I think the system is working well for both developers and users!