| Summary: | Unigine Heaven/Valley: Multi monitor rendering does not work | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | Knut Andre Tidemann <knut.tidemann> |
| Component: | Drivers/Gallium/r600 | Assignee: | Default DRI bug account <dri-devel> |
| Status: | RESOLVED MOVED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | git | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
Unigine vally output
glxinfo output X.org log dmesg output |
||
Please attach your xorg log, dmesg output, and glxinfo output. Additionally, you'll need a 3.14 kernel for OpenGL 3.3 support with r600g. Created attachment 94889 [details]
glxinfo output
Created attachment 94890 [details]
X.org log
Created attachment 94891 [details]
dmesg output
I have now attached the requested outputs. I thought that 3.14 was only needed for R7xx hardware to enable OpenGL 3.3 with the core profile? Atleast glxinfo reports version 3.3. (In reply to comment #5) > I have now attached the requested outputs. > > I thought that 3.14 was only needed for R7xx hardware to enable OpenGL 3.3 > with the core profile? You are correct. I misremembered. (In reply to comment #0) > It seems that Mesa is using the compatability context which is limited to > OpenGL 3.0. It's up to the application to choose a compatibility or core context. Mesa never has and probably never will support higher than 3.0 with compatibility contexts. You'd probably have to ask the Unigine developers why it wants to use a compatibility conext with GL_ARB_geometry_shader4 in this configuration. I only reported this because the proprietary works in this case. If this is an application bug, then I guess this can be closed as such. There is no reason why Mesa should fall back to the compatibility profile when more than one context is used I guess? (In reply to comment #8) > I only reported this because the proprietary works in this case. Presumably fglrx supports higher OpenGL versions and GL_ARB_geometry_shader4 in compatibility contexts. > There is no reason why Mesa should fall back to the compatibility profile > when more than one context is used I guess? Mesa doesn't (couldn't) 'fall back' to the compatibility context. It means the app didn't ask for a core context. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/497. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 94870 [details] Unigine vally output When trying to start the unigine demos with multiple monitors enabled (Wall 2x1 or any other of the options in the launch dialog), it will exit with a failure. It seems that Mesa is using the compatability context which is limited to OpenGL 3.0. I've attached the output log of Unigine Vally when started with multi monitor enabled. The demos run fine when only a single monitor is enabled. I'm currently using mesa-git g085f61b and linux 3.13.5 on Arch Linux with a Radeon 5730. The same issue can be seen when I try to enable dual output stereo 3D, which should start two separate windows that it will render to.