Instances vs. Objects

What is best for speed and size of game?

1. Many instances of as little objects as possible.

2. Many objects to as little instances as possible.

And why you think so?

I normaly try to do 1.

Because I have seen that every tileMap for example saves its picture to output, even they have the same...

I think thats for most other objects, too.

Since I had seen this, I only create needest objects.

Can for example look like this:

No one with an opinion?

I do not need 100% statements!

As far as my understanding of how the c2 engine works, you will get less gpu demand if you use one sprite with the same image rather than lots of different objects with the same image (draw calls are per object).

However, this will probably only achieve measurable gains on a low end mobile. And as soon as your project takes on a few thousand events, I imagine that you will not enjoy easily using one of c2's strengths - the layout editor. It would be difficult to edit and manage a game with only a couple of objects, and optimization techniques like render cells work on objects not animation names, so there could be balancing performance losses by doing this...

I would advise you do a performance test on the platform you are targeting - because any gpu gains might be offset by a collision checking load or other extra events you have to put together to manage your technique.

Also, don't waste your time.

To Organisation, for me I can say, its much better. I faster find anything I search. But that has much to du with order all!

Im also more a programmer as a designer, may be thats why I habe no problems to organize that. I order them in some sheets and groups, I separate function and creation. The sheet you see has only creations. By copy paste l create a new menu part in a minute.

In objects I search hole day to find anything... and mostly i take the wrong.

The last parts of your post are interesting, I will think about this things. Thanks for your opinion.

My english is bad, but with smartphone its a real horror! Sorry!

The answer is 1 since Construct2 reuse the sprites created in memory thus cloning will consume as little memory as possible, whereas when you create many sprites, then C2 has to memorize all these sprites thus consuming more memory!

I think you also better use spritefonts if you want best performance, works pretty much thesame and is faster, more important if you have moving and updating text..

I think you also better use spritefonts if you want best performance, works pretty much thesame and is faster, more important if you have moving and updating text..

Instead of Text("ButtonText")?

instead of regular text plugin yes, buttons could be graphics and are faster and more ways too change look, depends strongly on what you need it for, it might be better too make the app first , then to get caught in optimizing like its mentioned, just letting you know

instead of regular text plugin yes, buttons could be graphics and are faster and more ways too change look, depends strongly on what you need it for, it might be better too make the app first , then to get caught in optimizing like its mentioned, just letting you know

Buttons are grafics... And the text on is Text.

I do not think that graphics are faster than text, but I dont know it...

If you write the app sloppy and optimizing it at end you are a bad coder... Sorry, my opinion, no offense.

you dont have too believe me but they are faster, these are choiches you have depending on what you need from the app, its not sloppy, making optimizing that have little impact is counterproductive, ofcourse there are general programming rules that make for better code and should be used

I'll be watching spritefonts.