So, I realize that this is probably an upstream issue with xrandr, however I got no idea of how to provide any meaningful feedback beyond "Boxplorer https://code.google.com/p/boxplorer2/Works in window-mode and fullscreen with the radeon driver, only in window with fglrx. Any attempt to use the fullscreen mode with fglrx will result in ..the wrong buffer (I suppose?) being drawn (it draws a part of my desktop).
I noticed that fglrx uses xrandr 1.2 while the radeon driver uses 1.3, could that be (part of) the problem? and if so, is that something AMD is likely to include eventually anyway or does someone need to ask them to pretty please consider it?
Boxplorer does not render in fullscreen with fglrx
Re: Boxplorer does not render in fullscreen with fglrx
strife could be wine as well. Please do include wine version in future. Its not that wine is free of its own xrandr bugs.
This does sound simlar to a issue people attempting to run silverlight in wine are running into. This is why I particularly do want to know if you have tested with 1.6 and 1.7.x wine. boxplorer2 is open source so there is a possiblity of being able to build a test case of the problem from it and its many times simpler than silverlight.
This does sound simlar to a issue people attempting to run silverlight in wine are running into. This is why I particularly do want to know if you have tested with 1.6 and 1.7.x wine. boxplorer2 is open source so there is a possiblity of being able to build a test case of the problem from it and its many times simpler than silverlight.
Re: Boxplorer does not render in fullscreen with fglrx
Sorry about taking so long to reply, hadn't been thinking about this lately. I was thinking along the same lines, I've had similar problems before - some of which has disappeared with updates but as results seems to vary widely I was not sure how to tell problems with wine's implementation apart from whatever issues the drivers may bring - problem has been that that has been non-free games which can be hard to test. So I thought this might be a good test case, if I could just figure out how to get any meaningful data out of this.
Anyway, I've tested both 1.7.4 and 1.7.5 with similar results (with 1.7.5 it actually crashes when I try to switch back to windowed mode, but I got a feeling that somethings not right with the driver since I tried the radeon driver and then re-installed fglrx - windowed performance has taken a dramatic nose dive unless I use debug=trace+all). Anyway. BEFORE I possibly wrecked something by changing drivers I did try a trace+xrandr but that didn't turn up any err: messages - in fact it didn't produce much of anything just a lot of messages about modes.
In short, I'm now stumped.
Anyway, I've tested both 1.7.4 and 1.7.5 with similar results (with 1.7.5 it actually crashes when I try to switch back to windowed mode, but I got a feeling that somethings not right with the driver since I tried the radeon driver and then re-installed fglrx - windowed performance has taken a dramatic nose dive unless I use debug=trace+all). Anyway. BEFORE I possibly wrecked something by changing drivers I did try a trace+xrandr but that didn't turn up any err: messages - in fact it didn't produce much of anything just a lot of messages about modes.
In short, I'm now stumped.
