@PieceMaker , @Colludium , @shinkan , @glerikud , @spy84 ,
Thank you guys!
@Ashley , thank you for answer!
Yes, I mention many things and features! I could have mentioned many-many more!
I also understand that it is incredibly difficult to develop this software! However, since you are more than capable do develop it (I wish I was half as smart as you are
), why not do it in a way that it could result in a more functional, out of the box, software?
That is, if you agree that the things I mention are indeed helpful and could improve the workflow!
Now, you are mentioning the “cookie cutter” approach, and I agree that as users should be able to make our own systems, however, what I ask is for some basic, standard functions, as a starting point, a system that works well the basics and reacts closely to what we consider as “normal” Light behavior.
Just as I don’t “have” to build from scratch the Platform behavior and how it interacts with the solids (I wish however that it was unified with the Physics plugin, but that’s for another topic), I wish for a Lighting system that provides me with the basic stuff out of the box: Insert a light, set it’s radius, color and falloff, place it in your scene to illuminate some part of it, repeat as you please! Shadows and normal bumping will react automatically and you won’t have to worry about it!
This doesn’t mean that you won’t have the option to add more stuff on top of that! You could still change the blending modes for each light, add colored Sprites of any shape above and blend them with the light, mask out any parts of the light with other Sprites and Destination out blending, add webGL effects to the light etc.… We should be able to do all of those things, and more…
To be honest, I don’t really get how those nested layers could work with lighting, I’m not familiar with the term (I guess they are something like layers within a group like in Photoshop?), and I haven’t seen any other software that use them to understand their benefits. I vote for them however, the more options the better!!!
Anyway, please just keep in mind that there are many good, even great suggestions around the forum that have the potential to vastly improve Construct’s workflow, productivity and end result. Since you are developing C3, taking some of these suggestions into account early on, could help deliver a more robust and complete solution software from the start, rather than adding and changing things along the way, which is something that could cause backwards incompatibility issues, like when we were discussing about the Tilled BG object and if it should be removed-replaced by a more advanced Sprite Object…
Anyhow, who am I to tell you how to run your business, right?!
Please know that I’m just saying all those things out of genuine interest about Construct, the only software development platform that allowed me to express my creativity interactively!!!
I want a better Construct, it will help me be better also!