That is definitely possible, but I don't know how.

https://drive.google.com/open?id=0B-xiq ... 0lDRklrNVU

Thank you for responding. Okay, good. I'm glad to hear I shouldn't have a problem making long cut scenes. I have a big vision for this game, I have been planning on making it for a very long time now. And I am getting lots of help on it. I see so much potential in Construct 2 because it's simple and easy to use and since I am not a programmer, it makes it possible for guys like me to make awesome things. So once again, thank you.

Yea, I love Construct. It gave me a less-harsh introduction to JavaScript as a language. I have high expectations for Construct3. The sky's the limit for Scirra, and I could easily see them competing with the likes of Google in the enterprise web development arena.

If I ever finish this game I might start making plugins for sale here, lol.

Yea, you can do anything you want with those variables (within the typing constraints).

random() is a good system expression to learn.

You probably want to use the sprite collision detection, then see if the Physics behavior has a flag something like:

if Sperm sprite is colliding with planet sprite

then

Sperm sprite physics flag = off

then you can just manually move the sperm sprite around the planet object.

It was just that, an idea. I have never gotten it working myself, lol.

You will want to put a wait in there though. The asynchronicity of JavaScript is such that it will break without a short (like 0.05-0.1s) wait in the loop.

AutoScaling.capx

We use dynamic UI rescaling using Viewport.

It is a lot of work, but it works quite nicely. You could conceivably do it only when they resize the screen, but I have it running every tick on my client for now.

Note: This disables the inherent browser zoom though.

Usually, (kind of guessing here, based on past experience), the "secret" should be provided by Google on a per-developer basis. i.e. every developer has their own "secret" code that you include in all of your API calls.

I would ask Google for the secret.

Yea, object references and asynchronicity are the bane of my Construct existence.

I actually started building our website like this (the Load Image from URL way) and ended up going to Pode's iFrame plugin instead, since we needed more than just images.

That pode's iFrame thing is a marvel. You could conceivably nest Construct projects inside other Construct projects ad infinitum. It is nuts.

I have considered doing this for our more intensive UI elements, having independent subprojects that load inside of an iFrame.

You can definitely lerp the opacity.

Something like:

Set Opacity: lerp(0,100,((1-0.09^(x-2))/(1-0.01^(x-2))))

That way you have nice smooth transitions both directions.

Lol. lennaert beat me to it.