ArmA 2: OA Beta Build 72967

[M.Andersson(SWE) 4]

Is this beta "AFTER" 1.54 or pre 1.54????

[akd42 10]

It is after 1.54

[CarlGustaffa 4]

Stop whining about getting a beta patch 1 day after and asking for a hotfix...

It's not about whining and it's not about hotfixing something that went bad in a betapatch, but hotfixing something that went bad on the official patch. Unless there is something really wrong with those other things this beta touches, a hotfix is needed for those who rent servertime. They may not have the opportunity to run beta patches like the rest of us do, and being forced to run a server with stuck AI (due to only being allowed to run the official patch) is not good for the game.

For the record, I had no problems with downloading, installing and running the official patch (and the beta patch), other than the annoyance of SecuRom spinning up the disc making the game take longer to start. And I picked a random mirror. I'm on DVD release btw. No CRC errors and the like. Seems to me the problem must be on the receiving end.

Edited August 29, 2010 by CarlGustaffa

[NeoHazard 10]

Unfortunately you still wasted your time by not providing insight or thoughts on specifically why that is happening. Saying "I receive poor performance in this beta compared to other versions" is not going to help other people verify your claims or fix what may be a significant problem in future betas.

Providing your example mission and empirical evidence will.

hey JACK did you even read through this thread?

your dipshit comment is a waste of bandwidth. i'm sick of morons on this forum who can't act peaceably. must be a warmongerish type of mentality in people who play games like this. as if, you can't help but be in a state of conflict by acting like a petty jackass in constructing sentances to be aggressive in nature. i seriously don't need that attitude. I provided the information about the mission, I have my system specs in the sig and a description of the problem at hand with theories communicated amongst other board members. what are YOU going to help me with? youre not a developer. what the hell are you going to do for me? huh? youre just yet another dude who decided to be a dick to me in your sorry excuse for a helpful reply. go stick a gun barrel up your ass and call it a life.

[M.Andersson(SWE) 4]

Uhhmm...

Heres MY deal:

A2+OA DVD´s

Update 1.54

Cant play..

Get: No Entry ProfilePathDefault..

Im trying to start with

"C:\Program Files\Bohemia Interactive\ArmA 2\Expansion\beta\arma2oa.exe"

After the message i get a screan with colored boxes, on that is flashing..

Tried to printscrean but that turned out BLACK...

Ill see if i can get a rpt..

Edit: I have disc in player

Edit2: I can play A2OAco 1.54 alone but NOT with this beta..

A2OAco vers: 1.54.72888

Beta is this one...

Edited August 30, 2010 by Andersson[SWEC]

[CarlGustaffa 4]

i'm sick of morons on this forum who can't act peaceably. must be a warmongerish type of mentality in people who play games like this.

...

go stick a gun barrel up your ass and call it a life.

No further comments on this needed I guess...

[Nutlink 10]

Pretty please, can we finally get the M14 fixed? Please? I want to use this weapon so badly, but due to the aimpoint not being properly aligned I can't.

[CasualSoldiers 10]

I was getting "No Entry ProfilePathDefault." when using the AlpineStars mod launcher, using the "Launch OA BetaPatch" shortcut, with the mods added into its command line with ";@mod" it works, although it does seem that some mods take longer to load than others,, for example I was playing the second BAF campaign mission, and only after I cleared the minefield did I get a CBA message and the ShacTac hud started working....

[kklownboy 43]

;1735488']Uhhmm...

Heres MY deal:

A2+OA DVD´s

Update 1.54

Cant play..

Get: No Entry ProfilePathDefault..

Im trying to start with

"C:\Program Files\Bohemia Interactive\ArmA 2\Expansion\beta\arma2oa.exe"

After the message i get a screan with colored boxes' date=' on that is flashing..

Tried to printscrean but that turned out BLACK...

Ill see if i can get a rpt..

Edit: I have disc in player

Edit2: I can play A2OAco 1.54 alone but NOT with this beta..

