2020年3月29日日曜日

Press Release: Robot Fight Club - KICKSTARTER LAUNCHING 10Th MARCH 2020

Robot Fight Club
A game of card-fueled customisable combat where schoolkids in a retro-futuristic setting repurpose abandoned robots and launch a thrilling new combat sport.

KICKSTARTER LAUNCHING 10th MARCH 2020
Needy Cat Games, the game design team behind titles like Hellboy: the Board Game, Blitz Bowl, Devil May Cry: the Bloody Palace and Adeptus Titanicus, is excited to announce its first solo project: Robot Fight Club! The game will be hitting Kickstarter on the 10th of March, and we are mecha excited! (Sorry.) 

The game is set in a retro-futuristic world where a group of schoolkids have snuck into an abandoned robotics academy, and started up a secret fighting league with a bunch of renovated robots. Robot Fight Club is a two-player arena combat game which offers fast-paced, action-packed gameplay that rewards strategic thinking, forward planning and a healthy dose of risk taking. 

A session of play starts with both players choosing a character and building a team of two robots, each equipped with a range of system upgrades. Each of the six robots available in the core game has its own unique set of capabilities and control cards, and with 36 upgrade cards available, no two teams will be the same! With their teams built, players take to the arena, trying to win the best of three bouts and be crowned the champion. Bouts usually last 15-20 minutes, so a full play session can be completed in around an hour. 

The action during a bout features grid movement and simultaneous action selection, with players choosing from their limited (and ever-dwindling!) Control Decks to move around the arena, bring their systems online and deal some damage to the other team. You each have two robots in the arena but can only activate one at a time, and as your deck starts running low you'll have to decide whether to Reset, sacrificing a round of play to reclaim your discarded cards. 

Damaged robots drop scrap tokens into the arena, where they can be collected by either side. They act as a currency in the game – but do you spend them on rule-bending Innovation Cards during the bout, or save them for the post-bout refit where you can buy and install new upgrades? 

There's a whole heap of gameplay in the core game, but the After School Special and Extra Credit expansions add more robots and upgrades, arena hazards, support for three and four player games, and much more. 

"Robot Fight Club is a really special project for us. First up, it's our first indie game – we're doing this for ourselves for once! More importantly it brings together a lot of things we love to see in board games: a fun setting, a bevy of interesting decisions and a bunch of robots beating the oil out of each other. What's not to love?" – James M. Hewitt, game designer

So come and join the club. Fight for thrills, fight for glory, but most of all, fight for fun – because robot fighting is awesome!

Robot Fight Club is the first game published independently by Needy Cat Games and has been designed by James M Hewitt (Hellboy: The Board Game, Devil May Cry: The Bloody Palace, Blitz Bowl, Adeptus Titanicus, Warhammer Quest: Silver Tower, Gorechosen) and Sophie Williams (Hellboy: The Board Game, The League of Infamy, Bonefields: Ancient Grudges). 

About Needy Cat Games
Needy Cat Games is a small board game design studio run by James M Hewitt and Sophie Williams, based in Nottingham, UK. They've been designing games under the Needy Cat name since 2017 but James previously worked as a game designer for Games Workshop, where he worked on a number of bestselling titles. And yes, they do have a very needy cat. His name is Helo, and he is the worst. 

Key details and links
Number of Players: 2 (Expansion pack allows for 3 and 4 player games)
Time Required: 60-90 minutes.

AP 2006, Infiltrate!

In this episode I will be looking at (and also talking about) the Apollo game Infiltrate, which is kind of like a dumbed down Elevator Action for our Atari 2600. I don't have an exact date for the next game yet, but it will be tron Deadly Discs by M Network and will come out in January. If you have any Christmas memories that you would like to submit to the 6th annual Christmas show, please send them to me by the end of the day on December 16th. Also, I will be announcing a date and time for when Sarah and I will do a livestream of all the games I covered this year. If you are feeling charitable, please consider donating to my or my friends' Extra Life campaign. You can donate until the end of the year, every little bit will help kids who are sick. Please check the links below to donate. Thank you all so much for listening!

Please donate to my Extra Life campaign!
Sean's Extra Life page
Andrew's Extra Life page
Rick's Extra Life page
Bryce's Extra Life page
Marc's Extra Life page
Infiltrate on Random Terrain
Ed Salvo interview by Scott Stilphen
Infiltrate (Blue) on Atarimania
No Swear Gamer 492 - Infiltrate 

Game 363: Ultima VII: The Black Gate

A deceptively pleasant introductory screen.
             
Ultima VII: The Black Gate
United States
ORIGIN Systems (developer and publisher)
Released in 1992 for DOS; 1994 for SNES
Forge of Virtue expansion released later in 1992 for DOS
Date Started: 20 March 2020

I first played Ultima VII in 1999. I had just purchased my first Windows laptop after 7 years of Mac-exclusive ownership, and I was ready to catch up on a decade of RPGs. I had staved off my addiction while serving in the Army Reserves, going to college, meeting my eventual wife, and starting my career, and it was best for all of those endeavors that I did. But life had settled down by then, and I was ready to take the risk.

The first two "new" RPGs that I played were Might and Magic VI and Ultima VII. ("New" being post-1990, when my Commodore 64 had died. By then, Ultima VII was 7 years old, of course, but I still think of it on the "new" side of the dividing line between "old" games and "new" games.) I had a similar reaction to each of them: initial distaste, followed by growing admiration, followed by absolute awe.
          
