Several regions available to players in upcoming monster-catcher Nexomon: Extinction have been unveiled, giving potential players a good look at some of the areas and monsters they’ll find on their journeys.

Each area in the game is said to be home to different creatures, challenges, and stories. We’ve already seen the nine starter monsters that players will be able to choose from, but let’s take a closer look at these regions, shall we?

New Ignitia, Fire Region

Descend into New Ignitia – an underground volcanic city, built at the bottom of a deep chasm. The entrance to it is in a fiery region abundant in fire-type Nexomon, somewhere in the vast Solus desert.
The city itself is prone to attacks from powerful Tyrant Nexomon and recently Guild Tamers from Ignitia have been reported missing. Well-known for its quality pickaxes, making the long trip may well be worth it to pick up a new axe and help you mine elemental shards.

A Nexomon you might encounter here: Nekpanchi

Their puffy paws are actually deadly weapons, and with its natural instinct to fight, Nekpanchi can quickly harden them like iron to bash their foes.
Rarity: Mega Rare
Signature Attack: Fire Claw
Evolution: > Nekgiri > Felclaw

Solus, Desert Region

Tread lightly, there are many dangers in the Solus Desert. Tamers who do venture through this region will discover that it is rich in gemstones to mine and Mineral-Type Nexomon to capture. Travel past strange ruins, the skeletons of long-dead Tyrant Nexomon and avoid the attention of rutheless bandits as you head east to locate the desert fortress of Lateria.

A Nexomon you might encounter here: Rust

Rust uses its steel helmet both for defense and offense.
Rarity: Uncommon
Signature Attack: Headbutt
Evolution: > Rustu > Rustung

Frozen Tundra, Ice Region

While many think it is a lost cause, the Guild still maintains an outpost in the Frozen Tundra to hold back Tyrant Nexomon in the region. Home to powerful water-type Nexomon, many of whom can inflict the frozen status effect, the Tundra is unforgiving and only experienced tamers are permitted to travel there.

Those who do take on the icy climb will discover the deep ice caves, home to even more water-type Nexomon to catch and elemental shards to mine. To the very north of the region lies a cursed tower, which of late has been attracting even more wild Nexomon to the area.

A Nexomon you might encounter here: Cruff

Cruffs are naughty water Nexomon and very skillful at stealing items. When tamed they are very loyal and noble.
Rarity: Rare
Signature Attack: Water Blast
Evolution: > Croncho > Domigator

The similarities to Pokémon couldn’t be more obvious, which will no doubt put some fans of the genre off and intrigue others in equal measure. It’s launching on Switch later this year, so we’ll see how well it performs then.

In the meantime, feel free to share your thoughts on Nexomon: Extinction in the comments below. Can you see yourself giving this a go?

Update (Thu 16th Jul, 2020 19:00 BST): Today sees the launch of action-arcade puzzler Radical Rabbit Stew on Nintendo Switch. A new launch trailer has been released to celebrate (see above) and those who download the game during its first week on the Switch eShop will receive a 10% launch discount, taking the usual price of £12.99 down to £11.69.

Get your super spoons ready and whack those crazy rabbits into saucepans to free the space chefs – but think fast or the bunnies will attack!

Featuring bite-sized pick-up-and-play action, fast-paced whack-a-rabbit gameplay, scintillating puzzles, super-sized boss fights, juicy pixel graphics and a sizzling soundtrack, Radical Rabbit Stew is a hare-raising action-arcade puzzle game perfect for new players and 16-bit retro fans alike.

Original Article (Mon 25th Mar, 2019 14:00 GMT): Publisher Sold Out has today announced a partnership with Pugstorm which will see action-arcade game, Radical Rabbit Stew, launch on Switch and other platforms next year.

With its 2020 release date obviously a little while away, we’re told that more details will be shared later this year, but we do have a quick description and a collection of screenshots for you to check out below.

Make rabbit stew! In space!! Grab your trusty spoon and prod those crazy rabbits into saucepans to free the space chefs. But think fast or the bunnies will gobble you up! With bite-size ‘pick-up & play’ action, award-winning puzzles, juicy pixel graphics and a delicious soundtrack, Radical Rabbit Stew is a hare raising action-arcade game perfect for new players and 16-bit retro fans alike.

An early demo of the Switch version is set to be playable at PAX East this week, alongside Sold Out’s Nintendogs-like release, Little Friends: Dogs & Cats. Katie Clark, Product Manager at Sold Out, has shared the following in a press release:

“We’re so excited to be working with Pugstorm on Radical Rabbit Stew and were thrilled to see such a huge response to the announcement that we would be bringing Little Friends: Dogs & Cats to the west. We can’t wait for fans to go hands-on with both games at PAX East in the coming weeks!”

Will you be keeping an eye out for more news on this one going forward? Let us know in the comments below.

numpy.char.capitalize(a)

Original Documentation

Return a copy of a with only the first character of each element capitalized.

Calls str.capitalize element-wise.

For 8-bit strings, this method is locale-dependent.

Parameters:

• a: array_like of str or unicode: Input array of strings to capitalize.

Returns:

• out ndarray: Output array of str or unicode, depending on input types

See also

str.capitalize

Examples

Epic Games have just released a new set of tools aimed at making the lives of Blender users easier when working with Unreal Engine.  The tools consist of two projects, Send to Unreal and UE to Rigify.  Both are available on the Epic Games Github page, although you need to link your GitHub to your Epic account before it will work, instructions are available here.

Send to Unreal is a set of tools enabling you to easy export from Blender completely rigged, textured and animated meshes with a single menu selection.  Send To Unreal documentation is available here.

