Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
I need input on a possible bug in v3.5.0
#35
And, if this was some type of space shooter, and one needed to *really* optimize collision checking for speed, here's the tricks I'd use:

1) only check the protruding points.  They're going to collide before anything else does.  With these stars, that'd just be the 8 end points on the peaks, and honestly, you could probably get away with just the 4 tips at each of the cardinal directions.  
2) only check the protruding points in the direction we're traveling.

For example, if we're moving southwards (or down on the screen), there's not much need to check the topmost point to see if you crashed into something.  (Caveat: If other things are moving across the screen as well, you might want to check those other protruding points for collisions.)  If you can get by with just checking the point protruding in the direction you're traveling, then make use of that and you can reduce your collision checks down to a bare minimal, keeping FPS up as high as possible.  Wink
Reply


Messages In This Thread
RE: I need input on a possible bug in v3.5.0 - by SMcNeill - 01-21-2023, 08:44 PM

Possibly Related Threads…
Thread Author Replies Views Last Post
  Is this a bug with Round or is it just me BarrySWTP 10 1,243 07-07-2025, 08:40 PM
Last Post: BarrySWTP
  Exiting FOR NEXT, maybe a bug? Version 4.1.0 on Linux Circlotron 4 836 05-09-2025, 02:22 AM
Last Post: Circlotron
  Mix mode input of a binary open file Question! doppler 5 1,468 11-28-2024, 03:06 PM
Last Post: Petr
  I have fallen in a bug or weird behaviour TempodiBasic 2 665 10-08-2024, 06:09 PM
Last Post: TempodiBasic
  3.13.1 bug report - keyboard characters swapped Circlotron 3 989 06-03-2024, 05:16 AM
Last Post: Circlotron

Forum Jump:


Users browsing this thread: 1 Guest(s)