Helmut_AUT

Okay, since we are collecting all here: T-90 still can be taken out with about 120 rounds of 12.7MG ammo from M2 Humvee (and other M2 guns). There's a more detailed thread in the beta boards, Suma had already seen it and I don't quite understand why it isn't fixed.

I had no mods loaded when testing. Hummer with M2, AI-crewed T-90 with no ammo, 50 meter front to front at the Utes Runway, peppering the first ammo box all over the frontal arc of the T-90. Second ammo box - barely into it, crew exits and T-90 brews up. If you only hit the Gun area it doesn't seem to cook up, but I think it's the tracks and lower front profile that are still vulnerable. In the 1.05 impressions thread, someone else reported the same results, it's not just me. Dwarden, thanks for the response, but this was known and acknowledged by Suma before 1.05 release in this thread. I really don't get why such a massive game-changing bug continues to live for yet another patch circle.

Since I got no reponse in the impressions thread, but this has been confirmed by a mate at simHQ, I'm putting this in it's own post: I have the most weirdest bug here I've ever seen When I start a WARFARE based Scenario (Single-Player War Welcomes, or MP Superpowers on my own "LAN Server") and buy the M4 HOLO (the green SpecOps Rifle with Eotech Holo Crosshairs and M203 GL) the SIGHTS are OFF. The bullet impact is on the top mark of the crosshairs (the 12 O'Clock marker), not on the center point. However, if I use the same rifle in the Editor, it is perfectly zeroed. I'm not using any mods (I have a few desert units loaded, but they do not touch weapon configs) and even if some addon was interfering, why should it only happen in certain missions but not the editor? Totally freaking weird. By definition the weapon configs must be the same for any mission and editor preview? Why does WARFARE type missions change the sight picture so that the bullet is high? Aimpoints and Scopes seem to be fine, someone else said it might also happen to Ironsights. This is enough difference in rifle zero to miss people at 200 yards. ---------- Post added at 11:28 AM ---------- Previous post was at 10:09 AM ---------- 37 Views, no comments?

The weird thing is that Suma was aware of this from the betas, and said the only reason it wasn't fixed in them was that they did not want to put out the large file tracked.pbo in the beta downloads. By all means he expected this to be fixed with full 1.05 but it seems totally unchanged. From his explanation the MinimalHit value had a default setting which worked for some vehicles (M1A1) right out of the box but not for others, so they needed to set specific values for T-90 and deploy them via tracked.pbo in the patch. Maybe one of the Devs will look into this, it's a known problem and has already a solution framework implemented.

I'm not stupid. I tested with T-90 with no ammo, fully crewed, then team-switched into Commander of T-90 to check damage. And yes, the AI will constantly attack T-90 with MG - every played WARFARE based game against AI Avenger? Do not try to be so clever and invalidate other people's tests. M1A1 suffers no damage to mobility or gun from M2 Machine Gun, T-90 can be taken out by a suprise flank attack from a HUMVEE. I assume it hasn't been fixed for T-72 either... which means OPFOR has no serious armor in the entire game, you're better off using a BMP3. This bug has massive influence on any kind of WARFARE type game, especially playing against humans. If my entire 12000 Rubels worth Platoon of T-90 can be taken out by a few lucky Humvees costing 400 each, what's the point of using tanks?

Okay, I have the most weirdest bug here I've ever seen - please someone confirm this: When I start a WARFARE based Scenario (Single-Player War Welcomes, or MP Superpowers on my own "LAN Server") and buy the M4 HOLO (the green SpecOps Rifle with Eotech Holo Crosshairs and M203 GL) the SIGHTS are OFF. The bullet impact is on the top mark of the crosshairs, not on the center point. However, if I use the same rifle in the Editor, it is perfectly zeroed. I'm not using any mods (I have a few desert units loaded, but they do not touch weapon configs) and even if some addon was interfering, why should it only happen in certain missions but not the editor? Totally freaking weird.

