visualpython-users

[Visualpython-users] VSpace.py Demo

[Ron A. <rr...@ro...>]

I made some changes to the VSpace.py Demo I posted earlier.

Velocities are now time based instead of frame based, so that things should 
appear to move at the same speed on different speed computers.

The frame rate is limited by adding and removing asteroid objects.  So the 
number of asteroid objects acts as a rough bench mark.  On my system I get 
220 asteroids at 60 FPS.  Your mileage may vary of course. ;-)

Rotation of the world is done all at once by rotating the parent "space" 
frame instead of rotating frames individually.

You can zoom in and out of the field of view by pressing both mouse buttons 
at the same time.  This allows you to see how everything moves relative to 
the view.  This was disabled before.

The objects, asteroids, sun, stars, ship, are implemented with classes with 
an "animate" method.  This groups related code together in a much nicer way.


Enjoy,
   Ron Adam

Re: [Visualpython-users] VSpace.py Demo

[Bruce S. <Bru...@nc...>]

There's something wrong with the program you posted:

Traceback (most recent call last):
   File "C:\Documents and Settings\Bruce\My Documents\Python 
stuff\vspace.py", line 279, in -toplevel-
     ship.animate(period, len(asteroids))
   File "C:\Documents and Settings\Bruce\My Documents\Python 
stuff\vspace.py", line 121, in animate
     self.status.text = 'frame rate = %i, asteroids = %s' \
ZeroDivisionError: float divmod()

Also, I'll note that you have the following:

     scene.range = (0, 0, 0)
     scene.scale = (.1, .1, .1)

The scene.range statement is irrelevant, because the scene.scale 
statement is equivalent to scene.range = (10,10,10). But in the beta 
version setting the range to 0 gives an error, as it should; it's a 
failing in the production version not to give an error.

Bruce Sherwood

Ron Adam wrote:
> 
> I made some changes to the VSpace.py Demo I posted earlier.
> 
> Velocities are now time based instead of frame based, so that things 
> should appear to move at the same speed on different speed computers.
> 
> The frame rate is limited by adding and removing asteroid objects.  So 
> the number of asteroid objects acts as a rough bench mark.  On my system 
> I get 220 asteroids at 60 FPS.  Your mileage may vary of course. ;-)
> 
> Rotation of the world is done all at once by rotating the parent "space" 
> frame instead of rotating frames individually.
> 
> You can zoom in and out of the field of view by pressing both mouse 
> buttons at the same time.  This allows you to see how everything moves 
> relative to the view.  This was disabled before.
> 
> The objects, asteroids, sun, stars, ship, are implemented with classes 
> with an "animate" method.  This groups related code together in a much 
> nicer way.
> 
> 
> Enjoy,
>   Ron Adam

Re: [Visualpython-users] VSpace.py Demo

[Ron A. <rr...@ro...>]

Bruce Sherwood wrote:
> There's something wrong with the program you posted:
> 
> Traceback (most recent call last):
>    File "C:\Documents and Settings\Bruce\My Documents\Python 
> stuff\vspace.py", line 279, in -toplevel-
>      ship.animate(period, len(asteroids))
>    File "C:\Documents and Settings\Bruce\My Documents\Python 
> stuff\vspace.py", line 121, in animate
>      self.status.text = 'frame rate = %i, asteroids = %s' \
> ZeroDivisionError: float divmod()

If I change the time.time() calls to time.clock(), I get that too.

I did have the import wrong for the time module.  Since I originally wrote 
this on XP.

Changed:

    from time import clock

to:

    import time

    # use time.clock if it works, else use time.time.
    if time.clock() != time.clock():
        time.time = time.clock


There is differences between time.clock and time.time between linux and 
windows.  I'm using Ubuntu.  The above should fix it.

File attached with corrections.


> Also, I'll note that you have the following:
> 
>      scene.range = (0, 0, 0)
>      scene.scale = (.1, .1, .1)

Thanks, removed the scene.range assignment.


Ron