jaynus

Boxter is correct. That means legacy ACRE files are being loaded; wipe it and make sure you have no more acre_XXXX.pbo files, then re-install

Updated on dev-heaven for Beta 82423 http://www.dev-heaven.net/projects/jayarma2lib/files

http://tracker.idi-systems.com/projects/acre/wiki

Can I get a full directory listing of your @JayArmA2Lib folder? And is this with the latest version off of DH?

1.3's current working changelog (still fleshing out bugs from it). Again - not released yet. And we are currently fleshing out bugs from our testers. You can see our progress on finalizing 1.3 @ http://tracker.idi-systems.com/projects/acre/issues

1. Make sure you are running a supported beta patch if your running beta. 2. Make sure you are actually running up-to-date 1.59 patched 3. Make sure you are not using anything illegal; jayarma2lib does not support that.

jayarma2lib autoupdated+DH updated for 81201

they must be non-blocking asynchronous pipes.

mainly it comes down to effort vs reward. 1. Spend 3-8 hours coding up a enable/disable feature and testing it 2. Make you spend the extra 10 seconds to disable/enable yourself :?

Now that 1.2.10 is stable, we are finishing up the 1.3 push: Working VRC's (Vehicle Racks and Radios) http://i.imgur.com/xdisy.jpg http://i.imgur.com/PYGcb.jpg http://i.imgur.com/zGsnm.jpg

ACRE 1.2.10 released. THIS RELEASE IS DIFFERENT THAN PREVIOUS, TS3 WENT STABLE! :yay: :yay: What does this mean? It means you no longer have to run TS3 beta's. 1. You can uninstall the older ACRE via the control panel first. 2. Download and install the new official TS3 from the TS3 site. 3. Install ACRE. 4. Don't forget to run as administrator! DOWNLOAD Package: http://acre.unitedoperations.net/1.2.10.381/ACRE_V1.2.10.381.zip 32-Bit Installer: http://acre.unitedoperations.net/1.2.10.381/ACRE_V1.2.10.381_x86.exe 64-Bit Installer: http://acre.unitedoperations.net/1.2.10.381/ACRE_V1.2.10.381_x64.exe Six Updater This version is avialable via sixUpdater, and will automatically copy dsound.dll and acre_winXX.dll for you!! You can alternatively use the ACRE installers, or SIX updater. Your choice Six Updater Link: http://forums.bistudio.com/showthread.php?t=118605 Six Updater Direct Mod Link: sixupdater://mod=43a33648-962d-11df-8d10-001517bd964c CHANGELOG

http://unitedoperations.net/Thread-I44-Event-8th-of-May-AAR Small feedback/AAR from UO doing an I44 event with ~40 players.

FYI, trolling our release site and downloading the latest versions on their is at your own risk. Those are test/debug builds for our testers. Unless you see the official version updated & a post here, your updating to most-likely-broken-test-builds :) FYI - TS3 just went official stable with 3.0.0-rc1. We'll be updating shortly, and the TS3 standalone packages will be going away.

We are always looking for help on documentation.

Understood. We'll look into other sound mod solutions for our community. Thanks Jarhead!

hi jarhead - If ya can could you contact me either via pm, email or on the UO ts? (ts3.unitedoperations.net)? We have a custom build of jsrs we are finalizing for use within our community, and want to: 1. push all the config fixes upstream to you 2. permission and all that blah

Please file a ticket with the mission your using and a list of addons.

Sounds like hes getting something horribly confused. The capslock key wont even register as a valid hotkey unless ACRE is connected and working 100% (as in, in teamspeak, the key never exists until ACRE fully synchronizes and then tells teamspeak its a hotkey). Does he have capslock set as his VON key? as his TS3 PTT key? Sounds like something really fishy is going on here - because that means ACRE *is* working if capslock is activating - unless he has it set as a PTT already, which may explain some problems.

We are getting this from some current/former serviceman talking about how completely unlike the real radios the distortion currently is. One thing to remember is that we don't even implement the real distortion or signal lose yet. Everything assumes LOS analog signal, instead of digital signals. Once we get that in, everyone should be a lot happier. Our big problem with that, however, is that until we can confirm stability, digital signal lose is totally something we cant implement; we would get a million "I cant hear them" false bug reports. This is because digital signal decay means the actual transmission sounds fine; it just cuts out for signal lose. ---------- Post added at 07:31 AM ---------- Previous post was at 07:30 AM ---------- Try running teamspeak 3 as administrator; check your username in teamspeak (click on yourself) to see if it says ArmA2 is connected.

Have fun with that ;) ---------- Post added at 03:12 PM ---------- Previous post was at 03:11 PM ---------- [/color] lack of desire / motivation to make the gui's and then re-model the packs ourselves (cant use the models out of ACE)

@Foxhound: Awesome :) Nice to finally be releasing back onto AH again.

If your getting the acre_main error, just re-download and re-install. We had some web-server issues, causing some file corruption. new files should work fine. If you want to be careful, delete @acre before you re-install.

The "standalone" installers for 32-bit and 64-bit include the TS3 beta and create a "ACRE TS3" shortcut on your desktop

If you ticket with @ our tracker (tracker.idi-systems.com) with the appropriate models (p3ds) and/or interfaces (paa) we'll get to integrated them :) ---------- Post added at 11:35 AM ---------- Previous post was at 11:32 AM ---------- They are true implementations of VRC racks and aircraft radio consoles. This means like an actual rack you put radios into / take them out of. Some vehicles will have them by default, others will require the mission makers to add them. Additionally, since they are racks; they get different antenna's and power's due to being "racked". an example is VRC's supporting the PRC-148. Rather then "everyone just getting radios", the vehicle has a rack - which has 2 148's mounted inside of it. Any single person can use them at a time - or put them on "speaker mode" or whatever. Or a person can take it out of the rack.

The vehicle radio code itself is done. This interaction menu stuff is the beginning of integrating it into usability. e.g. we have all the code for it, but its just not accessible to the user yet. Once we confirm interaction is working, we are going to migrate that and some features into the interaction menus :)