Jump to content
Welcome to the virtual battlefield, Guest!

World War II Online is a Massively Multiplayer Online First Person Shooter based in Western Europe between 1939 and 1943. Through land, sea, and air combat using a ultra-realistic game engine, combined with a strategic layer, in the largest game world ever created - We offer the best WWII simulation experience around.

ATR verses P3F nerfed?


solitaer
 Share

Recommended Posts

I couldn't help but notice that both during later days of campaign 63, intermission and now in campaign 64 that killing the P3F with ATR is no longer possible. (seems it was nerfed/changed in the last patch)

Normally it would take maybe 5 shots (if you know where to shoot it) for it to flame. I have unloaded up to 20 shots into them in the most recent attempts with no results other than some leaking fuel and a face full of MG rounds. Could any other Allied ATR'ist confirm this or report a kill on a P3F via the rear flames spot (which is only spot as far as I know)?

Also have the spots changed on the P4D? The rear bottom left still works but what about the driver kill on right side behind the front wheel? Gunner death side of turret? Explosion point center of wheelbase? I can't see a result on any of these other than rear flame point.

Training server is not up so of course I can't test these theories. With the lack of actual anti tank weapons a nerf to the meager ones we have would be the nail in the coffen of this game for me.

Edited by solitaer
Link to comment
Share on other sites

A definitive answer from CRS for once would be nice.

BTW CRS if it wasn't nerfed then maybe it is a BUG. But you guys need to look into it either way.

Link to comment
Share on other sites

Tried the 3f last week on training and could flame it' date=' not sure about 4d though.[/quote']

Do you remember how many shots and where you shot it? Normal flame spot in center bottom rear or just to right of center.

Link to comment
Share on other sites

Neither was nerfed.

We made no changes to either weapon with v1.31, and subsequent testing reveals no bug relevent to this report.

Behaviour is identical to v1.30 behaviour.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...