Sign in to follow this  
Followers 0
dwarden

ARMA 2: OA beta build 102678 (1.62 MP compatible build, post 1.62 release)

22 posts in this topic

http://www.arma2.com/beta-patch.php

mirror :

[102678] Fixed: switchWeapon action broken (https://dev-heaven.net/issues/71136)

+ way more crash fixes both scripting and else

[102493] Fixed: execFSM/doFSM/commandFSM causes crash with non fsm file

[102469] Fixed: initAmbientLife causes a crash (https://dev-heaven.net/issues/71001)

[102440] Fixed: Smooth camera could sometimes jump very far briefly (caused crash https://dev-heaven.net/issues/32444)

+ more crash fixes including the MP fire+ground hit one

[102106] Fixed: Joystick state reset on start

[102082] Fixed: gearSlotData causes crash when no valid control is given (https://dev-heaven.net/issues/70912)

[101333] A new mission.sqm unit value forceHeadlessClient used to mark a role reserved for a HC (https://dev-heaven.net/issues/67648)

+ hotfixed crash from 101141 changes

[101141] Fixed: Scripting functions aimPos, eyePos, eyeDirection fixed for a crew (https://dev-heaven.net/issues/38606#change-152548)

[101032] New: Scripting function hasInterface to allow detecting a headless client or a dedicated server.

[100540] Fixed: Users connecting with blocked CD keys were sometimes shown "You are banned" message instead of "Bad CD Key".

+ SSL fix http://forums.bistudio.com/showthread.php?143091-Secure-ID-progress&p=2273013&viewfull=1#post2273013

+ multiple crash cases resolved (thanks to all who reported)

[100296] Fixed: MP: Player head movement using numpad keys was not visible to other players.

[100257] Fixed: ballisticsComputer uses wrong velocity (https://dev-heaven.net/issues/6823)

+ some beta regressions fixed, shall hotfix some of the often crashes of client/server seen in past weeks

+ possible slight performance increase when using BE filters

the build contain quite some of crash fixes I mentioned last two weeks

suggested to be used for server hosting as it shall be noticeably stabler

(if you still get any crashes, it's very important for us to get server's mdmp,bidmp,rpt files

(compressed e.g. to my email (which is my BIForum nickname @ bistudio.com)with subject CRASH)

BattlEye compatibility: ... SUPPORTED, enjoy ! ...

note: also deployed on STEAM! (inside "test" branch, default beta is 101747)

+++

Data fixes and improvements by the Community Config Project (CCP)

Changelog: https://dev-heaven.net/versions/1391

More info: http://forums.bistudio.com/showthread.php?141732-ARMA-2-Community-Configuration-Project-(A2CCP)

Share this post


Link to post
Share on other sites

Dwarden silly question you say

"please don't use 102xxx builds ... wait for next beta (hopefully this Friday) "

in this thread

http://forums.bistudio.com/showthread.php?146586-Server-Restarting-Every-Few-Seconds-After-Beta-Update

But yet you have released another 12xxxxxx should we use this latest BETA for dedicated servers still or use an older build like 11xxxx?

Thanks again for your support in ARMA2 many years after its release the best games devs ever.

P.S

I am saving up for ARMA 3 to get it upon release I was saving for supporters edition but cant affor that at all but yeah will be getting the ALPHA upon release even if I have to sell my better half :P

Share this post


Link to post
Share on other sites

it was meant for builds prior 102285

Share this post


Link to post
Share on other sites
it was meant for builds prior 102285

Ok thanks will install and test this tonight have 4 of us tonight not many but its easy to organise LOL

Thanks again BIS

Share this post


Link to post
Share on other sites

Hi, I've got 2 pc's at home, myself and my son have literally just started playing multiplayer online games. We have the latest beta (this one) installed. With one pc running OA only we see multiplayer games listed and refresh no problem at all, can connect and play. When both pc's run OA then we can no longer see multiplayer games listed at all. However in the vanilla 1.62 release we can both connect and see multiplayer games and connect to the same game no problem at all. Therefore it appears that there is something in the beta code (no idea which release) which is causing an issue with gamespy (I assume), perhaps some sort of ip clash (as we use a natted connection) that is causing it to no longer work and preventing both pc's from seeing any multiplayer games. I will test hosting our own lan game tomorrow with the beta to see if that works.

Andy

http://www.arma2.com/beta-patch.php

mirror :

the build contain quite some of crash fixes I mentioned last two weeks

suggested to be used for server hosting as it shall be noticeably stabler

(if you still get any crashes, it's very important for us to get server's mdmp,bidmp,rpt files

(compressed e.g. to my email (which is my BIForum nickname @ bistudio.com)with subject CRASH)

BattlEye compatibility: ... SUPPORTED, enjoy ! ...

note: also deployed on STEAM! (inside "test" branch, default beta is 101747)

+++

Data fixes and improvements by the Community Config Project (CCP)

Changelog: https://dev-heaven.net/versions/1391

More info: http://forums.bistudio.com/showthread.php?141732-ARMA-2-Community-Configuration-Project-(A2CCP)

Share this post


Link to post
Share on other sites
Hi, I've got 2 pc's at home, myself and my son have literally just started playing multiplayer online games. We have the latest beta (this one) installed. With one pc running OA only we see multiplayer games listed and refresh no problem at all, can connect and play. When both pc's run OA then we can no longer see multiplayer games listed at all. However in the vanilla 1.62 release we can both connect and see multiplayer games and connect to the same game no problem at all. Therefore it appears that there is something in the beta code (no idea which release) which is causing an issue with gamespy (I assume), perhaps some sort of ip clash (as we use a natted connection) that is causing it to no longer work and preventing both pc's from seeing any multiplayer games. I will test hosting our own lan game tomorrow with the beta to see if that works.

Andy

You do have two seperate copies of the game?

Share this post


Link to post
Share on other sites

Doing more tests this morning, appears that I can't see any multiplayer games at all when running the beta, with one or two pc's running at home, 1.62 is fine, seems to be beta release. Also as far as I can tell the switch weapon function still doesn't appear to be working. I've removed all community mods to ensure its not one of them causing an issue.

Hi, I've got 2 pc's at home, myself and my son have literally just started playing multiplayer online games. We have the latest beta (this one) installed. With one pc running OA only we see multiplayer games listed and refresh no problem at all, can connect and play. When both pc's run OA then we can no longer see multiplayer games listed at all. However in the vanilla 1.62 release we can both connect and see multiplayer games and connect to the same game no problem at all. Therefore it appears that there is something in the beta code (no idea which release) which is causing an issue with gamespy (I assume), perhaps some sort of ip clash (as we use a natted connection) that is causing it to no longer work and preventing both pc's from seeing any multiplayer games. I will test hosting our own lan game tomorrow with the beta to see if that works.

Andy

---------- Post added at 12:46 PM ---------- Previous post was at 12:43 PM ----------

Yes we have 2 separate copies of the game, its not a licensing issue. as i said 1.62 vanilla works fine, and as I just seems i can't see any multiplayer games, so the 2 pc's was a red herring.

Share this post


Link to post
Share on other sites

Hello sentryuk,

Have you looked at the Filters button on the MP screen? There maybe a ping or game more or some other parameter inadvertently set.

Share this post


Link to post
Share on other sites

Bullet impacts not broadcasting

Hi all I was playing MP coop last night and I was running a dedi server and playing from same machine (normally I run dedi server on a diff PC but did not have time to set that up.)

Any ways I was wacthing my mate snipe at a range of about 480m no more than 500m and I could not see his bullet impacts.

I remember this was a problem in a very old beta and seemed to be fixed from what I was told but never got a chance to test it my self.

I just want to confirm if its still pending or was actually meant to be fixed because last night it was not broadcasting at all :(

Please BIS take a look into this for me as sniping is all I do and makes spotting in a sniper team impossible.

Share this post


Link to post
Share on other sites

what build was last when it works ? or which build it ceased to work? CIT ticket with repro mission w/o any mods ?

Share this post


Link to post
Share on other sites

I remember this was a problem in a very old beta and seemed to be fixed from what I was told but never got a chance to test it my self.

Yes this was fixed in a old beta quite some time ago. I know for sure since I verified it with my brother, IIRC there was an upper limit at approx. 1000-1100 meters, beyond that bullet splashes was not seen but it was a big improvement from how it was before that.

Unfortunately I'm currently unable to test...

/KC

Share this post


Link to post
Share on other sites

If at some point you do get a chance to test this on a dedi server it would be great as it would just confirm I aint going mad LOL

I have no idea when it stoped I have been away from arma for a long time familys for ya.

Yes this was fixed in a old beta quite some time ago. I know for sure since I verified it with my brother, IIRC there was an upper limit at approx. 1000-1100 meters, beyond that bullet splashes was not seen but it was a big improvement from how it was before that.

Unfortunately I'm currently unable to test...

/KC

Share this post


Link to post
Share on other sites

#1 Observed that AI going/running downhill on Takistan (and many other islands) are jumping over invisible obstacles and sliding down. Expected that AI walks slowly or crouch down if the terrain is too steep (or too sharp-edged) for them. #2 Observed AI SL/TL using rangefinder or binoculars upon enemy contact report and in narrow streets of towns/cities (eg Zargabad). Expected AI SL/TL using rangefinder or binoculars in open areas and primarily "to scan" and perhaps "to observe" from greater distance. Suggest to let AI switch to rangefinder or binoculars only if the enemy contact is further than 200-300m. #3 Observed that AI SL/TL keeps ordering his team to last known position of an enemy contact and continues to do so until he is very close to this point. Expected better (AI) info sharing of the team/squad so that the AI SL/TL change his order as soon as it has been discovered that the contact/enemy is gone.

Edited by NoRailgunner
some more issues

Share this post


Link to post
Share on other sites

I was having an online freezing problem as reported in the link below. It stopped with this beta 102678, but yesterday it came back. The dev heaven ticket was closed after it was fixed. Is there a way to reopen the ticket?

https://dev-heaven.net/issues/70609

Share this post


Link to post
Share on other sites

#4 Using OA TWS rifles with A2 units does show up a full white or black screen - looking through TWS scopes the scenery should be/stay visible, no matter the unit and how often one switches TWS on/off. #5 Noticed an animation bug "waving" arms and hands by switching to or from AT/AA launcher.

Share this post


Link to post
Share on other sites
#4 Using OA TWS rifles with A2 units does show up a full white or black screen - looking through TWS scopes the scenery should be/stay visible, no matter the unit and how often one switches TWS on/off.

wasn´t that seasons/ temperature related?

Share this post


Link to post
Share on other sites

@ST the whole screen goes white/black - you can't see much its similar to the UAV screen bug after A2 release.

Share this post


Link to post
Share on other sites
I was having an online freezing problem as reported in the link below. It stopped with this beta 102678, but yesterday it came back. The dev heaven ticket was closed after it was fixed. Is there a way to reopen the ticket?

https://dev-heaven.net/issues/70609

Can anyone please let me know what the process is for reopening a ticket? Do I recreate it, duplicate it, contact some one?

Thanks

Share this post


Link to post
Share on other sites
Can anyone please let me know what the process is for reopening a ticket? Do I recreate it, duplicate it, contact some one?

Thanks

seems they see it fixed with BE client 1.191

Share this post


Link to post
Share on other sites

Yeah, it was fixed for about a week for me too, but it came back 2 days ago. Guess I'll just duplicate the ticket or some thing.....

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  
Followers 0