public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk> To: cygwin-xfree@cygwin.com, kdo@cosmos.phy.tufts.edu Subject: Re: AIGLX Date: Mon, 24 Jan 2011 18:38:00 -0000 [thread overview] Message-ID: <4D3DC72C.6000103@dronecode.org.uk> (raw) In-Reply-To: <E1PgL9i-00034B-Uv@cosmos.phy.tufts.edu> On 21/01/2011 17:52, Ken Olum wrote: > From: Jon TURNEY <jon.turney@dronecode.org.uk> > Date: Wed, 19 Jan 2011 21:11:12 +0000 > > Anyhow, can you try with 'GLWIN_NO_WGL_EXTENSIONS=1 XWin -wgl -multiwindow' > > Thanks. I did this and it worked. However, for a particular paraview > dataset that I happened to have lying around it is slower than direct > rendering by a factor of about 2. That may be related to the fact > that this particular scene has wiggly tubes with structure too small > to show on the screen, so there is a high ratio of data to things that > actually get displayed. For the same scene, unaccelerated indirect > rendering is much slower than accelerated, perhaps by a factor of 10. > So when you can't use direct rendering, acceleration is a big help. Ok, thanks very much for trying it out anyhow. It's very useful to have a data point like that for an actual real-world use case :-) Another factor is possibly that you aren't going to get awesome hardware accelerated performance with an Intel 845G, either. > Once I say -wgl, direct rendering no longer works. That is, if I > don't set LIBGL_ALWAYS_INDIRECT, then I get a long (infinite?) > sequence of errors like this: > > X Error: BadMatch (invalid parameter attributes) 8 > Major opcode: 73 (X_GetImage) > Resource id: 0xa0039a I can't reproduce this problem. Can you give me a few more details on the host which is running paraview: unix version, version of libGL and version of paraview? Do you get that error with other OpenGL applications (e.g. glxinfo) or just paraview? -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
next prev parent reply other threads:[~2011-01-24 18:38 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-19 18:53 AIGLX Ken Olum 2011-01-19 21:11 ` AIGLX Jon TURNEY 2011-01-21 17:52 ` AIGLX Ken Olum 2011-01-24 18:38 ` Jon TURNEY [this message] 2011-02-04 17:14 ` AIGLX Ken Olum 2011-03-05 18:05 ` AIGLX Jon TURNEY
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=4D3DC72C.6000103@dronecode.org.uk \ --to=jon.turney@dronecode.org.uk \ --cc=cygwin-xfree@cygwin.com \ --cc=kdo@cosmos.phy.tufts.edu \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).