Sapiens

Earlier in the week I discovered that I was looking in the wrong section of the file like a complete idiot. I was changing the option for faction makeup/loadouts and not the arsenal presets. Since then I've started fiddling around to add Ace into the mix, and will probably have to manually edit a loadout preset to strip the advanced medical items out of the list. Sorry to bother you with this wyqer, and thanks for the assistance MATR1X!

Maybe I'm just being picky. When I tested with KP_liberation_arsenal = 3; for the RHSUSAF arsenal preset, it seemed to include all available RHSUSAF and RHSAFRF equipment along with the normal ArmA stuff. I probably just need to tweak things myself instead of asking you to do it for me. :P

Hi Wyqer! Thanks for your continued work on Liberation and Support, I've had a ton of fun with both. :) While fiddling around in Liberation with RHS I noticed that the Arsenal list starts getting pretty long, with equipment for ArmA+DLC as well as both RHS factions. It's a little overwhelming. Maybe it sounds strange, but are there any plans to implement an option to pare down the equipment list? For example, during mission setup being able to limit Arsenal content to ArmA+RHSUSAF Only, RHSUSAF+RHSAFRF Only, etc. Maybe individual On/Off settings for each faction/equipment set would work better? Stock ArmA Equipment: On/Off RHSUSAF Equipment: On/Off RHSAFRF Equipment: On/Off Etc. I know I can set a custom equipment list in the config files (I'll have to check back through the thread or the wiki for the steps) but thought I'd suggest it as a feature as well.

Can anyone tell me what's going on here and how to fix it? I've had this issue for the past several updates. Tried resetting my controls to various profiles, clearing my .\Documents\Arma 3 folder, verifying my local game files, reinstalling the drivers for my gamepad, doing a clean GPU driver installation with DDU, and probably a few other steps I can't remember.

First off, thanks a ton for continuing to develop this mission! It's one of my favorites and I'm really happy to see it in the hands of some folks who know what they're doing. :wub: After playing with the 1.7.5 "bleeding edge" build from March 21st a bit, I managed to pick up a map on a few occasions (playing solo is rough) and noticed that my position is shown despite the button being disabled at the top. I'm also able to make waypoints without a GPS and have the marker appear on my HUD. Points of interest do still show up correctly as question marks however. Is this intentional behavior, or a side effect of playing on Regular difficulty, or something else? I noticed the same thing with the March 1st build.

Maybe I'm misunderstanding your post, but are you saying that your server isn't showing up in the server list? If that's the case shouldn't you contact your server provider for assistance? What makes you think the problem is on BIS's end of things?

Hey there Dakota. ;) I see that you've set reportingIP="arma2pc.master.gamespy.com";. Are you running an Operation Arrowhead server? If so, try using reportingIP = "arma2oapc.master.gamespy.com"; instead.

Am I misunderstanding this post? I realize I can modify description.ext directly, but forcing players to re-download the PBO seems a bit excessive. Is this type of setup not supported by Domination?

The PBO file goes in the .\MPMissions folder of your ArmA2 or OA installation directory, depending on which version of Domination you'll be running. Your server.cfg's missions section should look something like this if you want Domination to be the only mission available (in this example I'm using one of the OA Domination missions): class Missions { class DomiOA { template="co30_Domination_2_54A2_West_R_OA.Takistan"; difficulty="regular"; }; }; template= should be followed by the file name of the mission without the PBO extension. More basic information regarding this section is available in the BIS wiki here.

I seem to be having trouble defining custom mission settings in server.cfg. As far as I can tell my syntax is correct, but when I join my server it still uses the default settings instead of those I've defined. Would someone be so kind as to have a look below and tell me if I'm making any mistakes? I'm at a loss. Snippet of params defined in the mission's description.ext (working with Domination here, if that helps): class Params { class GVAR(TimeOfDay) { title = "Time of day:"; values[] = {0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23}; default = 16; texts[] = {"00:00","01:00","02:00","03:00","04:00","05:00","06:00","07:00","08:00","09:00","10:00","11:00","12:00","13:00","14:00","15:00","16:00","17:00","18:00","19:00","20:00","21:00","22:00","23:00"}; }; class GVAR(InitialViewDistance) { title = "Initial Viewdistance:"; values[] = {1000,1500,2000,2500,3000,3500,4000,4500,5000}; default = 1500; texts[] = {"1000 m","1500 m","2000 m","2500 m","3000 m","3500 m","4000 m","4500 m","5000 m"}; }; }; Snippet of the relevant section in my server.cfg: class Missions { class DomiOA { template="co30_Domination_2_54A2_West_R_OA.Takistan"; difficulty="regular"; class Params { TimeOfDay = 16; InitialViewDistance = 2000; }; }; };

I've spent several hours trying to set up an OA server in a Windows Server 2008 R2 environment. Initial setup was accomplished by installing Steam on the server and then allowing it to download both the client and server files, as this was much faster than uploading the entire game directory myself. I am unable to launch the server because BattlEye fails to initialize. I've tried running both the BE installer provided by Steam as well as the separate download posted by Dwarden, but since there's absolutely zero feedback I can't tell if they're successful or not. A separate BattlEye folder isn't created in my OA directory, though I'm not sure if this is supposed to happen on the server's end of things, or if I'm even supposed to be running the BattlEye installer in the first place. Any suggestions for determining the cause of this error and how to correct it would be very much appreciated. Thank you in advance. :) Update: After starting from scratch and choosing the "Reinstall BattlEye" optiona via Steam, things are working properly. I guess I just needed to take walk away from it for a while. :P Update 2: Upon further investigation it appears I had goofed up my command line. BattlEye seems to rely on the -profile (and/or -name?) switch to know where to put its files, and if you specify an invalid location it poops the bed.

I can't seem to get this working at all despite my best efforts to follow your instructions. I've completed Dwarden's steps for repairing missing registry entries and verified they were present, successfully installed beta patch 71900, replaced _runA2CO.cmd with Dwarden's version, then duplicated and modified it with your updated :run line. The original _runA2CO.cmd file still works, but the modified duplicate does not. No error messages appear, the command prompt simply flashes briefly and the game doesn't run. Any idea as to where I've made a mistake?

I've noticed that the Ballistic Addon Studio site has been down/unresolvable for a while now, and I was wondering if there are any places that host the latest versions of all of their work? I found quite a few things on OFPEC, but they're missing the Tonal Island project and there's no way for me to tell how up-to-date their files are or what else could be missing. Thanks in advance.

Converting one compressed audio format to another results a lower quality audio file (assuming it's a lossy format like MP3 and not a lossless one like FLAC), though whether you'll be able to tell the difference or not depends on your hearing and the audio hardware you're using. Ideally you'd just re-encode the original files to MP3, but if that's not possible you could try using WinAmp's DiskWriter plugin to dump WAVs of the WMS files and then encode them to MP3.

Converting one compressed audio format to another results a lower quality audio file (assuming it's a lossy format like MP3 and not a lossless one like FLAC), though whether you'll be able to tell the difference or not depends on your hearing and the audio hardware you're using. Ideally you'd just re-encode the original files to MP3, but if that's not possible you could try using WinAmp's DiskWriter plugin to dump WAVs of the WMS files and then encode them to MP3.