You can, I tested it (M2 HUMVEE 120 rounds to chassis of T-90 - bang). The T-90 and T-72 armor doen't really seem fixed, so they get a "Good" from me. The patch as a whole would be awesome if not for that unnecessary bug left.

Okay, first impressions: My test system at work had errors updating, the game system at home not. Everything seems to work fine, I do get the impression that I have a slight new "micro lag" when moving around fast. AI engagement ranges are trough the roof compared with 1.04, seems as good as the Zeus AI mod. Warfare mode has been improved (as in the beta). What hasn't been improved on is that T-90s still get brewed up with about 120 .50cal hits (slightly more than a single magazine). This is a SERIOUS problem since it renders OPFOR tanks about as dangerous as two or three M2-Hummers. The Apache is an absolute beauty. The view distance improvements (same as beta) are nice. All in all, no big surprises for those who played the betas, but a solid update with some sweet extra content. Still no magic "performance bullet" though, FPS killer trees still present, and the T-90 bug was known to the developers, should have been fixed by the "Minimalhit" value but isn't.

Oh, and just tested: 1.05 did not fix T-90 armor problems. Still brews up after max. 120 rounds 12.7mm from HUMVEE.

For those with errors: maybe try a defrag, as I understand it, the patch changes single parts of the large PBOs already installed, and if the install is fragemented, it might lead to these errors? I know my test system at work which failed is pretty dead with it's Hard drive.

Just installed on my real gaming machine - same file, same DVD installed from, no errors here. I think it may help to apply 1.04 before 1.05. Other difference is XP SP2 (on the failed box) vs. Win7 64bit on the working update, I "ran as admin".

I re-downloaded the torrent and same errors still, I'm running as admin. If you get errors, please state which mirror you used, but I don't think it's broken downloads we are seeing here. As far as I'm aware, a broken download would mean you couldn't extract the ZIP file. I'm using a German version btw, if maybe it's language-specific?

The entire game or just the patch? A reinstall of the whole game would be quite scary.

Just got the same, using the download from Bittorrent. This is a very old system here at work, I just used it to test various A2 addons and for mission making. I hope it's the system that causes this error and not the download...

Seems someone had mercy on the Cannon/Coax issue. From 1.05 changelog: Changed: AI gunners can autonomously use automatic weapons only when some automatic weapon is selected

Can anyone confirm that we need to move the Addons to User/Documents folder? I haven't seen the readme anywhere yet. Oh, and big kudos to BIS for pulling the DRM-annoyance for their legit customers.

Great - I had it running at work, then people fell on my desk, and I accidently closed Chrome... now I can't get into Tiscali anymore.

Tiscali link is also slowing down - certainly a lot of demand for that file.

Is this solid? I don't want to download 270 Megs just to find out that it's an "oops, doesn't work" premature leak. If it is, many thanks for those sharing their bandwidth. I knew they'd make this a christmas present...

Does the AI handle it well? Bridges and such never were their favorite...

I just noticed this today: If I load plain 1.04 and set up my own "me only" MP server with Superpowers Scenario, I can go to "Parameters" and only have two Parameters to chose from (victory condition and game specific like fast time+no arty). These two parameters are correctly translated into German Lang. If I do the same in the beta, I get much more parameters (number of capturable towns, Neutral AI strenght...) but they are all in english. Does anyone know which PBO stores the default MP scenarios? There's certainly a missmatch here, but the changelog doesn't mention any improvements.

Thanks Suma, now we know that this will be fixed in 1.05 Agree on the problems with target/ammo selection for tanks. The reason that damn Avenger could plink my T-90 dead was that my Gunner insisted on shooting the Coax. If you take out Hummers with a Sabot, you can mostly avoid their .50cal fire, but it requires a very active command style.

Were they working in 1.04? I never tried... last I tried was 1.02.

Lack of Night Vision for the US Tanks? Hard to belive...

Maybe they are using the Commanders .50cal ;)