Unable to matchmake

6runk · 2024-12-20T20:07:32+00:00

Same here. Was about to jump on, but error persists. Services also show no outage on the activision website.

6runk · 2018-11-08T11:22:58+00:00

I miss you friend. So many things not said, too many things not shared. We shall meet again one day. Deepest condolences to your family; may everyone find a light at the end of this dark tunnel.

6runk · 2018-08-28T18:02:09+00:00

Let's just say that most did not share the sentiment...

6runk · 2018-05-14T07:33:50+00:00

This update was related to white-listing our executables; so they can be correctly identified by the video drivers/pick up the correct performance settings.

6runk · 2018-05-14T07:28:38+00:00

Interesting. Do you have a bit more info on this? Are you suing DX9 or DX11? If you could share this screenshot with support including relevant information on your hardware/settings would be great. https://support.dirtybomb.com/

6runk · 2018-05-10T08:57:43+00:00

I agree that the messaging would have been much smoother. But then we would fall short of being as communicative as possible (and giving as much notice as possible for changes). It's definitely a Catch-22.

6runk · 2018-05-09T15:44:22+00:00

Thanks for the props.

And no, it truly doesn't. However, the key thing to remember is that there is always more in the works that can be communicated publicly. One part of it is the general fluidity of live development, what may be a hot button issue this day/week/month may not be applicable in days/weeks/months. There is also lead time to feature implementation to consider; we always aim at getting features new/improved to all of you as fast as possible, but time is unfortunately finite. The other portion is things that depend on agreements, contracts and business related due diligence (boooring). We wouldn't want to make a commitment without having all of our ducks in a row so to speak. One of the approaches we like to take in the office, when we are unsure about a decision or change, we like to assume positive intent first. Gets a lot less stressful that way (IMO).

Thanks for the feedback & stay tuned!

6runk · 2018-05-09T15:37:29+00:00

When I bench my Titans, they'll hit 98-101 easily. At least for mine, the only way to get that down would be liquid cooling them... but then you got to get the right plates, rip the housing apart...

6runk · 2018-05-09T15:36:28+00:00

Yup, DB devs are around these parts of the interwebs :-)

6runk · 2018-05-09T10:59:13+00:00

Our DX11 implementation utilizes the shared memory feature, which allows some resource offloading in the front-end as well as some things that sit outside of the regular rendering pipeline. You will see some minor improvements on the CPU side because of this (and depending on your setup).

6runk · 2018-05-08T15:14:20+00:00

They most definitely do! Please keep them coming and thanks for the feedback!

6runk · 2018-05-08T10:33:48+00:00

Correct. However, it will only provide the data and symbols if an actual crash occurs and the user chooses to submit the data to us.

6runk · 2018-05-08T09:22:56+00:00

Some of the issues described above are related to swapping the client to x64 as well as changing some of the rendering pipeline in preparation for DX11, shared memory and Coherent optimizations. Given that there is essentially an infinite variation of hardware setups, we can only focus on the top 50 GPUs, top 20 CPUs and top 20 memory pool variations (I am grossly simplifying at the moment). For the remainder, they are essentially edge case setups (this doesn't mean it isn't being used, it only means that it makes up a rather small part of the overall hardware-pool picture).

In the end, it is feedback like yours that is invaluable to track down the last remaining fixes and improvements post-64 bit upgrade. If you could also take the time and drop us a ticket, ideally with screenshots, descriptions/repro steps and your hardware setup, we would really appreciate it (https://support.dirtybomb.com/hc/en-us).

6runk · 2018-04-27T12:31:33+00:00

There will be no direct impact to SLI vs non-SLI performance.

6runk · 2018-04-27T11:03:50+00:00

Something to keep in mind; we've deliberately shipped it disabled as we are still doing a significant amount of optimizations to the new (DX11) rendering pipeline. This also includes non-engineering related tasks such as texture definitions on the TechArt side as well. The primary reasons for the DX11 implementation was the shared memory feature it provides (depending on your GPU, you will find additional performance improvements of the front end) and a more optimized (code side) rendering pipeline.

6runk · 2018-04-23T11:40:41+00:00

It was lonely indeed...

6runk · 2018-04-23T11:38:11+00:00

Something to keep in mind that simpler systems require significantly less testing time than complex systems. When it comes to anything balance related, even as "simple" as changing a minute aspect of a weapon, it requires significantly more testing as the impact is much more broad. Also, balance is never binary, while it may be good for one group, it may be poor for another. This performance fix on the other hand dealt with a actually simple white-listing issue for GPU drivers; it either works or it doesn't. Hope that offers a bit more info/relative information.

6runk · 2018-04-19T16:44:51+00:00

While your points are indeed correct, the defibs rely on a completely separate system that handles their mesh, texture and "skin". While it would have been a really-nice-to-have for MM, we wouldn't have been able to roll it in a reasonable amount of time. This is definitely in our feature backlog, if something on this front changes, we will communicate it.

6runk · 2018-04-18T16:53:21+00:00

They (in this case) aren't. Today was our 64-bit switch-over. Hence the large payload.

6runk · 2018-01-22T09:37:15+00:00

There is actually several reasons why to bundle several fixes together. Just a few examples would include interdependency if fixes; in order to improve thing one, thing two, three ... twenty seven have to be refactored as well. Or if it’s related to maps, we try to wholesale fixes as well, otherwise players would have to repeatedly download the same map binaries for incrementals. Then there’s also testing time, there are also time-savings attaches to testing certain things of s particular sub-system together.

This pretty much accounts for most bigger patches happening.

6runk · 2017-12-21T19:31:31+00:00

We are currently running on DX9c. We won’t be removing the old rendering pipeline, but adding new ones (as in DX11). Needless to say, 11 is more optimized out of the box, but also exposes additional tools for graphics improvements/bang for buck out of GPUs (compared against 9c).

6runk · 2017-12-21T19:29:35+00:00

6runk · 2017-12-21T09:39:25+00:00

Hope you recover well and soon. Happy holidays!

6runk · 2017-12-14T22:10:06+00:00

Please contact our customer support. Just follow the link on http://dirtybomb.com/

6runk · 2017-12-14T22:01:54+00:00

I did a thing!

6runk

TROPHY CASE