[REL] Dummy D3D DLL's that draws nothing in 3D mode
-
Thanks! Why not run it on Linux?
-
I might try that. Is the install the same? Just copy those files into the bin directory or do I need to install Wine first?
Iâve wanted to use Windows cuz it was easier for the less technically inclined to setup and use RDP versus VNC but Iâll try Linux if the install is just as easy as Windows.
-
https://github.com/sthalik/wine-hacks/tree/wined3d-null - Wine branch that works
tightvnc has GLX (needed for llvmpipe)
mesa-gl (use softpipe, llvmpipe is buggy, can use debian sidâs libgl1-mesa-swx11-dev). No need for libosmesa.RDP wonât work cause Falcon wouldnât persist in the background. Have to use persistent session that doesnât logout.
-
Testing now on a VM
-
RDP wonât work cause Falcon wouldnât persist in the background. Have to use persistent session that doesnât logout.
RDP with the /admin flag connects to the console, or does that not work either?
-
Try. If it works, please report back
You need d3dx9_43.dll anyway, stock one will do.
-
sthalik,
Did you just get divorced or lose your job or something? You seem quite prolific this week.
Just kidding of course. Hope it works keeping the server stable.
-
Got a few days off due to people testing my workâs product without the need for my involvement.
Please tell me of success stories as well as problems.
-
RDP wonât work cause Falcon wouldnât persist in the background. Have to use persistent session that doesnât logout.
RDP works fine with a Windows to Windows connection. You just use Disconnect rather than Logoff (its in the menu or just close the RDP window). BMS runs fine in the background and when you log back in, everything is as you left it. That is how I tested your fix previously.
-
-
When I unzipped it to the bin/x86 folder, it created a folder with the dllâs in it. Is that correct, or should the dllâs themselves be in the bin/x86 folder? And is that new execute necessary, or just needed for debugging? And, where do I find WINEDEBUG, to set it to -all?
-
When I unzipped it to the bin/x86 folder, it created a folder with the dllâs in it. Is that correct, or should the dllâs themselves be in the bin/x86 folder? And is that new execute necessary, or just needed for debugging? And, where do I find WINEDEBUG, to set it to -all?
AFAIK the dllâs have to be in the x86 folder. At least this worked on our lenovo t-61 notebook âserverâ (win7)
-
Excellent work sthalik! Currently compiling your wine branch for x86 linux mint for testing.
-
AFAIK the dllâs have to be in the x86 folder. At least this worked on our lenovo t-61 notebook âserverâ (win7)
Thought so, but I had to ask. Thanks.
-
when u say u tested it⌠well u say it works,but how correct is that? what i mean is in 2d there are synch problems. with this have u measured cpu load? or fps count? I know asking for a fps count in souch solution is way odd, but itâs a good number that reasures u that the engine works ok.
-
Hmmm, compiled and successfully installed the wine branch. Now I get over the menus (without the new wine it crashed after clicking âLaunchâ) to the loading screen but there it crashes
LLVM ERROR: Program used external function ââ which could not be resolved!
Itâs a virtual machine (virtualbox-ose with linux mint x86). Is it supposed to be running in a virtual machine?
Best regards
Loki
-
Loki: it has to work.
Why are you using LLVM?
First post includes instructions how to use softpipe instead of llvmpipe.
http://wiki.winehq.org/WineD3DOnWindows
You need git mesa of course.
If you use llvmpipe youâre gonna get not just that, but REALLY NASTY AND UNSOLVABLE CRASHES. You have been warned!
-
Copy thanks for the fast reply. Iâll have to dig deeper I guess.
-
You can use generic configure script instead of scons on UNIX. The scons script is only required on Windows. You can even make yourself a Debian package and hold it if you know how to modify debian/rules.
-
Thanks for the fast answer again! Just that I get it right: I need your modified wine running (I think I got that covered) Itâs seems to be running because it enables me to get into the main ingame menu of BMS. I can successfully start a campaign and so on⌠(As I already said it just crashed after the loading screen before the 3D world) The configure parameters donât have to be special right?
Plus: The git version of mesa. Thatâs where I am stuck a bit now⌠Am I missing something else? And is there an easy way to tell the mesa autoconf script not to care about outdated libdrm_radeon (which weâre not going to use anyway AFAIK)? Itâs surprisingly annoying to convince this thing not to look for thatâŚ
In case I make it to âmakeâ ^^ do I need special build parameters for mesa?
Did I forget something important? I am really looking forward to a low profile falcon bms host on a linux system!