This may be the first CRPG with an expansion pack that takes place within the main quest.
            
But I still remember the reasons behind my initial reaction, and a few of them remain valid criticisms. I bought it as part of an Ultima anthology, so I would have played it after hitting Ultima IV-VI in quick succession. Compared to the small, crisp icons of the previous games, the Ultima VII characters seemed impossibly lanky and awkward. The creators must have taken to heart the criticisms of the tiny Ultima VI game window because they made the entire screen the game window--but then they zoomed it in so much that you still only see a tiny area.

They removed the ability to choose a character portrait, and I hated--still hate, really--the long blond-haired jerk that I'm forced to play. The guy looks like he's about 50, which doesn't bother me as much today as it did then. The typed keyword-based dialogue that I absolutely cherished had been replaced by clicking on words spoon-fed to you by the game. And then there was all the clicking! For the first time, the Ultima interface wasn't using my beloved keyboard shortcuts but instead wanted me to click around on things. I hate that now and I hated it more then, when the mouse was still new and uncomfortable.
          
I still find everything about this screen annoying.
          
Finally, there was the plot. 200 years have passed?! And all my old companions are still alive?! Who is this Red Thanos taunting me through the computer screen? And what in Lord British's name have they done to Lord British?!

This is all to say that I'm glad I'm not playing Ultima VII for the first time. This is a game that vastly benefits in a replay, at a point where I've accepted its weaknesses but also have a full understanding of its strengths. In fact, the position that I'm in right now--knowing that I'm in for a good game but not remembering much of it because I haven't played it in maybe 13 years--is just about perfect.

So let's back up and note all the things that the game does right, starting with the animated, voiced introduction, perfectly scored. The game opens on a pleasant scene of Britannia. A butterfly dances around a grassy hillside at the edge of a forest. There's a lilting tune with a timbre suggesting an organ but a melody suggesting more of a flute.
                
The first appearance of the Guardian.
           
But after a few seconds, the music fades and is replaced with an ominous, themeless tune in a low register. Black and blue static fill the screen. A red face with glowing yellow eyes and teeth like rocks pushes through the screen to address the player directly:
               
Avatar! Know that Britannia has entered into a new age of enlightenment. Know that the time has finally come for the one true Lord of Britannia to take his place at the head of his people. Under my guidance, Britannia will flourish, and all the people shall rejoice and pay homage to their new Guardian! Know that you, too, shall kneel before me, Avatar. You, too, shall soon acknowledge my authority, for I shall be your companion, your provider, and your master!
            
I would note that in contrast to the comically awful narrations at the beginning of both Ultima Underworld and Ultima VII: Part Two, the Guardian's voice is reasonably well-acted by Arthur DiBianca, who I gather was just a programmer who happened to have a nice bass voice. [Edit: I was wrong. The Guardian was voiced by a professional actor, Bill Johnson, who remained with the character for the rest of the series. He also played Leatherface in The Texas Chainsaw Massacre.] The voice immediately gives us a paradox because the Guardian looks like an ape, an orc, a monster, yet his voice is clear, his speech intelligent and articulated. Just what kind of foe are we facing? One who knows who we are, who has the ability to push through into our world.

(Incidentally, having never played Ultima VIII or Ultima IX, I still don't really know the answers to the questions about the Guardian's origin and motivations. I know it'll be tough, but I'd appreciate if no one spoils it.)
            
As the screen fades, the camera pulls back to show that the player is somehow playing Ultima VII on his computer, with a map of Britannia and a Moonstone sitting beside it. No, it doesn't make sense. Don't think about it.
          
I can't not think about it. How is my character playing Ultima VII? Does he have his own character? How far down does it go?
           
"It has been a long time since your last visit to Britannia," the title screen says, two years constituting "a long time" back in those heady days of annual releases. The character picks up his moonstone and heads out to the circle of stones in his back yard--only to find a moongate already there. Without hesitation, he plunges through to the title screen, which features not the triumphant, adventurous introductory music of most RPGs but rather a dark, dreadful march in 2/4 time. Something awful is coming, it says.
                
I'm not sure this ever gets answered.
         
Before we get into character creation and the opening moments of the game, let's diverge to the manual, which is perhaps the most brilliant game manual of all time--a superlative unlikely to ever be broken now that game manuals no longer exist. It manages to educate the player on the basics of Britannia and the past Ultima games while perfectly serving the plot of the current game. It is the only manual that I know that was written by the game's villain. I realize that's a bit of a spoiler, but you'd have to be a particularly dense player to not realize that something is at least a little fishy with "Batlin of Britain," and a veteran player of the Ultima series reads it with an escalating horror.

The manual is called The Book of Fellowship, and it describes the history, geography, and society of Britannia in the context of the growth of a quasi-religious/philosophical order called the Fellowship. Jimmy Maher has a particularly excellent article examining the parallels between the Fellowship and the Church of Scientology. (Garriott had apparently read a 1991 Time magazine exposé of the Church while the game was in its planning phase.) But I also see a lot of the (then-) growing "prosperity gospel" in the Fellowship, and Batlin strikes me as much of a Joel Osteen (although no one at ORIGIN would have been aware of him in 1992) as an L. Ron Hubbard. One particular analogue with prosperity theology (and not Scientology) is the organization's "layered" approach to scripture. The Fellowship does not reject the Eight Virtues of the Avatar any more than prosperity theology rejects the Bible. It simply adds its own new layer of interpretation (simplification) on top of them, encouraging its followers to hold true to the past without really focusing on it. The emphasis is all on the new material--in the case of the Fellowship, their Triad of Inner Strength.

