WINE is just a compatibility layer, so no such option.
It integrates your Windows programs/games with Linux/MacOS/Unix (BSD,openBSD,etc) it's not a "virtual" desktop type thing.

Although I do appreciate the reminder of how to do it in WinXP.
It's been 3+ years since I had XP on a PC.
All the other PCs in the house (none of them mine) are all 7 and newer.

At this point seems like the Virtual machine with the GPU pass-through (thereby allowing the "virtual" OS to "see" the physical hardware) running an older version of the OS, is the best option. Pending a bugfix.

Barracuda

Surely they didn't do like MS and decide that "you don't need that old stuff anymore", did they?...

I think it's just a bug in the driver.

There have been many improvements to the driver over the last few years.
Also WINE has added several things... I think it's just a case of work on new stuff invariably messes with the old.

Similar to moving in furniture, you can catch a wall or corner, and mess up all that drywall and/or trim work... End result, you have to fix it.


Using the native Linux version Counter Strike Source, running the stress test, I got the following results over the last few years:

Shortly after I built the PC, running 1920x1080, Detail maxed, 8x AA, 16x Anistropic (sp?) Filtering.
Motion Blur, Bloom and High Dynamic Range all turned OFF.
(Mainly because I hate those "visual tweaks".)

XFX R7 370X @ 1050mhz (factory OC)
Gigabyte R9 380 @ 980mhz (factory OC)

Averages:
With FGLRX:
R7: 273fps
R9: 253fps
R9 OC'd to 1050mhz: 263fps
Any higher and the R9 would be unstable.

switch to AMDGPU/Mesa (RadeonSI driver) (~kernel 4.9):
R9: 233fps

Then:
R9: 213fps

Later still:
R9: 230~ish

Kernel 4.13-4.14:
R9: up to 257-260fps
OC'd to ~1050mhz: 263fps

EDIT: May have been Mesa 17.2.4... Last file I can find on my PC.
Current: Kernel 4.15.2/4.15.3/mesa 17.3 (RadeonSI driver),
R9 @ factory 980mhz: 273.94fps avg.

EDIT: w/ mesa 17.3.5:
EDIT: R9: 276fps
EDIT: It's climbing again.

The highest it's been for the for the R9 EVER, and matching the older R7.
In addition to adding the Polaris (RX 4xx/RX 5xx) and the Vega 56/64 too.

So I'm sure in all of this, plus wine, someone probably commented or typo'd something somewhere.

Barracuda

IT'S FIXED!!!


A few days ago I upgraded both the kernel and wine.

I had just played through Homeworld: Cataclysm (~2000) and decided to have another run through the original Homeworld (~1999) since it has been at least a few years since I played it.

I upgraded wine to 3.3 and the kernel to 4.15.7 and was about to start Homeworld...

Then I remembered I hadn't checked SH4 yet, so I started it up, and no flickering!!!

So I quit, and started via the terminal to see the output.
I'm still getting the FOCUS LOST/FOCUS RECEIVED messages in the terminal, but no flickering.

I tried the "Battle off Samar" single mission and all was working correctly.

So as soon as I finish my run though Homeworld I plan on resuming my saved game.

I'm still not sure which part was causing the error... but that's what you get for riding so close to the leading/bleeding edge.

Barracuda

I can confirm that sh3 is working as well :up: , only thing I did is updating to kernel 4.15.7 , wine and everything else unchanged .

So it was the kernel....
Good to know.:up:

I'll edit my first post, so anyone that runs across this thread doesn't have to read 3 pages to find the answer.

Barracuda