This podcast has a little storminess to it, as it was recorded during a thunderstorm. There’s also tons of interesting news.
This week’s items include:
Let us know what you think.
Paul returns to the show to drown his sorrows in the discontinuation of a game series he loved, and the podcast ran so long it has to be split into two parts.
The first half of this podcast includes the following news items:
Stay tuned for Part 2.
As the Wrath of the Lich King beta lives on, the world (and software behind it) is ever changing. Apparently, the rune system has changed a lot since its first inception. This requires a delicate balance, as the goal is a well rounded Death Knight class without epically overpowered features. Too much power and people will feel cheated while others feel overly destructive. End result, everyone would be a Death Knight.
The rune system that Blizzard has created is more straight forward than the initial system because it contains less variables. The Death Knight has a secondary bar, much like a Warrior, that starts empty and slowly climbs with “Runic Power,” an energy generated when you cast spells and expend rune energy. It works much like the warrior class, as it builds it will open up some abilities in your bar that were “grayed out” because they couldn’t be cast yet.
What the heck is a rune? Above your character profile you’ll have six little circles, called runes, these little guys work much like the rogues energy. The three styles of runes are: Blood, Frost and Unholy runes and they’re coordinated with your spells and sword strike abilities much like a paladin or warrior. Each rune “goes dark” when you expend its energy – this limits your access to use the Death Knights abilities much like expending all your rogues energy stops the rogue from using their neat features. However, once its energy is expended, it will grow your runic power a slight bit, “charging” it for later use.
After a week off from Jonah being at PAX East 2015 and Paul being at GDC, the podcast is back, as this week’s Gaming Flashback is the landmark Guitar Hero. In addition, the podcast learns too late that Cities: Skylines runs on Windows XP. Paul also deals with goats, and the podcast is giving away a free code for Catlateral Damage.
This week’s news items include:
This week’s Question of the Week, “What is your favorite gaming snack?”
I like using keyboards for racing games that have simplified acceleration, braking, reversing, and turning such as TrackMania (four keys for all), but fighters and etc. are difficult for me via keyboards.
Mice allow for more angular granularity than controllers because of the area of movement across the mousepad/surface when using an adequate sensitivity, and mice can be polled around 1KHz or more versus controllers being polled around 250Hz, as far as I know.
If mouse sensitivity is set too high above 800 CPI or so, noise becomes an issue (quantization occurs at too low of CPI), so I recommend mice equipped with the 3360/3366 sensor as the older mice with 30×30 or less pixel/photo-diode arrays might have more trouble with noise because correlation imaging sensors will always be imperfect.
Here’s a thread regarding mice with said sensors from a reputable forum:
http://www.overclock.net/t/1602282/lets-compile-all-3360-3366-and-their-release-dates-for-everyone/0_100
The reason of 800 CPI or so being the sweet spot for current mice is, each pixel on the tracking surface or “matrix” is approximately 30 microns in diameter because of the lens magnification and sensor height from the tracking surface, so 25.4mm to convert an inch / 0.030mm = roughly 846.666 of these pixels are able to fit in an inch on the tracking surface, and the aforementioned sensors should be the same.
Each pixel is divided to achieve a higher resolution, so noise becomes an inevitable issue making a larger photo-diode array more ideal.
http://www.pcgamer.com/gaming-mouse-myths-busted/#page-1