The manual begins with Batlin of Britain's introduction of himself. He presents himself with false humility as just a regular man, a fellow "traveller" through life, who has happened to stumble upon a bit of wisdom that he wants to share. Throughout his biography, he brags-without-bragging that he has served in all eight of the classical Ultima roles: Born and raised by druids in Yew, a first career as a fighter in Jhelom, then as a bard in Britain; trained by a mage from Moonglow; serving for a while among a company of paladins in Trinsic and as a tinker in Minoc; and finally spending a sojourn with the rangers of Skara Brae before ending up as a humble shepherd in New Magincia. His series of portraits through these sessions show a square-jawed, hale, charismatic figure, and it's no surprise when we actually meet him in-game to find a fatter, oilier version than is presented in the official portraits.
            
What kind of pretentious jackass divides his own biography into sections called "part the first" and "part the second"?
             
During his description of overcoming some wounds in Minoc, Batlin says:
              
A healer there told me that without the proper treatments (for which he charged outrageous prices) I would most probably die! I angrily sent him away. After a time I did mend. I had learned that the healing process takes place mostly in one's mind and have since placed no trust in healers who greedily prey upon the afflicted.
               
Here is our first actual contradiction with the world as we've come to know it as an Avatar. It manages to parallel Scientology's rejection of traditional psychology, sure, but also the Christian Science rejection of traditional medicine and perhaps "New Age" medicine in general.

He describes in his history how he met his two co-founders of the Fellowship, Elizabeth and Abraham (the "E.A." being an intended swipe at Electronic Arts, which would have the last laugh by purchasing ORIGIN the same year), and how his experiences led him to develop the Triad of Inner Strength. If the casual reader is not yet convinced of Batlin's villainy, it should become apparent in the section where he discusses the "ratification" of the Fellowship by Lord British. Though calling him "wise" and paying him obsequious homage, Batlin manages to paint the king as a capricious, dismissive sovereign, uninterested in the Fellowship until Batlin managed to "prove" himself with a display of confidence that manages to reflect the Fellowship's own philosophies. The section brilliantly manages to associate Batlin with the king and the king's favor (for those who still admire the king) while also planting a seed of doubt about Lord British's fitness to rule.

What he does to the Avatar is less subtle but far more damaging. Batlin knows that if his Fellowship is going to replace the Eight Virtues as Britannia's predominant theology, and if he himself is going to replace the Avatar as the spiritual figurehead, he must undo the Avatar. But the memory of the Avatar is too popular, his friends too influential, for Batlin to use a direct attack. Thus, he snipes and undermines and saps from all angles while pretending to admire the Avatar himself. "The Fellowship fully supports the Eight Virtues of the Avatar," he says, but that "it is impossible to perfectly live up to them. Even the Avatar was unable to do so continuously and consistently." Thus pretending to support the Eight Virtues while rejecting them, he introduces the Fellowship's Triad of Inner Strength:
            
  1. Strive for Unity: Work together to achieve common goals.
  2. Trust Thy Brother: Don't live your life full of suspicion and doubt.
  3. Worthiness Precedes Reward: Do good for its own sake before expecting compensation.
 
Maher's article points out how these three principles are not only kindergarten-level theology, but how easy it is to twist them towards evil ends. "Work together, don't question, don't ask anything in return" could be the motto of a fascist organization as easily as a charitable one.

Most of the slights against the Avatar occur during the second half of the manual, ominously titled "A Reinterpretation of the History of Britannia." Batlin walks through the events of Ultima I through VI much as the previous game manuals did, but with the occasional anti-Avatar salvo disguised as support. For instance, after describing the events of Ultima II, he says:
          
While there have been speculations as to the motivations of the Avatar, there is insufficient evidence to show that the Avatar was driven to violence by jealously over Mondain's romantic involvement with Minax. That being said, such theories are hereby denounced and should not be given consideration.
           
Soon afterwards, he "formally disagrees" with "those who say the Avatar should have handled [the events of Exodus] differently." He casts aspersions--no, sorry, alludes to other people casting aspersions--on the Avatar's motives in the Quest of the Avatar. As for Ultima VI: "Those who say that this terrible and destructive war could have been prevented had the Avatar not appropriated the Codex from its true owners are merely dissidents who are grossly misinformed." Leaving aside the fact that the Avatar wasn't the one who took the Codex, Batlin commits here the slimy politician's trick of introducing a slur while simultaneously denying it, thus seeding doubt while trying to remain above it. I've learned the hard way to at least try to keep politics out of my blog, but it's literally impossible not to think of Donald ("many people are saying") Trump when reviewing this aspect of the Batlin character or indeed the Batlin character as a whole. If I didn't say it here, someone would have filled in the blank in the comments as they did in the Maher article.

Aside from the undermining of the Eight Virtues, Lord British, and the Avatar, the manual is notable for numerous asides that make the veteran player eager to jump in and start swinging his sword. In his description of his time as a fighter, Batlin talks about "unruly lords wag[ing] war against each other . . . over Lord British's objections." Clearly, peace has broken down, but why? We later hear that Skara Brae is for some reason a "desolate ruin" (remind me to come back to another Batlin quote when I actually visit Skara Brae). Lock Lake near the city of Cove has become polluted. The town of Paws is said to be languishing in poverty. Some mysterious figure called the "Sultan of Spektran" has set up his own government on the island previously occupied by Sutek. The gargoyles have their own city, called Terfin, but there's a suggestion that local mines might be exploiting them for labor. Runic writing has fallen out of favor. There have been recent droughts. And worst of all, magic has been breaking down and its practitioners going insane.

