Search results

  1. G

    Collision detection problem that shouldn't be

    BAH! I found it! First off thanks for your input to all of you. M-HT thank you, that makes total sense and it may have caused me problems eventually. I've implemented your suggestion to make my code more efficient as I didn't need to recheck collisions that had already been checked so I changed...
  2. G

    Collision detection problem that shouldn't be

    No need onpon4 for a mockup as I understand what you are saying. However, the balls dont stick together. They dont bounce at all. Well they bounce just fine off the walls (similar code) but they dont bounce off each other. They simply pass by/over/under each other. Its odd about the repost as...
  3. G

    Collision detection problem that shouldn't be

    repost import pygame, sys, glob, random, math from pygame import * from random import * h=600 w=800 screen = pygame.display.set_mode((w,h)) clock = pygame.time.Clock() class ball: def __init__(self): # sets the x and y values of the start position for our sprite...
  4. G

    Collision detection problem that shouldn't be

    Oh my. Sorry. Pygame.org doesn't have a dev forum so I Googled "pygame forum" and it took me here. My apologies. However, that Pandora device looks like fun. I may have to pick one up.
  5. G

    Collision detection problem that shouldn't be

    Good evening fellow pygame enthusiasts. I've been working on a Ball class script. Its a fairly simple thing I think but boy o boy am I ever not seeing why my collision isn't working. I've made a constructor member function which seems to work fine. I've made an update function which also works...
Back
Top