Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Lorgan]

sexy

[notajf]

Alright, I did some major updates, got collision detection and reponse working beautifully now (you can walk up stairs and even jump on stairs), and changed the way PyGG2 was rendered. Orpheon now gets 450 FPS when we unlock the FPS limiter (standard it's on 80, anything more is overkill).

A screenshot:

nice!

[Blackbird88]

Alright, I did some major updates, got collision detection and reponse working beautifully now (you can walk up stairs and even jump on stairs), and changed the way PyGG2 was rendered. Orpheon now gets 450 FPS when we unlock the FPS limiter (standard it's on 80, anything more is overkill).

A screenshot:

Holy shit yesss!

[Flaw]

If you're wondering why I'm not collaborating much/at all yet, it's because of the following reasons:

• School
• Because I said I would be working primarily on gameplay-related coding (sentry logic, round managing, etc)
• Plans for ( )

[Malpracticeisdead]

I might try to take part in this, but what I will be able to do will be incredibly limited, considering I have no experience with Python. I'm looking forward to how this'll turn out though.

[Flaw]

I saw "nightcracker - PyGG2" on a server today. Did you actually get some networking ready, or did you just for some odd reason use that name?

[nightcracker]

Just for shit's n giggles.

[Liam]

I'm so glad to see this moving ahead! I've learned a lot about Python and the Pygame library while reviewing the code put up so far. The next part is a mystery to me though. How are you going to get two people interacting with one another in a game? Is this where Twisted comes in?


That 450 fps is awesome, btw! I wonder what that number would be on less powerful hardware...

[Flaw]

Also, nightcracker, is your project actually in Orpheon/PyGG2's main branch? I seem to be getting some mapless, collisionless void with very glitchy shooting.

[nightcracker]

Also, nightcracker, is your project actually in Orpheon/PyGG2's main branch? I seem to be getting some mapless, collisionless void with very glitchy shooting.

Nope, I usually work in my own fork: https://github.com/nightcracker/PyGG2

I'm so glad to see this moving ahead! I've learned a lot about Python and the Pygame library while reviewing the code put up so far. The next part is a mystery to me though. How are you going to get two people interacting with one another in a game? Is this where Twisted comes in?


That 450 fps is awesome, btw! I wonder what that number would be on less powerful hardware...

Yes, that's were Twisted comes in (though Twisted is not necessary, it's a nice library).

And it would probably be around 100-200 FPS on less powerful hardware.

[notajf]

Also, nightcracker, is your project actually in Orpheon/PyGG2's main branch? I seem to be getting some mapless, collisionless void with very glitchy shooting.

Nope, I usually work in my own fork: https://github.com/nightcracker/PyGG2

I'm so glad to see this moving ahead! I've learned a lot about Python and the Pygame library while reviewing the code put up so far. The next part is a mystery to me though. How are you going to get two people interacting with one another in a game? Is this where Twisted comes in?


That 450 fps is awesome, btw! I wonder what that number would be on less powerful hardware...

Yes, that's were Twisted comes in (though Twisted is not necessary, it's a nice library).

And it would probably be around 100-200 FPS on less powerful hardware.

This is assuming we're only rendering 2 or 3 objects, like we are at the moment. Realistically we'll have hundreds of objects to render and a more modest framerate.

[Orpheon]

Pulled in nightcrackers stuff again, and resolved to start working on this again.

Did a bit of testing around, and I noticed a few things:

1.

Code: [Select]

   def collide(self, frametime):
        GameObject.collide(self, frametime)

        if objectCheckCollision(self):
            self.destroyInstance = TrueFor some odd reason self.destroyInstance is never marked as True, even in the middle of the wallmask.

EDIT:

Code: [Select]

class GameObject(pygame.sprite.Sprite):
    def __init__(self, root, xpos, ypos):
        pygame.sprite.Sprite.__init__(self)

        self.root = root

        self.x = xpos
        self.y = ypos

        self.hspeed = 0
        self.vspeed = 0

        self.image = None
        self.rect = (0, 0, 0, 0)

        self.root.GameObjectList.append(self)
        self.destroyInstance = False

    def beginStep(self, frametime):
        pass

    def step(self, frametime):
        pass

    def endStep(self, frametime):
        self.x += self.hspeed * frametime
        self.y += self.vspeed * frametime
       
        self.x = max(self.x, 0)
        self.y = max(self.y, 0)

    def draw(self):
        if self.image:
            x, y = int(self.x), int(self.y)
            xoff, yoff = self.rect[0:2]
            xview, yview = int(self.root.Xview), int(self.root.Yview)
           
            # range checking - TODO consider sprite heigth/width
            if x >= xview and x < xview + self.root.Wview and y >= yview and y < yview + self.root.Hview:
                self.root.Surface.blit(self.image, (x - xoff - xview, y - yoff - yview))There is no "GameObject.collide()".


2.
Jumping Bug in PyGG2

[nightcracker]

Both aren't bugs  

1. The function was removed because the object should check for collision itself in either beginStep, step, or endStep IMO. Why? Because it will make collision resolving (what actually should be done if something does collide) much easier. I'm not saying that the .collide function is bad, I'm saying that calling it directly in the main loop was bad. As a cause of this the collision detection of bullets was temporarily disabled, causing you to think destroyInstance was never set.

2. The second is sort more of a known issue. The current physics are just an example implementation by me until it gets replaced with real tested code.

[Phantom Brave]

>script kiddo
>does real programming

[Nukleus]

I've just finished my first book on python, I'm looking into pygame now, hopefully I'll be able to contribute down the track