oosyrag's Forum Posts

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

  • 2 Nov, 2022
  • Quote

  I took a sample of 10m perlin noise values, sorted them, and recorded the threshold value for each percent of total samples.

  There will be some variation no matter what (that's why 50% isn't at exactly 0.5), but statistically speaking it should be close enough to not have any noticable difference in practice.

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

  • 2 Nov, 2022
  • Quote

  You can adjust your ranges instead. If you use the chart I posted in your previous post regarding noise, you can get a pretty good approximation - 0-0.382 will contain roughly 10% of the returned values, 0.382-0.437 will be the next 10%, 0.437-0.462 will have your next 10%, ect. Edit: This is without normalization, which you shouldn't need.

  dropbox.com/s/60uu0inwekr2iaf/classic2d-percentagedistribution.PNG

• • oosyrag
  • 
  • • Joined 20 Feb, 2013
    • 
    • 61 topics • 4,717 posts
  • 3

  • 2 Nov, 2022
  • Quote

  Also check you player collision boxes if you're running an animation.

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

  • 2 Nov, 2022
  • Quote

  Uncheck Project properties -> Editor -> Preview effects

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

  • 1 Nov, 2022
  • Quote

  Sorry, I meant you're picking the player. You need to pick a target, that is closest to player.x, player.y.

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

  • 1 Nov, 2022
  • Quote

  Your first event says pick nearest to target x and y, rather than player x and y.

• 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,717 posts
  • 1

  • 31 Oct, 2022
  • Quote

  You could refer to the manual on expressions and system expressions.

  construct.net/en/make-games/manuals/construct-3/project-primitives/events/expressions

  construct.net/en/make-games/manuals/construct-3/system-reference/system-expressions

  Recommend you go through the beginner tutorials as well.

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

  • 31 Oct, 2022
  • Quote

  Wait, this doesn't work exactly. If I, say, have 1.568M coins, and then I spend it on something, the numbers goes like 1.432575234M. Do you know a way to fix this?

  You can use the float(left(number,digits)) expressions to truncate a number. Or you can multiply by 1000, round(), then divide by 1000 to round to the nearest thousandth.

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

  • 31 Oct, 2022
  • Quote

  Do you have another event setting the text to the variable by itself?

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

  • 31 Oct, 2022
  • Quote

  Are you setting the right text object?

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

  • 31 Oct, 2022
  • Quote

  You might have other events or behaviors causing issues.

  dropbox.com/s/zk127tkxeez2kqq/pathfindingdebug.c3p

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

  • 31 Oct, 2022
  • Quote

  Is your event sheet linked?

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

  • 31 Oct, 2022
  • Quote

  You're doing something wrong. Pathfinding reaches max speed just fine in a minimal project. No idea what you're doing wrong with the information you've provided though.

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

  • 31 Oct, 2022
  • Quote

  The simplest way is to use the layout bounds with the scroll to behavior, it already does everything you want by default.

  Otherwise, you'll need to define your own bounds and margins. You'll need four bounds, top, right, bottom, and left. You'll also want two margins, horizontal and vertical, or you can simply use half the viewport height and width as your margins. You can use the clamp() expression to keep the final value within a minimum and maximum value.

  + System: Every tick

  -> System: Set scroll X to clamp(Target.X,LeftBound+(LayoutWidth÷2),RightBound-(LayoutWidth÷2))

  -> System: Set scroll Y to clamp(Target.Y,TopBound+(LayoutWidth÷2),BottomBound-(LayoutWidth÷2))

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

  • 30 Oct, 2022
  • Quote

  There is not enough information to even begin to guess what your problem is.