Subscribe to GameFromScratch on YouTube Support GameFromScratch on Patreon

6. June 2016

 

In a recent blog post the Amazon developer team discussed the upcoming support for VR devices in Lumberyard 1.3.  This support comes in two forms, supporting actual VR devices in your game and using VR to develop your game.  Both are being provided in the form of “Gems”, which is basically Amazon’s way of saying plugin.  To add support for a new VR device, you create a gem that implements the IHMDDevice interface, acting as a bridge between Lumberyard and the device’s SDK.

Utilizing Gems, small chunks of code can be created that interact with the engine but don’t require editing the engine code itself. This means that developers can add support for any VR device without having to delve into the engine source. As long as a new VR device conforms to the public interfaces that Lumberyard has defined, the engine will automatically use it. Developers can create their own integrations for additional devices without having to wait for an official Lumberyard update, as they would in other engines. With so many new VR devices coming out soon, we wanted to provide a way for customers to make their own support decisions. Additionally, developers can easily override existing device support to add any experimental features that may be important for their gameplay. Below is a high-level diagram of the way this works inside the engine.

The HMDManager contains an IHMDDevice, which is then implemented by a device-specific Gem. The manager takes care of device initialization and device-abstracted head-mounted display (HMDs) interaction with the rest of the system. On the rendering side, Lumberyard’s stereo renderer makes use of the D3DHMDRender object, which takes care of creating graphics-API-specific render targets, social screen rendering, and frame submission to the VR device. To add support for any new VR devices, you simply wrap the vendor-specific SDK in a Gem as defined by IHMDDevice. That’s it! There’s no need to edit Lumberyard’s underlying HMD code, which is represented by the Lumberyard Engine section of the diagram.

On engine startup, the selected HMDs are scanned for connectivity and selected for use. If you want to support both the Rift and the Vive, for example, simply go into the Project Configurator, enable both Gems, and the engine will pick which one to use at runtime based on which device is plugged in.

 

They also go on to describe the new VR developer functionality that will be part of Lumberyard 1.3:

Developing in VR

Game developers need to be able to see what they’re doing in the editor at all times. Without a way to see VR in the editor, developers would have to export a level, load it into the launcher, enable VR, and take a look around. This is obviously inefficient. The Lumberyard Beta 1.3 editor will have full VR Preview support built in. VR Preview utilizes the same Gems system as the engine runtime, and it works in a similar fashion. We’ve added the “VR Preview” button to the editor, which you can click to see in VR right away. This allows developers to make VR-specific adjustments to their level designs right in the editor, which reduces iteration time. Flow Graph nodes are an important part of developing in Lumberyard, but they can only be debugged in the editor. With VR Preview, users can debug their VR Flow Graph nodes and see what they’re doing.

The cool part of their implementation is there is no performance penalty for enabling VR if VR functionality isn’t used, making this functionality “free” from a processing perspective.

 

So, what devices are supported?  Well until 1.3 ships the answer is unknown.  They address it with this comment:

Rift and HTC Vive support were top requests (our demo was presented on the Rift), but many developers were just as interested in other devices, like the Samsung GearVR, PSVR, and OSVR.

But never actually state what gems will ship with the 1.3 release, meaning it might be left to developers to implement the various VR headset SDKs. 

GameDev News

24. May 2016

 

CryEngine recently moved to a pay what you want price structure with the release of CryEngine 5.  Then with the release of CryEngine 5.1 a few weeks back, they had this to say:

Git is a very widely used version control system that allows users to instantaneously access any revision of a file that has ever existed in their repository. This makes comparing revisions of a file and tracking changes over time very convenient, particularly as each time a set of changes is committed to the repository, a description of the change can be added. EDIT: We are finishing up the last details and users will get access to Git very soon.

 

Well that “very soon” is today.  The CryEngine source code is now available on Github.  The console (Xbox1/PS4) specific bits still require a proof of appropriate license to access, but otherwise everything is here.

image

 

Keep in mind though, this isn’t a typical open source release and is governed by a proprietary license.  Read well before using!

GameDev News

13. May 2016

 

Amazon just added Substance Integration to their Lumberyard game engine in the form of an extension.  Lumberyard is Amazon’s fork of CryEngine released several months ago.  You can see Lumberyard in action in this video.  Substance is a pair of products from Allegrothimic composed of Substance Designer and Substance Painter.  They enable you to recreate real world materials for physically based rendering (PBR) and is proving extremely popular among texture artists.  Substance Painter was featured in our GameDev Toolbox series earlier if you want more details.

 

