Warmoer

In the internal weapons bay?

I have set up Oxygen 2 for ARMA 3 according to the various tutorials, and opened one of the vehicle samples. When the run Buldozer, it fires up the ARMA 3 exe, starts loading in the viewer screen and then suddenly it stops working. Below is my crash report - any assistance will be greatly appreciated! ===================================================================== == P:\buldozer.exe == P:\buldozer.exe -buldozer -noland -window Exe timestamp: 2013/12/11 21:37:10 Current time: 2014/01/17 00:10:06 Type: Public Branch: Stable Version: 1.08.113494 Allocator: Windows ===================================================================== No product.bin found, using defaults for a core engine. Splash window: Unable to load config file: dta\splashwindow.bin Initializing Steam Manager unable to load subscribed content list. list will be updated from steam unable to load published content list. list will be updated from steam unable to load cached items meta info. save and update functionality will be broken Steam Manager initialized. ==== Loaded addons ==== F:\Program Files\Steam\steamapps\common\Arma 3\dta\bin.pbo - unknown F:\Program Files\Steam\steamapps\common\Arma 3\dta\core.pbo - 0 F:\Program Files\Steam\steamapps\common\Arma 3\dta\languagecore_f.pbo - 60330 ======================= DX11 - Initializing DX11 engine. DX11 - Detecting best GPU adapter. DX11 - Detected best GPU adapter 0 : "NVIDIA GeForce GTX 780", benchmark result = 42.8452, level coef = 1, total result = 42.8452 DX11 - Using DXGI adapter 0. - adapter description : NVIDIA GeForce GTX 780 - adapter vendor ID : 4318 - adapter device ID : 4100 - adapter subsys ID : 906237016 - adapter revision : 161 - dedicated video memory : 3140157440 - dedicated system memory : 0 - shared system memory : 1154744320 Error: CoInitilizeEx (XAudio2-1st trial) return 80010106 PhysX3 SDK Init started ... PhysX3 SDK Init ended. ======================================================= ------------------------------------------------------- Exception code: C06D007E at 754EC41F graphics: D3D11 resolution: 1024x768x32 Addons: Mods: A3 Distribution: 0 Version 1.08.113494 Fault time: 2014/01/17 00:10:08 Fault address: 754EC41F 01:0000B41F C:\Windows\syswow64\KERNELBASE.dll file: world: Prev. code bytes: 0C EB 03 89 45 C0 8D 45 B0 50 FF 15 5C 11 4E 75 Fault code bytes: C9 C2 10 00 CC CC CC CC CC 8B FF 55 8B EC 56 8B Registers: EAX:01E1FB4C EBX:00000000 ECX:00000001 EDX:00000000 ESI:014EAF50 EDI:0167C6C0 CS:EIP:0023:754EC41F SS:ESP:002B:01E1FB4C EBP:01E1FB9C DS:002B ES:002B FS:0053 GS:002B Flags:00200202 ======================================================= note: Minidump has been generated into the file C:\Users\Fred\AppData\Local\Arma 3\buldozer_2014-01-17_00-10-06.mdmp

I tested 8c yesterday, multiplayer coop with myself being the only player. When spawning an AI squad, a broken script message kept sitting on the screen that appears to be related to healing. This would only go away when I got rid of the team. Other than that, a great mission. I do find the enemies to be WAY too lethal at ranged engagements (I played infantry only). Please consider adding an enemy difficulty parameter as well. Great mission, thanks!

I am really enjoying the Beta content, and started working through the helicopters tonight. The cancelled Comanche, or Blackfoot in ARMA 3 was a departure from the default helicopter gunship seating arrangement where the pilot would be located in the front, whereas the systems operator/gunner (or UAV/UCAV operator) would sit in the rear. This is the primary reason why the rear seat was not elevated as per say the Apache, and visibility is actually poor from the rear. Can the devs please move the pilot seat to the front, as it should be for this aircraft; it is very difficult flying approaches from the rear, unless landing spots are approached sideways. Worth the fix, please! Sent from my iPad using Tapatalk HD

