oosyrag's Recent Forum Activity

  • Well local input prediction is the solution. If you set it up properly you will avoid the rubber banding movement as well. I'm guessing you didn't sync up your movement with the client input ready condition, but have no way of knowing without seeing your events.

  • Do you have local input prediction set up?

  • You do not have permission to view this post

  • A. Use an invisible helper object. Pin it above your player and scroll to that instead of your player.

    B. Make sure unbounded scrolling is not checked in your project properties. Set your layout size properly so there is no extra space below your level.

  • You want to add the condition where player is overlapping enemy (and also a trigger once while true), because you only want this event to happen when you actually hit the enemy, rather than any time your y is greater that his.

    Alternatively, use a invisible helper "target" sprite that is pinned just above the enemy to trigger an event when landing from above.

  • I'm not seeing why you wouldn't have control of the size of the object. Anyways if you try to mix your rendering methods you will run into issues, as you have found. So if you position and display your key the same way you would display a wall, which is working properly, the key should also display properly. If you didn't make the effect yourself maybe you can ask the original creator how to adapt it for smaller objects.

  • That makes sense. Again so what are you doing differently with the key compared to the walls as far as position and projection go?

  • Based on the information given in the screenshot, I wouldn't even know where to start looking in to the problem. It may be the same for others, so that's why no one is replying.

    How are you determining the positions of objects and projecting them in 3d, and what are you doing differently with the key compared to say a wall so that it doesn't behave like you expect it to?

  • You were talking about computer science and JavaScript.... That would be applicable to c2 or c3 equally...

  • Seed - "A pseudorandom number generator's number sequence is completely determined by the seed: thus, if a pseudorandom number generator is reinitialized with the same seed, it will produce the same sequence of numbers."

    It is used as a basis to get a specific set of random numbers. The term seed I believe does come from a plant's seed. The same set of random numbers will always "grow" from the same seed.

    Permutation - "In mathematics, permutation is the act of arranging the members of a set into a sequence or order"

    In construct, a permutation table is a randomized set of numbers that are saved and can be referenced at a later time.

    Threshold - "Minimum or maximum value (established for an attribute, characteristic, or parameter)"

    Generally speaking, this is a cutoff value at which something takes effect.

  • I don't believe the turret behavior has a way to exclude specific instances of objects.

    You should probably work at recreating a similar result with events, which you will have much more control over.

  • I saw this a few years ago. I don't know if it is still relevant.

    twitter.com/2xTacker/status/917781791066423296

    Alternatively, have you tried Wait 0 for updating the helper sprite's position? That should make it run at the end of everything else in the sheet, although again I don't know if that would make a difference with behaviors.

    The true solution would be to use sin and cos to determine where the object should be, in effect recreating the orbit with events rather than using behavior. Then you have control of when the position gets updated.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
oosyrag's avatar

oosyrag

Member since 20 Feb, 2013

Twitter
oosyrag has 39 followers

Trophy Case

  • 11-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

21/44
How to earn trophies