A2OAco vers: 1.54.72888

Beta is this one...[/quote']

you should use the beta shortcut in the Arma2 root. you can copy it to your desktop too.

[mrcash2009 0]

@Andersson[sWEC]

If you installed the beta goto the root of your arma2 folder and it should have created:

"Launch Arma2 OA Beta Patch" shortcut, simply use this, right click and create a shortcut of it to desktop then add your mod lines or whatever to this ... example of what it contains:

TARGET:

"(DRIVE LETTER):\Program Files\Bohemia Interactive\ArmA 2\Expansion\beta\arma2oa.exe" -mod=Expansion\beta;Expansion\beta\Expansion -nosplash

START IN:

"(DRIVE LETTER):\Program files\Bohemia Interactive\ArmA 2"

The target is a bit of a weird one with beta, I got stuck too until I realised the shorcut existed in the root, I tried manual and got confused some time back with all this.

EDIT oops Kklownboy said it too :)

Edited August 30, 2010 by mrcash2009

[AnimalMother92 10]

Pretty please, can we finally get the M14 fixed? Please? I want to use this weapon so badly, but due to the aimpoint not being properly aligned I can't.

Apparently it's being worked on (finally)

Updated by Dwarden 3 days ago

• Status changed from Assigned to In progress
  
• Target version set to Upcoming version
  
• % Done changed from 0 to 50
  
• Reproducible for you changed from No to Yes
  

http://dev-heaven.net/issues/11588#note-15

[MavericK96 0]

So it looks like Steam updated 1.54 to this build as being current? I ran OA vanilla (no beta) and it's build 72967.

[AnimalMother92 10]

So it looks like Steam updated 1.54 to this build as being current? I ran OA vanilla (no beta) and it's build 72967.

Seems so :)

http://twitter.com/FoltynD/status/22310340823

ARMA 2: British Armed Forces + A2: OA hotfix now@STEAM

[slimSpencer 10]

hi there,

fyi - i maybe discovered a problem with 72967 in mission Harvest Red.

Pls. see http://dev-heaven.net/issues/13395

Anybody else here with the same problem?

regards

Edited August 30, 2010 by slimSpencer

[no use for a name 0]

hey JACK did you even read through this thread?

your dipshit comment is a waste of bandwidth. i'm sick of morons on this forum who can't act peaceably. must be a warmongerish type of mentality in people who play games like this. as if, you can't help but be in a state of conflict by acting like a petty jackass in constructing sentances to be aggressive in nature. i seriously don't need that attitude. I provided the information about the mission, I have my system specs in the sig and a description of the problem at hand with theories communicated amongst other board members. what are YOU going to help me with? youre not a developer. what the hell are you going to do for me? huh? youre just yet another dude who decided to be a dick to me in your sorry excuse for a helpful reply. go stick a gun barrel up your ass and call it a life.

LOL!! Stay classy...

[KeyCat 131]

Anyone else having audio issues (audio volume getting lower and lower in the Huey enroute) while playing stock scenario 01: Trail By Fire with Build 72967?

/KC

[M.Andersson(SWE) 4]

you should use the beta shortcut in the Arma2 root. you can copy it to your desktop too.

:butbut:

How could i have forgotten this.????? :o

I went into betafolder and created a shortcut...LOL:yay:

[akd42 10]

The following are problems from 1.54/BAF that persist in 72967. For those that have not been reported on the community bug tracker, I cannot make tickets as I can't login or retrieve password there, and there is no contact info for login/account help. Somebody else will need to make tickets.

1. When turning out from commander view in armored vehicles, the viewpoint gets stuck on a fixed-position, zoomable view with the current sensor (daylight/nvs/thermal) applied. You can cycle through vision modes and a rangefinding reading is displayed. You can only get out of this stuck view by switching to external view and back. Oddly enough, every once in a while it doesn't happen. Tested with Warrior and M1A2 Tusk.

