oosyrag's Recent Forum Activity

  • I would use the Pick Nth instance system condition. It is basically picking by IID.

    Keep track of the "current" instance in a variable, and you can increase and decrease that by 1 through input, and pick the proper enemy sprite based on that, from 0 to enemySprite.count.

    If you need some other sort of order, you could add an instance variable to the enemy sprite and pick by comparing that for more control.

  • Project files won't work, but external files could.

    Ajax can post and get files from web sources and nwjs can do so for local files.

  • The sprite in question isn't exactly large by todays standards, relatively speaking. The size of your viewport doesn't really matter as far as the device is concerned. However it might cause memory issues if you have a lot of animation frames (it also might not, it really depends on how many frames it contains). Your idea of splitting up the boss into multiple pieces is a good idea and a fairly common technique to optimize memory usage in other games. If there are significant areas that do not need animation, it can make a huge difference in memory use, especially as your frame count increases.

    Running out of vram can cause your game to either fail to load, crash, or otherwise run at extremely low fps.

  • Since there is no expression to get the pin distance, you'll want to keep track of it manually in a variable.

    Set sprite.pinDistance to max(0,sprite.pinDistance-retractionAmount) (or use a tween here for control of the amount over time)

    Sprite - Pin - Set Pin Distance to sprite.pinDistance

  • Nothing I've tried myself, but I imagine using some sort of xml/json project file to describe the objects and offsets for each piece of your ship rather than a visual editor. The exact method and format would be up to you. An additional advanced step would be to create your own editor app dedicated to positioning pieces, then exporting to your preferred format as data.

    At least that's how Barotrauma and other games with objects that consist of multiple pieces usually do it AFAIK.

  • You need to position your 0 parallax layer elements in the top left of your layout, where the dotted line shows the viewport.

  • I believe the effect he is going for is for the magnifying glass to be positioned at the actual angle the character is from the center of the viewport, but constrained to the border area of the screen.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Put event 3 and 4 in subevents under a For each condition. Also since period is a measure in seconds it doesn't make sense to have it be a negative number... although it seems to work I would change it back to a positive number and use the following

    + System: For each Grump

    ----+ System: Grump.Sine.CyclePosition > 0.25

    -----> Grump: Set Mirrored

    ----+ System: Grump.Sine.CyclePosition > 0.75

    -----> Grump: Set Not mirrored

  • Ray casting finishes within a single frame and the event sheet runs from top to bottom. Separate the ray casting events and ray intersected events to check each ray after they are cast.

  • I haven't tried it myself yet, but I imagine if you used an intermediate data structure like an array to store your base tile upon generating a chunk (instead of setting the tile directly), then setting all the tiles in one go with the bitwise auto tiling function based on that array (compare array values instead of tile values), it should work fine.

  • Being able to click and drag to toggle/lock multiple layers at a time as is common in CAD software would be a nice usability improvement.

  • You do not have permission to view this post

oosyrag's avatar

oosyrag

Member since 20 Feb, 2013

Twitter
oosyrag has 39 followers

Trophy Case

  • 12-Year Club
  • 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
  • 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
  • Email Verified

Progress

22/44
How to earn trophies