sarka |
Monday 9 December 2013 at 8:56
|
sarka
|
Hi
I got Steam installed very nicely with POL on Ubuntu 12.04.3 LTS, and it seems to work ok.
Whenever I try to launch Chivalry, I get the popup with MW and DW. I click on MW, and then I get an error with a bunch of Wine debug stuff that doesn't tell me anything.
From what I've read, it should be very easy to get this working :I What should I try? Is there someone that has made it work? Instructions?
|
booman |
Monday 9 December 2013 at 22:50
|
booman
|
First of all there is a bug with any Wine version 1.7.7 and older. They won't allow you to launch Steam. So make sure you are using Wine 1.7.8 Looks like some people got Chivalry running on WineHQwithout audio. The game requires directaudio and disabling d3dx11 There may be some graphical artifacts also. Chivalry just isn't getting good testing reviews. I don't have it so I can't testing it in PlayOnLinux either.
|
sarka |
Tuesday 10 December 2013 at 0:51
|
sarka
|
I just got it working!
Had ton install Steam as Win7 with Wine 1.7.8, vcrun2008 with same settings, dotnet3sp1 with Wine 1.5.2 and again dotnet4 with Wine 1.7.8.
Then d3dx11 disabled, virtual desktop with some appropriate resolution and Wine set to emulate XP and IT STARTED! Sound works, FPS is pretty good (but has sharp drops?). Very playable with low graphics by a short test run.
Some graphical glitches, less and more map-dependent. Parts of textures on distance are black - no idea why.
Now I have only BF3 to get working... That might take some doing :D
Oh, for some reason Ubuntu doesn't switch back to native (1920x1080) resolution when quitting the game, if the game is set to a lower resolution without virtual desktop. I would even argue, that FPS was better without virtual desktop, but other glitches make it very annoying to use.
|
booman |
Tuesday 10 December 2013 at 16:27
|
booman
|
Awesome! Honestly I don't think you really needed to do all of that. I have confirmed that Wine 1.5.18 will install any dotnet without problems... but of course Steam won't run.
I would install in this order: - Do a manual installation
- New virtual drive
- 32-bit virtual drive
- Wine 1.5.18
- Windows Version: Win7
- check virtual desktop, size: 1024x768
- Install dxfullsetup, dotnet 30, dotnet 40, d3dx11, vcrun2008
- Install Steam - Dont launch
- Steam shortcut
- Set your POL Display settings for opengl, memory and fbo
- Wine configuration - disable d3dx11
- Reboot Windows
- Change Wine to 1.7.8
- Set -no-dwrite
- Launch Steam
- download game or restore backup
- Launch game
- Adjust resolution for fullscreen (virtual desktop will automatically resize)
That should do it!
As for Battlefield 3, I've messed with it and Origins is a totall pain! If you can get Origins to download the full game and launch, then you have gotten farther than anyone else has...
|
sarka |
Wednesday 11 December 2013 at 8:07
|
sarka
|
* 11.5 Windows Version: WinXP
Chivalry launcher crashes if Windows version is 7.
Maybe I'll try Bad Company 2 first, seems that it's easier to do :)
|
booman |
Wednesday 11 December 2013 at 18:58
|
booman
|
Really? Chivalry won't even run with Windows set 7? Not cool. Remember when you re-install you don't have to download the whole game again. cut-n-pate the chivalry game folder to your desktop /home/username/.PlayOnLinux/chivalry/drive_c/program files/steam/steamapps/common Of course replace "username" with your loging and "chivalry" with the correct virtual drive name. This way you can just cut-n-paste the game back in the new virtual drive and then install. By they way... what is MW and DW? Do you know how to post the debug output so we can see errors?
|
sarka |
Thursday 12 December 2013 at 13:55
|
sarka
|
MW is Medieval Warfare and DW is Deadliest Warrior -addon. I haven't tried to get rid of the artifacts yet. Will get back to it sometime. It works very well with WinXP, I'll try to get the debug data for 7.
|
booman |
Thursday 12 December 2013 at 16:59
|
booman
|
Oh cool, I didn't realize they already had an addon... pretty cool. If I had Chivalry I would totally test it in PlayOnLinux for you. If I remember correctly, Chivalry was made with the Source engine... Maybe they will have a native linux port in the future since Source is now Linux compatible...
|
sarka |
Friday 13 December 2013 at 20:52
|
sarka
|
It's UE3 engine, and there has been some gossip about Linux port :) I hope it comes reality sometime...
|
booman |
Monday 16 December 2013 at 22:31
|
booman
|
It's UE3 engine, and there has been some gossip about Linux port :) I hope it comes reality sometime...
Right, I forgot it was UDK. I have successfully installed several UDK games in PlayOnLinux. None of them are multi-player, so I can't confirm if it works. The most recent game I have installed is Game of Thrones. Runs perfectly with basic libraries: - dxfullsetup
- vcrun2008
- vcrun2010
- physx
- corefonts
- tahoma
|
gwarokk |
Thursday 19 December 2013 at 3:30
|
gwarokk
|
For me the popup where you choose which game to play crashes, I can't seem to find a way around it...the game used to work until I got deadliest warrior
|
booman |
Friday 20 December 2013 at 0:44
|
booman
|
Hmm I've had a problem like this with Borderlands 2. I would actually launch steam and then go back to PlayOnLinux and make a new shortcut to Borderlands2.exe and launch it Try this with Chivalry, maybe there is some kind of "launcher" that isn't working properly?
|
gwarokk |
Friday 20 December 2013 at 3:12
|
gwarokk
|
True, this does work with running the original game. I can launch the exe separately. However running the deadliest warrior exe launches "chivlauncher" instead of the game. Kinda irritating.
|
booman |
Friday 20 December 2013 at 4:54
|
booman
|
Ah, that is the launcher, but is it still having problems? Are there any other .exe files for Chivalry?
|
gwarokk |
Friday 20 December 2013 at 5:49
|
gwarokk
|
It is having problems. The original game exe is called UDK.exe, I can launch it with that just fine. Deadliest warrior has its own binaries in a seperate folder with 64 bit and 32 bit versions, both called CDW.exe...those both execute the launcher. I found another binary inside the CDW 32 bit folder called ALPHA.exe which appears to start deadliest warrior (The splash screen appears) but that crashes also. So I really am at a loss here.
|
booman |
Friday 20 December 2013 at 17:13
|
booman
|
Ok, at least we tried. Always use the 32-bit exe's What happens when you launch UDK.exe? Does it actually launch the game or does it go to the launcher again? Lets go to the debug on those and maybe it will help us find out whats wrong. Make a shortcut with the ALPHA.exe and when you run it, click Debug instead. Then you will get an error/bug output. Then post it here. Also try it with UDK.exe and debug
|
gwarokk |
Saturday 21 December 2013 at 5:05
|
gwarokk
|
http://pastebin.com/0hm9k9EZ - this is for the ALPHA.exe
http://pastebin.com/C4SV5Xe8 - UDK.exe
http://pastebin.com/8p5rTM5w - And this is what happens when i try with the launcher, just for fun
|
booman |
Friday 27 December 2013 at 0:49
|
booman
|
I'm guessing none of them will run Chivalry since you posted outputs for all the EXE's.
I noticed some repetitive errors in all of your outputs.
I've seen these dbghelp errors before with other games. Notice the "addr64" make sure you are using a 32-bit virtual drive. You will probably have to install it again to be totally sure.
Also, you can set dbghelp in the Wine Libraries with different options. Like Native,Builtin, etc.... I would experiment with those settings.
fixme:dbghelp:validate_addr64 Unsupported address fffffffff71f0000
This error should be easy to fix just by enabling GLSL in PlayOnLinux Configure in the Display options. Set to Enable
err:winediag:wined3d_dll_init The GLSL shader backend has been disabled. You get to keep all the pieces if it breaks.
This error may be tricky, but I have seen other games that try to force DirectX 11 and you can disable it to fix the problem. Try going to Wine Configuration again and the libraries tab. Enter d3dx11 and click add Then set it for disable
fixme:d3d11:D3D11CreateDevice stub: adapter 0x175748, driver_type D3D_DRIVER_TYPE_UNKNOWN
|