Application Details:
Version: | Steam |
License: | Retail |
URL: | http://limbogame.org/ |
Votes: | 0 |
Latest Rating: | Gold |
Latest Wine Version Tested: | 1.9.18 |
Maintainers: About Maintainership
What works
Game play, achievements, steam cloud sync from Steam cloud.
What does not
Full screen video
Workarounds
What was not tested
Hardware tested
Graphics:
Additional Comments
Full screen does not work as it runs in black screen. Installation as follows: WINEPREFIX="/home/user/.wine-limbo" winecfg Note this would be using a 64bit version of Wine/Windows. Owner name was set. Mic set to USB mic. Windows version set to Windows XP. Steam was installed by: wget http://media.steampowered.com/client/installer/SteamSetup.exe cd "/home/user/.wine-limbo/drive_c" wget http://media.steampowered.com/client/installer/SteamSetup.exe WINEPREFIX="/home/user/.wine-limbo" wine ./SteamSetup.exe An error appears, but it is irrelevant as the steam client installs and then begins to update. Upon updating, Limbo is selected to install. Steam is then closed down. The following file is edited: vi /home/user/.wine-limbo/drive_c/Program Files (x86)/Steam/SteamApps/common/Limbo/setings.txt Change: windowmode = false to windowmode = true Relaunch game with: WINEPREFIX="/home/user/.wine-limbo" wine "C\Program Files (x86)\Steam\Steam.exe" Launch game from library. This runs game in a small window as it wants to run in 720p. Good luck.
Operating system | Test date | Wine version | Installs? | Runs? | Used Workaround? | Rating | Submitter | ||
Show | Gentoo Linux x86_64 | Sep 02 2016 | 1.9.18 | Yes | Yes | No | Gold | Rob | |
Show | Gentoo Linux x86_64 | Feb 19 2016 | 1.9.3-staging | Yes | Yes | No | Gold | Rob | |
Show | Gentoo Linux x86_64 | Dec 29 2013 | 1.7.8 | Yes | Yes | No | Gold | Fletch Hasues | |
Show | openSUSE Tumbleweed (rolling release) | Dec 26 2012 | 1.5.20 | Yes | Yes | No | Platinum | Rob | |
Current | Gentoo Linux x86_64 | Dec 01 2013 | 1.4.1 | Yes | Yes | No | Gold | Fletch Hasues |
Override the following dll 's before (or after) installing Limbo:
export WINEPREFIX="❚❚❚❚❚❚"
winetricks d3dx9_43 d3dcompiler_43
In the instance of a failure you would find Limbo might fail to launch successfully (backtrace will indicate a failure in d3dcompiler_43), e.g.:
Backtrace:
=>0 0x056396a9 in d3dcompiler_43 (+0x1e96a9) (0x0033e238)
1 0x055285e4 in d3dcompiler_43 (+0xd85e3) (0x0033e63c)
2 0x0552750e in d3dcompiler_43 (+0xd750d) (0x0033e668)
3 0x054b6e6f in d3dcompiler_43 (+0x66e6e) (0x0033f3a4)
4 0x100e6186 in d3dx9_43 (+0xe6185) (0x0033f650)
5 0x004862e3 in limbo (+0x862e2) (0x03058489)
Alternatively you might see a vertex error KW_VERTEX popup dialog from Wine.
Note: you only need to specify the WINEPREFIX env variable if you are not using the default location: WINEPREFIX="${HOME}/.wine"
More recent test indicates that the issue is still present in Wine release wine-1.9.18 (Vanilla).
"First Time" Setup
To stop the firstevery time (!!) setup of the MS DirectX redistributable, for the default SteamApps location, in a 32-bit Wineprefix:
rm -rf "${WINEPREFIX}/drive_c/Program Files/Steam/steamapps/common/Limbo/DirectX_Redist"
... or for the default SteamApps location, in a 64-bit Wineprefix:
rm -rf "${WINEPREFIX}/drive_c/Program Files/Steam/steamapps/common/Limbo/DirectX_Redist"
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
by Marcin on Sunday August 28th 2016, 4:24
by Rob on Sunday August 28th 2016, 17:10
What's your Desktop Environment?
Graphics card and driver?
Any fancy (Wine) mouse warp settings? :-)
I'll try and reproduce the issue - if you can give me some idea of your setup!!
Thanks
Bob
by Marcin on Monday August 29th 2016, 1:40
So I have a laptop with Kubuntu 14.04.3 x86.
I have wine 1.9.16 + wine-staging 1.9.16
installed DirectX.
My graphic card is intel graphics 3000 (my built-in card, I haven't installed my nvidia card drivers because I have been afraid of my linux will crash).
I have default driver.
No, any fancy settings. Mouse is working fine, but the game is not.
by Rob on Monday August 29th 2016, 4:30
I've just supported a chappie (who I used to work with) fix his Ubuntu Mate 16.04.1 install... He's using a decent Intel Haswell generation IGP Core i5... The interface was freezing up and the CPU core's were spinning hard just to run Mate's Compton compositor (yeh - even a RaspPi Zero could run that DE!!)
Wtf - I thought - time to nuke that out-of-date Intel graphics driver...
You would need to purge:
launchpad.net/ubuntu/+source/xserver-xorg-video-intel
I set a grub kernel modeset line (I think - appeared to work):
i915.modeset=1
See:
wiki.archlinux.org/index.php/intel_graphics
I'm an "Nvidia guy" so I don't much about the Intel i915 graphics stack. But what I did seemed to fix all the stock Ubuntu weirdness...
Your graphics stack is from the Sandy Bridge generation... That's the first of the "modern" Intel IGP's that this procedure would apply for.
by Marcin on Monday August 29th 2016, 5:25
xserver-xorg-video-intel-codename, where codename is vivid, trusty, and others.
I have trusty (14.04) but I have installed video graphic driver for vivid , but why ?
by Marcin on Monday August 29th 2016, 5:26
by Rob on Friday September 2nd 2016, 18:38
Btw I see you've edited your test results a bit - but left them in a limbo state (sorry couldn't resist that one!!) I can't currently access the updated test submission...