Jump to content

Kindling

Member
  • Content Count

    124
  • Joined

  • Last visited

  • Medals

Posts posted by Kindling


  1. It does, Roger, but the problem is that the function we require - D3D11CreateDeviceAndSwapChain - is within the base d3d11.dll which isn't provided by winetricks and doesn't work under WINE when copied from a Windows system (like many core Windows OS libraries). D3DX11 isn't provided in any redistributable, either, it's a core part of the Windows operating system from Windows Vista onward.

    I have tried to implement the function similarly to the currently provided workaround for EVE Online's DirectX 11 requirement, but this doesn't allow the game to launch and probably wouldn't have the game running if it did (many more DirectX 11 functions are likely required). The next potential issue after DirectX 11 is BattlEye - the BattlEye application requires a few functions that aren't currently provided by WINE and will need to be re-implemented from a 'black-box' or clean-room perspective to avoid infringing Microsoft's EULA.

    That's as far as I've been in considering ARMA3 support under WINE. To go forward, we need somebody to implement more of DirectX11 - Austin English's work seems promising in that direction. Alternatively, a native port of ARMA3 to Linux is required.

    I think we need to be wary about jumping to any conclusions from Gustavsson's interview, there - he's certainly interested in Linux as a platform, but I think that EA is more likely to sit in the background and watch for a while, yet. As they're directly competing with Valve in distribution, I'm betting that they'll be waiting to see if Linux becomes a more popular system or not before they jump to port anything, though perhaps they'll look at publishing some of their more obscure content under Linux to 'test the waters' (as BiS seem to be doing, themselves, with ARMA Tactics!). I could be wrong, of course, I've just become a little salty concerning promises of Linux support by now.

    That said, I hope that if they do port any games they do it natively. WINE is great as a way to run Windows binaries but it's been created only to translate Windows API calls to Linux ones - it's another layer between the hardware and software, another level of potential problems and performance issues. It still encourages the Windows 'way of thinking' and programming styles which are totally suboptimal under Linux. To get the most out of Linux, you have to port natively.


  2. @rogerx, D3D11CreateDeviceAndSwapChain: This is a known bug and it's due to a lack of DirectX 11 support in WINE. Currently, only the dedicated server application and (possibly) headless client application will run at all.

    @gagagu, missing dll: winetricks xact will work just fine, as will copying over a DLL from a Windows PC or (perhaps) going into winecfg -> libraries tab and adding 'xapofx1_5' as 'disabled'.


  3. Try:

    sudo apt-get install linux-image-extra-3.2.0-23-virtual
    sudo modprobe snd_dummy

    If you don't get an error, great - it worked!

    Hopefully that solves the dsound errors - the only crashes I've seen have been from BattlEye.

    If you do find yourself with occasional crashes (not so bad that it's unusable but bad enough that you find yourself having to check the server every few hours or so), you can try creating a wrapper script and cronjob. Something like:

    #!/bin/bash
    if ! ps aux | grep arma3; then 
    cd /home/arma/.wine/drive_c/ARMA3 && wine arma3.exe -server -port=2302
    fi
    

    After changing the switches and paths to your own configuration, add it to a cronjob with:

    crontab -e

    and add:

    * * * * * /home/arma/arma3.sh

    To have the ARMA3 server checked every minute and restarted if necessary.

    NOTE: If you want to do this, you'll need to use:

    winetricks nocrashdialog 

    To disable the GUI popup on a crash, so the script knows to restart the server.


  4. @NoPlanB: I've added a link to your post on the OP, so you are free to update the script in the future!

    @Radioman: I know that you're saying that you disabled the firewall, but what does 'iptables -L -v' give you? The client will favour servers that are geographically close, with low latency. Can you connect directly using the IP? Also, have you checked your server configuration to ensure that you are connecting to the correct master server? Can you ping that master server from your own server?

    In the case of the snd_dummy not found error, are you actually receiving any ALSA errors? Are you using a custom-configured kernel? If not, what version kernel are you using ('uname -a')? What are the contents of '/lib/modules/`uname -r`/kernel/sound'? Can you run 'find /lib/modules/`uname -r`/kernel/sound -type f -name snd-dummy\*' and provide the output, if any? Also, the output of 'zcat /proc/config.gz | grep SND_DUMMY'?

    If your kernel is customized, then you'll have to build with CONFIG_SND_DUMMY=y or CONFIG_SND_DUMMY=m (preferably the latter, if you don't want a permanent fake sound card).


  5. What filesystem are you using? Are you sure that all the files are correct and that integrity is preserved? I'd attempt to create a prefix under an NTFS or FAT32 partition and see if you still get the error, after 'verifying files', of course.

    Otherwise, it might be worth looking into:

    • File/directory permissions
    • Directory names - check that you don't have a mix of lower/upper-case directories or files mixing up WINE. It doesn't really care about case, but you never do know. Possibly use the small C program included with the ARMA 2 Linux dedicated server or your own script to rename every file and folder to lower-case only.
    • WINE drive mapping - C: should be the prefix root, Z: should be your BSD root. Make sure that they exist in the WINE registry or through winecfg and point to the correct directories, make sure that the path to ARMA isn't ambiguous in Windows directory syntax (eg. no 'strange' symbols, nothing that could cause crazy escape string problems).


  6. @barry100:

    I've tested the steps on a 'clean' Ubuntu install, and it works just fine for me. You shouldn't need any other packages - xvfb provides a minimal X11 configuration.

    @Comp_uter15776:

    BE has a few issues under WINE, though I've not seen that particular issue but this bug report contains patches for both Ubuntu Precise and Quantal for a similar issue. It seems to be fixed in Raring, so you may wish to look into upgrading if the server is only used for A3.

    @Otoris:

    This could be anything, really - it's a very low-level issue. Do large Linux applications work fine? If you're getting crashes with other applications, use memtest86 to check your RAM and a stress-test tool to ensure that your processor isn't failing. Otherwise, it's probably something wrong with WINE - remove it and re-install it, preferably from a different source.

    @NoPlanB:

    Thanks, I'm sure that this will be very useful for others. Do you mind if I add it to the original post?

    @gagagu:

    Debatable. Certainly, Linux tends towards minimalism and light-ness in comparison to Windows and the modularity of Linux means that applications are each optimized for their specific purpose (Linux application philosophy is 'do one thing, do it well') - on the other hand, the code was written for Windows, not WINE. The WINE group are doing as much as they can to enable Windows applications to be run under Linux and there have been many cases of applications running especially quickly, and also occasions of applications running especially slowly - or not running at all. Mileage will vary as almost every application under a Linux system is highly customizable and configurable, so I'd suggests looking into Linux optimization if you'd like to get the most out of Linux and WINE applications alike.

    @icedragon64:

    Make sure that you're specifying all the paths correctly when you launch ARMA 3 (Windows-style switches as seen in other threads and relative to the directories as WINE sees them). You also might look to verifying files under Steam for ARMA 3 and adding missions, as you mentioned.

    @warezit:

    You'll need to 'killall Xvfb' to stop any running xvfb processes - you'll want to 'killall x11vnc', too. Restarting will also terminate those processes. It sounds like Steam may be waiting for your input - try logging in through VNC once you've got it running and have killed the previous processes - I believe you'll find a dialog box or further information on-screen.

    Thanks for the corrections, I've modified the OP as appropriate.


  7. Hi,

    I've installed the ASM as described on the GitHub. Only FPS is monitored, the other stats stay at 0.

    ASM reports 64.2 FPS, whereas #monitor reports 50.

    This happens regardless of the mission played.

    I'm running the server on Linux Wine.

    Any ideas why ?

    Thanks.

    Hi there Sacha, you're saying that the statistics returned by the application are incorrect when the ARMA server is run through WINE and this client application from Windows? Can you run the ARMA server under WINE with logging enabled and use this application to attempt to retrieve statistics again? To enable logging on Linux, append '2>&1 > logfile.txt' to the 'wine ...' command you use to run the server - you can message me a link to the log file saved on Pastebin or similar and I'll see what I can deduce. Unfortunately, I can't really do any testing of my own at the moment.


  8. Running multiple concurrent ARMA 3 installations under different WINE prefixes using WINE should also be possible. Each WINE prefix is a new Windows installation as far as any programs resident in the prefix are concerned and WINE has much, much less overhead than any L1 or L2 VM software (such as KVM, VMWare or Xen that emulate a whole physical system or OpenVZ that runs multiple Linux instances under a single kernel).


  9. I have a server running on Linux using Wine.

    Users experience desync when the player count goes above 15.

    Anyone else having these issues? Is there any way to fix this?

    Server Specs:

    Intel Quad-Core Xeon E3-1230 3.20Ghz

    8GB DDR3 Memory

    100mbit dedicated connection

    It's difficult to troubleshoot this kind of issue - have you noticed anything odd in your WINE or server log? Have you checked iostat, vmstat, ntop and such output during the desync to ensure that you're not facing a performance bottleneck with CPU, HDD or RAM/swapping? If not, it's probably not a WINE/Linux issue (in which case you should search the forums or create a new topic). Also, be sure you don't have anything you don't need listening for connections (netstat will show you listening ports), have a look at the firewall (note 'dropped packets' in iptables -Lv and ip6tables -Lv) and generally make sure the problem is not due to your server connection or latency.


  10. Never used Wine on a server environment.

    Does it work on a non-window-manager installation? I don't want to clog up my server install with useless window manager

    I guess the answer is no, seeing how A3 client creates a new window

    It's happy with a fairly minimal set of dependencies - check my ARMA2 WINE server install script, I'm pretty sure that build will work happily with the ARMA3 server app (though I've not tested that yet). You do need some sort of X server to render the application window but I'm sure you'll find that xvfb is very light.


  11. hello, sorry but I'm little confused :( ... 1st time I use wine.

    my arma installation path is:

    /home/username/.local/share/wineprefixes/steam/drive_c/Program Files/Steam/SteamApps/common/Arma 3

    so, if I want my username.arma3alphaprofile file in the game root, I create a directory username in that path and the username.arma3alphaprofile inside.

    then I run thre game with -profile="c:\Program Files\Steam\SteamApps\common\Arma 3\username\username.arma3alphaprofile"

    correct?

    peppe

    Correct! :)


  12. hello bullkanox,

    tnx to try support me but the command string is in " ", so the syntax is correct. I also try your string without results ...

    Peppe

    You'll have to use Windows paths for the profile directory - all the options, configs etc should be in a Windows format. Instead of -profiles="/home/username/Documents/Arma 3 Alpha/username.Arma3AlphaProfile", use -profiles="C:\Documents and Settings\Username\My Documents\Arma 3 Alpha\username.Arma3AlphaProfile" for example. C: refers to the folder /home/username/.wine/drive_c and you can use 'winecfg' to add new drive maps, effectively allowing you to alias any folder as any Windows drive letter if you'd like WINE to have more access over different locations.

    And yes, saro is absolutely right - you need to be using at least WINE 1.5.x (I've only tested with 1.5.24 and up). You might have trouble with stable LTS-class distros like CentOS, Debian Stable and RHEL as they may not include support for the latest library versions that WINE 1.5 requires - in this case, it's possible to either separately install the up-to-date libraries to /usr/local or bootstrapping another distro into a chroot, perhaps Debian Testing/Unstable with debootstrap or a chroot install of Funtoo but I don't suggest this unless you're an experienced Linux administrator. It's much easier to simply try a different distro or update to a 'testing' release if outdated libraries are an issue, though of course this can cause other issues.


  13. Hey guys I dont know much about wine but followed instructions to setup Arma2 on playonlinux with wine

    I cant get past the loader as it doesnt recognize the mouse

    But just found this link

    http://www.codeweavers.com/compatibility/browse/name/?app_id=6107;forum=1;msg=127264

    this is a recent thread & looks like the solution - I didnt try it yet coz I dunno WTH I am doing

    Yes, that'd work - I don't see why it doesn't recognize your mouse though - that advice no longer applies since rawinput is included with the latest versions of WINE.

    In PlayOnLinux, try going to Configure button > (select your virtual drive) > General tab > Wine version and choosing wine-1.5.27-linux-amd64 instead of System or whatever version you have selected.


  14. out of curiosity, is there any benefit to running a server over wine?

    As opposed to running the native dedicated server on Linux? You have the ability to load extension DLLs that are required for some plugins and you can run Windows-specific utilities. Of course, with no current dedicated Linux binaries you can't run the server any other way on a Linux system at the moment.

    As opposed to running on Windows? You have more control over low-level aspects of your server (eg. tweaking scheduler), Linux's system overhead is much lower (even running WINE), you have all the Linux administrative perks (Linux is architecturally more secure, much more stable and is free and open source).

    Hi all,

    Arma2 installed on wine, the server start but Steam want go offline :( I dont understand why. My credentials are saved on remote system. I try to edit the steam.cnf to force offline mode but steam wont start if offline ....

    What does Steam do when you attempt to run it in offline mode, simply exit or does it still try to run online? I've never tried running it always-offline, I simply use Steam -> Go Offline in the menu when required. Have you tried that?


  15. Glad we're up and running!

    Couple minor glitches:

    1. What is that thing where when the mouse pointer goes off the side of the Wine window it stops working for the Wine app?

    2. In Steam, my menus are "blanked out" now, the words don't appear, but I managed to remember where the games option was.

    1. I've mostly used fullscreen mode, personally, but I believe that it's possible to alter the way that WINE treats the mouse - try each of these options:

    winetricks mwo=force
    winetricks mwo=enabled
    winetricks mwo=disabled

    I'm not entirely sure that they work with rawinput, but they're certainly worth trying. Another option is the 'Allow DirectX apps to stop the mouse leaving the window' in the 'Graphics' tab of 'winecfg' - this may achieve the desired effect.

    2. This should be fixable by going into the WINE configuration app ('winecfg' in a terminal), choosing the 'Libraries' tab and adding 'dwrite' then setting it to 'disabled' or by always launching Steam with the '-no-dwrite' launch option. You can read more about potential Steam issues on WINE on the excellent WineHQ AppDB.

    Also, what is a good place to start with dialing down the video settings in ARMA to get less lag? I do like how a low framerate blurs instead of stutters, though. Very organic looking.

    There is a lot of information available on this! Google search for 'arma 2 tweaking guide' and you'll find lots of different tweaks for configuration files (research each option before you apply it :)). In addition to these, there are startup parameters that you can edit by right-clicking the game in Steam and selecting 'Properties' then 'Launch Options'. One particular option worth looking at is the -malloc one which allows you to specify a memory allocator - I've not done extensive research into this under WINE, and it can affect your performance quite drastically. It's worth trying different combinations (one step at a time) to optimize your gameplay to be as smooth as possible (Maximum FPS isn't everything - a stable 30fps is much better than an average 50fps that jumps all over the place :)). I believe that the first step, generally, is to look at disabling 'VSync' and dialing down object detail.

    re : PulseAudio :

    You can imagine that for me, I don't know the difference between a "drastic alteration" of the package and a tweak! I know what I know, and I don't know what I don't know, you know? :yay:

    Parenthetically, I have to say the thing I love about Linux is that I feel free to just type anything into the terminal that some dude on the internet suggested in a forum, because if I mess up the OS I don't really give a toss. I'll have it re-install in an hour, in contrast with Windows where you really lose, and it takes forever and a pint of blood to reinstall. Maybe just now with getting this game installed am I reaching a point where I'm "invested" in my setup.

    Indeed! That's the best thing about VMs - they're much more tightly integrated into Linux than they are Windows and therefore have much better performance. The great thing about having a VM is that you can install a distro that you're vaguely interested in, create a stable 'snapshot' and then do pretty much anything and revert it back in a few clicks! A great way to learn about the different roles of software components in a Linux system is to simply tear them out of the VM installation one by one and see what works and what doesn't. Procedurally destroying a system can be quite cathartic, too :). I agree that it's much easier and faster to install Linux than Windows, though, especially if you want to keep your files.

    Thanks I will check that out. I think it says a lot that guys like me are even using Ubuntu -- I have a lot of other stuff going on in life and not a lot of time to invest in learning it, but it basically works for me and it's always satisfying to triumph over your adversities when things go tits up.

    Can't thank you enough for all the help bro.

    It's great to see people using Ubuntu, Fedora and all those other Linux distros - I'm always happy to help! :)


  16. Sorry, I'm a little confused - this looks like a log from the Linux version of Steam. Note 'Running Steam on ubuntu 12.04 32-bit' and a message talking about GLib (a GNOME library). You may also wish to note that WINE doesn't use PulseAudio (unless Ubuntu patches it on their end? They don't as far as I know.) - it relies on OSS or ALSA for sound. I'd imagine the 'Access Denied' error simply means that it can't contact the PulseAudio server (which is not running because it's removed from the system). Furthermore, removing PulseAudio was often recommended in it's formative days due to the complications it often caused but this is no longer the case, as it's the framework that provides the ability to have multiple applications play sounds at the same time and is much improved over the mess that was initially adopted. It's also part of the Ubuntu provided desktop - you'll have a fairly hard time getting support from the Ubuntu community if you're altering the 'packaged experience' so drastically.

    Of course, this has nothing to do with the current discussion, but as an aside I'd recommend that if you are interested in all of the gloriously disparate and disjointed components that make for a full Linux desktop, you look at setting up an ArchLinux VM to play with. I'd hope to save you from the frustrating 'trial by fire' that many of us Linux users - hobbyists and professionals alike - have endured when we realize just how much we can customize our systems - there's nothing worse than ending up with a problematic production system, too bloodied and broken to update yet comfortably customized enough that you have no motivation to reinstall. :)

    So, what happens when you 'cd ".wine/drive_c/Program Files/Steam"' and 'wine Steam.exe' in the terminal? The mouse issue sounds like a lack of rawinput - this was a patch integrated into WINE in version 1.5.13. Since you're running WINE 1.4, this feature will not be available to you and you won't be able to use the mouse.

    To update to WINE 1.5, simply install the latest version of WINE from the WINE Team PPA

    sudo add-apt-repository ppa:ubuntu-wine/ppa
    sudo apt-get update
    sudo apt-get install wine1.5

    The game should now work fine and you'll hopefully have it in your Steam library - I'll update the main post with the PPA instructions. :)


  17. Ah, that should be an easy fix. Try opening a terminal and type:

    mv "~/Desktop/[ARMA 2 OA Demo folder name]" "~/.wine/drive_c/Program Files (x86)/Steam/SteamApps/"

    (eg. mv "~/Desktop/Arma 2 Operation Arrowhead Demo" "~/.wine/drive_c/Program Files (x86)/Steam/SteamApps/"

    This is assuming a WoW64 prefix, which you would have if your Linux installation is 64bit. If the distro is 32bit or you have a 32bit WINE prefix (ie. 'ls ~/.wine/drive_c' doesn't show the 'Program Files (x86)' folder), replace 'Program Files (x86)' with 'Program Files'. Once this is done, close and re-open Steam then right click the ARMA 2 Operation Arrowhead Demo game then 'Properties', 'Local Files' and 'Verify integrity of game cache' and it should fix any further issues. Of course, make sure to open Steam under WINE and not the Linux version (Help -> System Information should list a Windows variant under 'Operating System Information' and not your distro name).

    You shouldn't need to run any type of installer - Steam should simply open the game. If you do have any problems, run Steam from the terminal and it will show a log of all the behind-the-scenes info that may be useful to debug the issue.


  18. I see this is an old thread but it was really useful to me so I figured no harm in a bump...

    I am following Kindling's instructions to install the ARMA2/OA demo using playonlinux.

    When I get to the point of selecting the ARMA install file to run, amazingly it works in the sense that the game runs. I can play or at least initially check it out. The game starts itself in the installation process.

    However, the instillation process does not complete, and when I exit the game, it is not installed. What am I doing wrong?

    Any help greatly appreciated. I'm at a noob-to-intermediate level with linux. I'm running ubuntu 12.04; follwed the instruction to use wine 1.5.13 on the install. Computer is something like core 2 duo 2.0ghz /3gig ddr2 / radeon gt610. Anything else to figure it out I can provide.

    Anyone have any ideas?

    Hi,

    This isn't really an old thread - you might have missed this, but there's 11 pages and the last post was yesterday. :)

    I'm not entirely sure what you mean - do you mean that you can install the ARMA II: OA demo via Steam but it doesn't show in the games list after installation? Or do you get any kind of installation error? Can you run everything in a terminal ('cd .wine/drive_c/Program\ Files\ \(x86\)/Steam/ && wine Steam.exe' for example) and provide the output around the time that the installation fails?


  19. Fortybot: Good luck with that! Drive corruption can be a dangerous beast. You might want to check the SMART data of your drive(s) (use the Disk Utility) to make sure that it's not a chronic failure due to hardware age or failure. If not, I'd suggest looking at doing an ATA Secure Erase or even zeroing the drive multiple times with DBAN - this should 'teach' your disk's firmware about any damaged sectors. And, of course, always keep backups of anything important.

    LkFp: That's very interesting, as it sounds like similar issues to the bug tickets I linked in the main post that were observed under the AMD proprietary fglrx module. This would suggest that Mesa/Gallium is catching up! It'd be great if you could provide some screenshots or videos and perhaps compare the results with those in the bug reports.

×