GeometriX's Forum Posts

  • I've never experienced this. I use Chrome for 99% of my testing (I know, that's probably not a good idea), and this hasn't come up for me before.

    So it could mean your Chrome is out-of-date, or there's some weird bug/incompatibility in your game, or there's an actual bug in C2 or Chrome.

    Could you post your capx, or attempt to replicate the issue with a simplified example?

  • trim("Hello My Name Is John")

    Manual entry on system expressions

  • This isn't a bug.

    When you use apply the physics behaviour to an object, any other motion you give it directly conflicts with the physics. You're basically telling C2 "this object is bound by the laws of physics", and also "spin this object because I said so" - which are conflicting messages.

    First, you should use the "apply torque" action to rotate your lab instead of simply rotating the sprite. But this requires that you set immovable to no, which is obviously a bit of an issue because the lab would collapse to the ground. I'd suggest that you create a new, invisible or visible, non-collidable object (a "pin" so to speak) and bind the lab to that with a revolute joint. Set the pin to be immovable, effectively trapping the lab in place but allowing it to rotate freely.

    You should also alter the density of your sand and lab objects to better represent their approximate mass in the real world (so the sand doesn't "push" around the lab).

    Here's an updated capx for you.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • This is something I've had to deal with a number of times, and for the life of me I can't figure out how to do it. In the past I've resorted to certain objects being made up of nine different collision boxes to get something workable, which obviously isn't appropriate for every situation.

    If anyone can offer advice, I'd gladly listen to it, too.

  • ome6a1717 Post your capx so we can take a look.

  • BluePhaze, oh, right you are then. Didn't realise that was what you meant.

  • BluePhaze, you don't need to convert number to a string to display in text boxes. Text boxes can display any content directly, including arrays, and numerical and even boolean variables (although it converts the latter to 0/1)

  • ome6a1717, there isn't a tutorial that I know of. Maybe it's worth me writing one, actually. But you can read up the basics here. Shout if you need help.

  • Supporting multiple screen sizes tutorial.

    I'm not sure about the white line issue, but unless there's a specific reason why you chose PhoneGap, I'd suggest exporting to CocoonJS instead.

    Can't help you with those other issues, sorry.

  • I'm certainly not a veteran, but I've found that this is generally a very active forum. But you have to realise that it operates 99% as a technical help forum, since it's flooded with newcomers who just need help getting a thing right.

    Also, if a topic seems dead, most of the time it's because the help request was too vague, poorly worded, uninformative or, sometimes, too complex.

    I wouldn't really consider talking about general game design, ethics or practices here because, frankly, there are forums better suited (and designed) for it. But as a place to discuss Construct, this is perfect, and I would never have purchased C2 in the first place if the forum members here weren't so damn helpful.

  • Use "Rotate towards position" instead. Use a low value for the degrees, like 1 or 2, and it'll be buttery smooth.

  • Wait, why are you declaring whattoshoot so far down the list of actions. Surely it should be set first, as the shooting action takes place?

    I.e.:

    On turret shoot -> set whattoshoot random etc.

    sub-events:

    whattoshoot = 1...

    whattoshoot = 2...

  • You probably shouldn't be duplicating menu/UI elements across your layouts, anyway. If you make one change down the line then you'll have to go through each layout and make the changes again. Probably why you're getting bothered enough to request this feature.

    I suggest either building your UI elements with events (use a common event sheet called "UI" or something, and include that for each layout's event sheet), or create a single global layout that's persistent across each screen.

  • Text boxes, or the text object? Text boxes are for receiving input, text object for displaying text/strings/variables/whatever.

    If you are using the text object, though, what seems wrong?

  • When you drag an instance in from the object pallet it creates a new instance with default settings. If you want to duplicate an instance already in the layout, click and drag that object while holding Ctrl, and it will also duplicate its settings.