I have reached to our live team and they are proposing a few scenarions for this specific issue. (we have seen your vid.me video https://vid.me/XGYC regarding FW framerate drops) Here are some cases that we would like to see:

Case 1:
Use the same PS3, play a few Skirmish battles, record a video and send us the link.

Case 2:
1.Find a different PS3 (that is newer and doesnGÇÖt have any disk issues).
2.Play a few FW battles on that PS3 and note the performance.
3.Record a video and send us the link.

If this is possible, this would pinpoint the issue further. The video that you shared with us recently does indicate that there may be some issue with the hard drive because we had similar issues with faulty hard drives, but that's just our guess right now.

Would like to drop in and note that it's Skirmish itself that usually brings about the slideshow. All those null cannons, everything constantly getting hacked. I can play other game modes for several hours with little to no issue, and Skirmish sort of "triggers" the downhill slope into unplayability. That's how it goes in my experience.

Capture card is not extremely necessary by the way. Even a phone recording of gameplay for a few minutes will do just like vid.me link was made. :) Plenty of options to capture video directly from your phone!

But yeah - thank you for your feedback so far guys.

Obviously not the issue here for everyone but when was the last time you deleted and reinstalled Dust? It is best practice to delete and reinstall some time very soon after each update as that extra data seems to pile up and cause issues of its own.

Next add-on the Dust514 pack, with SSD and Water cooling: The only way to play normally, 30 000 dollars or 600 000 000 000 aurums



Just irony Frame, If we are always in Dust, it's because it's the best game ever. But frustration comes when we love something and when we can't do it normally.

So the community rage is the best compliment for your work. We prefer continue playing dust frustrated instead of playing something else running properly.

.
.
first half we were crushing the enemy until their mcc had about only 35% of their armor left. Then all of a sudden boom frame rates dropped badly, the enemy did not even secure the objective once prior to this, its like they flipped a switch and cause the frame rates to drop, it actually cost us the battle and it seemed the harder we pushed to re gain the objective the more lagg we would experience, or the closer we got to the enemies the more lagg we would get as well.

I am uploading that video plus a factional warfare video of basically the same thing happening. They are uploading to the tube as I speak and I will post here for you within 24 hours tops.

The funny thing is I am using a 500 GB ps3 slim brand new maybe 2 months old tops. I hardly ever experience frame rate issues except when dealing with certain enemy players. hmmmm.

For example one enemy died 5 times and got zero WP all battle, seemed as if they were just sitting around messing with framerates for their team. You can verify all of this by looking at the domination scoreboard after battle.

Not only that but when the enemy team does all this with such accuracy it makes you think the problem is not with hard drives but more so with certain players causing this to happen during battles.

I will post the videos for you here are soon as they are done uploading.

Another question, why do the framerates drop so badly only once the enemy team knows they are losing so badly? Seems a little more fishy than just hard drive issues, if it was hard drive issues the framerate issues would be constant all throughout the battle not just starting at an exact time right when the enemy needs it to happen to secure them the victory, it all sounds pre planned and staged by certain players. I am not pointing any fingers but it makes no sense especially since I am using a bran new system with 500 GB hard drive.

Anyways, my point is if it was hard drive related framerates would drop as soon as the battle started not right when the enemy needed them to drop to win the battle. I am sure you understand my point and the proof will be here for you soon to watch.
.
.

Spawn in - die instantly. It starts loading the environment, but it didn't finish, so it has to dump, but you are already spawning in again before the dump finished, now it's trying to load while dumping, and dead again, now it's loading and dumping twice as much and do in and so forth