Amazon announced the new extension on their blog:

To enable the Lumberyard Substance Editor tool, go to your Project Settings inside the Project Configurator and select “Enable Packages” on the top right. This will let you enable the Substance extension for your project.

Working with .sbsar files within the Lumberyard Substance Editor grants many advantages over standard workflows. Ceramic tile textures, for example, could have sliders for adjusting the size of tiles, how they’re arranged together, and how they’re lined up. In the editor, you can make changes to these variables and see the results update in real time. To do this, use the editor to import your .sbsar file, which will then generate a .smtl (our file format for Lumberyard Substance materials) and .sub files (Substance textures). When selecting your .sbsar file, you’ll see your Substance file’s exposed settings as well as all the textures that can be generated from it.

From the Lumberyard Substance Editor, you can also change parameters at run-time using Lumberyard’s Flow Graph. As you configure a texture applied to an object in your game world, Lumberyard will show you real-time previews of the end result, both from the editor window and on the actual object. Substance works within Lumberyard as a project extension, which includes the ability to use the Substance API, the Lumberyard Substance Editor plugin, and Flow Graph nodes.

GameDev News

29. April 2016

 

It was only a few months back that Amazon launched Lumberyard, their CryEngine powered game engine.  In March they released Lumberyard 1.1 then earlier this week they just released Lumberyard 1.2.  At least out of theZombiesEditor gate they are keep the updates coming at a good pace.

 

So what exactly is in Lumberyard 1.2?

  • new audio tutorial on integrating Wwise audio in Lumberyard
  • extended mobile support from 1.1.  More iOS and Android devices added included iPhone 6 series, Air2 and iPad Pro, with Note 5 and Nexus 6 added on the Android side )
  • network bindings for components enabling network synchronization
  • improve particle editor including library support, GPU particle rendering, advanced playback controls, a gradient editor and more
  • UI Animation system enabling you to animate certain properties of UI components.

That’s the new features, then comes the rather massive list of changes and features.


