Small issue with WinUAE under Wine

[P-J]

Hi guys,

Using the latest stable version of Wine (1.2.3) under Xubuntu, and having a tiny issue with WinUAE.

The emulator itself works amazing well, but the problem is in the GUI. It can be reproduced my hitting F12 to go into the config and then clicking either 'ok' or 'cancel'. When you hit either button, the emulation advances a couple of frames and then the GUI reappears and emulation paused again. You can repeat these steps ad nauseum, but the only way to recover is to hit 'restart' and then you can hit 'ok' and start the emulation again.

I realise Wine isn't likely to be high up on anyone's priority list but just wondered if there was a local fix I could do for this, or if it was something that Toni might be able to solve quite easily.

Cheers

//edit : I haven't provided any logs as I didn't think GUI issues would benefit much from logs, but I'll certainly provide them if it's necessary!

[mark_k]

That bug in Wine's keyboard handing has been around for a long time.
See http://bugs.winehq.org/show_bug.cgi?id=10643.

Comment 5 in the winehq bug page gives a workaround: after pressing F12 to bring up the settings window, click in the emulation window then press and release F12.

[P-J]

Originally Posted by mark_k

That bug in Wine's keyboard handing has been around for a long time.
See http://bugs.winehq.org/show_bug.cgi?id=10643.

Comment 5 in the winehq bug page gives a workaround: after pressing F12 to bring up the settings window, click in the emulation window then press and release F12.

Ah, lovely, thanks

I certainly wouldn't expect Toni to work around a WINE bug, I thought it might be something simple. Now I know this there's no WinUAE bug here

[mark_k]

As of Wine 1.5.16 the reappearing settings window bug no longer shows up, so using WinUAE is more comfortable.

(The Wine bug is still present, it's just that raw input support works in Wine now, and WinUAE uses that in preference to DirectInput.)

[jman]

Originally Posted by mark_k

As of Wine 1.5.16 the reappearing settings window bug no longer shows up, so using WinUAE is more comfortable.

Thanks for the hint, I'll give it a whirl under Lubuntu.
I'd like to compare the speed of FS-UAE against WinUAE/WINE.

[FrodeSolheim]

Originally Posted by jman

Thanks for the hint, I'll give it a whirl under Lubuntu.
I'd like to compare the speed of FS-UAE against WinUAE/WINE.

Just remember run with comparable settings when comparing the speed

One thing is that performance can be quite bad on Linux desktops right now, when using (most) compositing window managers with default FS-UAE settings. Unity is among the worst . This is not a bug in FS-UAE and affects other OpenGL apps as well - especially when syncing to vblank, which FS-UAE does by default.

Turning off compositing is best, but using video_sync = off will also reduce/remove the issue. With some desktop environments, running full-screen also sidesteps the problem. I have written some additional documentation here: http://fengestad.no/fs-uae/performance

[jman]

Originally Posted by FrodeSolheim

Just remember run with comparable settings when comparing the speed

Thank you very much for the heads-up! I've just installed FS-UAE and perceived a slight sluggishness compared to WinUAE, so I'll check your docs and see what I can improve.

By the way I'm using a pretty basic desktop manager (lxde) so I hope the footprint is low (wow and I'm talking about a AMD 965 with 8gb RAM!).