Not an actual solution, but what if you first load the font, then set the text to something but have it invisible or with 0 opacity for a second (with the wait action) and then set it visible? I also have noticed this popping, it lasts for a few ticks and it only happens once per game session. I believe that this will hide it. Think of it like a workaround.

lucid I'm glad to read about a set time frame. Christmas will start at late November this year! My wish for Santa is to have some good & practical tutorials giving examples and explaining how to use Spriter's advanced features in C2. Like setting up and triggering collision boxes, variables, action points, audio etc... And workflow practices, like using character maps for crowd npcs, or a setting up a scene that has multiple Spriter objects...

winsonzhong ,

I think they 'll add it sometime after the v1.0 release.

Yes, this is very helpful, thank you very much for making it

Aphrodite , thank you for the clarification. It's the concept behind some actions that confuses me. Since I am not a programer and I am introduced to programming concepts within Construct, I feel that sometimes the logic is very clear ("do x get y"), however the lack of foundational knowledge (in programing) other times make the logic behind conditions and procedures feel somewhat obscure. I can't really put in in words, it's more like a feeling, some steps seem to be way steeper than others. Perhaps this is something that someone that has a background in programming doesn't experience as vividly as I do.

Enough psychoanalysis for one post though, thanks again for the information ;o)

fldr , there is a custom plugin called SpriteSheet by R0J0hount. It can act as a scalable Tilled Background and in fact, it offers animatable x,y offset values. The Downside is that it only shows the effect of the tilling at run time. Still, it can be very useful and it's a step forward the right direction which is tillable, animated sprites!!! (coming soon I hope)

shinkan , ok, but will they happen incrementally, or it will just go from 0 to 1000 at once? And if they do happen incrementally, isn't this adding more calculation time between each tick? I mean, surely a repeat 1000 times event should demand 1000 more calculations than just a single every tick event (both having the same actions). I hope I am not as stupid as I feel right now 8/

Thanks

Thank you Iolva

I am not sure I see the problem with the meander textures. Are you perhaps referring on the fact that every 5th vertical line is a bit thicker than the others? If so, I am sure that you can avoid that in Ps. Just use the offset effect and you will notice it there also.

As for Icarus, since it isn't a tilled texture, you can't really see any problems. On the other hand, I see now what you mean. You want a way to resize the sprites. The Icarus sprite isn't actually reduced in pixel information. The original pixel dimensions are intact. While the TB image is downscaled either from within C2 or in Ps. The downscale is what causes the artifacts. There isn't anyway around this however, you' ll have to predetermine the actual pixel dimensions for your TB textures. C2 (for the moment) only repeats the original dimensions.

Scaling sprites also introduces some artifacts but since most of the time you wont have repeating/tilling sprites you don't noticed very much. Scaling an image on an external image editor (like Ps) does produce better results however (in my opinion). So, perhaps do the scaling in Ps or gimp (you can also check for seems on those software and fix them on the spot) and after that import them into the Tilled Background object.

Aphrodite , may I ask what happens with the loops? When for example we have something like this:

-everytick ----> set Sprite X to self.X + 30 * dt

-Repeat 100 times ----> add 1 to variable Y

-etc

The Repeat event how much does it "last" when C2 reads the Event Sheet? I know that without the repeat 100 times, C2 will add 1 at every every tick, but with the loop condition what is happening under the hood? Does the program "halt" until the CPU adds the 100 values and then it continues to the next event?

I am a bit confused with the looping logic in programming

danno55 , sorry for highjacking your topic, but I thing there is some relevance into this.

Ok I did a test and realized that if you want to have the enemy waves in the following order [normal wave, normal wave, Boss wave, ...] then you'll have to use WaveVariable % 3, not % 2.

Here is a practical example.