UE to Rigify goes in the other direction and enables you to import Unreal Engine rigs into Blender and make them compatible with Rigify (which needs to be enabled separately).  UE to Rigidy documentation is available here.

You can see the new Blender Tools in action, including a step by step tutorial on using Send To Unreal, in the video below.  It should be noted that you need to configure Blender to use Unreal Engine 0.01 scale, which I personally found extremely buggy in the current release.  Details on scene scale are available here, however at time of writing following these instructions caused Blender to crash every time I copied an armature into the Rig folder.  There is a good chance I did this part incorrectly in the tutorial, but it’s the only way I found to successfully export while not crashing Blender!

[embedded content]

Art GameDev News Blender Unreal

<!–

–>

Daniel

With the release of Visual Studio 2019 16.7 Preview 4, you can now try out our new experimental Razor editor for local development with MVC, Razor Pages, and Blazor. We’re excited for you to give it a try!

Enabling the new Razor editor

To enable the new experimental Razor editor in Visual Studio 2019 16.7 Preview 4 or later:

1. Install the latest Visual Studio preview

2. Go to Tools > Options > Environment > Preview Features and select the Enable experimental Razor editor option:

   

3. Select OK and restart Visual Studio

That’s it! You’re now setup to use the new Razor editor when working with Razor files locally (.cshtml and .razor).

What is Razor?

Razor is a templating language based on HTML and C# used to define dynamic rendering logic for .NET web apps based on MVC, Razor Pages, and Blazor. In MVC and Razor Pages apps you use Razor to define the rendering logic for your views and pages using .cshtml files. In Blazor, you use Razor to author reusable UI components in .razor files. Razor is a critical part of the experience for building web apps with .NET.

You can give Razor a try today by building your first web app with ASP.NET Core or Blazor.

Why a new Razor editor?

Part of the value of Razor is the rich tooling experience Visual Studio provides for editing Razor files. Visual Studio today provides IntelliSense, completions, and diagnostics for HTML, CSS, JavaScript, C#, and Razor specific syntax all within the same Razor file.

Visual Studio does some tricky gymnastics to enable editor support for all of these languages at the same time in Razor files. The Razor document is parsed to determine its constituent parts, and then each part is projected into a language specific buffer called a projection buffer. What you see in Visual Studio when editing a Razor document are a collection of little windows into each of these projection buffers to make up one whole document. Each language service then independently handles the editing experiences for each of these separate projection buffers.

For example, consider the following Razor code:

@{ ViewData["Title"] = "About";

}

<script type="text/javascript"> alert("Hello, World!");

</script>

The way Visual Studio handles this Razor code looks something like this:

This project buffer setup works well for Visual Studio and Visual Studio for Mac, but it’s problematic for remote editing scenarios, like Visual Studio LiveShare or Visual Studio Codespaces. It also can’t be used for editors that don’t have projection buffer support, like Visual Studio Code. The lack of a central orchestrator for the Razor editor also makes it difficult to enable new features without careful coordination between the various language service implementations (since they each control their own experience in projected scenarios).

A Razor Language Server

To enable broader support for Razor editing, we have been working for some time on a new Razor editor for ASP.NET Core projects based on a Razor Language Server. This new Razor Language Server implements editor features like auto completion, go to definition, etc. through the Language Server Protocol (LSP), which defines a standard way for an editor or IDE to enable these features. An IDE specific Razor extension then handles coordinating with the Razor Language Server and the other language servers for HTML & C#.

This new Razor Language Server is already being used to enable Razor support in Visual Studio Code as part of the C# extension. It will be the basis for the Razor editing support in Visual Studio Codespaces and Visual Studio LiveShare. And now it is available for local development in Visual Studio as a preview feature.

Currently our focus has been on making the new LSP based Razor editor have functional parity with the existing Visual Studio Razor editing experience (as noted below, there are still a few functional gaps to address). In future releases we expect to fill these functional gaps add significant new functionality, like bringing many more of the C# editing features to Razor, and enabling other new Razor specific productivity improvements.

Known issues

The new Razor editor is currently experimental and has some known limitations. The following Razor editor features have not yet been fully implemented and will be added in a future release:

• JavaScript and CSS IntelliSense support
• Colorization for C#, JavaScript, CSS, Blazor components, Tag Helpers, and tooltips
• Formatting is limited to only C# code in @code and @functions blocks with no embedded HTML markup or Razor syntax
• URL picker support in HTML
• C# snippets (‘prop’, ‘ctor’, etc.)
• Complex C# completions (for example, generating overrides)
• Go-to-definition/implementation from C# to Razor
• Renames in C# files do not propagate to Razor files
• Matching identifier highlight support for HTML and curly braces

There are also some functional issues with the new Razor editor in 16.7 Preview 4 that will be addressed in a future release:

• C# error squiggles may be misaligned
• Unnecessary informational errors reported for unnecessary using directives in Razor files
• Blazor components & Tag Helpers are currently colored like C# classes and don’t respect the Tag Helper colorization option

Give feedback

These are still the early days for the new LSP-based Razor editing experience in Visual Studio. We know that there’s still a lot of work to do before it can replace the existing Razor editing experience in Visual Studio. The new Razor tooling will remain optional and experimental in 16.7 and we don’t expect to make it the default Razor editor until it surpasses the functionality of the existing editor. But, we wanted to share our progress as early as possible to start getting your feedback on how well the new Razor editor works for you. To ensure we ship the best Razor editing experience possible, please give the new Razor tooling a try and let us know what you think. You can share your feedback with us by creating Razor Tooling issues on Github in the ASP.NET Core repo. We appreciate your feedback!

Apple on Thursday offered an inside look at Apple Sanlitun, the company’s latest retail location in China.