2. Selecting 1800m zero on the Jackal GMGs returns the zero to 100m.

3. Tripod-mounted GMGs don't have an option to select zero, as with the Jackal-mounted GMGs.

4. Vehicle- and tripod-mounted L111A1 (M2HB) and M621 (Lynx 20mm) are using the M240 firing sound. And all M240s co-ax and otherwise, except the new L7A2 mini-tripod, are using the same firing sound. I noted that with the Jackal HMG, this is true for the player, but not the AI. L7A2 GPMG mini-tripod is using 7.62 Russian ammo/tracers and PK firing sound.

5. I seem to have lost all automatic cannon impact sounds (tested Wildcat 20mm, Warrior CTWS, Bradley 25mm, and Apache 30mm). Edit: not sure on the Wildcat 20mm now. Seems it does have a very quiet explosion sound.

Partially reported here: http://dev-heaven.net/issues/13362

6. Switching firing mode (single/full) on the L85A2 AWS also switches optics mode, but only after the first time you switch from NV to thermal mode. The Qioptiq Kite depicted on the rifle is an image intensification sight and should have night and day-filtered modes, not night and thermal modes.

7. Laser rangefinder reading displayed in open air gunner view of Stryker MC.

8. L85A2 AWS 800m zero is way off (to the high side).

9. L110a1 (British M249 SAW) has strange behavior and is not in line with the near identical US Army SAW. Prone recoil is okay, although it seems to have an excessive downward component at the end of firing. Crouched and standing recoil pulls the gun very strongly upward and right in a way that is impossible to control, but only if you are not moving. Several problems here:

• A heavier gun firing the same cartridge as a lighter gun should not have more recoil, yet compare the L110A1 crouched/standing to the M4A3 on full auto in the same positions.
  
• Identical US M249 SAW does not show the same behavior.
  
• The very pronounced upward component goes away if you are simultaneously moving while crouched/standing, with the gun behaving more like the M249 fired standing still crouched/standing.
  

10. CRV7-HEDP has little to no area effect. It seems to only have effect with a direct hit to a vehicle/object, and only on that target. HEDP warhead should have a blast radius of 10m with potential lethality from fragments to 55m. It is the same warhead and should have the same effect as the US Hydra rockets in the game. CRV7-PG seems to have same performance. On the other hand, CRV7-FAT is devastating against infantry in the open, which is also wrong. FAT is Flechette Anti-Tank and contains 5 solid penetrator flechettes. It should not be an effective area weapon against soft targets due to low density of projectiles. Perhaps the effects are simply switched, or perhaps the devs actually intended FAT to be GPF (General Purpose Flechette) rounds, which contain 80 flechettes and are very effective against area soft targets. Regardless, HEDP is broken.

11. Gunner/pilot command and targeting systems on the Wildcat are all screwed up and impossible to use effectively. For starters, pilot can magically self-designate and guide the CRV7-PG rockets all on his own, leaving the gunner just along for the ride. If gunner is also commander, controlling pilot engagement is a nightmare. Whenever the LD is active and acquired, pilot will fire rockets continuously, but will also move about wildly, causing the LD to swing off targets and rockets to spray all over the place. Control of the PG munitions needs to be taken away from the pilot and given to the gunner. Pilot should have unguided control of rockets when switching to manual fire. Pilot should always have control of cannon and should move to engage with cannon if given a target. Gunner should be able to laser designate any point, fire a single rocket and have it guide to target on the LD point actively controlled by the gunner. Ideally, LD point would also lock camera to that spot on the ground so targets can be engaged while the helicopter is moving.

Related: http://dev-heaven.net/issues/13380

12. CRV7 rockets have barely audible firing sound on the Apache AH1 (Wildcat is normal).

Reported here: http://dev-heaven.net/issues/13363

13. AS50 and AS50 TWS have both semi-automatic and full-automatic modes. The AS50 is a semi-automatic rifle and should not have a full auto option.

