Crystal Tools

As a video game company with different production teams, Square had wished for its employees to efficiently share their know-how and technology even before the merger with its competitor Enix. The desire for a common development infrastructure and engine dates back to the 1997 role-playing video game Final Fantasy Tactics, which was created in the transitional period from 2D to 3D game production.[3] Back then, the artists working on the game asked programmer Taku Murata for a fast way to check how their work would look in the final game. As the development was carried out on personal computers, the graphics were displayed on computer monitors. This looked very different from the PlayStation console's actual graphics displayed on a television screen. Initially, a faithful preview of the game's visuals was too time-consuming because all data had to be transferred from PC to console first. To evade this step, Murata created an instant preview tool. With this, he soon witnessed a boost in the artists' productivity and in the quality of their work. For 2000's Vagrant Story, the developers opted to reuse this instant preview tool rather than programming a new one from scratch.[3] Murata and his colleagues added new functions to create a unified preview and cutscene tool tailored to the game's fully polygonal 3D graphics. With 2001's PlayOnline service, the company then made its first foray into introducing a common software for all its divisions.[1]

After the Square Enix merger, however, the individual teams still continued to program and customize their own tools for each game, which would eventually go to waste as only their respective creators knew how to use them. With the amount of assets and tools required by the in-development Final Fantasy XII and the impending advent of the seventh console generation, a common data format for the company was proposed in 2004. It was to be developed in-house and replace general-purpose formats such as FBX and COLLADA. Realizing the goal of an engine with a common set of tools proved to be difficult, as many production teams wanted to further their own interests rather than those of the company as a whole. Select staff members from different company divisions teamed up to work on the project on a voluntary basis, but their loose organizational structure failed to yield results. Nevertheless, Murata considered this group effort a first step in the right direction.[1] In 2005, he was appointed general manager of the newly formed Technology Division.[3] Although this enabled Murata and his subordinates to talk about a company-wide engine more extensively, the lack of manpower again prevented any significant achievements.[1]

Following the public's positive reaction to the graphics of the Final Fantasy VII Technical Demo for PS3 presented at the Electronic Entertainment Expo in 2005, it was decided to release the role-playing video game Final Fantasy XIII on the PlayStation 3 rather than the PlayStation 2 as originally planned.[6] In August 2005, the Technology Division began working on the White Engine, a PlayStation 3 engine that was supposed to be exclusively used for Final Fantasy XIII.[1][6][7] Eight months later, however, it was decided to repurpose the engine to further make it compatible with other projects such as the action RPG Final Fantasy Versus XIII (later rebranded and repurposed into Final Fantasy XV) and the massively multiplayer online role-playing game (MMORPG) Final Fantasy XIV.[6][7][8] In order for the company to stay competitive in a multi-platform environment, support of the engine was extended from the PlayStation 3 to the Xbox 360 and Microsoft Windows, both of which were successful in Western markets.[1][5] This marked the official development start of a company-wide engine for whose purpose the Technology Division was expanded into the Research and Development Division in September 2006.[1][3] Murata remained the division's general manager with a full-time staff at his disposal.[1]

During development of Crystal Tools, the Research and Development Division continually surveyed what types of tools were needed to create Square Enix's flagship titles. Among the most frequently requested features was an extensive use of character close-ups. This made the staff realize that the Final Fantasy series put great emphasis on the "anime-like coolness" of its characters. Consequently, the engine's developers focused on attractive visuals rather than on accurate physics. To achieve a stylized look, a post-processing filter for additional lighting, blur, and visual effects was implemented. Square Enix's large teams were typically composed of a mix of industry veterans and rookie game developers. To accommodate this, the graphical user interface of the engine became another main feature and was designed to be as intuitive as possible. The large investments into technology and human resources quickly made the White Engine the company's biggest project to date. After one year of work, version 1.0 of the engine was completed in September 2007.[1]

Crystal Tools in 2009

After version 1.0 had been finished, the engine's code name White Engine was changed to the official title Crystal Tools.[1][2][5] This was not only done to represent the company and its works better, but also due to the refractive effects of real-life crystals that were meant to symbolize the flexibility of the engine.[5] Over the next few months, the programmers advanced the engine to version 1.1 and added preliminary support for the Wii.[1] In September 2011, Final Fantasy Versus XIII director Tetsuya Nomura announced that his team had replaced Crystal Tools with a proprietary action game engine that was supplemented by the lighting technology of the company's new Luminous Studio engine.[9] Other teams, such as the staff behind Final Fantasy XIII-2, kept using and refining Crystal Tools.[10] For Lightning Returns: Final Fantasy XIII, the engine was adjusted to make it more suitable to games with an open world design.[11]

While Final Fantasy XIII was in production, the development of Crystal Tools caused significant problems and delays. The programmers spent much time on taking all demands from staff into account. Based on this feedback, Murata's team tried to adapt the engine to the needs of several game projects, which proved to be virtually impossible and prevented the engine's specifications from being finalized.[12] Furthermore, as separate groups were working on the individual tools of the engine, there was no comprehensive software documentation to ensure usability and compliance.[13] Unable to wait any longer, the Final Fantasy XIII team had no choice but to begin creating assets to keep to the game's production schedule. However, the lack of specifications resulted in these assets being incompatible with the engine. In the end, it was decided that Final Fantasy XIII was to be the principal focus of Crystal Tools and the game's team began cooperating with the Research and Development Division more closely to receive the required tools and specifications.[12] While preliminary support of Crystal Tools was developed for the Wii, the console did not fully support all components.[3] In 2008, Murata said that Square Enix might license the engine out to other companies at some point in the future, although the limited documentation and the impracticality of supporting licensees posed great problems in doing so.[1][5] Two years later, Final Fantasy XIII producer Yoshinori Kitase stated that developing an engine from scratch to go with a new game may have been a mistake and a likely cause for the long period between the title's announcement and release.[14]