Deus Ex: HR - Full Screen Issues (+180 issue)

[Cheekio]

Hello! First time poster so let me know if I miss anything in particular. The details:

Game: Deus Ex: Human Revolution - Director's Cut
OS: Ubuntu 14.04
Wine Version: wine-1.6.2 (installed from repo)
Graphics Card: Nvidia K1100 (2gb)
Driver: nvidia-331, straight from apt-get (with nvidia-primus, new to 14.04)
Processor: i7-4800MQ
System Ram: 8gb

Steps taken:

Installed Steam
disabled dwrite so as to get text in Steam
Installed the registry keys mentioned here: http://appdb.winehq.org/objectManager.p ... &iId=26695
Installed Spelunky (which required a d3 library and something else, figured I'd mention that works great)
Installed DX:HR
Installed PlayOnLinux and followed the above directions (but didn't get any confirmation it was working or not)
Turned off Steam Community Overlay


What's the problem:
Seems to be rendering the game correctly, but as I manually selected a low resolution on the first pass, the game is scrunched into a box in the top middle of my screen, with the extra screen area rendering as blank. The left launchpad bar in Ubuntu is clearly visible over the game, and I've got that damn 180 degree issue where the mouse decides to stop at screen's edge. Also may be some shadow rendering issues, but I understandably haven't played much.

This seems to be a stupid issue to be hung on, because the game is working nearly fine- it just needs to be a little bigger and actually grab control of the mouse. Any thoughts?

[Cheekio]

Boy do I feel stupid- I didn't see that topics were approved when you first come to the site, so I typed out the above post again when I thought it didn't got through the first time.

The second time around I took a picture to make clear my description of the visual bug. On the plus side, the game seems to play normally (with about 1 second of input lag) if I set my resolution to my laptop's native 2880 x 1640.

Would be an option if I had ten laptops running the game as a cluster, but with just one I think I need scaling!

[Cheekio]

Boy do I feel stupid- I didn't see that topics were approved when you first come to the site, so I typed out the above post again when I thought it didn't got through the first time.

The second time around I took a picture to make clear my description of the visual bug. On the plus side, the game seems to play normally (with about 1 second of input lag) if I set my resolution to my laptop's native 2880 x 1640.

Would be an option if I had ten laptops running the game as a cluster, but with just one I think I need scaling!

Also, how does one edit their posts on this forum?

[spoon0042]

I'm pretty sure there's an edit button under each post you made.

Anyway, wine 1.6.2 is out of date, you should try an updated version, instructions are here: http://www.winehq.org/download

You'll probably want to start with a clean wineprefix after upgrading, just delete ~/.wine if there's nothing important then repeat the steps other than installing PlayOnLinux - that isn't supported here. You should also poke around wine's appdb - http://appdb.winehq.org/objectManager.p ... &iId=13150 - the latest test results seem to say it mostly works.

[Cheekio]

I'm pretty sure there's an edit button under each post you made.

Anyway, wine 1.6.2 is out of date, you should try an updated version, instructions are here: http://www.winehq.org/download

You'll probably want to start with a clean wineprefix after upgrading, just delete ~/.wine if there's nothing important then repeat the steps other than installing PlayOnLinux - that isn't supported here. You should also poke around wine's appdb - http://appdb.winehq.org/objectManager.p ... &iId=13150 - the latest test results seem to say it mostly works.

Thanks for the advice!

I went forward with the uninstall of wine, flatten of the directory, and reinstall with wine 1.7 via the Ubuntu ppa.

Looks like I was selecting an unsupported resolution, so I tried 1366x768 and it at least seemed to go full screen. Incremental successes! It still is running into the 180 issue, and not correctly resetting the resolution upon close, but I can definitely live with the latter.

With regards to the 180 issue, I've tried setting "Automatically capture the mouse in full-screen windows", but that doesn't seem to make a difference. Are there any logs I can search through for reasons this would be breaking, or additional steps I can try to take to solve the 180 issue?

edit:

Welp: https://bugs.winehq.org/show_bug.cgi?id=33479#c29

That's disheartening, but it looks like there's an install via git workaround that I may be able to pursue. I'll be looking for a build via git guide, although it's unlikely I'll be able to keep the giant DX:HR download folder between git changes.

Does wine run straight out of the cloned git repo, or is the repo an installer?

Alse re:editing, apparently you can't edit your first couple posts. Makes sense to combat spam.

edit2: I cloned the git repo, remove/purged wine & wine1.7, and am make/make installing the repo sans the raw-input breaking commit. The bug was reported in 2013 and is still at large, so I might as well take matters into my own hands, right?

[olivierfrdierick]

Wouldn't the MouseWarpOverride registry key help with the mouse issue?

Source: UsefulRegistryKeys - The Official Wine Wiki

p.s. If you made the last post of a thread less than an hour ago then you can edit it.
If the post is older than an hour or someone replied to it then you cannot edit anymore.
That's how it works for me.

[Cheekio]

Good to know- I abuse the edit function on forums posts, so I'll do less of that here.

I'm very familiar with git, but I'm getting conflicting build information. I ran into my first error with a 32bit vs x64 error (I'm running a modern, 64 bit operating system), and these are the links that seemed most applicable:

http://wiki.winehq.org/WineOn64bit
http://wiki.winehq.org/Wine64#head-7996 ... 973d3b33e1

Not sure how to proceed, I can't imagine installing from the binaries is that hard, but having definitive, up to date guide would go a long way.

[spoon0042]

Did not know that about editing posts, heh.

Since you're using Steam you don't need to reinstall / redownload every time, just backup (I think) C:\Program Files (x86)\Steam\SteamApps somewhere (you can even stash it somewhere permanently and use a symlink).

Unfortunately to build on 64-bit systems you will need to go through the process described in http://wiki.winehq.org/WineOn64bit - luckily it seems to be less of a hassle on an up to date Ubuntu system at least.

Good luck.

[Cheekio]

After getting the WoW64 installation working, I installed steam and redownload DX:HR. Setting everything up, I run into this:



So it looks like I'm missing an important configuration step somewhere along the way. Any further thoughts? Again, the game renders great on the Ubuntu default package and on the 1.7, the only major changes to this git installation is that it reverts the raw-input commit.

Is there a reason why that hasn't been reverted in master? It's been a known, major regression bug since 2013.

[Cheekio]

Looks like if I run the program DXHRDC.exe, it kicks up steam and finally spits out that error message when it hits this line:

Code: Select all

fixme:d3d11:D3D11CreateDevice stub: adapter (nil), driver_type D3D_DRIVER_TYPE_HARDWARE, swrast (nil), flags 0, feature_levels 0x33d748, levels 0x1, sdk_version 7, device 0x33d750, feature_level 0x33d754, context 0x33d74c

I'm way out of my depth, I'm a python programmer so whatever Wine is written is might as well be Latin. You know, some of the words look familiar but I really have no idea what I'm looking at. Any debugging steps to get a build-from-source wine installation running like an Ubuntu package would be much appreciated!

[Cheekio]

Wouldn't the MouseWarpOverride registry key help with the mouse issue?

Source: UsefulRegistryKeys - The Official Wine Wiki

p.s. If you made the last post of a thread less than an hour ago then you can edit it.
If the post is older than an hour or someone replied to it then you cannot edit anymore.
That's how it works for me.

After I couldn't get the install from source working, as it's not interfacing with ubuntu/my hardware correctly, I tried installing wine from this ppa: https://bugs.winehq.org/show_bug.cgi?id=33479#c4

I'm not normally the one to install software from untrusted PPAs, so I'm clearly at the end of my rope. That setup, however, seemed to break videos, menus, and not allow the game to render at all, so I was happy to uninstall/remove the ppa.

After that I tried reinstalling wine1.7 via Wine's PPA and modified the above registry key, and it didn't have any effect on the mouse issue despite trying all values listed.

If anyone has any advice I'll gladly take it, I'm pretty much out of options!

[olivierfrdierick]

fixme: ...whatever... stub: means that the app made a call to a builtin DLL function that is not yet implemented in Wine.
This line is related to directx 11 which I think is not yet implemented in Wine.

8.1. Does Wine support DirectX? Can I install Microsoft's DirectX under Wine?

Wine itself provides a DirectX implementation that, although it has a few bugs left, should run fine. Wine supports DirectX 9.0c at this time. Plans for DirectX 10 are underway.

I don't think winetricks can install directx 11 either.

I just made a search about Deus EX Human Revolution DirectX version and found that the game uses DirectX 11 by default.

There seems to be an in-game option to set which directx version to use.
Obviously you cannot access that in-game settings, so I suggest to use regedit in Wine to check if there's a registry settings about directx version in HKEY_CURRENT_USER\Software\Eidos\Deus Ex: HRDC\Graphics\.
I don't have that game so I cannot tell which exact registry key to look for.

Source: FAQ - The Official Wine Wiki, Out of game setting configuration

[Cheekio]

That's a shame because the winehq ppa installations were having no problem with figuring out which DirectX version to use.

As I wasn't making any headway with the source, and ubuntu handled that so gracefully, I reached out to one of the ppa maintainers who made a patched-ubuntu ppa with a bunch of changes for guildwars. He more or less led me to try modifying a .deb package with the commit reversion. The process I followed is as follows:

First I cloned the git repository so I'd have access to the commit history:

Code: Select all

git clone git://source.winehq.org/git/wine.git .wine-git

Then I used revert to see the differences that the regression inducing commit introduced:

Code: Select all

git checkout -b revert/raw-input-commit
git revert 76bbf106a28c4caa82873e8450bde7d4adc765bf
git diff master

From there, I installed the wine ppa so I had access to the latest versions of wine, and downloaded the source of wine1.6 so I could revert the commit by hand:

Code: Select all

sudo add-apt-repository ppa:ubuntu-wine/ppa
sudo apt-get source wine1.6

(1.7's source isn't available via the ppa) Then I dove into the newly created wine1.6-1.6.2 directory, and found the file affected by the commit.





With those changes made to the 1.6 ubuntu package, I could let the commit reversion changes ride along with whatever magic is rolled into the ubuntu package that lets the source work on my machine:

Code: Select all

dpkg-buildpackage -rfakeroot -uc -b

That command took quite a while, but it left me with a slew of .deb packages that I could double click, and I ended up installing wine_1.6.2-0ubuntu4_amd64.deb.

It installed fine, so I went ahead with the regedit key additions, wineconfig changes, and installed Steam without issue. Now I wait for Deus Ex: Human Revolution to download so I can try it out. Steam says 1 hour and 27 minutes remaining, time to bust out a book or something.

Edit: Nope. Still the 180 degree mouse issue. No idea why, I reverted the code that apparently introduced the regression, but here we are. If anyone's got more ideas how to get around this, I'd be all ears.

[ZombieRedShirt]

Cheekio, did you have any further luck with DX:HR?
If you're still having trouble with the restricted mouse movement, I've solved that by building wine from the git repo and reverting the following patch:
git show 76bbf106a28c4caa82873e8450bde7d4adc765bf | patch -p1 -R

Make and configure the wine source after that and you should be good to go with DX:HR.
As for the problems you're having with shadows, I've found that they simply don't work properly in some areas and that shadows must be disabled completely. The rest of the graphics in the game work fine, however.

[Cheekio]

With regard to compiling from source, I'm not sure how the x32 / x64 stuff is supposed to work. I don't get why I don't need a slew of i386 libraries to install via the Ubuntu package repo but do if I try to install from source.

I'll try that route again, I guess.

[olivierfrdierick]

The i386 packages that you have to install when building Wine from source are development packages.
If you were building 64 bits wine you would have to install 64 bits development packages.
The Wine in the wine package is pre-compiled and so has no need of development packages.

[ZombieRedShirt]

Cheekio, I've been using a virtual machine (virtualbox to be precise) and ubuntu 11.10 to get my wine compilation done. It's a hassle, but at least it allows me to do what I've got to do. Not sure if you can do this yourself, but it's either that or a partition with an older install since more recent linuxes all have this unfortunate multilib problem.

[Cheekio]

I'll try the Ubuntu 11.10 trick. As soon as I get a compiled version working I'll try submitting the change as a patch.

[olivierfrdierick]

A few days ago I compiled Wine on Ubuntu 10.04 Lucid Lynx 64 bits.
I followed the WineOn64bit chroot Ubuntu part.
There are some differences in the name of some of the libraries (git is git-core for example) and the configuration file in chroot.d was ignored by schroot I had to put it in /etc/schroot/schroot.conf.
configure could not find some libs: libopencl-dev, liblcms2-dev and a third one, but those features seemed unimportant to me so I got on without them.
I could launch steam and connect. The game I was trying to play at that time did crash with an unhandled exception error but it's probably due to older libs in Ubuntu 10.04.

I also compiled Wine in a virtualbox debian 32 bit install last week.

Just saying that I never had problems compiling Wine so far.

[ZombieRedShirt]

Cheekio and Oliverfriedrick, when I made my post about using ubuntu 11.10, I should have clarified that I'm using that to build wine in both 32 and 64 bit forms. If all you want is 32 bit wine (which is what you get from the ubuntu repos) then you can just use the most recent 32 bit ubuntu (or preferred distro) in virtualbox.