I think my problems with Mesa 7.11 has to do with the fact I do 10.5 builds and 
run them on 10.6 and 10.7.  7.11 built on 10.5 works fine on 10.5… but it 
crashes on 10.6 and 10.7… the version I'm using is… one of the 7.8 revisions I 
think, and the 10.5 build runs fine on 10.6 and 10.7.  I'm not sure I feel like 
troubleshooting Mesa changes to why this is happening… I'm hoping that more 
users will stop using 10.5 so I can just kill off support for it  :-)  I think 
I'm going to stick with the older version since I cannot see any performance 
difference in Wine using it and 7.11, until I can drop 10.5.  I could just put 
10.5 and 10.6+ versions in there and have it use the 10.5 one only on 10.5 I 
guess.

To the STO crash.  STO will be free in the future, but I'm not sure when they 
are finishing it up… they are beta testing their Free to Play switch over right 
now.  So far I haven't personally found any other game that raises this error, 
and STO didn't use to either until an update 6 months ago or so.. they changed 
how they were doing something.  I don't play it too often and when I do I just 
run a Virtual Desktop and it doesn't crash… someone gifted me a Lifetime 
Membership back during beta so it is free to me :-)

on RCT3 - I had tested it 4 times before I sent that email… but now I went to 
get more logs and its working fine… 100% fine, and no idea why.  Its launching 
with no problems now and it switches fullscreen and windowed with quartz-wm 
acting great with it… I have no idea why it was solid white the first 4 times.  
It sticks in the screen captured mode fullscreen though, but I'm not sure thats 
an XQuartz problem, it looks like the game is not sending anything to Wine to 
know it should be trying to change resolutions again…. and it won't affect 
Wineskin since it is going to shut down the whole X server and switch back 
wether the game says to or not.

Neverputt… you can play with that easily since its free, and it works by 
default in almost any version of Wine platinum.  I do not know why it auto 
minimizes, but you can get it back… the troubling part is that quartz-wm just 
vanishes and the windows are then non-decorated… but that might all be part of 
the bug you are talking about.  Wine already has known issues with window 
managers quite often, is why they have the option to disable them anyways.

XQuartz has come a long way in the last couple of years  :-)

On Sep 29, 2011, at 2:47 PM, Jeremy Huddleston wrote:

> 
> On Sep 29, 2011, at 12:35, doh123 wrote:
> 
>> Only got 3 game I can find I already have here that have an option to change 
>> between window and fullscreen that wants to take place while running.. not 
>> restarting the whole game.
>> 
>> Neverball is a freebie thats easy to test on… and its very problematic if 
>> Wine allows the window manager access to the windows.
>> If starting in a window, then going to fullscreen, it minimizes itself, and 
>> I have to select it from the 'window' menu to see it, then it looks like its 
>> working… but if you then go back to windowed, the actual window decorations 
>> are gone, even though there is still space for them, and then toggling back 
>> to fullscreen again keeps leaving that extra empty space at the top with the 
>> picture pushed down.
> 
> yeah, there is a bug in quartz-wm for minimization/maximization that shows up 
> in Wine.  I'm guessing that this is the issue you're seeing here rather than 
> fullscreen.
> 
>> 
>> Star Trek Online (and Champions Online… since STO is a re-skin using the 
>> same engine and interface).. used to just crash right away….  Now it seems 
>> to go from the log in window thats windowed with quartz-wm decoration, to a 
>> fullscreen mode just fine… but I cannot get back out, because at times when 
>> trying to change resolutions, or switch to windowed, or even hit Cmd+Opt+A… 
>> it crashes X11.bin with a "Could not destroy window 252 (3)." or similar 
>> destroy error.  This is not related to quartz-wm though because if I disable 
>> quartz-wm the same crash happens… and it also happens on 1.9 and 1.10 series 
>> servers.  I'll attach the crash if you wanna look at it.. it is kinda 
>> annoying and happens with my builds too.
> 
> Thanks.  That's an assert that we're calling due to a FatalError in 
> xprDestroyFrame.  Additional logs might help explain why we weren't able to 
> destroy that window.  Is there anything free that reproduces this?
> 
>> 
>> On Roller-coaster Tycoon 3, if Wine isn't stopping quartz-wm, then the 
>> screen just goes white… you can hear the sounds and click through things and 
>> hear the menu is working and everything, but all you can see is a solid 
>> white screen.  Another problem with this game… wether or not quartz-wm is 
>> doing its thing, when you exit out of the game during fullscreen, XQuartz 
>> stays stuck in the fullscreen mode and I have to Cmd+Opt+A out.
> 
> Are you seeing any CGErrors in your logs?  That sounds like some surface 
> sharing isn't setup right for DRI.
> 
> 
> _______________________________________________
> Xquartz-dev mailing list
> Xquartz-dev@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
> 


_______________________________________________
Xquartz-dev mailing list
Xquartz-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev

Reply via email to