Perhaps the biggest shock is that it has been 200 years since the Avatar last visited Britannia. This is presumably since his last visit in Ultima VI, not Ultima Underworld. The manual makes no acknowledgement at all of the events of Underworld; no mention is made of a colony on the Isle of the Avatar, nor its destruction in a volcanic eruption.

Ultima IV: Quest of the Avatar still has the best quest of the series, in my opinion, but Ultima VII may have the best plot. This isn't the first time that a CRPG has featured writing and plotting worthy of a novel (I would probably give that award to Starflight), but it's still rare in the era. I understand that we owe this depth of narrative to lead writer Raymond Benson, who would later go on to take over the James Bond novel series. Benson was a playwright and composer who had previously worked on computer adaptations of Stephen King's The Mist (1985) and the James Bond games A View to a Kill (1985) and Goldfinger (1985). He was recruited by ORIGIN in 1991 and wrote some dialogue for Martian Dreams before beginning Ultima VII.

Someone like Benson was exactly what ORIGIN needed. The company may have "created worlds," but they always did so in a way that was both a little sloppy and a little too tidy, with poor respect for their own canon. I have discussed at length my disappointment over the way the game treated the concept of "the Avatar" after Ultima IV. Well, here, in the opening documentation of Ultima VII, we have an in-game character who personifies that lack of respect, who manages to take the confusion over ORIGIN's retcons--was the Avatar really the same hero who defeated Mondain?--and twist it to his own ends. When I finished the manual in 1999, I was never more eager to leap into a world and start putting things right. I am only slightly less eager now.

Note: To avoid loading transitions and other throwbacks to an earlier age, the developers of Ultima VII changed the way DOS allocates memory. Their solution required players to boot from a special disk. I remember that this created all kinds of problems when I originally tried to play the game in the late 1990s. Also, processors had gotten so much faster that the characters moved at lightning speed, and I had to use a special program called Mo'Slo to slow things down. I don't think I ever got the sound working properly back then. The emulation era and the folks at GOG sure make this much easier.

2020年3月24日火曜日

Sega CD - The Other CD Expansion


The Sega CD is treated like the unwanted step-child of the CD expansions.  Early CD systems and expansions before the PlayStation were not the breakthrough product their manufacturers hoped they would be.  They did not deliver the substantially superior gaming experiences they promised and were generally considered too expensive for what they did deliver.  And what they delivered was often unimpressive, ports of cartridge games with enhanced audio and superfluous cutscenes, FMV games which relied on route memorization, PC game ports that had no business being run on hardware that did not have a hard drive, a keyboard or a desk with which to use a mouse and interactive entertainment software which was barely interactive and not entertaining.  Today we are going to take a look at the Sega CD, its hardware, its quirks and ultimately the games that make it worth considering as a device on which to play games rather than to put on a collector's shelf.

Read more »

2020年3月21日土曜日

The Inspirations Of Oceanhorn 2: Knights Of The Lost Realm - Part 1

The best thing about being a small team of developers is that we get to come to work and exchange opinions on what games we played lately, what retro titles our colleagues should check out, and what we could learn from the design of this or that game.


By popular demand, we decided to go over some of the games we think had some influence on our work for the Oceanhorn series, and in particular on its newest chapter, Knights of the Lost Realm.

   


Our first guest is Miko, Cornfox & Bros Game Artist. "I work very closely with Heikki (Cornfox's Creative Director) to create the visual style of the game. I focus mostly on environment art, but have worked on other things as well," says Miko, "We're trying to capture the feel of the original Oceanhorn, but the transition to the new Unreal Engine physic-based rendering opened up new possibilities for the series."  




Knights of the Lost Realm sports a world inspired by quite many late-90s RPG games: in contrast to what came before, often set in a medieval world of knights and castles, here we have both technology and industrial elements seamlessly integrated into a "classic" RPG setting. Breath of Fire 3, Grandia and Alundra (all from 1997) are good examples of this style, where coal, electricity, and gritty backdrops are mixed with classic RPG stuff.






"The world of Oceanhorn 2 is not completely industrialized, and in most areas it doesn't go as far as many of the environments do in FFVII, for example." continues Miko, "We are big fans of this classic though, and one can most likely see the influence Midgar had had on Arcadia's capital, the White City. Like Midgar, it has a circular design and you can see gigantic pipes rising over the walls of the city, but unlike Midgar it's not a dystopia. The White City is a beautiful and bright place, where the sun is always shining. In a way, we try to bring the scale of things to a level similar to what you see in FFVII: even if we use a different aesthetic approach, you feel like you could easily just walk on the pipes."



The more advanced technology in Oceanhorn 2 quite often have rounder and smoother shapes, much like some of the vehicles found in Akira Toriyama's work. The Yellow Bird, Trin's airship, is the perfect example of this rounder design. The most advanced Arcadian tech takes this up a notch, featuring an even sleeker and aggressive design, inspired by modern sports cars or jet planes.


"And then we have the Living Fortresses," says Miko, "compared to the original Oceanhorn, we had a bit more technical freedom with the art, so we tried to make them look even more sophisticated and dynamic. If the Living Fortress in the first title was our version of the Metal Gear Rex, the Living Fortresses in Oceanhorn 2 are an evolution on that, Cornfox's Metal Gear Rays."


