Ashley's Recent Forum Activity

  • BEFORE you make a post, have a look at these options:

    Tutorials

    If you're new, try a tutorial before asking questions in this forum. Tutorials cover a lot of basic ground and will get you going in Construct much quicker. Find Classic tutorials here: http://sourceforge.net/apps/mediawiki/construct/index.php?title=Tutorials

    Frequently asked questions

    Also, check your question isn't asked on the FAQ before posting!

    Documentation

    Otherwise, check the documentation! You may be able to find what you are looking for there, without having to make a post.

    Read & search the forum

    Many questions have been answered and many problems solved in past posts in the forum archives. The forum has been active for a few years now. Click Search and see if you can find a solution in an existing post before making a new post. You could also try Google with the extra term site:scirra.com which will search for pages on the Scirra website.

    You can also learn a lot simply by regularly hanging around the forums and seeing what kind of posts come up. It pays to be an active member of the community!

    Tried all that?

    Feel free to ask your question, and we hope someone can help you However, remember these important points when posting:

    1) Explain the problem clearly! We don't know what you are trying to do, so make sure you explain your goal and precisely what the problem seems to be.

    2) Post a .cap file! (".cap" is the format Construct saves files in) This can help everyone solve your problem much more quickly if we can investigate what you've done ourselves and try it out. It saves us time from having to set up what you described, and also, you might forget to mention something important you did in your .cap file (which could be the cause/solution to your problem). Also, the simpler the file is, the better. Post a .cap!

    3) Bookmarked events help others find the events you're talking about in larger projects.

    4) If it crashes, it's a bug! Ideally, software should never crash. A crash indicates the program has failed, not the user. In this case, post a bug report.

    Thanks, and we hope you solve your issue quickly!

  • Have you tried the Ghost Shooter tutorial? It covers this in the tutorial as well.

  • OK, got a cubic expression in the next build!

  • Beautiful artwork and animations, I love the style It was quite hard though... nowhere to hide from enemies!

  • Thanks, yeah, as I suspected, it's a picking problem when you put a family in to an object parameter. Fortunately, there's a good workaround: use the 'to position' actions instead of the 'to object' actions. For example, Move to position enemynode.x, enemynode.y and Set angle toward enemynode.x, enemynode.y work fine. I'll see if I can get the object versions working as well.

  • Can you send me the OGG file you tried with which didnt work?

  • So does playing MP3 and OGG from file work OK then?

  • Can you make a simple .cap demonstrating the problem?

    There's a known issue with object parameters which might be relevant - the pairing doesn't work for families as you'd expect sometimes. If instead of using an object parameter you use a position and do Family.X, Family.Y, that might make it work.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I really would not recommend anyone uses Dev-C++. As far as compilers go, it's old, beta, unfinished and unmaintained, last updated in 2005. That's getting on for four years ago - I strongly recommend you keep up to date with at least regularly maintained compilers.

  • Happy 2009! As for new years resolutions, eh, dunno... get to Construct 1.0, lol

  • It sounds like you're on the right track for calculating the mean X - but you can possibly simplify it simply by dividing by the count when the for-each has finished, like:

    + Always

    -> Set x_sum to 0

    -> Set y_sum to 0

    + For each swarm_object

    -> Add swarm_object.x to x_sum

    -> Add swarm_object.y to y_sum

    + Always

    -> Set mean_x to x_sum / swarm_object.count

    -> Set mean_y to y_sum / swarm_object.count

    Remembering events and actions are read in top to bottom order, this leaves you with the mean x and y in mean_x and mean_y.

  • Yeah, we're hoping to get python working again by 1.0.

Ashley's avatar

Ashley

Early Adopter

Member since 21 May, 2007

Twitter
Ashley has 1,766,647 followers

Connect with Ashley

Trophy Case

  • 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
  • Forum Unicorn Made 10,000 posts in the forums
  • Forum Mega Brain Made 20,000 posts in the forums
  • x125
    Coach One of your tutorials has over 1,000 readers
  • x74
    Educator One of your tutorials has over 10,000 readers
  • x5
    Teacher One of your tutorials has over 100,000 readers
  • Sensei One of your tutorials has over 1,000,000 readers
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • RTFM Read the fabulous manual
  • x42
    Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

32/44
How to earn trophies

Blogs