R0J0hound's Recent Forum Activity

  • To be able to restore the window change the script to:

    from ctypes import *
hwnd=Window.AppWindow
region=windll.gdi32.CreateEllipticRgn(0,0,640,480)
oldRegion=windll.user32.SetWindowRgn(hwnd,region,0)[/code:297le7j1]
then later when you want to restore the window shape run this:
[code:297le7j1]windll.user32.SetWindowRgn(hwnd,oldRegion,0)[/code:297le7j1]

  • Python doesn't work too well in 0.99.62, you'll need a newer version since python support has gotten better in newer versions. You can install multiple versions of Construct at the same time, just install to different folders.

  • I did some tests to shed some light on the cause.

    The max y position reached when jumping can be calculated with the following formula:

    StartingY - (jumpStrength^2)/(2 * gravity)[/code:1lcbmjqd]
It seems that the platform behavior goes about 20 pixels higher than what is calculated when running 60fps.
I switched to unlimited framerate and it was only higher by 2 pixels on my computer.

The platform behavior seems to have a more accurate jump height with higher framerates, and a less accurate one with lower framerates.

Here's my test of the platform movements jump height with two other methods of computing motion.
[url]http://dl.dropbox.com/u/5426011/examples3/JumpTest.cap[/url] made in 0.99.96

A workaround could be to set gravity to zero and manually change the vertical velocity every tick with a more accurate method like Verlet.

Hope some of this is helpful.

  • chrisbrobs,

    Method 1 is all that is needed to get it to run: Just extract the zip file and run the cap.

    The fact that construct crashes when you try to open the cap usually means that you are trying to open a cap file made in a newer version of construct than you have installed.

    The example was made with Construct 0.99.96, so you need at least that version to run the example.

    If the crashes occur after opening the cap file when you click "run layout" then it is perhaps another problem. In which case what are the error messages, as they will help me figure out what the problem is.

  • What are the crash messages? Also what version of Construct are you using? The example was made with 0.99.96. If you can't open the cap then either you're opening it in a older version of Construct or the cap is corrupted.

  • Uncheck the Application property "Enable Scripting", unless you are using python scripts.

  • Do you have the Application property "Enable Scripting" checked? That property should only be used if using python. If you aren't using python and that's enabled then construct will crash if ~ 700 objects are created without running any python scripts.

  • After a few minutes of experimentation it would seem that with an "Eye Distance" setting of 500 that a sprite with ZElevation of 250 will appear twice the size it is when it's ZElevation of 0.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • You can add attributes at runtime with the action "System" -> "Add/ Remove attributes from object". Be advised that trying to remove an attribute with that action does nothing as it is not implemented. Another idea if you use sprite objects is you can enable\disable collisions with the "set collision mode" action.

  • Here is a barebones example for making a ellipse window. All the required python files are included in "py.zip" so no python install is needed. Just keep "py.zip" in the same directory as the cap or exported exe.

    http://dl.dropbox.com/u/5426011/examples3/ellipseWindow.zip

  • 1.

    On the AI event sheet change event 4 change "Start of Layout" to "Timer equal to 0" and add a "For each npc_zefi_tier1ship" condition.

    + System: Timer is Equal to 0
+ System: For each npc_zefi_tier1ship
+ npc_waypoint_generic: Pick one at random
-> npc_zefi_tier1ship: Move to npc_waypoint_generic 
[/code:2vp89ioj]
Also on event 7 remove the "Delay 2000 ms" condition as it causes all the enemy ships to be picked.

2.
The fixes for 1 pretty much fix 2.

3.
What PixelRebirth said.

  • To prevent going into the wall you could add a "overlapping at offset" condition to check for collisions before motion.

    + MouseKeyboard: Key Left arrow is down
+ Sprite: [negated] Sprite: overlaps "Solid" : offset (-1,0)
-> Sprite: Set X to.X-1

+ MouseKeyboard: Key Right arrow is down
+ Sprite: [negated] Sprite: overlaps "Solid" : offset (1,0)
-> Sprite: Set X to.X+1

+ MouseKeyboard: Key Up arrow is down
+ Sprite: [negated] Sprite: overlaps "Solid" : offset (0,-1)
-> Sprite: Set Y to.Y-1

+ MouseKeyboard: Key Down arrow is down
+ Sprite: [negated] Sprite: overlaps "Solid" : offset (0,1)
-> Sprite: Set Y to.Y+1
[/code:31phvxjq]
R0J0hound's avatar

R0J0hound

Member since 15 Jun, 2009

Twitter
R0J0hound has 155 followers

Connect with R0J0hound

buymeacoffee.com

Trophy Case

  • 15-Year Club
  • Jupiter Mission Supports Gordon's mission to Jupiter
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Forum Hero Made 1,000 posts in the forums
  • Forum Wizard Made 5,000 posts in the forums
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • Enduring Visitor Visited Construct.net 90 days in a row
  • Unrelenting Visitor Visited Construct.net 180 days in a row
  • Continuous Visitor Visited Construct.net 365 days in a row
  • RTFM Read the fabulous manual
  • Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

28/44
How to earn trophies