If you want to know more about the games and styles that inspired us during the development of Knights of the Lost Realm, stay tuned for Part 2!

2020年3月20日金曜日

Weekend Gaming Update 4/22/2019

   Friday night watched a great episode of Dragons and Things on Twitch while I painted minis. I don't think I have mentioned Dragons and Things here, which is a shame. It's a live play stream of a bunch of crazy people playing Pathfinder. It's a lot of fun, and they interact a lot with the viewers, which is what drew me to it so much in the first place. Anyway, from 6:00-10:00 Pacific that's what I am usually doing (which is 8 to midnight for me).

   Played a game of Infinity with my buddy Zach and his son. Went to a local-ish game store to play, Montag's Games. I ought to do a Store Report on them, but I may have already. They've just moved into a new space, though, so it may be time for an update.




   I finished the following minis over the weekend:

Reaper Bones Mechanical Monkeys
These are destined to serve Otto Maton if he ever reappears...

 Reaper Bones village woman with her rugrats.

 Frostgrave Soldiers (Archer and Infantryman)
These are painted for the witch, specifically, but could be used for anyone really

More Frostgrave Soldiers (Tracker and Man-at-Arms)
More Frostgrave terrain


Closer up


So, knocking a few things out. Which is good, considering what's on the way soon...

Battlefield V - Review | Pro-GamersArena




Battlefield V - Review:

Battlefield V's (It's not Battlefield Vietnam which was released back in 2004) road to release hasn't actually been smooth, nor typical of an EA product. And to be honest, I didn't expected going in that playing Battlefield V's multiplayer would feel so much amazing and satisfying as Battlefield V doesn't feel like a complete experience at the launch. Battlefield V creates the impression that there's a sizeable number of modes and significant bug fixes still to be delivered. In this article, you're gonna hear from us about the Battlefield V Review. 


Quick Facts:

  • Initial release date: 15 November 2018
  • First released: 20 November 2018
  • Engine: Frostbite
  • Platforms: PlayStation 4, Xbox One, Microsoft Windows


Straight away, it worth focusing on that while Battlefield V is set during WWII, it doesn't feel outdated. Mechanically speaking, it's the absolute best-feeling Battlefield in quite a while. These short stories plan to tell the stories behind the soldiers that battled in the two world wars, with Battlefield V's selection highlighting some of the more dark records of World War 2. The three being referred to bring a profound jump into the British Special Boat Section, the Norwegian resistance during the German occupation, and the efforts of black West African soldiers in their offer to overthrow the Nazi reign in France. Additionally: for better and for more worse, the game doesn't retread familiar. ground. It spins around the period's lesser-known stories and settings, which can be at the same time reviving and a bit of disappointing, particularly for 1942 fans.



Over the majority of its current multiplayer modes, Battlefield V's default mechanics step toward the hardcore. Health recovery is limited, The time to execute is reduced, and the spotting system is almost entirely removed. And keeping in mind that a portion of these changes feel like a Band-Aid being ripped off, Battlefield V is a superior shooter as a result of them. All things considered, the revisions are more thoughtful than essentially adopting the majority of the hardcore rules. And, in lieu of the whole removal of 3D spotting, just a bunch of gadgets and certain battle characteristics would now be able to put that infamous red circle over enemies heads. This change will help you remain connected with Battlefield V's stunning surroundings instead of playing the HUD. In nutshell, these changes aim to underscore teamplay, fulfilling gunplay, and immersion and every one of them find their marks.

Here's an amazing gameplay by TheRadBrad.





Also Read: Overkill's The Walking Dead - Review 


Most important of all, the gun handling is fluid. Combat feels misleadingly easy, yet it's sufficiently layered to liberally reward skillful play, thoughtful strategies, or more all, teamwork. The maps are generally magnificent and advance shifted playstyles, from the flowing fields of Arras - a moment classic - to the omnipresent, all-knowing bridge of Twisted Steel. Wonderfully, every character class is impactful and enjoyable.

The incentives for coordinating with your four-person squad are borderline coercive. Lost health no longer again recovers past a specific point without a medkit, and ammo reserves are less abundant - most weapons are sustained by just two additional magazines to begin, making a Support partner an exceptionally welcome ally.


But there are many flaws which can't be neglected and need to be fixed as soon as possible like, at launch, Battlefield V was suffering from an unusually high amount of bugs and glitches which can possibly ruin a match. We've read reports of much further issues, but we ourselves have suffered with animation glitches that make pointing from turrets an impossibility, and the act of your weapon isolating from your character meaning you can't aim properly because the butt of your rifle is in your face as opposed to the iron sights. In addition, geometry in some cases neglects to stack in, leaving a church's bell tower suspended in mid-air, while trees and rocks don't show up properly, making them look like pixelated messes. The wonderful finish, however, was the point at which the 'Return to combat area' warning inaccurately showed up on our screen, which means we were killed following eight seconds for absolutely no reason. All of these issues is in all likelihood a basic fix via a patch, but they start to add up after occurring consecutively match after match to make an experience that you can't completely depend on to be reasonable nor stable.

An amazing video showing some funny glitches in Battlefield V by IGN.









Also Read: Cyberpunk 2077 | Release date, trailer, gameplay, news and more.



Battlefield V: Maps And Modes

Battlefield V offers eight maps at launch, and I felt all the maps to be quite enjoyable. Fjell 652 happens on a high-altitude Norwegian mountain overlooking the total of the Norvik map and is liable to exceptional and atmospheric snowstorms. Twisted Steel is built around a huge bridge that serves in as both a fabulous milestone and a functional mechanism to add a straight path to the map's familiar open environment speckled with rural villages.



