Bruce Sherwood wrote:
> Interesting. On a Del XPS M1330 laptop with NVIDIA 8400M GS graphics
> performance is pretty good, with decent rotate and zoom. When I set
> scene.show_rendertime = True, I get this report:
>
> cycle: 200 render: 50
>
> This means that it takes 50 ms to render the scene, and there are 200 ms
> between renders. This behavior is a bit strange, in that Visual attempts
> to balance computation and rendering, so with a render time of 50 ms I
> would have expected a cycle time of 100 ms (50 ms computation, 50 ms
> render).
>
> Bruce Sherwood
>
> Symion wrote:
>
>> Hi there,
>> Here is another program dealing with large numbers of objects
>> (200,000 points)!
>>
>> Source: Shell_2.py <http://home.iprimus.com.au/knoware/webpage/Shell_2.py>
>>
>> This is a Stellar Anatomy type demonstration.
>>
>> Symion
>>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>
>
Hi there,
I have found that by carefully selecting rate(x), the response
performance can be improved.
A faster response can be achieved by changing self.type=1, this selects
the square shape for points instead of round.
However if you change self.size=1 then each point size depends on the
reciprocal of the distance from the center,
that really slows things down, but gives a very pleasing globular effect.
I'm left wondering what else I can use it for? Maybe a Brownian motion
generator to get the whole thing boiling!
|
