https://bugs.winehq.org/show_bug.cgi?id=45375
--- Comment #30 from Paul Gofman gofmanp@gmail.com --- (In reply to halome from comment #28)
Created attachment 65480 [details] wine 4.19 logs
the log files are empty.
I also did a second test. When I boot up the game and load Last Resort and go to the beach. The distance was when you look out into the sea but when your on the beach below a certain Z axis level the map will turn black but once you your above the z axis the black textures will disspaear. This is how I ran the game in the terminal to get these results. My cmst is set to 0, and my multiply_special is set to 2 in the registry.
This looks pretty much like the issue described in Comment #24 p2, which was concerned here initially. Please note that 'multiply_special' has no effect on mainstream Wine, it is in Wine Staging only. Are you using Wine Staging to test this? The memory issue is the same between development and Staging.
env WINEPREFIX="/home/USERNAME/PlayOnLinux's virtual drives/HaloOnline" wine "C:\windows\command\start.exe" /Unix "/home/USERNAME/PlayOnLinux's virtual drives/HaloOnline/drive_c/Halo Online/eldorado.exe" pulseaudio --disable-shm=true > haloonline.txt
That's not how it works. pulseaudio has nothing to do with Wine, or even less so with game executable command line. It is host daemon which runs an instance per each user session. You can get some basic idea from 'man pulseaudio' or searching some information on the Web. It is known to be one of the major VM space users if run with its typical default parameters. To do what I suggest to try (along with the latest Wine version), you should do the following before running the game with Wine:
1. Kill currently running instance. E. g., 'killall pulseaudio'. 2. Start it from the terminal; 'pulseaudio --disable-shm=true. 3. Find the newly created process and make sure it is started: ps <pid>