And coming to modes, Shorter game modes, for example, Team Deathmatch, Domination, and Frontlines make up the numbers to give a multiplayer experience that will feel exceptionally familiar to returning players. Instead of update any of its online mechanics, Battlefield V refines and makes minor enhancements to the chaotic and tremendous battlegrounds it is known for. Despite everything you'll have those great Battlefield moments as you hold out against axis forces while your ticket counter drops to an alarming number, explode a rooftop to cut the rubble down onto your opponents, or you swoop in from the air and take out a target from a plane's gunner seat. There's no enormous disclosure to reveal, rather a stunningly better Battlefield experience to find.




Battlefield V: Company Coins?

Perhaps Battlefield V's greatest takeoff from what it's known for comes as its customization and cosmetic capabilities. Your Company enables you to kit out the four classes of assault, medic, support, and recon to your correct taste, with class particular weapons for each and a preposterous measure of customization to whack to finish everything. Specializations enable you to affect the stats of a weapon, choosing four of eight unique upgrades to better your odds of survival. And in addition that, you can give it an extension and add decals in five distinct territories, and after that, each weapon has its very own level progression to work through. And afterward, there's your soldier themselves, who can be kitted out with various headgear, outfits, and face paint to truly make them look like it. It's an astronomical measure of customisation, and it's everything fuelled by the in-game currency named Company Coins. 


Earned by leveling up and finishing day by day orders, the money can be spent on cosmetic items for either your solider or skins for your weapons. This extends the visual abilities beyond basic unlocks via progression and enables you to pick what you need when you need it. There is no real way to buy Company Coins by means of microtransactions, however, EA has expressed that a different paid currency will be introduced at a later date.


Also Read: Days Gone | PS4 Release date, Gameplay



The Verdict:

Battlefield V is going to be an extraordinary game, of that we're certain, but because of various glaring omissions at launch and one an excessive number of glitches, the final product isn't there just yet. The good news is that fixes are already taking off, and with a year or a greater amount of free maps and modes on the way, Battlefield V can just show signs of improvement from here. 









Going Your Own Route

"Leave me alone and let me go to hell by my own route." 
– "Calamity" Jane Cannary, shortly before her death in Deadwood, South Dakota, in 1903. 
I love open world adventure games like Runebound, Fortune and Glory, and the mother of them all, Talisman. I also love the historical western genre, and have often found myself wishing, "if only there were a wild west version of Talisman..."

Well, now there is. Western Legends took Kickstarter by storm last year, billing itself as a wild west sandbox board game, and for the most part it delivers on that promise.

Players take on the roles of legendary historical figures such as Doc Holliday, Calamity Jane, Billy the Kid, or even lesser known characters like Bass Reeves or Y. B. Rowdy (this game does a better job than most at equal representation, with nearly half of the playable characters being women or people of color). The object of the game is to roam the countryside earning "Legendary Points" towards a goal determined by the length of game the players decide on at the start.

Players can earn points by prospecting for gold or herding cattle, but the real meat of the game is in the decision to either follow a path of law and order as a Marshal, or become a Wanted outlaw. Marshals spend the game tracking down non-player bandits as well as players who have gone renegade, facing off in combat via a clever poker-based game mechanic. Outlaws can choose to rob the bank, steal cattle, but have to watch out for player Marshals as well as a non-player Sheriff, because getting caught will force them to pay a hefty fine and set them back to the start of the outlaw track. Players can even switch careers midway through the game -- you aren't locked into a single course of action and can switch gears as needed.

The problem with a lot of open world games is that it's often difficult for players to figure out what they should be doing. Western Legends deals with this through several goal-oriented game mechanics. First of all, each player character comes with a set of goal cards outlining fairly simple tasks to perform such as winning fights or rustling cattle. There is also a story deck, which rewards players who achieve certain goals with bonus points or equipment as well as a bit of back story.

If I have any problem with Western Legends it's that it doesn't really shine at lower player counts. Playing the game with two requires the use of a third character, the Man in Black, whose actions are determined by a random set of cards. It works, but the game is a lot more fun with a full table of 4-5 players so Marshals have plenty of outlaws to chase, and outlaws have plenty of other outlaws to distract the Marshal...

Rating: 5 (out of 5) a terrific game that does exactly what it set out to do, which is to provide open-ended board game adventures in the wild west.

2020年3月16日月曜日

Not So Lucky!

What's going on everyone!?


Today was spent running errands and preparing for our big move to our new place so by the time we got home this evening, everyone was ready for bed. 


That being the case, I decided to play a solo game of Carcassonne on the mobile app for the #2019gameaday challenge. 

Tonight I got my butt kicked by the Ai which surprised me because I thought I was actually doing good, lol!

As always, thank you for reading and don't forget to stop and smell the meeples! :)

-Tim

2020年3月6日金曜日

Tech Book Face Off: Programming Massively Parallel Processors Vs. Professional CUDA C Programming

After getting an introduction to GPU programming with CUDA by Example, I wanted to dig in deeper and get to know the real ins and outs of CUDA programming. That desire quickly lead to the selection of books for this Tech Book Face Off. The first book is definitely geared to be a college textbook, and as I spent years learning from books like this, I felt comfortable taking a look at Programming Massively Parallel Processors: A Hands-on Approach by David B. Kirk and Wen-mei W. Hwu. The second book is targeted more at the working professional, as the title suggests: Professional CUDA C Programming by John Cheng, Max Grossman, and Ty McKercher. I was surprised by both books, and not in the same way. Let's see how they do at teaching CUDA programming.

