mumu64's Forum Posts

  • hi, C2 (r178) keeps previewing in a particular browser, even after I changed the preview-browser in Preferences (and closed C2, all browser windows and restarted pc).

    I was wondering if other people had this and what I can do to change my preview browser. I could not find anything in the forum by searching on "previewing in browser" or "can't change browser preview".

  • What happens if I use podes html5 iframe plugin, admob and Crosswalk?

    It will not display ads?

  • Scary to post, but do you want to have a look at my small game?

    https://play.google.com/store/apps/deta ... e.shortest

    Thanks.

  • KFC perhaps the loop delay is caused by the size of the file. Would that be possible? Maybe if you try cutting it in 2 , 3 or 4 pieces, it would not have a delay?

  • I am interested in replies on this thread, so I am replying.

  • I am wondering if anyone knows if this is misdoing on my side or a bug/compatibility issue.

    Thanks.

  • > I think you can use this action to enlarge the sprite and replace the "+" for "-" to decrease the size.

    >

    > action

    > --> set width = self.width+10*dt

    > --> set height = self.height+10*dt

    >

    But I cannot use every tick there isn't it?

    Then the ball travelling diagonal will decrease in a different rate than when travelled straight?

    How do I use it in reference to it's Y rather than leaving it to time?

    Thanks for response

    This is what I quickly can come up with, but if this works, it only makes the ball bigger, when moving up on the Y-axis, instead of smaller. (perhaps it needs a negative value somewhere to inverse it? Poor math skills here)

    Start layout:

    BeginY (Y of where player near camera stands) - EndY (where other player stands) = glob var Difference

    set BallOriginalSize to (ball.width, ball.height)

    every tick:

    set Distance to BeginY-Ball.Y

    set VarThatSetsSize to Distance/Difference

    SpriteBall: set width to VarThatSetsSize * BallOriginalSize

  • I think you can use this action to enlarge the sprite and replace the "+" for "-" to decrease the size.

    action

    --> set width = self.width+10*dt

    --> set height = self.height+10*dt

  • You do not have permission to view this post

  • Would it be useful if Scirra spends 1 or 2 C2-updates about 5-10% on new features, 20-25% on bug fixes and the rest of the time on a better performance?

    I am not complaining about features, bug fixes or performance, but I am wondering if this would be useful. (since it already seems an already complete package)

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • I think it is only semantics, but I am curious in comparing. It helps me, for instance, to get more knowledge about C2.

    Can C2 be seen as a game engine, just like some games are "powered by Unreal Technology" (using the Unreal engine)?

  • Can I get an e-mail or Scirra-notification when a new update of iframe is released?

  • > What would be the efficient/elegant way?

    >

    ... Don't use text object on mobiles. Instead use one spritefont and make 5 instances (one for each option)

    I will, from now on.

    Text objects demand more memory?

  • First set touch sprites and options text as container of each other so they get picked together.

    First off, thanks for the reply.

    Do you mean: I select one textobject and press: add container and select a touch sprite. Then go to the next textobject and select the corresponding sprite object?

  • On screen I have: Option 1, option 2, option 3, options 4, option 5. (text objects)

    When you touch option 1, I want it to have opacity 100 and the others opacity 30.

    I also added square sprites on top of each text object, so that the user has more space to touch the option.

    Option texts are put in family OptionsTextFamily.

    Square touch sprites have been put in family OptionsTouchFamily.

    What would be the efficient/elegant way?

    The not elegant way is:

    On touch TouchSprite1 --> set options1Text opacity to 100

    set options2Text opacity too 30

    set options3Text opacity too 30

    set options4Text opacity too 30

    set options5Text opacity too 30

    On touch TouchSprite2 --> set options1Text opacity to 30

    set options2Text opacity too 100

    set options3Text opacity too 30

    ... and so on.