[visionegg] Re: New User, Seg Fault


Hey Andrew!

>> Pygame Parachute Traceback:
>>   File "C:\Python22\Lib\site-packages\VisionEgg\PlatformDependent.py",
>> line 192, in sync_swap_with_vbl_post_gl_init
>> Fatal Python error: (pygame parachute) Segmentation Fault

>The problem seems to occur when trying to synchronize buffer swaps with
>vertical sync.  To get the demos running, turn off this feature in the
>GUI console.  (The Windows Display settings control panel may allow you
>to set this feature anyway.)


I turned off the option to synchronize buffer swaps.  This had no
noticeable effect.


>It appears that the offending line (192) in PlatformDependent.py is the
>if statement below:
>
>import OpenGL.WGL.EXT.swap_control
>if OpenGL.WGL.EXT.swap_control.wglInitSwapControlARB(): # Returns 1 if
>it's working
>     OpenGL.WGL.EXT.swap_control.wglSwapIntervalEXT(1)
>
>Try running the above lines direct from the Python interpreter and see
>what happens.  It looks like either a PyOpenGL or possibly a driver

The above lines do nothing.  Run individually (which might be what you
meant), both functions return 0:


-----Begin-----
>>>
>>> import OpenGL.WGL.EXT.swap_control
>>> if OpenGL.WGL.EXT.swap_control.wglInitSwapControlARB():
...     OpenGL.WGL.EXT.swap_control.wglSwapIntervalEXT(1)
...
>>>
>>> OpenGL.WGL.EXT.swap_control.wglInitSwapControlARB()
0
>>> OpenGL.WGL.EXT.swap_control.wglSwapIntervalEXT(1)
0
>>>
-----End-----


>problem to me.  Perhaps you can update your OpenGL drivers?  (It looks
>like this in the onboard video of an Intel 845 mainboard?  Perhaps you
>need to update your mainboard drivers?) If you can isolate any further,
>we can submit a question or bug report to the PyOpenGL team.

Yes, I have the Intel 82845G, and I just updated the driver from Intel's
website.  Still no effect.  =(


>> Hmm, looking at the output of check-config.py again, it has listed:
>>
>> VISIONEGG_USER_DIR = H:\VisionEgg
>>
>> which doesn't exist; everything has been installed to the C:
>> directory.  Might this have something to do with the problem?  If so,
>> how do I change this?
>
>That's strange...  That means that os.path.expanduser("~") returns
>"H:".  If what you say is true, this sounds a bug in that Python
>function, which is possible but unlikely.  Is there an H: drive at all?


Well the H: drive does exist.  It is a networked drive that is pretty much
my "default" drive, insofar as when I open the command prompt, it puts me
in H:\>.  However, I installed everything python- and visionegg-related to
the local disk (C:).
Again, I'm not sure if this is a problem, becuase check-config does find
the other directories properly (ie. config file, visionegg module,
system_dir).


Any more ideas?  Let me know if you need any more details.  Thanks!

--
Asif Ladak



=====================================The Vision Egg mailing list
Archives: http://www.freelists.org/archives/visionegg
Website: http://www.visionegg.org/mailinglist.html

Other related posts: