I am still using Construct 2 and don't really see a need for Construct 3. I get your point, but it depends on what you're targeting.

As for Adobe, yeah, exactly, I still use CS 5.5

What I would like to see is a plugin for CPM Star ads. I started a new topic about it, but seems nobody cares, and mobile builds that work straight out of the build service without the need for any additional steps ( as far as I know you can still only build a test version and additional steps are needed before you have a store ready app )

Then I will probably get Construct 3. Right now version 2 seems fine, and too many projects going on to just transfer them to v. 3. I will finish those in version 2. I don't want any surprises.

I paid on average $700 each year, for about 5 years, to Autodesk for maintenance of Softimage ( 3D modeling and animation ).

That is pretty much the same as subscription. Gave me continuous access to all new features and so on.

In those 5 years I think they added some 3D cube in the upper right corner which you could click on and rotate to rotate the view. Never used it because you had always been able to do exactly the same thing by holding down the S key and using your mouse to rotate.

So about $3500 for that. Then they decided to kill off Softimage and tried to force everybody to switch to their other 3D programs, Maya or 3DS Max. Fortunately enough people complained about it, so they decided to let us use Softimage perpetually.

Right now they only offer subscription and prices are insane, so I quit the whole thing, but at least I can continue to use the latest version I had registered when I let my maintenance contract expire. There is pretty much no functional difference between Maya 2018, Maya 2015 or Softimage 2015 vs. whatever year . It's all the same thing. That is why they and a lot of other companies want subscription. There simply isn't anything left to add to warrant upgrade prices, so they want to force you into software rental instead of ownership. Same for audio software, video, whatever. It all peaked a long time ago. It is all the same thing now as it was 5 years ago or even 10 years ago. The only thing that's different is support for newer file formats, video resolutions and so on. Actual editing, modeling, animation, whatever software does is exactly the same. If you look at Construct 3 vs. 2 you will see pretty much the same thing.

For me nothing clears up until it is finally available and I can use it and test it myself.

I know I could already, but I will wait until it's done. ( We are talking about this completely new C3 runtime or just a regular C3 runtime ? )

I don't use any plugins that need to be ported and I am still on Construct 2. Mostly because I do not see anything in version 3 that I need right now.

No problems with performance with Construct 2 ( so far )

Benchmarks ( of all kinds, not just Construct runtime ) , for the most part are bullshit, I only care about real life performance. Game either runs fine or it doesn't.

If they made sure ads worked perfectly and if I could export everything directly from Construct 3 ( working APK, iOS versions, whatever ) I'd gladly give them $500 a year, but right now, v. 3 is not quite what it's supposed to be.

That should be easy with some events

Let's say each letter is of same size , about 50 x 50

Each letter has an instance variable scale which can be 0 or 1. When 0 then it should be 50 x 50, when clicked scale var changes to 1 and that letter should be 75 x 75. That is the idea.

Execution would be something like this.

Every tick:

If instance var. scale = 1 and width < 75 set width. Letter.Width + 1 and width. Letter.Height + 1

To scale down do the opposite: If instance var. scale = 0 and width > 50 set width. Letter.Width - 1 and width. Letter.Height - 1

Now you probably only need a for each letter loop to set var. scale = 0 on all letter instances each time you click, and set it to 1 only on the clicked letter. That way on each click all letters will scale up or down depending on their instance variable changes.

You can also add some variables to limit scaling, once it reaches 75 x 75 it stops there and on scale down stops at 50 x 50