Patch 69645 - changes under the hood

[Alex72]

Noticed 2 crashes AFTER exit. And i think i played MP both times. So when i hit exit and it looks like ARMA closes perfectly the background stays black (some of it and i can see the desktop in a corner) with a "send error report to MS". I took it as a fluke the first time but it happened a second time. Think i saved the RPT, but will test it tonight and see.

[MadDogX]

New beta is here, peeps. Finally, a separate volume slider for VoN!

Let's see if the disappearing ground bug has really been fixed.

[^Th0mas^]

Please report back if the patch have some AI changes as well

[fabrizio_T]

@Suma:
Hint: please check out the "killed" event Handler.
It looks it's being called multiple times for same unit.

[Sickboy]

Double killed EH problem is probably because of setDammage 1 usage inside handleDamage eventhandler (In this situation, the killed eh seems triggered twice ).
We have/had the issue too in our Wounding system
Even setHit["body",1] inside a handledamage EH triggers the killed EH twice.

[Kroky]

I would like to see a function to adjust the FOV in the game menu in with the next beta patch. I think this would be useful, since not everybody is happy with the FOV right now and there will be never a setting that makes everybody happy. So everybody could adjust it for himself.

[mrcash2009]

New beta patch 69645 may appear not huge based on the change list, but it contains very significant changes under the hood.

As the changes were made to the engine core, including the core memory allocator, extensive testing is badly needed.

Download at http://www.arma2.com/beta-patch.php or directly from ARMA2_Build_69645.zip, feedback welcome.

patch 69645

Ive been running with 63826 since it arrived and no complaints at all (or any beta previous).

I installed 69645 the other day .. and bam ... really bad FPS ... really laggy on map, laggy when moving and turning. I did updated Nvidia drivers to latest WHQL just before and had not played for a while and I use mods.

So today I simply loaded the game with 69645 vanilla and the SP mission "Sipher" running it at night as a single SF player at 50 percent difficulty. This is basically hardly any enemy near you at start apart from heli insertion ... just you and no other AI at night in Chernarus. The map was laggy on start for briefing when it was dynamically placing items .. 5 second pause to then allocate items ready for mission. In the heli it was lagging and then when i got out spinning was awful the best way to describe it is the lag and fps was like I was in a middle of a large firefight with 5 heli and 4 10 man units each side and I was dropped into it, in the day maxxed out using all AI mods. Yet im 1 man no AI near me and at night with no mods.

So .. I then exited and saved the mission at the point of stood after heli insertion. Exited, flipped my "beta" folders around so it would load 63826 and went back into game. I then resumed the Cipher mission, low and behold the heli is still flying away im stood on my own and spinning on a dime, smooth as silk like the map was totaly empty and acting as it should.

I repeated this on simply 1 man on different maps, flipping between old and new beta to load same mission, every time it was the same.

So to report, never in any time of using A2 and betas have I seen such a massive performance drop to unplayable since using them. Something is very strange with the way its handling in the 69645 beta. I can repeat the issue time & time again.

To recap by simply introducing 69645 my system running A2 with usual setting never changed (with or without any mods) and just putting 1 player on a map runs like ive installed it on a single core 1 gig machine with built in graphics card ... remove and play 1.05 or old beta and it runs totally fine.

BI ... if you want more info I fine with supplying more just ask me what you need.

To conclude ...

"69645 on my rig runs so bad that its unplayable"

Which im totally surprised at becuase all betas and A2 have not been that bad at all for me. PLus the difference is so obvious and extreme that if this was a released patch I would be making some serious complaints to BI ... im not because this is beta but you might want to see how this works on rigs like my combination because so far this runs to the point of broken almost.

[Flash Thunder]

Suma from the changelist

Optimization: Grass is not rendered when flying "fast" and "high"

Can parallax maps also not be rendered unless the player is almost at ground level 10 feet?

Unless im just seeing stuff, yesterday when I was flying around Utes I could still see the parallax effect even at relatively high altitude, obviously this could help alot in terms of performance and take some pressure off from the renderer.

please ignore if already added in.

Thanks.

[Alex72]

We are at beta 70313 now. You answered a 2 week old post.

[Flash Thunder]

We are at beta 70313 now. You answered a 2 week old post.

I know but It would seem more off topic in that thread since it mainly deals with the ex thread command.

I dont want to be beaten by posting this in that thread.

Where should I post this Alex?