Just did an FW battle with Ghost Kaiser, Booby Tuesday, and some others. We were cloaked for an extremely long time after spawning, then rubber-banded back to our spawn areas. Rubber-banding continues to happen a couple more times, and there was some pretty bad lag
Frame rate issues were extremely awful, and made fighting in any sort of engagement pointless.
Once battle is over, I get an internal error.

This is not acceptable, but I'm sure you guys have some line about how you already resolved the server issues, and I'm sure you won't bother acknowledging the frame rate issues. Frame rate was actually pretty close to perfect in Warlords 1.1, and the best I've ever see in Dust's history, good job ruining it.

Oh great! I can't connect to Dust anymore! just endless loading circle with (CONNECTING... Attempting to login ...)
Success, logged in, after like 3 minutes.
Oh, tried to login to character, and another endless loading circle. Just perfect.

For this battle, according to the server log, the average ping time of the battle was 153 ms, which was normal, and your average ping time was more than 400 ms which would cause network issues (rubber-banding). What's your internet connection, and how is your PS3 connected, wired or wireless?

For this battle, according to the server log, the average ping time of the battle was 153 ms, which was normal, and your average ping time was more than 400 ms which would cause network issues (rubber-banding). What's your internet connection, and how is your PS3 connected, wired or wireless?

For this battle, according to the server log, the average ping time of the battle was 153 ms, which was normal, and your average ping time was more than 400 ms which would cause network issues (rubber-banding). What's your internet connection, and how is your PS3 connected, wired or wireless?

I would like to point out that frame rate was very good, perhaps the best it has ever been in Dust for me in Warlords 1.1. This recent build reduced my frame rate more regularly, and more substantially, so I think it's incorrect to assume my PS3 is what is responsible, unless one is to assume that my PS3 just happened to take a dramatic downturn on the day of the patch.

New vids starring my brother, Velvet Overkill.


Before downtime on the day 7/30 (day of this post).

Around 9:30 EVE time. https://vid.me/92L5

Around 9:55 EVE time. https://vid.me/VX1u (minor, but noticeable when the sentinel hides behind the crate at 14 seconds, and when he is first shot)

Around 10:05 EVE time. https://youtu.be/195o0xBfahM (should be noted that the Gallente Research Lab is on this map)

No prob! :)


The more videos/examples of fresh systems (with or without SSD) would be useful. We don't mind more material to take a look at as long as it contributes to the investigation. But yes, the current theory does include issues with hard drive, but does not exclude other options.

I would like to point out that frame rate was very good, perhaps the best it has ever been in Dust for me in Warlords 1.1. This recent build reduced my frame rate more regularly, and more substantially, so I think it's incorrect to assume my PS3 is what is responsible, unless one is to assume that my PS3 just happened to take a dramatic downturn on the day of the patch.

Addendum on the PC match I earmarked as a lagmatch - I was not the only player lagging. Not all players were lagging either, though.

Here're some other perspectives.



Here's a non-lagging perspective from character J0LLY R0G3R playing in 480p: https://www.youtube.com/watch?v=8zqVP-3SmFY

Unfortunately I don't have a comms log but I'm not sure how helpful our collective bitching about lag would be, anyway.

[...] found this excerpt:



Guess what outpost that relates to.

I am currently trying to figure out a way to prove the theory that the problem lies with the hard drive. If I could only replicate the problem at will, I could switch out my current drive for an SSD to see if that helps. But no point trying that without a valid test.

Need a monster theory from Keeriam that we can prove.

[edit]
The problem wouldn't actually be with the hard drive, just that there is a bottleneck with IO caused by poor design or a giant dirty subtle bug.

I was sitting on a static menu yesterday, 10 minutes after switching on the PS3. Only on-screen movement was flashing chat channel icons. The hard drive light was *constantly* flickering, I'd guess an average 50% load. There is no reason for that much activity in that situation.

If that is the baseline for just having the DUST client loaded, no wonder things start falling over without having to do too much else.

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.

No prob! :)


The more videos/examples of fresh systems (with or without SSD) would be useful. We don't mind more material to take a look at as long as it contributes to the investigation. But yes, the current theory does include issues with hard drive, but does not exclude other options.

I would like to point out that frame rate was very good, perhaps the best it has ever been in Dust for me in Warlords 1.1. This recent build reduced my frame rate more regularly, and more substantially, so I think it's incorrect to assume my PS3 is what is responsible, unless one is to assume that my PS3 just happened to take a dramatic downturn on the day of the patch.

New vids starring my brother, Velvet Overkill.


Before downtime on the day 7/30 (day of this post).

Around 9:30 EVE time. https://vid.me/92L5

Around 9:55 EVE time. https://vid.me/VX1u (minor, but noticeable when the sentinel hides behind the crate at 14 seconds, and when he is first shot)

Around 10:05 EVE time. https://youtu.be/195o0xBfahM (should be noted that the Gallente Research Lab is on this map)

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.

Thank you!

Can some of you look at this: https://www.youtube.com/watch?v=qEPGLymvS2U and let me now if it helps with the frame rate in game? Thanks!

Addendum on the PC match I earmarked as a lagmatch - I was not the only player lagging. Not all players were lagging either, though.

Here're some other perspectives.



Here's a non-lagging perspective from character J0LLY R0G3R playing in 480p: https://www.youtube.com/watch?v=8zqVP-3SmFY

Problem with the disk drive you say? Here's another video link to the issues everybody is getting https://youtu.be/mfajcwaCHGs

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.

Thank you!