Updating project from 0.99.96 to r2?

This forum is currently in read-only mode.
From the Asset Store
Fantasy Game includes more than 600 sound effects inspired by hit computer games like World of Warcraft and Diablo.
  • So,

    I'm returning to construct after a lengthy absence... My project was originally developed on Construct 0.99.96. It still seems to be working on THAT version of the program quite well.

    But I was hoping to update to R2. Unfortunately, when I try to load my game into R2 (after adding back in the "orbiter" plug-in from my old plugin folder) the game suddenly starts to behave rather strangely.

    It's a Space War/Asteroids type game... And in R2 the player ships (which use box physics) move at about 50 times normal speed, turning and flying insanely fast... They also randomly get stuck whenever they're supposed to be wrapping from one side of the screen to the other (I created a simple wrapping event of my own in 0.99.96), and they shoot bullets (which also use physics) that some times move at lighting speed and sometimes don't move at all.

    Thinking maybe this was just something that was changed in R2, I tried the project out on Construct Classic 1.2 as well with the exact same results.

    So, I have to assume were there changes to the box physics behavior from 0.99.96 to 1.2/R2? If that is the case, is there anywhere these changes are documented so I can made adjustments to my project? If there were no changes, does anyone have any ideas what might be causing these speed up effects when using R2?

    Any help greatly appreciated! Thanks!

  • Ah yeah, I remember somewhere between the 0.99's and 1.0's there was a change in the Physics engine (maybe an entire switch from Newton to Box2D?), but it should work the same after you lower your values down.

    To move a physics object now as of R1.2 you can store the old X and Y velocity, disable the physics behavior, move the object, then re-enable it and set the X and Y velocity to the previous value.

    Also, there is a layout size limit of 20,000 in each direction for the physics engine I think, otherwise the physics objects will just stop.

  • it should work the same after you lower your values down.

    I was guessing it might be something like this... Any idea about how much these need to be lowered? I guess I can just play around with the numbers a little.

    To move a physics object now as of R1.2 you can store the old X and Y velocity, disable the physics behavior, move the object, then re-enable it and set the X and Y velocity to the previous value.

    This part kind of lost me... Did you mean I have to do this in the event sheet? Just lowering the values will not fix my problem?

    Could you elaborate a little? I'm really rusty on all this stuff!

    Thanks!

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Yes, for "teleporting" objects you'll need to do that in events sorry for the confusion!

  • Yes, for "teleporting" objects you'll need to do that in events sorry for the confusion!

    Right! Got it! So far, no teleport in the game. But I was thinking of adding it so that helps.

    Thanks again, you the man!

  • Okay... So this is interesting.

    For each of the ships in my project, I have added phycics behavoir. So if I select one of my ships in the layout editor, under the properties tab there is a PHYSICS section under the BEHAVIORS menu.

    If I load in my working Construct 99.96 project into Construct R2, all the values in this PHYSICS menu are the same. The MASS value I have for my ship is set to 1.4.

    But, as I stated before, the ship moves too fast under Construct R2.

    But, it turns out, if I go in an RETYPE the mass value at 1.4 -- I don't even have to change the number, just type it in again -- the ship suddenly flies at the correct speed.

    So, clearly something about the 99.96 file format is being read incorrectly by R2.

    Now, I still have another problem. I have a simple Edge Wrap event in my project. The idea is if a ship flies off one edge of the screen, it appears on the opposite side (exactly like the game Asteroids.)

    There was the WRAP BEHAVIOR back when I was using 99.96 but it didn't work for me because of (I think) the shape of my ships... if you approached an edge slowly, the ship got CAUGHT there -- jerking a little back and fourth but never able to wrap to the other side.

    Well, that problem is back with R2... Here is my wrap Event sheet:

    <img src="http://i232.photobucket.com/albums/ee215/JDoejoe/Wrap_zpsb70ec6f4.jpg" border="0" />

    Works great in Construct 99.96 but not in R2...

    Does this fall under the "Teleport won't work with physics since r1.2" you were talking about jayjay? I'm assuming the WARP BEHAVIOR will also not work with a physics object? Does anyone have code for a PHYSICS WRAP/TELEPORT laying around that I can look at?

    Thanks!

  • Glad to hear! And here's an image of what I mean to instantly move a physics object as of R1.2 and up:

    <img src="https://dl.dropbox.com/u/4714446/ExamplePortalMove.png" border="0" />

  • Glad to hear! And here's an image of what I mean to instantly move a physics object as of R1.2 and up:

    <img src="https://dl.dropbox.com/u/4714446/ExamplePortalMove.png" border="0" />

    That did it... Project now working in R2! Thanks a million again!!

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)