Thanks Smurf, great news!

I cannot work out if this was intentional, but this has changed from last week's update. Usually when toggling between walking and jogging modes (by pressing "c"), the movement mode will carry over between default cross-hair aiming and sight-aiming. The latest patch changed this. When in walking mode and aiming through the cursor/cross-hair and I switch to iron sights, the movement mode changes to jogging. Keeping the iron sights up and pressing "c" will toggle back to walking mode. As soon as one switches to cursor/cross-hair aim again, the movement mode will now revert in the opposite jogging. The movement mode has always been persistent between different aiming modes. Is this a bug, or has the change been intentional? Changing the aiming mode should not toggle between walking and jogging.

If people want fear in their lives, get married or get a mortgage, but when I play ARMA I want to enjoy it. For a military "sandbox" experience BIS is trying very hard to force us into something we don't want, and is the same thing that has been holding the series back since the start. Recent versions of the Alpha have messed with the awesome movement animations that brought the controls into the "21st Century" to quote Dsylexi.

I just read in the latest development update (22 May) that the single slot savegame mechanism will be brought back, and that only Recruit level will have multiple saves. This is a step in the wrong direction, together with some other animation "tweaks" that is making the movement system less pleasant than it was at the start of the Alpha. Whilst the Devs are perhaps satisfying the requests of a vocal minority, you are likely to lose the ground you gained with potential new customers to the series. There is a fine line between perceived realism and fun - good luck with that. Sent from my iPad using Tapatalk HD

This issue has nothing to do with hacking - it is a bug. It happened to me tonight on a TDM game while walking around a destroyed building. I found myself being flung in the air, and dropped straight down to my death. Unless someone managed to "hack" me into the air, it is probably just an alpha bug. I saw it happen to others on the server as well. Sorry to ruin the angry mob movement...

I love this campaign so far, but now I am stuck at the end of Dead Chill:

Don't use it, unless it is something that is built into ACE, but I'm not using any weather or effect addons except for ACE. Couldn't spot the inflatable at all, so difficult to say if it drifter away. I might retry the mission - maybe use the six-grenade launcher to level the objective camp.

I am currently stuck in SEAL 1 (ACE) mission 2. All the objectives complete, but my inflatable is not at the extraction. It was one heckuva fight to get there, and I'm not keen on retrying the mission just to see if it will work the next time? Who left it untied on the beach? Any ideas how to fix this?

Made a quick vid of the CQB Kill House in Doolittle's excellent 1ID Training Camp mission. Unedited, using ACE 2. Not my best round, but it shows the course quite nicely. <object width="560" height="340"><param name="movie" value="http://www.youtube.com/watch?v=2IAbUSIVq_8&hl=en_GB&fs=1&"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/watch?v=2IAbUSIVq_8&hl=en_GB&fs=1&" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="560" height="340"></embed></object>

Sorry, I have the wrong mission in this thread. It was most probably the demo man that went down, and I didn't check his loadout. I suspected that the Littlebirds destroyed the fuel, but there was no debris or any burnt out containers. The marker was still red on the map, and probably the reason for the mission not ending. After I saw the mission isn't going to end, I called in the Littlebirds, and another 2 appeared making it a total of 3 flying around over us, so I am sure someone didn't order them by accident. Thanks for your reply.

Played it 2 player coop yesterday. Good mission with a few glitches: ~ Could do with some armament selection in the beginning of the mission, and some weapon/ammo crates in the camps. ~On the way to 4th objective a friendly Littlebird started attacking the bad guys and basically wiped them out. This is apart form the Littlebird support that we never called. ~ 4th Objective - destroy fuel supply. There were no fuel, just a roof of an old fuel station. Nothing that would signify a fuel supply. And even if there was a target, we did not have any explosives available. Other than that the mission work well, was very unpredictable, and kept us on our feet. Had to keep re-arming team members from bodies as they sprayed a lot of ammo. Thanks for the great mission!