ASSET PROCESSOR
• The Asset Processor now stores log files in a logs subfolder (located in the same location as
the Asset Processor executable file). These logs include detailed information that you can use to
diagnose issues in the Asset Processor.
• The Asset Processor now recognizes when copies of the tool are stored in different locations for
different projects on the same machine. If you attempt to run Lumberyard Editor while the
Asset Processor from a different branch or version of Lumberyard is running, you will receive
notification and the option to run the correct Asset Processor or exit the old version. This helps
to prevent connection to and communication with the incorrect Asset Processor.
• To allow you to get started while assets compile in the background, the Asset Processor now
supports priorities assigned to asset types to compile in the configuration file. By default
meshes and animations are preferred over textures.
• A new algorithm is now used to order the Asset Processor’s build queue and dynamically
reorder the queue based on the connected platforms and the assets requested by these
platforms. Unconnected platforms have a lower priority than connected ones.
AUDIO
• The default audio error logging verbosity is now set to Errors & Warnings to increase visibility.
• Added a flow graph node to control Audio components.
• Added a method to stop all sounds to the audio proxy.
CLOUD CANVAS RESOURCE MANAGEMENT
• To help reduce confusion about their purpose, removed the Development deployment and
Hello World feature from the default project.
• Deployment stacks are no longer created under the project stack. This change allows you to
create, update, and delete deployments without risking changes to other deployments.
COMPONENT ENTITY SYSTEM
• Added the ability to push unrelated entities with instanced entities to a slice asset.
• The Entity Outliner can now show multiple components of the same type.
FBX IMPORTER
• The FBX Importer now automatically converts FBX units to meters. This allows you to use scenes
from different content creation packages because the content is automatically scaled logically
upon import.
• The FBX Importer now reads Up-Axis orientation data. This allows you to use scenes from
different content creation packages because the content is automatically oriented logically
upon import.
GAMELIFT
• Changed the command that is used to start the Amazon GameLift server from start_lobby
to gamelift_start_server.
• Added support for idle timeout in all modes. Idle timeout is disabled by default. To enable idle
timeout for Amazon GameLift, you can add +sv_idle_seconds 600 to your server’s
command line in the Amazon GameLift dashboard.
• Removed the GridMateGameLift static library and moved all Amazon GameLift code in the
Multiplayer Project to the Amazon GameLift Gem.
• Changed the include paths for Amazon GameLift session header files from
GridMateGameLift/Session/.. to GameLift/Session/...
LUMBERYARD INSTALLER
• The installer now automatically installs the Visual C++ Redistributable Packages for Visual
Studio 2013, if it is not already on your machine.
• To help provide clarity, the installer now clearly states the build version that will be installed.
• To help improve functionality, the installer now reports metrics when certain steps are
completed.
MOBILE SUPPORT
• Improved the error messages for configuring an Android project to help diagnose problems.
• Added support for the Android devices Samsung Galaxy Note 5 and Motorola Nexus 6.
• Created a separate download package for iOS developers to help with line ending problems in
JSON files.
• Various updates for iOS include exposing global blending weight and fixing VisArea bugs.
• Improved the Xcode project generation for iOS by using rsync to copy assets.
• Added support for enabling r_VisAreaClipLightsPerPixel in GMEM for iOS.
NETWORKING
• Created a Gem for GridMate GameLift integration. This Gem contributes to Lumberyard’s
modular approach, allowing you to more easily customize the engine for your needs. You can
optionally include this Gem in your Lumberyard game project.
• Disabled the Connect and Host flow graph nodes for the Multiplayer Gem.
• Added the ability to search for Amazon GameLift sessions by game instance ID. This enables
you to create a custom matchmaking service with your game hosted by Amazon GameLift.
• Added support to the GridMate API for reusing EC2 instances in Amazon GameLift, which
removes the need to spin up a new instance for every game session.
• Modified replica initialization to take a debug name.
• Updated AzFramework to require GridMate. On Xbox, GridMate requires winsock
(ws2_32.lib) to link in. On Windows, GridMate links in using a pragma in code.
• Removed support for Windows XP and earlier by updating the _WIN32_WINNT version to
0x6000 (Windows Vista), and removing the unnecessary inet_ntop() implementation.
• Modified UpdateFromChunk to call per chunk and not per replica.
PROJECT CONFIGURATOR – Various updates include adding metrics reporting, ensuring the
ProjectConfigurator.log file is saved to the engine root, and updating the project template to
match the latest changes to the Empty Template.
TWITCH CHATPLAY
• The Twitch:JoinIn:CreateLink flow graph node now includes an Error port, which is
signaled if the link was not created successfully. The GameName port was removed; the game
name is now copied from the sys_game_name console variable.
• You can now use the joinin_uriScheme console variable to set the URI scheme for the
JoinIn link. The default value is game.
• You can now use the chatPlay_GroupServerList console variable to set the list of group
chat servers and ports.
UI EDITOR
• In the Samples Project, the UIDemo level was renamed to UIEditor_Sample.
• Removed the UiDemo Gem and added the functionality to the Samples Project.
• Added the UiInitializationBus to help simplify the process of writing custom UI components that
require data initialization after loading a canvas in-game.
• In the File menu, New has been renamed to New Canvas.
• In the component properties, the Selected state has been renamed to Hover.
• In the Properties pane, the Components button has been renamed to Add Component and is
now located at the top of the pane.
• Added the ability to remove components by right-clicking the component.
• Added the flow graph nodes Ui:Element:SetIsEnabled and
UI:Interactable:SetIsHandlingEvents.
• Added the image types Stretched to Fit and Stretched to Fill to the Image component. These
image types maintain the aspect ratio of the texture when the element is a different aspect
ratio.
• You can now show the anchor preset in use by using the icon to the right of the anchor values
in the Anchor properties.
MISCELLANEOUS
• Renamed the following parts of EBus for clarity:
o EBusEventGroupContainerTypes renamed to EBusHandlerPolicy
o EBBCT_SINGLE renamed to EBusHandlerPolicy::Single
o EBBCT_MULTI renamed to EBusHandlerPolicy::Multiple
o EBBCT_MULTI_ORD renamed to EBusHandlerPolicy::MultipleAndOrdered
o EBusContainerTypes renamed to EBusAddressPolicy
o EBCT_SINGLE renamed to EBusAddressPolicy::Single
o EBCT_ID_UNORDERED renamed to EBusAddressPolicy::ById
o EBCT_ID_ORDERED renamed to EBusAddressPolicy::ByIdAndOrdered
• Updated EBus to declare traits as follows:
static const AZ::EBusAddressPolicy AddressPolicy =
AZ::EBusAddressPolicy::ById;
static const AZ::EBusHandlerPolicy HandlerPolicy =
AZ::EBusHandlerPolicy::Single;
• Various EBus updates include adding script bindings, removing “Listener,” and improved
documentation.
• Updated the Lumberyard Waf build system (lmbr_waf) QT tool to resemble the Waf QT5
version.
• In Lumberyard Editor, you can now opt out of sending metrics by clicking File, Global
Preferences, Editor Settings, and selecting the opt-out check box.
Fixes
Lumberyard Beta 1.2 includes the following fixes:
AI – The editor no longer crashes when:
• Attempting to grab an AI human in-game in the GameSDK project. This error occurred for AI
humans that had a nonexistent grab type specified in the entity settings.
• Saving CGF files for certain brush objects.
ASSET PROCESSOR
• Fixed an issue that caused the Asset Processor batch file to hang when attempting to cancel by
pressing Ctrl+C.
• Fixed an issue that prevented Lumberyard Editor from launching if the Asset Processor from a
previous build is running in the background.
• Fixed an issue that caused exported geometry (CGF and i_caf files) from 3D Studio Max to
appear as failed in the Asset Processor.
• Fixed a bug that caused numerous Asset Processor icons to appear in the system tray after
switching projects or closing tasks.
• Fixed an issue that prevented the Asset Processor from identifying changes to
sys_game_folder in the bootstrap.cfg file.
AUDIO – Fixed an issue with undoing operations that caused the Audio Controls Editor to crash.
CINEMATICS
• Fixed an issue that prevented movies or frames in Lumberyard from rendering to the paths with
spaces specified in the Render Output dialog box in Track View.
• Fixed an issue that caused incorrect sequence ranges to save when toggling between the
Seconds and Frames time units in the Sequence Properties dialog box in Track View.
• Fixed an issue that caused the editor to crash when using sequence names over 1,000
characters long.
CLOUD CANVAS
• Fixed a bug that caused stackStatusListModel to erroneously use columnCount()
rather than the enum ColumnCount when filling out a row.
• Fixed an issue with the mobile analytics client using the default retry strategy that caused long
pauses when a network connection is not present.
• Fixed an issue that caused lmbr_aws to crash if the Metrics DLL does not exist.
• Added validation for key name, bucket name, and file name in the S3 Download and Upload
nodes.
• The Forgot your password link in the Login to Amazon Lumberyard dialog box now displays the
password assistance page as expected.
• Various fixes include removing a dangling GridMate GameLift reference from the multiplayer
Gem and removing an unnecessary dependency on IAM within Client Manager.
FBX IMPORTER
• Fixed an issue with importing FBX files that do not have a scene settings file that caused the
Asset Processor to erroneously report a failure.
• Fixed an issue that prevented the entry of characters that would have resulted in a duplicate
group name.
• Fixed an issue that caused the Scale property to allow both 0 and negative values when
importing assets.
• Extended the iterators in the Scene API with unit tests.
FLOW GRAPH
• Fixed floating point precision issues that caused the flow graph node Math:Equal to become
unreliable when reporting equality between numerical values.
• Fixed an issue that caused the flow graph node Math:EvenOrOdd to reverse even and odd
numbers for the node outputs.
• Fixed an issue that caused flow graphs, game tokens, track view sequences, and objects to
delete when right-clicking the viewport while a level loads.
• Fixed an issue that caused the editor to crash when attempting to add comments to a new flow
graph by using shortcuts (for example, Right Alt+F, Right Alt+E, Right Alt+V, Right Alt+O, or
Right Alt+D).
• Fixed an issue that prevented an automatic refresh when a flow graph component is added to
an entity.
• Fixed an issue that caused the audio component to stop all triggers from executing on the
owned proxy upon deactivation.
• Fixed an issue that prevented the component flow graphs from uninitializing properly.
• Fixed an issue that caused unusual behavior when selecting Change Group Name from the
Global Flow Graphs menu.
GEMS
• Fixed a crash issue when shutting down the Gem Registry.
• Fixed a shutdown crash issue in the Game Effect and Lightning Arc Gems.
• Fixed an issue with deploying Monolithic builds for game projects that include Gems.
• Fixed an issue with building tests for a new Gem that resulted in a failure and Uber file error.
• Fixed an issue with release configuration failing on launch, resulting in a “Failed to load Gems
project” error message.
GEPPETTO
• Fixed an issue that prevented the animations list in Geppetto to remain in sync and display
properly.
• Fixed an issue that erroneously allowed invalid values (0 and negative numbers) for the scale
when importing an FBX.
• The editor no longer crashes when importing a new i_caf file with blendshapes.
• The character tree list no longer displays deprecated CGA files.
• The skeleton file type list no longer displays unsupported formats, such as SKEL and CGA.
• The Resource Compiler no longer crashes due to the System Allocator from the Resource
Compiler Scene and Scene API.
LUMBERYARD EDITOR
• Fixed an issue that caused level slice to persist slice references across editor level sessions.
• Fixed an issue that prevented scripts from successfully reloading in the editor for entity objects.
• Fixed an issue that prevented the Camera Sample level’s dynamic fly-by camera angle from
functioning correctly when the Cycle balloon cameras button is pressed.
• Fixed various stability issues with loading meshes.
• Fixed an issue that caused the animation component to send multiple OnAnimationStopped
events.
• Fixed an issue with live-lock during loading if a level includes a certain number of mesh assets.
• Fixed an issue that prevented the Component Palette window from unregistering from the
plugin and closing properly.
• Fixed an issue with invalid bound on an object when instantiating component entities from a
slice, resulting in the object being off at the origin and breaking selection in the editor.
• Fixed an issue that prevented values to be set when rotating a designer object on the Y axis to
90 or -90 and beyond.
• Fixed an issue that prevented the use of spaces in the Lumberyard installation path.
• The editor no longer crashes when:
o Selecting a mesh file in PreviewModelCtrl.
o Attempting to push entity changes to a slice.
o Reloading slices and the flow graph wrapper accesses deleted objects.
o Using proximity triggers that activated only once in profile.
o Dragging an asset from the file browser into the viewport when a level is not loaded.
o Cloning a game token.
o Modifying the level library before loading a level.
MANNEQUIN
• Fixed an issue that prevented the Transition editor from saving changes to procedural clips.
• Fixed an issue that prevented the Mannequin Sequence file from saving properly.
• Maya 2015 no longer crashes when using the User Defined Properties (UDP) tool.
3DS MAX EXPORTER
• The editor no longer crashes when setting up an AnimObject that uses a character and
animation exported from 3D Studio Max.
• Fixed an issue that misaligned the skin and bones after exporting from 3D Studio Max and
assembling in Geppetto.
MOBILE
• Fixed an issue that caused textures compressed by the Resource Compiler with
colorspace=*,[auto|sRGB] to crash when loaded on iOS.
• Fixed an issue that prevented skinned character shadows from working correctly in the GMEM
render path.
NETWORKING
• Fixed a buffer overflow vulnerability in CarrierThread::ProcessIncomingDatagram
when receiving incoming datagrams.
• Fixed a buffer overflow vulnerability in CarrierThread::ReadAckData() when receiving
malformed system ack messages, preventing a denial of service.
• Fixed a crash in the object stream when skipping unreflected root node in binary mode.
• Fixed a bug that prevented game code from receiving the SignIn system event.
• Fixed a bug that prevented RPCs from being called for proxies when multiple chunks were
bound to a replica.
• Fixed a bug for processing unknown chunk types.
• Fixed an issue that caused existing players to disconnect and the server to crash if the number
of players attempting to connect exceeded the maximum number of players allowed, as
specified by the sv_maxplayers value.
PARTICLE EDITOR
• Fixed an issue that prevented the Gradient Editor from preserving set values.
• Fixed an issue that caused the delete confirmation dialog box to display twice when attempting
to delete a particle or folder.
• Fixed an issue that prevented a modified color value from saving to the XML file.
• The editor no longer crashes:
o After editing a particle from an imported library and closing the Particle Editor by
clicking Cancel in the warning message dialog box.
o After creating a library and closing the Particle Editor without saving the library.
o When attempting to hide the Attribute panel in the Particle Editor.
• Fixed an issue in the particle library version 27 that prevented particles from loading correctly.
• Fixed an issue that prevented “forward” planar decals from rendering properly in certain
projects.
• Fixed an issue that caused materials cloned with a .ddna file to bind an incorrect
smoothness/gloss texture.
• Fixed an issue that caused the sun position and lighting to move when opening the Sun
Trajectory pane.
• The particle orientation now loads correctly in a level.
• The environment probe preview option now renders correctly.
• The editor no longer crashes in debug when configuring the layout to use multiple viewports.
• Added support for MIN_MAG_MIP_LINEAR as a shader token, which resolves asserts in debug.
PROJECT CONFIGURATOR – A warning message about running lmbr_waf configure after creating
a project now persists within a single session of the Project Configurator. Previously the warning
message would disappear after the first time a new project was created.
SAMPLE LEVELS
• Fixed an issue that caused a ‘texture file missing’ warning message to display when opening the
Animation_Basic_Sample level.
• Fixed an issue that caused the Animation_Basic_Sample level to crash when using the
SamplesProjectLauncher.exe standalone launcher.
SETUP ASSISTANT
• Changed the default SDK requirements for running a game. If you want to compile game code
only, you can now run a Waf configuration step. The Codejock Xtreme Toolkit Pro, which is
included with Lumberyard, is now marked as required.
• Various fixes include updates to text, icons, and page functionality.
UI EDITOR
• Fixed the pop-up position of the Sprite Border Editor and the Anchor Presets widget.
• Fixed various issues with running a game in the editor and loading a canvas in a game that is
already loaded in the UI Editor. For example, loading a canvas in-game when it is loaded in the
editor will result in a copy of the canvas that is used by the game.
• Fixed a bug in the UITextInput component that prevented selecting a text range backwards
from functioning correctly.
• Fixed an issue with sliced images where the image rectangle is thinner than the sprite borders,
resulting in the borders overlapping.
• Fixed a bug that caused changes to save when clicking Cancel in the Sprite Border Editor.
• Fixed a bug that caused the browser to save when clicking Cancel in the Changes have been
made dialog box.
• Fixed an issue that caused the UI Editor to become unresponsive when 20+ canvas files are
open in the editor.
• Reinstated the Font Effect property in the Text component property pane.
• The image texture browser now properly supports the file formats listed in the browser: .bmp,
.dds, .gif, .jpeg, .png, .tga, and .tif.
MISCELLANEOUS
• Fixed an issue that prevented AZStd::conditional_variable.wait(…) from halting a thread.
• Fixed an issue that prevented the AZ::Entity cached shadow from updating.
• Fixed an issue that caused AZ::Entities to vanish when moved from the initial position.
• Fixed an issue with selecting more than eight entities by adding entries to the dynamic pop-up
menu allocation.
• Fixed an issue that caused the Resource Compiler to connect to Perforce during asset
processing, even though the Perforce plugin is disabled in the editor.
• Fixed an issue with saving changes in the Audio Controls Editor that caused the Perforce
connection to break and display an error message.
• Various fixes to the CodeGenPreview solution include updates to AZCore/AZCoreTests
and support for proper include paths for rapidxml

 

