oosyrag's Forum Posts

• • oosyrag
  • 
  • • Joined 20 Feb, 2013
    • 
    • 61 topics • 4,759 posts
  • 2

  • 23 Nov, 2021
  • Quote

  Yeah I understood that was what you were going for, but it will probably be a bit jarring if you do that no matter how you implement it, and I haven't really seen any other game use a design like that. If you just always have the camera rotate and pan based on mouse position it will be much less dizzying I think.

• • oosyrag
  • 
  • • Joined 20 Feb, 2013
    • 
    • 61 topics • 4,759 posts
  • 1

  • 23 Nov, 2021
  • Quote

  Try simply setting the camera to halfway between the player and mouse position every tick.

  You can have the 'camera' object always on the mouse, and have both the camera and player object scroll to enabled.

• • oosyrag
  • 
  • • Joined 20 Feb, 2013
    • 
    • 61 topics • 4,759 posts
  • 2

  • 23 Nov, 2021
  • Quote

  The manual is a pretty great place to start.

  Note that you don't need to know any JavaScript at all to use construct.

• • oosyrag
  • 
  • • Joined 20 Feb, 2013
    • 
    • 61 topics • 4,759 posts
  • 1

  • 22 Nov, 2021
  • Quote

  Can you provide the link for the data you're trying to get?

• Try Construct 3

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

  Try Now Construct 3 users don't see these ads
• • oosyrag
  • 
  • • Joined 20 Feb, 2013
    • 
    • 61 topics • 4,759 posts
  • 1

  • 20 Nov, 2021
  • Quote

  Use a single variable to calculate and represent change over time. Adjust this variable by adding and subtracting from it when appropriate. Display the variable.

• • oosyrag
  • 
  • • Joined 20 Feb, 2013
    • 
    • 61 topics • 4,759 posts
  • 2

  • 20 Nov, 2021
  • Quote

  construct.net/en/tutorials/using-3d-construct-2746

  See the section on using 2d layers.

• • oosyrag
  • 
  • • Joined 20 Feb, 2013
    • 
    • 61 topics • 4,759 posts
  • 2

  • 20 Nov, 2021
  • Quote

  I recommend xirsys.com

• • oosyrag
  • 
  • • Joined 20 Feb, 2013
    • 
    • 61 topics • 4,759 posts
  • 1

  • 19 Nov, 2021
  • Quote

  Start with the official beginner's tutorials to see if the event system makes sense to you, even though they are not for visual novel type games.

  I believe there are other game engines that are focused on make visual novels that would be more suitable for you if your intent is to make a visual novel.

• • oosyrag
  • 
  • • Joined 20 Feb, 2013
    • 
    • 61 topics • 4,759 posts
  • 1

  • 18 Nov, 2021
  • Quote

  I'm not quite sure I understand your question, but it seems like the timer behavior and it's expressions should have everything you need.

  construct.net/en/make-games/manuals/construct-3/behavior-reference/timer

• • oosyrag
  • 
  • • Joined 20 Feb, 2013
    • 
    • 61 topics • 4,759 posts
  • 1

  • 18 Nov, 2021
  • Quote

  Use tags in the solid behavior, and the sprite object's 'set solid collision filter' action.

  construct.net/en/make-games/manuals/construct-3/behavior-reference/solid

  construct.net/en/make-games/manuals/construct-3/plugin-reference/sprite

• • oosyrag
  • 
  • • Joined 20 Feb, 2013
    • 
    • 61 topics • 4,759 posts
  • 1

  • 18 Nov, 2021
  • Quote

  I would avoid layers simply because it is inflexible, as it requires manual creation of the layers and can't be done at runtime, as well as not scaling well for larger puzzles.

  I'm not sure if 36 layers would have any performance issues, but I suspect it might, since (I think) force own texture will draw each layer individually, and drawing your entire screen 36 times over every tick sounds like it might run into fill rate issues. The more layers you have the problem will only get worse, so again it is inflexible and unscalable.

  As will all performance issues, try it out yourself and test if it is acceptable on your target platform.

• • oosyrag
  • 
  • • Joined 20 Feb, 2013
    • 
    • 61 topics • 4,759 posts
  • 1

  • 18 Nov, 2021
  • Quote

  Familiarize yourself with blend modes and force own texture on layer. This will be used to 'cut' your pieces out of the image.

  The straightforward way would be to have a layer for each puzzle piece, which consists of the cutout with blend mode over the image. We want to avoid using so many layers, so instead use a single layer to temporarily define each piece, and paste it to an instance of a canvas object.

  If I were to attempt it I would probably approach it over time, pasting one canvas instance/puzzle piece per tick and moving it out of the way, while cycling through animation frames of the various cutouts in place and moving the main image accordingly.

• • oosyrag
  • 
  • • Joined 20 Feb, 2013
    • 
    • 61 topics • 4,759 posts
  • 1

  • 17 Nov, 2021
  • Quote

  Well... slightly less tedious, as I consider changing the size of an object is easier than modifying collision polygons. You could for example, put all the visible sprites in a family, then use a single set size action on start of layout (self.x/y*1.01 or similar)

• • oosyrag
  • 
  • • Joined 20 Feb, 2013
    • 
    • 61 topics • 4,759 posts
  • 2

  • 17 Nov, 2021
  • Quote

  You cannot.

• • oosyrag
  • 
  • • Joined 20 Feb, 2013
    • 
    • 61 topics • 4,759 posts
  • 1

  • 17 Nov, 2021
  • Quote

  construct.net/en/forum/construct-3/general-discussion-7/report-bugs-amp-post-128538

  construct.net/en/forum/construct-3/general-discussion-7/announcing-new-construct-161682