From: Martin G. <ge...@la...> - 2009-05-20 20:07:36
|
I installed Visual 5.1 and Python 2.6 on a new laptop running (32-bit?) Vista and found that demo programs that opened more than one window behaved oddly. For example, gas.py did not display any spheres in the "gas box" but the velocity histogram was updating as expected. Remove the code which displays the histogram, then the colliding spheres appear as expected. Similar odd behavior occured with graphtest.py . Anyone else see this? Thanks, Marty |
From: Bruce S. <Bru...@nc...> - 2009-05-20 20:27:48
|
I don't recall ever seeing this. In both gas.py and graphtest.py a graph is involved, so it might be useful to try a multiple-window program such as waves.py or controls.py to verify that the problem has to do with multiple windows rather than graphs. Despite it being a new laptop, it's worth seeing whether there's an update available for the graphics driver. What graphics hardware do you have? Unfortunately, in the case of a laptop, the laptop manufacturer has to pull some difficult tricks to shoehorn everything in, so typically you have to get graphics driver updates from the laptop manufacturer rather than from the manufacturer of the graphics card, and there's a chance that the laptop manufacturer doesn't have the driver quite right. Bruce Sherwood Martin Gelfand wrote: > I installed Visual 5.1 and Python 2.6 on a new laptop running (32-bit?) Vista and > found that demo programs that opened more than one window behaved oddly. > For example, gas.py did not display any spheres in the "gas box" but the > velocity histogram was updating as expected. Remove the code which > displays the histogram, then the colliding spheres appear as expected. > Similar odd behavior occured with graphtest.py . > > Anyone else see this? > > Thanks, > Marty > > > |
From: gelfand <ge...@la...> - 2009-05-21 02:36:01
|
The graphics driver (for Intel video) is the most recent release from Dell. Both waves.py and controlstest.py show the "bad" behavior as well. For example, in waves, only the middle window actually displays a wave, the upper and lower ones (corresponding to 2.0 and 0.5 kg mass) are empty. Any suggestions for further debugging, or is this definitely a video driver issue? Marty On Wed, 20 May 2009 14:27:45 -0600, Bruce Sherwood <Bru...@nc...> wrote: > I don't recall ever seeing this. In both gas.py and graphtest.py a graph > is involved, so it might be useful to try a multiple-window program such > as waves.py or controls.py to verify that the problem has to do with > multiple windows rather than graphs. > > Despite it being a new laptop, it's worth seeing whether there's an > update available for the graphics driver. What graphics hardware do you > have? > > Unfortunately, in the case of a laptop, the laptop manufacturer has to > pull some difficult tricks to shoehorn everything in, so typically you > have to get graphics driver updates from the laptop manufacturer rather > than from the manufacturer of the graphics card, and there's a chance > that the laptop manufacturer doesn't have the driver quite right. > > Bruce Sherwood > > Martin Gelfand wrote: >> I installed Visual 5.1 and Python 2.6 on a new laptop running (32-bit?) >> Vista and >> found that demo programs that opened more than one window behaved oddly. >> For example, gas.py did not display any spheres in the "gas box" but the >> velocity histogram was updating as expected. Remove the code which >> displays the histogram, then the colliding spheres appear as expected. >> Similar odd behavior occured with graphtest.py . >> >> Anyone else see this? >> >> Thanks, >> Marty >> >> >> |
From: Symion <kn...@ip...> - 2009-05-22 09:40:44
|
gelfand wrote: > The graphics driver (for Intel video) is the most recent release from Dell. > > Both waves.py and controlstest.py show the "bad" behavior as well. For > example, > in waves, only the middle window actually displays a wave, the upper and > lower > ones (corresponding to 2.0 and 0.5 kg mass) are empty. > > Any suggestions for further debugging, or is this definitely a video driver > issue? > > Marty > > On Wed, 20 May 2009 14:27:45 -0600, Bruce Sherwood > <Bru...@nc...> > wrote: > >> I don't recall ever seeing this. In both gas.py and graphtest.py a graph >> is involved, so it might be useful to try a multiple-window program such >> as waves.py or controls.py to verify that the problem has to do with >> multiple windows rather than graphs. >> >> Despite it being a new laptop, it's worth seeing whether there's an >> update available for the graphics driver. What graphics hardware do you >> have? >> >> Unfortunately, in the case of a laptop, the laptop manufacturer has to >> pull some difficult tricks to shoehorn everything in, so typically you >> have to get graphics driver updates from the laptop manufacturer rather >> than from the manufacturer of the graphics card, and there's a chance >> that the laptop manufacturer doesn't have the driver quite right. >> >> Bruce Sherwood >> >> Martin Gelfand wrote: >> >>> I installed Visual 5.1 and Python 2.6 on a new laptop running (32-bit?) >>> Vista and >>> found that demo programs that opened more than one window behaved oddly. >>> For example, gas.py did not display any spheres in the "gas box" but the >>> velocity histogram was updating as expected. Remove the code which >>> displays the histogram, then the colliding spheres appear as expected. >>> Similar odd behavior occured with graphtest.py . >>> >>> Anyone else see this? >>> >>> Thanks, >>> Marty >>> >>> >>> >>> > > ------------------------------------------------------------------------------ > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > is a gathering of tech-side developers & brand creativity professionals. Meet > the minds behind Google Creative Lab, Visual Complexity, Processing, & > iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian > Group, R/GA, & Big Spaceship. http://www.creativitycat.com > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > > Hi there, I don't think the previous message got through, so here it is. I have a ASUS Laptop with a graphics card that only supports Pixel Shader 2.0, and I have to report the same problem when opening two or more windows. When I ran Wave.py and graphtest.py both stopped working after a short time, while the processor was running hot. The following routine runs Ok if you set 'double=0', but if you set 'double=1' then the processor runs at a high rate and after a while the program falls over. Source Code : EarthSunMoon.py <http://home.iprimus.com.au/knoware/python/EarthSunMoon.py> Symion |
From: Symion <kn...@ip...> - 2009-06-08 10:02:16
|
Bruce Sherwood wrote: > It is unclear to me whether you can run multiwindow programs simply by > disabling shaders, using the standard VPython-Win-Py2.6-5.1.exe, or > whether it is necessary both to disable shaders AND run the > nonstandard VPython-Win-Py2.6-5.1-exp.exe. > > Could you please report on this point? Thanks. > > No hurry, as David Scherer is away for a couple of weeks, and I won't > know how to interpret your data, but it may mean something to him. > > Bruce > > Hi, I should have been more precise, I had installed the experimental version - VPython-Win-Py2.6-5.1-exp.exe! I only mentioned disabling shaders because it might have some bearing some where, and it was necessary in order to remove the V-IDLE error messages that appear every time I run a program. Now I know this means Materials are not available to me, but I still have control over Transparency and Lights. The results are still good and stable, I can now rely on my own information window instead of relying on V-IDLE window. This might be a good time to point out that Multiple Windows are useful when running Vpython programs off the web, as V-IDLE is not necessarily present when programs are accessed by Firefox browser and important information may not be displayed. This may be more of an issue for Mozilla Firefox than Vpython as the exact method Firefox uses when running programs is very strict and there does not seem to be any way of appending info to the executable name! (pythonw.exe) Although I thought there was a python.ini (default) entry in the Firefox/Tools/Options/Applications/ device, (under python file: Action?) but it seemed to disappear from the options list and I have been unable to find any reference to it!! Which reminds me, scene.range MUST now be specified early in the program, before reading it or a nasty error message interrupts program flow. This seems a bit odd as scene.range should have been set to a default state on initialization. Symion |