Edited August 31, 2010 by akd42

[PuFu 4600]

for issue no1, press numpad 0 or whatever your sights key is assigned to.

[das attorney 858]

I think officially, it's the <NUM/> as default and BIS refer to it as 'optics key'; not to sound cheeky (be pedantic) or anything. But yes, PuFu is right. :)

Regarding issue 9, it looks like a deliberate decision. If the BAF M249 had less recoil when crouching/standing, then it would be a really good point fire weapon and conquer all enemies, regardless of stance. As it stands, it's good at point fire when prone (devastating), and suppresses better when crouching/standing, so the guys with L85's can get stuck in on suppressed targets (like when the section are on the move). No real issue to me.

As for no recoil on the move; that's a BIS issue with all guns. M16's, for example exhibit this behaviour, albeit on a smaller scale. Check it out. :)

EDIT: Anyway, only a crazy Rambo Assault Gunner would regularly fire on the move with a SAW. You're better off running somewhere decent and get prone to maximize fire.

EDIT2: Hmm, maybe the word "maximize" was taken from Hiram Maxim, who literally maximized fire for the first time...

Edited August 31, 2010 by Das Attorney

[akd42 10]

for issue no1, press numpad 0 or whatever your sights key is assigned to.

Works if you have 3rd person view disabled. If external views are enabled, it just switches back and forth between the optic view and the external view. You can, however, escape the optic view in that circumstance by pressing the external view key [NUMPAD ENTER] a few times.

I think officially, it's the <NUM/> as default and BIS refer to it as 'optics key'; not to sound cheeky (be pedantic) or anything. But yes, PuFu is right. :)

Regarding issue 9, it looks like a deliberate decision. If the BAF M249 had less recoil when crouching/standing, then it would be a really good point fire weapon and conquer all enemies, regardless of stance. As it stands, it's good at point fire when prone (devastating), and suppresses better when crouching/standing, so the guys with L85's can get stuck in on suppressed targets (like when the section are on the move). No real issue to me.

I don't buy it. US M249 SAW is the same weapon but has different recoil behavior. L110 does not behave like its identical twin. It should. If the other SAWs need to be changed, so be it. Anyways, recoil prone is also strange/inconsistent with other MGs. It has a very strong down/left return motion.

As for no recoil on the move; that's a BIS issue with all guns. M16's, for example exhibit this behaviour, albeit on a smaller scale. Check it out. :)

The difference is less exaggerated. Just pointing out that the L110 behaves just like the other SAWs when you are moving, but not when you are stopped. That is very odd.

EDIT: Anyway, only a crazy Rambo Assault Gunner would regularly fire on the move with a SAW. You're better off running somewhere decent and get prone to maximize fire.

Irrelevant. Nothing in the above report was an argument for "easier" assault fire with the SAW. When moving, the L110 behaves like the US and USMC M249. If you have a problem with that behavior, make a separate report. Edited September 1, 2010 by akd42

[das attorney 858]

As I said, not an issue for me, despite the differences in behaviour from the default M249. I think it's pretty good as it is. No point converting it into an uber weapon by reducing recoil when crouching/walking. If you haven't put a ticket in CIT and you feel strongly about it, then be my guest.

[akd42 10]

As I said, not an issue for me, despite the differences in behaviour from the default M249. I think it's pretty good as it is. No point converting it into an uber weapon by reducing recoil when crouching/walking. If you haven't put a ticket in CIT and you feel strongly about it, then be my guest.

Try reading my posts again. You are not comprehending.

[mosh 0]

Anyone else having audio issues (audio volume getting lower and lower in the Huey enroute) while playing stock scenario 01: Trail By Fire with Build 72967?

/KC

I noticed that too, but only once. I exited game, restarted, and mission played fine.

[Dwarden 1125]

Seems so :)

http://twitter.com/FoltynD/status/22310340823

i knew it,

this feeling of something watching me from hills ... :D