GaMEChld

I don't use a penny, I use the lever of a standard sized nailcutter, but any similarly shaped metal should work great. It's just a second to put in, no fiddling around, no getting it stuck, good balance. Though I've been playing Namalsk lately, havent been auto running at all since theres so much to do there.

Blow me. That worth a reply?

Lol, blow me. If you are going to defend a 3 month period to fix graphical bugs that not only made the game unplayable at times, but that others have exploited to corrupt the graphics of players travelling in certain directions, then you have your head up your ass. :-)

The blood icon was not previously useless, as it provided an extremely clear notification that you are bleeding (far more clear than watching the debug monitor), and the debug monitor provided more information than your current blood level. Keeping track of bandit kills, murders, and humanity were my primary purpose for it. Getting killed while fiddling with the on button for it was very refreshing. Anyways, I'm out. Took the entire summer to fix some game breaking graphical glitches, so my confidence in the standalone is pretty low. Good luck all.

Sigh, anyone know of a way to default the debug monitor to ON in this new version? Freaking Rocket fixes one thing and breaks another. Indicators don't work with debug on. I don't even think turning the debug monitor off was a feature many were clamoring for.

I don't understand what is gained by leaving the problem objects in the game when they are known to still be broken. I understand it would be "hiding" the problem, but by all means, hide the damned problem until there is a fix to be tested. So put out a 2.6 hotfix with the problems removed entirely, then when you think you have a handle on the problem, release a 2.7 with the objects returned. And if rocket actually thought 2.5 fixed the graphics, then I don't know what his testing methodology is. If he had no problems on 2.5 before releasing it, he should post the versions of ARMA, and the hardware and software specs of the test platform to see if anyone can reproduce it. All the apologists are defending this as an alpha that we are testing, but it doesn't feel like testing conditions. We "tested" this version, its broken, as was the previous version, and these "tests" are months long between iterations. We knew the answers to these tests within days (or even hours) of the version releases. Meanwhile, I just played 30min in DayZ Lingor and was astounded at how much of an improvement it was. I'll probably spend the rest of my dayz time there until the stand alone is out (if it is reported to be in good shape). The thing about the stand alone that worries me is how reliable will fixes come if we had these game breaking graphical problems for basically 2 patches over the course of 3 months. It doesn't build confidence...

From what I hear, things were better in 1.7.2.3? Perhaps we should roll back everything?

1.7.2.5 actually made things worse for me, as before I used to at least be able to relog and be good to go for a while, now certain places like Cherno and Balota are nearly permanently artifacting for me. Thats with arma versions 95883-96061 on catalyst 12.6 & 12.8