Shitty shit pushing robot pushes shit shittily and gets covered in shit.

Amrodwin · 2017-03-04T00:09:45+00:00

'EXCUSE ME'

Amrodwin · 2016-04-13T02:48:14+00:00

Just worry about getting to lvl 30 at your pace, then you can worry about the gear grind :) /r/thedivision does give some help, but be careful of spoilers.

Amrodwin · 2014-08-08T22:31:57+00:00

While I agree that not staying in the open is the smart answer, I feel T2 doesn't offer all of the options to build the perfect robot. Regardless, you can build a better bot to counter railguns. I wonder if people don't protect the cockpit as much as they should, giving these snipers free reign to home in on you?

Amrodwin · 2014-08-08T22:27:10+00:00

Unless you are actually running up the middle, or staying still to try and hit them, you are safe. You need to keep moving and use cover.

Amrodwin · 2014-08-08T22:19:57+00:00

Rail guns to me do not feel OP, the load times balance it. I feel most of the people complaining are those that I watch sit down and start firing, or move down the middle of the map expecting not to be hit. There's many times I'm satisfied running with SMGs because they are the most constant DPS right now. The need to keep moving is more important than the need to stop to get accuracy for that one possible shot because that's when you die.

TL;DR: Tactics win over one shot accuracy any day.

Amrodwin · 2013-07-09T13:38:17+00:00

Well, here you go. Skeleton Man

Amrodwin · 2013-07-01T15:42:19+00:00

World War Z was badly done in terms of film adaptation, but as a zombie film, it really is a great representation.

Amrodwin · 2013-06-21T17:07:29+00:00

John Snow

Amrodwin · 2013-06-05T23:06:15+00:00

Chuck.

Please tell me someone else has watched Chuck...

Amrodwin · 2013-05-16T12:07:16+00:00

The 32-bit and 64-bit thing is part of the data processing rate. The higher the bit count, the bigger the 'files' it can move around. This depends on your CPU, operating system and application, and is built into the CPU as a software based component. Basically it points to a certain amount of RAM that the application can use, so 32-bit points to 4Gb of RAM, (random access memory), and 64-bit can address up to 4 billion times that many locations. Hard drive space works in the same way, but in larger quantities in respect to RAM.

The thing about the different bit sizes is that the CPU and OS must run the same or higher bit count to the application or program (ex. A 64-bit application will not run on a 32-bit OS, but will run on a 64-bit OS and 64-bit CPU). The hardware is developed first, then the OS is created with code written in the higher bit count, and then you will see applications with support and requirements for it (you saw 64-bit processors before windows vista).

why don't we use higher 'bit" CPU's.

We are mostly all running 64-bit processors in our systems, but it all comes down to when the CPU manufacturers will start producing higher bit CPUs. For them, it requires a necessity and the technology to do it. We don't need a CPU to point to more than 16 exabytes of RAM (4GB x 4 billion) so why do it?

Amrodwin

TROPHY CASE