The complete and massive release notes are available in this PDF.  Let’s hope Amazon keeps improving Lumberyard at this rate in the future, we might have a real fight on our hands!

GameDev News

22. March 2016

 

A week ago CryEngine V was launched and I have been intending to check it out but I couldn’t.  Put simply, the login servers just didn’t work.  Some people managed to get in eventually, but if you tried to login in while the servers were broken it damaged that login and it would never work.  I just received the following email:

 

Hi YOU!

Due to last week's server issues some users have yet to receive their confirmation email, and are still unable to login.

Our team solved the problem, but we need affected users to register again. If you haven't received an activation email or your log in doesn't work, we kindly ask you to register again. You can use the same registration email as before.

If you still have any issues after doing so, please contact us.

We are very sorry for the inconvenience caused, and thank you for your understanding.

Thanks,
CRYENGINE Support

 

Signing up for a new account finally got me in.  That said , it seems my desired username is now taken as a result.  Considering my last major experience with CryEngine was when they leaked all their developers information several years back, I will say I’m not exactly thrilled with their server side support...

 

If you’ve been waiting to try CryEngine, try it again.  I personally managed to create an account this time at least.

 

EDIT: Nevermind... spoke to soon

image

 

Seriously CryEngine, this is beyond pathetic at this point.

EDIT2:  The CryEngine Login Failed. Server not reachable error seems to be linked to authorizing your account.  For some reason when I went back to the confirmation email and authorized a second time it started working.

GameDev News

Month List

Popular Comments