The Division 2

It's a CPU problem with the engine. A lot of people are experiencing it. I had no problems running the alpha or private beta, but when I started playing the OB I was having stuttering and 2-3 second freezes. Changing graphic settings does nothing, but I did manage to make the game mostly playable with a fresh install. My PC is getting old and have an I5 2300 and a 1050ti. Div 1 runs smooth as silk on med/high settings, but while also hammering my cpu I don't have any performance issues.

It has to be just shitty code. I don't get why a game that is basically a single player shooter should need so much cpu juice.

I had been staying away from all of the beta play in an effort to keep this as new as possible. That said, I did play the open beta up through the first mission just to get a feel for it a little bit. I enjoyed it as I expected as I am really a pve type for the most part. The only issues that really bothered me were the hard coded keybinds that you could not change in the menus and the fact that it was so bloody difficult to tell which armor item you were wearing.

For the first issue, I use ESDF for my movement, but even in the tutorial section, you had to select an inventory item and hit F to do something (I forget what exactly), but hitting my F key just moved the selection to the next item in my inventory forcing me to click and hold the mouse button to manually select something. It is very minor but over time it could really get annoying. The inventory issue again was minor but still bugged me. The weapons had the #1 and #2 beside them so was easy to differentiate between equipped items and just inventory. In Div 1 it highlighted your chest armor so you knew which one was being worn. Now you have to look at the tiny equip icon at the bottom of the screen to see if it is grayed out or not.

Other than those 2 annoyances, I liked what I saw and it should be fun. Spring break is next week, so will probably be playing a good bit as it is nice timing on release. Again.. apostolos223 if anyone will be playing on pc.

It all depends on what is eating those CPU cycles. Open task manager, click on CPU, that should tell you what is eating up all the CPU cycles. If it's the game? Then, I agree. It's the game.

I've seen a lot of instances of windows where it's some networking thing. Another reason I've gotten rid of that piece of trash thing called M$.

After I stopped using DX12, the crash issue went away for me. So it was silky smooth for the most part. I then started streaming at 1080x60fps to see how stable it ran, and it ran perfectly. Checked OBS and zero dropped frames. Then I checked the playback on that VOD and it's choppy as fuck. Le sigh.

Non WASD unite.

I use "ASDF" for my movement and it is annoying that even when you are running forward by holding F that it triggers the mission pop up and stops you dead in your tracks. I don't recall off hand, but I could swear you I had to retap F in Div 1 to make the same thing happen.

Well think about it, you have to purposely move your hands OFF the keys you usually use for typing in order to use wasd for movement. Why not just leave them there so you don't have to move your hand back and forth when trying to type something in chat? In addition, it puts even MORE keys in reach for hotkeys by not moving your hand closer to the edge of the keyboard.

Besides, hard coded key binds on a PC game is a big development failure no matter how you look at it imho. That shit is pc game development 101

*steps off his soap box*

Bandwagon said:

Put another 2 hours into this last night. Next to zero interest in it now. Just feels boring to me, but I'll try watching some streams a few weeks after it comes out.

Click to expand...

You are not alone. Just was boring, and that's after putting another 6 hours into it during Open Beta. I'm really glad that they have these betas though so I can get in there and see if it's a game that hooks me in or not.

With this one, I had no desire to keep grinding. I didn't feel more powerful while getting newer guns, or levels, because stuff just scales. In the end, I felt there wasn't a point to what I was doing.

goishen said:

It all depends on what is eating those CPU cycles. Open task manager, click on CPU, that should tell you what is eating up all the CPU cycles. If it's the game? Then, I agree. It's the game.

I've seen a lot of instances of windows where it's some networking thing. Another reason I've gotten rid of that piece of trash thing called M$.

Click to expand...

if I hadn't done this why the hell would I say it was the game? Try doing a google search for "division 100% CPU" you'll get results for Div 1 and 2. This wasn't a guess it's a known issue.

Anything other than ESDF does not compute. WASD means you're either not resting on home row or you're using your pinky for movement which is even worse. And with ESDF your primary 'action' key becomes A and you have a finger hovering over it all the time, no need to move one off of the movement keys to hit it.


MarcoStyle did some testing on mod effects in the beta. Normally I take his videos with a large grain of salt because they are vastly skewed towards PVP performance, but in this case his findings are pretty much the same as my own (though I didn't bother testing anything but ARs, LMGs, and MMRs). Stability having no effect on SMGs is a bit of surprise though. SMGs sucked anyway though, can't see myself ever using one unless ballistic shield turns out to be a top-tier skill choice.

Edit: One issue I did have with the video is that he used a FAL as his AR, when the CTAR, P416, and Police M4 are best in class by a large margin. They shoot like a laser with an easily controllable recoil even on console, so I'm not convinced stability has much point there either.

Video:

Or image version if you can't be arsed watching a 17.5m video about something that can be easily summed up in a chart: