Before running the script, put it in the directory where you store your installer. This way the script should find it automatically.

Instead of installing The Witcher: Enhanced Edition installed an older version. I hope somebody will write me how to fix this.

I’m not sure to understand your issue, the ./play.it script installs the game shipped in the GOG installer you used, nothing else.

Well, I think it's time to give up on this thing. Wasn't going to play the game anyway, just wanted to see if these various scripts would work.

Code is on the long side so I put it on pastebin: https://pastebin.com/RNNJRd22

Besides it not working out, I was also a little discouraged by extra folders being created when I specified a custom one. Looks like the script created games/game-name, which would make my folder structure a bit messy.

First time I forgot that I had the files on the NTFS disk. The script ran through everything, but the .deb never appeared, just a folder with some sub-folders were left over from the building process. Lots of wasted time.

edit: Maybe my disk names make me look like a gun nutter, but they're named such becasue I'm an AC/DC fan, they have a song called Big Gun, and in a moment of low creativity I chose Big Gun and Small Gun for the big and small disk :blush:

I think this is once again an issue related to spaces in directories names. I will set up a test environment to see if I can provide better support for these.

Hi to everyone!

On Opensuse forum I wrote a post about "How I made this works!" ))))

May be it will be usefull...

Today I've installed GOG The Witcher Enhanced Edition Director's Cut under WINE 2.13. AMD FX 6350 + Radeon HD 5850. And there were a lot of graphical bugs:


strange black lines every were around
bad shadows and lights
black textures, black trees, black druids bread


After 6 hours of research, I found solutions and now I can play with pleasure!!! Here are screenshots in archive as attachment.

Here is a solution. I hope It will be useful:


Open regedit for wine (I'v installed q4wine): /usr/bin/q4wine-cli -p "Default" -d "system" -i "regedit"
Create subfolder: HKEY_CURRENT_USER\Software\Wine\Direct3D
Make string variables there: CheckFloatConstants=enabled, VideoMemorySize=1024 (your_video_carb_memory_size in MB)
In console: winetricks d3dx9
Winecfg: Windows version=Windows 7, DLLS: d3dx9_36 = native



cat /etc/X11/xorg.conf.d/50-device.conf

Section "Device"
Identifier "Device0"
Driver "radeon"
Option "monitor-DVI-0" "Default Monitor"
Option "EnablePageFlip" "on"
Option "DRI" "3"
Option "TearFree" "on"
Option "ColorTiling2D" "on"
Option "AccelMethod" "EXA" #valid options are XAA, EXA and Glamor. EXA is the default.
Option "RenderAccel" "on" #enabled by default on all radeon hardware
Option "ColorTiling" "on" #enabled by default on RV300 and later radeon cards.
Option "EXAVSync" "on" #default is off, otherwise on. Only works if EXA activated
Option "EXAPixmaps" "on" #when on icreases 2D performance, but may also cause artifacts on some old cards. Only works if EXA activated
Option "AccelDFS" "on" #default is off, read the radeon manpage for more information
EndSection


My system by glxinfo is:

direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4

client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:

Extended renderer info (GLX_MESA_query_renderer):
Vendor: X.Org (0x1002)
Device: AMD CYPRESS (DRM 2.49.0 / 4.4.76-1-default, LLVM 3.8.0) (0x6899)
Version: 17.0.5
Accelerated: yes
Video memory: 1024MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.1
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.0
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD CYPRESS (DRM 2.49.0 / 4.4.76-1-default, LLVM 3.8.0)
OpenGL core profile version string: 4.1 (Core Profile) Mesa 17.0.5
OpenGL core profile shading language version string: 4.10
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

Big thank you for sharing your findings with us ;)
I’ll see if I can include some parts of it into the ./play.it scripts, to avoid others the long search you had to go through.

You are welcome!

All that The Witcher needs is CheckFloatConstants=enabled and native d3dx9_35 (all mentioned in my report: https://www.gog.com/forum/general/the_judas_does_this_run_in_wine_thread_v1173/post42 ). It also needs a Wine version later than 1.9.5-staging, as that was when CheckFloatConstants was implemented IIRC.

I’ve had a good experience with The Witcher on WINE 1.8.x, with an AMD GPU + Mesa drivers, so CheckFloatConstants might be needed only with some drivers. If it’s related to WINE bug #34052 (The Witcher: Character models are sometimes invisible), I never experienced it, but this one seems to be nvidia-specific.

About d3dx9_35, it’s already installed by the ./play.it script when you run the game for the first time.

Yes, it does seem to be an Nvidia-specific thing (before it was implemented I experienced this problem a lot on my old system with an Nvidia GPU - haven't really tested without setting it on my new system though), but having it enabled doesn't cause any problems for AMD/Intel GPUs.

That’s what I wanted to know before adding this tweak to the ./play.it script, it should be done soon ;)

Actually, it has a minor performance impact (even for Nvidia). It largely seems to be smaller than even the Wine devs were concerned about. It also provides zero benefit if the driver in question doesn't implement the spec as undefined as the binary Nvidia driver does.

The ./play.it script will apply this tweak only in the WINE prefix dedicated to The Witcher, so if the performance impact is not too heavy it should go unnoticed as it won’t affect any other game.
If people start to experiment slowdowns after I add this to the script, I think I’ll disable it until I find a solution to apply it only if the binary nvidia driver is used.

The game is old & not very demanding by today's standards so I wouldn't worry about it. When I was testing my wrapper it seemed to run just fine even on an i3-6100 with integrated graphics.