Programming Massively Parallel Multiprocessors front coverVS.Professional CUDA C Programming front cover

Programming Massively Parallel Processors

The polite way to critique this book is to say, it's somewhat verbose and repetitive, but if you can get past that, it has a lot to offer in the way of example CUDA programs that show how to optimize code for the GPU architecture. A slightly less polite way to say that would be that while this book does offer some good code examples, the writing leaves much to be desired, and much better books are out there that cover the same material. The honest assessment is that this book is just a mess. Half the book could be cut and the other half rewritten to better explain things with clearer, non-circular definitions. The only good thing about the book is the code examples, and many of those examples are also redundant, filling the pages of the book with lines of code that the reader has seen multiple times before. This book could have been a third the length and covered the same amount of material.

Even though that last bit was a pretty harsh review, we should still explore what's in the book, if only to see how the breadth of material compares to Professional CUDA C Programming. The first chapter is the normal introduction to the book's material, describing the architecture of a GPU and discussing how parallel programming with this architecture is so different than programming on a CPU. The verbosity of this chapter alone should have been a clue that this book would drag on and on, but I was willing to give it a chance. The next chapter introduces our first real CUDA program with a vector addition kernel. We're still getting started with CUDA C at this point, so I chalk up the authors' overly detailed explanations to taking extra care with novice readers. We end up walking through all of the parts of a working CUDA program, explaining everything in excruciating detail.

The third chapter covers how to work more efficiently with threads and loading data into GPU memory from the CPU with a more complex example of calculating image blur. We also get our first exposure to thread synchronization, something that must be thoroughly understood to program GPUs effectively. This chapter is also where I start to realize how nutty some of the explanations are getting. Here's just one example of them describing how arrays are laid out in memory:
A two-dimensional array can be linearized in at least two ways. One way is to place all elements of the same row into consecutive locations. The rows are then placed one after another into the memory space. This arrangement, called row-major layout, is depicted in Fig. 3.3. To improve readability, we will use Mj,i to denote the M element at the jth row and the ith column. Pj,i is equivalent to the C expression M[j][i] but is slightly more readable. Fig. 3.3 illustrates how a 4×4 matrix M is linearized into a 16-element one-dimensional array, with all elements of row 0 first, followed by the four elements of row 1, and so on. Therefore, the one-dimensional equivalent index for M in row j and column i is j*4 +i. The j*4 term skips all elements of the rows before row j. The i term then selects the right element within the section for row j. The one-dimensional index for M2,1 is 2*4 +1 =9, as shown in Fig. 3.3, where M9 is the one-dimensional equivalent to M2,1. This process shows the way C compilers linearize two-dimensional arrays.
Wow. I'm not sure how a reader that needs this level of detail for understanding how a matrix is arranged in memory is going to understand the memory hierarchy and synchronization issues of GPU programming. This explanation is just too much for a book like this. Readers should already have some knowledge of standard C programming, including multi-dimensional array memory layout, before attempting CUDA programming. I can't imagine learning both at the same time going very well. As for readers who already know how all of this stuff works, they could easily skip every other paragraph and skim the rest to make trudging through these explanations more tolerable.

The next chapter is on how to manage memory and arrange data access to optimize memory usage and bandwidth. We find that memory management is just as, if not more important than thread management for making optimal use of the GPU computing resources, and the book solidifies this understanding through an extended optimization example of a matrix multiplication kernel.

At this point we've learned the fundamentals of GPU programming, so the next chapter moves into more advanced topics in performance optimization with the memory hierarchy and the compute core architecture. Then, chapter six covers number format considerations between integers and single- and double-precision floating point representations. The authors' definition of representable numbers struck me as exceptionally cringe-worthy here:
The representable numbers of a representation format are the numbers that can be exactly represented in the format.
This is but one example of their impenetrable and useless definitions. More often than not, I found that if I hadn't already known what they were talking about, their discussions would provide no further illumination.

Now we get into the halfway decent part of the book, the extended example chapters on parallel patterns. Each of these chapters works through a different example kernel of a particular problem that comes up often in parallel programming, and they introduce additional features of GPU programming that can assist in solving these problems in a more optimal way. The contents of these chapters are as follows:
  • Chapter 7: Convolution
  • Chapter 8: Prefix Sum (Accumulator)
  • Chapter 9: Parallel Histogram Calculation
  • Chapter 10: Sparse Matrix Computation
  • Chapter 11: Merge Sort
  • Chapter 12: Graph Search
As long as you skim the descriptions of the problems and solutions, and focus on understanding the code yourself, these chapters are quite useful examples of how to write performant parallel programs with CUDA. However, the authors continue to suffer from what seems to be a mis-interpretation of the phrase, "a picture is worth a thousand words." For every diagram they use, they also include a thousand words or more of explanation, describing the diagrams ad nauseam. 

The next chapter covers how to kick off kernels from within other kernels in order to enable dynamic parallelism. Up until this point, all kernels have been launched from the host (CPU) code, but it is possible to have kernels launch other kernels to take advantage of additional parallelism while the code is executing on the GPU, an effective feature for some algorithms. Then, the next three chapters are fairly useful application case studies. Like the parallel pattern example chapters, these chapters use CUDA code to show how to take advantage of more advanced features of the GPU, and how to put together everything we've learned so far to optimize some example parallel programs. The applications described are for non-Cartesian MRI, molecular visualization and analysis, and machine learning neural networks, so nice, interesting topics for GPU programming.

