Discussion in 'Crossover' started by Gizmo, Jun 30, 2013.
Not GOG, no, just Unreal Tournament. II and III are there, but not the original.
Do you think searching for GOG UT would make a difference?
Oh, wow, there it is: GOG.com - Unreal Tournament GOTY
Well, that fixed it. Works like a champ now.
Really? cool, guess the Game Of The Year edition has all the patches and updates.
Did you install with the GOG script or the GTOY script?
Funny that they are separated even though its the same game.
Not sure what you mean? There was no script for plain UT, GOTY or otherwise, only for the GOG GOTY edition and GOG UT Gold.
On a side note, it installed wine 1.4.1. I wonder if the thing would work properly under 1.6 with the addition of the POL script?
Sorry, I rarely search the PlayOnLinux database when I install a game...
Ok now I did.
You are right... the only Unreal related scripts are for GOG.com
Definitely install newer versions of Wine first. They have a lot more success than the older versions.
Try Wine 1.7 or 1.6-rc4
Remember you can always use the Wine Manager in PlayOnLinux to try your game in another version of Wine.
There are a lot of patched versions of Wine available too.
1.6 was what I tried it under first, and it puked. Research has suggested a number of potential reasons. I'm assuming the POL script takes all the fixes and rolls them in, which is why I wondered if the POL script would work with 1.6, with suitable modification.
One thing I have not been able to figure out is if you change from one Wine version to another, do they affect the Windows DLL's in the virtual drive? Does Wine leave residual registry settings and DLL's every time you apply one to a virtual drive?
If yes, then I can definitely see a possibility of corrupting files and causing problems.
I'm leaning more towards "no" because I havn't seen very many errors indicating a problem from one Wine that wasn't there in another Wine.
I change Wine versions all the time and I'm pretty sure it is totally independent of the virtual drive. Which make it nice for testing one game with many Wine's to discover which is the perfect match.
I have found that Wine 1.5.25 & 1.6-rc4 are both very stable.
If you are still having problems with Unreal, its probably time to start over with a new virtual drive and install again.
Hell, I recommend NOT using the provided script and actually doing a manual installation instead.
I've had a lot more success this way.... mostly because the scripts are not updated for newer versions of Wine, PlayOnLinux, patches, etc.
Well, as I said, I ripped wine out by the roots, deleted the virtual drive, the whole nine yards, reinstalled, and it was still sporadic at best, under 1.6 (I don't know what rc, the Fedora 19 package just says version 1.6 release 1.fc19).
Not good. WineHQ seems to show that Wine 1.5.17 & 1.5.22 & 1.5.2 run it as Platinum.
Oh, did I tell you to do these steps?
Select Unreal Tournament GOTY virtual drive
Click on display tab
GLSL Support: default
Direct Draw Renderer: opengl
Video Memory size: check your video card specs
Off-screen rendering mode: backbuffer
render target mode lock: default
Strict Draw Ordering: default
Also did you do these changes in the:
/home/username/.PlayOnLinux/wineprefix/drive_c/program files/unreal tournament goty/System/UnrealTournament.ini
OpenGLDrv.OpenGLRenderDevice UseS3TC "true"
GameRenderDevice to "D3DDrv.D3DRenderDevice"
FrameRateLimit to "60"
SwapInterval to "1"
Tried your advice with 1.6, still unreliable.
I've never had so much trouble with an older game like this.
I noticed on WineHQ's that they mention OpenGL was never finished for Unreal Tournament... maybe that has something to do with it? But, they have gotten it to run.
Its on my list now, if I can't do it, nobody can!
Yeah, but it's solid as a rock with 1.4.1 and the POL scripts.
How do you look at the POL scripts to see what they are doing? I'd like to see what the POL scripts using 1.4.1 do when run using 1.6.
Man.... asking the right question to the wrong man.
I'm going to find out, they do a great job keeping everything online for us.
They have a GIT repository: https://github.com/PlayOnLinux/
Now that I think about it... there is probably a directory where the scripts reside after downloading them.
While I was working on the POL manual I discovered something...
In the Display settings for your virtual drive the Direct Draw Render has a GDI setting for legacy engines.
Specifically ones that have bugs in OpenGL. I wonder if this setting would fix your problems with Unreal Tournament since OpenGL was never really finished?
Try setting Direct Draw Renderer: GDI
Do a Windows Reboot and try launching again.
Yeah, that didn't fix it. I can still run it in 1.4.1, but even 1.7.0 crashes with the GDI setting.
It runs in 1.4.1? How well does it run?
We come up with sooo many great solutions...why the hell won't they work!! ":O}
Separate names with a comma.