R0J0hound's Recent Forum Activity

  • One possible way to do a serial could be the following:

    So say you want the serial to be in the format of

    aaaa-bbbb-cccc-dddd

    1234-4567-8901-2345

    You can then let it be a good serial if

    a+2*b+3*c+5*d is in the range of (55000 to 55005) or something.

    To generate them you could do something like the following which should give you a few good serials.

    repeat 100000 times

    --- set a to int(random(10000))

    --- set b to int(random(10000))

    --- set c to int(random(10000))

    --- set d to int(random(10000))

    ------ a+b*2+c*3+d*5 is in the range (55000 to 55005)

    --------- save as valid serial.

  • Hi, would you consider making a plugin or behaviour out of your 3d object engine, please?

    Probably not. That would mean re-writing it in javascript which doesn't appeal to me.

  • WebMagi

    It's just a matter of using joints to link it together. Then to manipulate it with just physics you can use a dummy object that's moved by the mouse that you connect and disconnect from objects. Here's an example of a possible way to set it up.

    https://dl.dropboxusercontent.com/u/542 ... aunch.capx

  • WebMagi

    I can't think of any examples off hand, but a search for "angry birds" on the forum will give examples of a slingshot which is similar.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • spongehammer

    Haven't started working on it yet.

    WebMagi

    This behavior would be useful for the simulation part of what you're doing. Adding the joints should be as easy as using one of the add joint actions and specifying the two objects and stuff like where the joint should be.

    To make the object manipulable with the mouse you can use something like the drag n drop behavior as a base. To move other objects when dragging one you would need to move them by the same amount, the pin behavior could be used for it.

  • Works now.

  • You do not have permission to view this post

  • You do not have permission to view this post

  • That's cosmetic, the transformation only transforms the object's origin. To complete the illusion of the circle being a sphere the circle's origin would need to be moved to the bottom.

    In your capx you can fix it being off center by not moving the canvas' and have their origins be in the center.

    canvas1: set angle to 0

    canvas1: clear

    canvas1: paste layer

    canvas1: set angle to 45

    canvas2: set height to 480

    canvas2: clear

    canvas2: paste canvas1

    canvas2: set height to 240

    You'll probably want to make canvas2's height to be twice the screen height so stuff will be drawn from the top to the bottom.

    Still in order to not have empty triangles in the corners you'll have to make canvas1 much larger than the screen (that could probably be calculated but it's probably easier to guesstimate).

  • I fail to see how my example that newt quoted is wrong. It's the same as the transform in the op except everything is already rotated by 45. The second example quoted by christina is for a perspective transform, which isn't the same. The main difference is axes of motion in my example are relative to the screen instead of to the iso grid. Other than that christina's example is a valid iso transform.

  • Fizzick

    There currently isn't a way to access that property.

    Valex

    You might be able to set the joints max force to limit the impulses of the joints. Another thing you could try is lowering the fixed time step from1/30 to 1/60.

    —

    Thanks for the bug report, I'll look into it when I have a chance.

  • kayin

    Converting the events over is not so much hard as it is tedious and very time consuming. I wouldn't be concerned with the source code, instead I'd be looking how events are stored in the cap files. I already have that info and can access it with the capreader library I made. The catch is none of the condition or action names are stored, only indexes. Those indexes can be used to get the names from the plugins but I haven't done anything for that yet.

    Once past the technical stuff we then have the events, some of which can be converted over directly. Others have different behavior in c2, and others have no equivalent at all in c2, such as attributes. In those cases it becomes very hard to solve. It would either require generating more events in c2 to get it to do the same thing or write a custom c2 plugin to handle those events. Neither of which sound appealing or easy to do. So instead if we spit out all the events as text in comments it would at least give you an outline where you can insert events and handle different behavior on a case by case basis.