The last five chapters were either more drudgery or topics I wasn't interested in, so I skipped them and called it quits for this long and tedious book. For completeness, those chapters are on how to think when parallel programming (so a pep talk on what to think about from authors that couldn't clearly describe much else in the book), multi-GPU programming, OpenACC (another GPU programming framework, like CUDA), still more performance considerations, and a summary chapter. 

I couldn't bring myself to keep reading chapters that wouldn't amount to anything, so I put down the book after finishing the last chapter on application case studies. I found that chapters seven through sixteen contained most of the useful information in the book, but the introduction to CUDA programming was too verbose and confusing. There are much better books out there for learning that part of CUDA programming. Case in point: CUDA by Example or the next book in this review.

Professional CUDA C Programming

Unlike the last book, I was surprised by how readable this book was. The authors did an excellent job of presenting concepts in CUDA programming in a clear, direct, and succinct manner. They also did this without resorting to humor, which can sometimes work if the author is an excellent writer, but it often feels forced and lame when done poorly. It's better to stick to clear descriptions and tight writing, as these authors did quite well. I was actually disappointed that I didn't read this book first, instead saving it until last, because it did the best job of explaining all of the CUDA programming concepts while covering essentially the same material as Programming Massively Parallel Processors and certainly more than CUDA by Example

The first chapter is the obligatory introduction to CUDA with the requisite Hello, World program showing how to run code on the GPU. Right away, we can see how well-written the descriptions are with this discussion of how parallel programming is different than sequential programming:

When implementing a sequential algorithm, you may not need to understand the details of the computer architecture to write a correct program. However, when implementing algorithms for multicore machines, it is much more important for programmers to be aware of the characteristics of the underlying computer architecture. Writing both correct and efficient parallel programs requires a fundamental knowledge of multicore architectures.
We need to be prepared to think differently about problems when parallel programming, and we're going to have to learn the architecture of the underlying hardware to make full use of it. That leads us right into chapter 2, where we learn about the CUDA programming model and how to organize threads on the device, but it doesn't end there. Throughout the book we're learning more and more about the nVidia GPU architecture (specifically the older Fermi and Kepler architectures, since those were available at the time of the book's writing) in order to take full advantage of its compute power. I like how the authors grounded their discussions in specific GPU architectures and showed how the architecture was evolving from one generation to the next. I'm sure the newer Pascal, Volta, and Turing architectures provide more advanced and flexible features, but the book builds a great foundation. Chapter 2 also contains the clearest definition of a kernel that I've seen, yet:
A kernel function is the code to be executed on the device side. In a kernel function, you define the computation for a single thread, and the data access for that thread. When the kernel is called, many different CUDA threads perform the same computation in parallel.
This explanation is the essence of the paradigm shift from sequential to parallel programming, and it's important to understand the effect it has on the code that you write and how it runs on the hardware. In addition to the excellent writing, each chapter has some nice exercises at the end. That's not normally something you find in programming books like this. Exercises seem to be left to textbooks, like Programming Massively Parallel Processors, which had them as well, but in Professional CUDA C Programming they're more well-conceived and more relevant.

The next chapter covers the CUDA execution model, or how the code runs on the real hardware. Here is where we learn how to optimize CUDA programs to take advantage of all of those independent compute cores on the GPU, and this chapter even gets into dynamic parallelism earlier in the book rather than waiting and treating it as a special topic like the last book did.

Chapter 4 covers global memory and chapter 5 looks at shared and constant memory. Understanding the trade-offs of each of these memories is important to getting the maximum performance out of the GPU because most often these programs are memory-bound, not compute-bound. Like everything else, the authors do an excellent job explaining the memory hierarchy and how those trade-offs affect CUDA programs. The examples used throughout the book are simple so that the reader doesn't get bogged down trying to understand unrelated algorithm details. The more complex examples may be thought-provoking, but simple examples do a good job of showcasing the specifics of the topic at hand.

Chapter 6 addresses streams and events, which are used to overlap computation with data transfer. Using streams can partially, or in some cases completely hide the time it takes to get the data into the GPU memory. Chapter 7 explains more optimization techniques by using CUDA instruction-level primitives to directly control how computations are performed on the GPU. These instructions trade some accuracy for speed, and they should be used only if the accuracy is not critical to the application. The authors do a good job of explaining all of the implications here.

The last three chapters weren't as interesting to me, not because I was tired of the book this time, but because they were about the same topics that I skipped in the other CUDA books: OpenACC, multi-GPU programming, and the CUDA development process. The rest of the book was excellent, and far better than the other two CUDA books I read. The writing is clear with plenty of diagrams for better understanding of each topic, and the book organization is done well. If you're interested in GPU programming and want to read one book, this one is it.


Between these two CUDA books, the choice is obvious. Programming Massively Parallel Processors was a bloated dud. It may be worth it just for the large set of example programs it contains, but there are other options coming down the pipeline for that kind of cookbook that may be better. Professional CUDA C Programming was better in every way, and really the book to get for learning CUDA programming. The authors did a great job of explaining complex topics in GPU architecture with concise, understandable writing, relevant diagrams, and appropriate exercises for practice. It's exactly the kind of book I want for learning a new programming language, or in this case, programming paradigm. If you're at all interested in CUDA programming, it's worth checking out.