Guys, I am having a problem (found a partial solution here in previous page) about missing/using native d3dx9_43.dll and correct loading of JPEG textures. Yes, I am using wine-1.7.29 (Compholio).

$ env WINEPREFIX="${HOME}/.wine" /usr/bin/wine C:\\\\Games\\\\LFS\\\\LFS.exe
fixme:winediag:start_process Wine-Compholio is a Wine testing version containing experimental patches.
fixme:winediag:start_process Please don't report bugs at winehq.org and use our issue tracker instead:
fixme:winediag:start_process https://github.com/compholio/wine-compholio/issues
fixme:d3d:resource_check_usage Unhandled usage flags 0x10.
fixme:winediag:AUDDRV_GetAudioEndpoint Winepulse is not officially supported by the wine project
fixme:winediag:AUDDRV_GetAudioEndpoint For sound related feedback and support, please visit http://ubuntuforums.org/showthread.php?t=1960599
^[ err:d3dcompiler:compile_shader HLSL shader parsing failed.
err:d3dcompiler:compile_shader HLSL shader parsing failed.
fixme:d3dcompiler3DAssemble flags 1
...
err:d3d_surface:surface_load_location Surface 0x22db9b0 does not have any up to date location.
err:d3d_surface:surface_invalidate_location Surface 0x22db9b0 does not have any up to date location.
err:d3dcompiler:compile_shader HLSL shader parsing failed.
err:d3dcompiler:compile_shader HLSL shader parsing failed.
fixme:d3dcompiler3DAssemble flags 1

I think I should attach some pictures to be more clear.
Any help would be appreciated. Thank you!

PS: glxinfo |grep direct
direct rendering: Yes

PS2: 0.6G is more affected by this "bug".

Same thing seems to be happening on OSX with Wine now too, just tested it.

Whatever happened between some of the previous test patches (early ones worked fine) and the 0.6G final version broke Wine support.

So 0.6F should work correctly?

Quote from Matrixi :

Whatever happened between some of the previous test patches (early ones worked fine) and the 0.6G final version broke Wine support.

for the first time reading something like this ^^ i have no suspicion at all that wine support was broken on purpose

unfortunately i think with broken things on linux you either maintain both sides of the code yourself or have a lot of patience.

Quote from Michalxo :

So 0.6F should work correctly?

Works for me atleast. Tried .6F on both Winebottler and Wineskin on OSX, no problems after injecting the d3dx9_43.dll file.

Quote from CarlLefrancois :

for the first time reading something like this ^^ i have no suspicion at all that wine support was broken on purpose

unfortunately i think with broken things on linux you either maintain both sides of the code yourself or have a lot of patience.

What?

All you should need is D3DCompiler_36.dll and d3d9_36.dll or newer to get LFS working again. Mine works perfectly with rev. 43 versions of these libraries.

You need also GPU which supports pixel shaders (I have one).
And to install the DX dlls, like MadCatX wrote.
And some reasonably fresh wine version (lacking on my side, so I'm without working shaders too right now).

Under recent linux + ok GPU + DX dlls installed it should work well (several people reported that it works).

You do need the 43 versions:

D3DX9_43.dll
D3DCompiler_43.dll

We are not allowed to supply them in our download, unless we supply the entire runtime. But nearly everyone has it installed, and those who don't are directed to the MS site to get it. On Wine it's different but I hear you get these files by using Winetricks.

Can confirm, injected D3DCompiler_43.dll aswell and now 0.6G is running flawlessly.

I would just like to notify you of a question by another user, something about gallium9:
https://www.lfs.net/forum/thread/86897-0-6G-broken-in-wine-with-gallium9

Speaking about LFS on Wine... Any idea why LFS crashes when you copy a message from the chat in-game and try to paste it somewhere else?

Copying the message is fine but when you hit CTRL+V LFS crashes instantly.

I don't know much about Wine but that sounds strange as you would LFS to be unaffected by pasting something somewhere else, even if that clipboard entry originated from LFS. Is there a crash address or offset in a crash message, so I try to see where in LFS the crash occurs, if it is in LFS?

Here is the error log that is outputted. This only started to happen since the last couple of updates (DX9 perhaps).

After linux upgrades (including wine) I gave the LFS another try, and I was still having problems with pixel shader.

When I run winetricks in GUI mode, I could not find the d3dcompiler, but running this in terminal:

did install the shader compiler, and now LFS 0.6G works for me too.

Also while I was experimenting with winetricks, I checked also DirectX sound dll ... very bad idea , you do not want this. So I reverted back (actually set it up nas (builtin, native) calling option). All's fine.

I just somehow lost keyboard config (back to default mouse LMB=accel, while I had it on "a") in the meantime (during one of OS upgrade steps, but not first one (I was going trough three of them)), weird. Not sure, if it was wine upgrade related, or LFS.exe itself action.