This is a good article. Click here for more information.

Sonic Team

From Infogalactic: the planetary knowledge core
(Redirected from List of Sonic Team games)
Jump to: navigation, search
Sonic Team
Native name
 ソニックチーム
Sonikku chīmu
Formerly called
  • Sega CS3
  • Sega R&D No. 8 (AM8)
  • Sega GE1
Division
Industry Video games
Founded 1990; 34 years ago (1990)
Founders
Headquarters Shinagawa, Tokyo, Japan
Key people
Products List of Sonic Team games
Parent Sega
Website <strong%20class= "error"><span%20class="scribunto-error"%20id="mw-scribunto-error-1">Lua%20error%20in%20Module:Wd%20at%20line%20405:%20invalid%20escape%20sequence%20near%20'"^'. http://<strong%20class="error"><span%20class="scribunto-error"%20id="mw-scribunto-error-1">Lua%20error%20in%20Module:Wd%20at%20line%20405:%20invalid%20escape%20sequence%20near%20'"^'.Lua error in Module:EditAtWikidata at line 29: attempt to index field 'wikibase' (a nil value).

Sonic Team[lower-alpha 1] is a video game developer owned by the Japanese video game company Sega as part of its Sega CS Research and Development No. 2 division. Sonic Team is best known for the long-running Sonic the Hedgehog series and games such as Nights into Dreams and Phantasy Star Online.

The initial team, formed in 1990, comprised staff from Sega's Consumer Development division, including programmer Yuji Naka, artist Naoto Ohshima, and level designer Hirokazu Yasuhara. The team took the name Sonic Team in 1991 with the release of their first game, Sonic the Hedgehog, for the Sega Genesis. The game was a major success and contributed to millions of Genesis sales. The next Sonic games were developed by Naka and Yasuhara in America at Sega Technical Institute, while Ohshima worked on Sonic CD in Japan. Naka returned to Japan in late 1994 to become the head of CS3, later renamed R&D No. 8. During this time, the division took on the Sonic Team brand but developed games that do not feature Sonic, such as Nights into Dreams (1996) and Burning Rangers (1998).

Following the release of Sonic Adventure in 1998, some Sonic Team staff moved to the United States to form Sonic Team USA and develop Sonic Adventure 2 (2001). With Sega's divestiture of its studios into separate companies, R&D No. 8 became SONICTEAM Ltd. in 2000, with Naka as CEO and Sonic Team USA as its subsidiary. Sega's financial troubles led to several major structural changes in the early 2000s; the United Game Artists studio was absorbed by Sonic Team in 2003, and Sonic Team USA became Sega Studios USA in 2004. After Sammy Corporation purchased Sega in 2004, Sonic Team was reincorporated to become Sega's GE1 research and development department. Naka departed during the development of Sonic the Hedgehog (2006), and Sega Studios USA was merged back into Sonic Team in 2008. The following decade was marked by Sonic games of varying reception, with head of studio Takashi Iizuka acknowledging that Sonic Team had prioritized shipping over quality.

History

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

See also: Sega development studios

1990: Formation and Sonic the Hedgehog

File:Yuji Naka' - Magic - Monaco - 2015-03-21- P1030036 (cropped).jpg
Yuji Naka, programmer for Sonic Team and later division president

In 1983, programmer Yuji Naka was hired into Sega's Consumer Development division.[1] His first project was Girl's Garden, which he and Hiroshi Kawaguchi created as part of their training process.[2] For his next game, Phantasy Star (1987) for the Master System, Naka created pseudo-3D animation effects.[3] He met artist Naoto Ohshima while working on the game.[4]

During the late 1980s and early 1990s, a rivalry formed between Sega and Nintendo due to the release of their 16-bit video game consoles: the Sega Genesis and the Super Nintendo Entertainment System.[5][6][7] Sega needed a mascot character that would be as synonymous with their brand as Mario was with Nintendo.[5][6][8] Sega wanted a killer app and character that could appeal to an older demographic than preteens, demonstrate the capabilities of the Genesis, and ensure commercial success in North America.[6]

Sega held an internal competition to submit characters designs for a mascot.[8][9] Ohshima designed a blue hedgehog named Sonic,[5] who was inserted into a prototype game created by Naka.[8] The Sonic design was refined to be less aggressive and appeal to a wider audience before the division began development on their platform game Sonic the Hedgehog.[8] According to Ohshima, Sega was looking for a game that would sell well in the United States as well as in Japan. Ohshima and Naka already had the game and character ready, with Ohshima having worked with Sega's toy and stationery department on design ideas. Ohshima claims that the progress they had already made encouraged the company to select their proposal, as theirs was the only team to have put in a high amount of time and effort. This left him confident their proposal would be selected.[10]

The Sonic the Hedgehog project began with just Naka and Ohshima,[11][10] but grew to involve two programmers, two sound engineers, and three designers.[12] Hirokazu Yasuhara joined to supervise Naka and Ohshima and develop levels, and became the lead designer. He satisfied Naka's request for a simple, one-button design by having Sonic do damage by jumping.[13] Sonic the Hedgehog was released in 1991 and proved a major success, contributing to millions of sales of the Genesis.[5] The development team took the name Sonic Team for the game's release.[5] Naka has referred to Sonic Team as only a "team name" at this point.[1]

1994–1998: Re-establishment and new intellectual properties

File:Naoto ohshima gdc 2018.jpg
Naoto Ohshima, Sonic Team artist who designed the Sonic the Hedgehog character

Shortly after the release of Sonic the Hedgehog, Naka, Yasuhara, and a number of other Japanese developers relocated to California to join Sega Technical Institute (STI), a development division established by Mark Cerny intended as an elite studio combining the design philosophies of American and Japanese developers.[5][14] While Naka and Yasuhara developed Sonic the Hedgehog 2 with STI, Ohshima worked on Sonic CD, a sequel for the Sega CD add-on. Though Naka was not directly involved in the Sonic CD development, he exchanged design ideas with Ohshima.[15]

Following the release of Sonic & Knuckles in 1994, Yasuhara quit, citing differences with Naka. Naka returned to Japan, having been offered a role as a producer.[5] He was placed in charge of Sega's Consumer Development Department 3, also known as CS3.[16] Naka was reunited with Ohshima and brought with him Takashi Iizuka,[17] who had also worked with Naka's team at STI.[6] In the mid-1990s, Sonic Team started work on new intellectual property, leading to the creation of Nights into Dreams (1996) and Burning Rangers (1998) for the Sega Saturn.[5] Naka stated that the release of Nights is when Sonic Team was truly formed as a brand.[1]

The Saturn did not achieve the commercial success of the Genesis, so Sega focused its efforts on a new console, the Dreamcast, which debuted in Japan in 1998.[5] The Dreamcast was seen as opportunity for Sonic Team to revisit the Sonic series, which had stalled in recent years.[5][8] Sonic Team was originally creating a fully 3D Sonic game for the Saturn, but development moved to the Dreamcast to align with Sega's plans.[8] Takashi Iizuka led the project; Iizuka had long wanted to create a Sonic role-playing video game and felt the Dreamcast was powerful enough to achieve his vision. The game became Sonic Adventure, launched in 1998,[5] which became the bestselling Dreamcast game.[18]

Around this time, CS3 was renamed to Sega Research and Development Department 8 (R&D #8).[19] While sometimes referred to as AM8 or "Sega-AM8",[5][20] based on the R&D structure being titled the Sega Amusement Machine Research and Development (AM) teams, Sonic Team focused solely on home console games.[21] Until 2000, media referred to Sonic Team's designation as both R&D #8[22] and AM8.[23]

1999–2003: Dreamcast and Sega restructuring

In 1999, shortly after the release of Sonic Adventure, twelve Sonic Team members relocated to San Francisco to establish Sonic Team USA, while others remained in Japan. Shortly afterward, a number of key employees—including Ohshima—left Sega to form a new studio, Artoon. Sonic Team achieved success in the arcade game market in 1999 with the launch of rhythm game Samba de Amigo, released the following year for the Dreamcast. The studio also began developing online games; in 1999, they released ChuChu Rocket!, a puzzle game that made use of the Dreamcast's online capabilities. In 2000, Sonic Team launched the role-playing game Phantasy Star Online to critical and commercial success.[5]

Sega began to restructure its studios in October 2000 and spun off its software divisions into subsidiary companies.[1][5] When the departments took new names, Naka felt it important to preserve the Sonic Team brand name,[5] and the division's new legal name as a company was SONICTEAM, Ltd.[5] Naka was installed as the CEO, and Sonic Team USA became a subsidiary of the new company.[1]

Despite a number of well-received games, Sega discontinued the Dreamcast in 2001[5] and exited the hardware business.[18] Sega transitioned into a third-party developer and began developing games for multiple platforms.[18] From 2000, Sonic Team in Japan began to release fewer games, with a few releases such as the puzzle game Puyo Pop and the action game Billy Hatcher and the Giant Egg. The company changes and lack of a Sega console affected Sonic Team; according to Naka, in a 2006 interview, "Our approach was always to create strategic title concepts, which included the hardware. We do somewhat miss the idea of being able to address these constant challenges."[5] However, originality remained important for Naka; Sonic Team developed Sonic Heroes instead of Sonic Adventure 3, explored the digital card game genre with Phantasy Star Online Episode III: C.A.R.D Battle, and developed the original game Billy Hatcher.[24] Naka credited the enduring success of Sonic to the character's appeal to children. Naka's goal was to appeal to the largest audience possible and to appeal to children.[25]

Early in 2003, Sega president Hideki Sato and COO Tetsu Kamaya announced they were stepping down from their roles, with Sato being replaced by Hisao Oguchi, the head of Hitmaker. As part of Oguchi's restructuring plan, he announced his intention to consolidate Sega's studios into "four or five core operations".[26] Sonic Team was financially solvent and absorbed United Game Artists, another Sega subsidiary led by Tetsuya Mizuguchi and known for the music games Space Channel 5 (1999) and Rez (2001).[5][27]

2004–present: Reintegration and recent years

In 2004, the Japanese company Sammy acquired a controlling interest in Sega and formed Sega Sammy Corporation.[5] Prior to the merger, Sega began the process of re-integrating its subsidiaries into the main company.[28] Sonic Team USA became Sega Studios USA,[5] while SONICTEAM Ltd. became Sega's Global Entertainment 1 research and development division (GE1).[29][30] The team is still referred to as Sonic Team.[8] As of 2005, senior Sega figures including Toshihiro Nagoshi and Yu Suzuki were reporting to Naka; according to Takashi Yuda, he was involved in all Sega game development.[31] Naka announced his departure on 8 May 2006 and formed a new studio, Prope, to focus on creating original games.[5] He left Sonic Team during the development of Sonic the Hedgehog (2006), released as part of the 15-year anniversary of the Sonic franchise. Sonic the Hedgehog was panned for its bugs and design flaws; Sonic Unleashed (2008) received mixed reviews, but sold well.[8] Both games were released for the PlayStation 3 and Xbox 360; Sonic Team also developed a series of Sonic games for the Wii and Nintendo DS, such as 2007's Sonic and the Secret Rings.[18]

By 2010, Sonic Team had become part of CS Research and Development No. 2 (CS2), Sega Studios USA had been reintegrated into the Japanese team, and Iizuka had become the head of the department.[32][33] After a series of poorly received Sonic releases, Sonic Team refocused on speed and more traditional side-scrolling in Sonic the Hedgehog 4: Episode I and II, Sonic Generations, and Sonic Colors, which all received better reviews. In 2015, Iizuka recognized in an interview with Polygon that Sonic Team had prioritized shipping games over quality, and had not had enough involvement in later third-party Sonic games, such as Sonic Boom: Rise of Lyric. He hoped the Sonic Team logo would stand as a "mark of quality"; he planned to release quality games and expand the Sonic brand, while retaining the modern Sonic design.[8] Iizuka stated that doing new things with the franchise has good and point points at times.[34]Sonic Team's first Sonic game exclusive to smartphones, Sonic Runners, was released in 2015. An endless runner, it was designed to have more replay value than other games in the genre.[35] Sonic Runners received mixed reviews[36] and was unprofitable,[37] resulting in its discontinuation a year later.[38]

In 2017, Sonic Team developed and released Sonic Forces, and oversaw the development of Sonic Mania by Christian Whitehead. Forces was aimed at a broad audience of young and adult players, while Mania was focused on fans of the original Genesis games.[39] Mania became the best reviewed Sonic game in fifteen years[40] following nearly two decades of mixed reviews for the franchise.[8][41] At SXSW in March 2019, Iizuka confirmed Sonic Team was also working on a new Sonic game, which became Sonic Frontiers.[42] Sonic Team also contributed to the 2019 reboot of Sakura Wars.[43]

Sonic Team USA / Sega Studios USA

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Not to be confused with Sega Studios San Francisco.
Sega Studios USA
Formerly called
 Sonic Team USA
Division
Industry Video games
Fate Merged with Sonic Team
Founded 1999; 25 years ago (1999)
Defunct 2008
Headquarters San Francisco, California, United States
Key people
  • Takashi Iizuka
Parent Sonic Team

Sonic Team USA, later Sega Studios USA, was a division of Sega and of Sonic Team while Sonic Team was a subsidiary company. It was founded when twelve Sonic Team members, including Takashi Iizuka, relocated to San Francisco, California, in 1999,[5] and was a subsidiary of SONICTEAM, Ltd. by 2000.[1] The team worked on game development, translation,[44] and market studies in the United States,[45] until they returned to Japan and merged back into Sonic Team in 2008.[46]

Sonic Team USA translated Sonic Adventure and tested ChuChu Rocket! in America[44][45] before beginning work on Sonic Adventure 2. They took inspiration from their location in San Francisco, as well as Yosemite National Park and other areas of the United States.[44] Sonic Adventure 2 was released on 23 June 2001,[47] and was ported to the GameCube.[48] The next Sonic Team USA project was Sonic Heroes (2003), the first Sonic game developed for multiple platforms.[49] Sonic Team USA took a different approach with Heroes from the Sonic Adventure games, focusing on gameplay more similar to the Genesis games to which even casual gamers could adapt.[50]

After SONICTEAM, Ltd. merged back into Sega in 2004, Sonic Team USA was renamed Sega Studios USA.[5] The division's next project was Shadow the Hedgehog, released in 2005,[51] a spin-off starring Shadow.[52] Unlike previous games, Shadow the Hedgehog was targeted at older players and featured different gameplay styles, including the use of guns and different endings to the game.[53] Shadow the Hedgehog was critically panned for its mature themes and level design,[54][55] but was a commercial success, selling at least 1.59 million units.[56][57]

The final Sega Studios USA game was Nights: Journey of Dreams, the sequel to Nights into Dreams and the first Nights game since the cancellation of Air Nights in 2000.[58][59] Iizuka felt it was important to retain the original game's concepts while developing new mechanics, and released it on the Wii, a more family-oriented console.[60][61] Journey of Dreams was also designed to have a more European feel, in contrast to the Sonic games, which were more American. The sound and CGI were completed by Sonic Team in Japan, while Sega Studios USA handled the rest of the development for the 2007 release.[62][63]

Sega Studios USA oversaw the development of Sonic Rivals (2006) and Sonic Rivals 2 (2007) by Backbone Entertainment.[64] In 2008, Sega Studios USA merged with Sonic Team,[46] making Iizuka the head of Sonic Team and a vice president of product development for Sega.[32][33] In 2016, Iizuka relocated to Los Angeles to oversee development with the goal of making Sega's studios in Los Angeles "a centralized hub for the global brand".[46]

Games

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: List of Sonic Team games

Sonic Team has developed a number of video games, with many of them becoming bestsellers.[65][66] The studio is best known for its Sonic the Hedgehog series of platform games, which account for the majority of Sonic Team's work; the 1991 release of Sonic the Hedgehog is considered one of the most important moments in video game history, as it propelled Genesis sales and displaced Nintendo as the leading video game company.[67] Sonic Team have also developed a wide variety of other games, including action games such as Nights into Dreams, Burning Rangers, and Billy Hatcher and the Giant Egg, the online puzzle game ChuChu Rocket!, the online role-playing game Phantasy Star Online, and the music game Samba de Amigo.[5] Phantasy Star Online is credited for introducing online RPGs to consoles and was the first online RPG for many players.[68][69] According to Sean Smith of Retro Gamer, few companies could claim to have released as many AAA games over such a long period, especially between 1991 and 2000.[5] Some Sonic Team games, such as the original Sonic games for the Genesis and Nights, are considered some of the best video games ever made.[70][71] Iizuka has said Sonic Team would be open to developing a third Nights game or a sequel to Knuckles' Chaotix (1995), if Sega were to commission them.[72]

Sega and Sonic Team have been frequently criticized for their handling of Sonic the Hedgehog after the beginning of the 3D era of video games. Edwin Evans-Thirlwell of Eurogamer described the 3D Sonic games as "20-odd years of slowly accumulating bullshit", and that unlike Sonic's main competitor, Nintendo's Mario series, Sonic in 3D never had a "transcendental hit".[73] Zolani Stewart of Kotaku argued that Sonic's portrayal starting with Sonic Adventure with the addition of voice acting and a greater focus on plot and character narrative changed Sonic into "a flat, lifeless husk of a character, who spits out slogans and generally has only one personality mode, the radical attitude dude, the sad recycled image of vague '90s cultural concept."[74] Sega of America marketing director Al Nilsen and Sonic Mania developer Christian Whitehead said they felt the number of additional characters added to the series was problematic, with Whitehead describing the characters as "padding".[8] In 2015, Sega CEO Haruki Satomi acknowledged that Sega had "partially betrayed" the trust of the longtime fans of their games and hoped to focus on quality over quantity.[75]

See also

Notes

  1. ↑ Japanese: ソニックチーム Hepburn: Sonikku chīmu?

References

  1. ↑ 1.0 1.1 1.2 1.3 1.4 1.5 Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ 5.00 5.01 5.02 5.03 5.04 5.05 5.06 5.07 5.08 5.09 5.10 5.11 5.12 5.13 5.14 5.15 5.16 5.17 5.18 5.19 5.20 5.21 5.22 5.23 5.24 5.25 Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ 6.0 6.1 6.2 6.3 Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ 8.00 8.01 8.02 8.03 8.04 8.05 8.06 8.07 8.08 8.09 8.10 Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ 10.0 10.1 Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ 18.0 18.1 18.2 18.3 Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  31. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  32. ↑ 32.0 32.1 Lua error in package.lua at line 80: module 'strict' not found.
  33. ↑ 33.0 33.1 Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  36. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  38. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  39. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  40. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  41. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  42. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  43. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  44. ↑ 44.0 44.1 44.2 Lua error in package.lua at line 80: module 'strict' not found.
  45. ↑ 45.0 45.1 Lua error in package.lua at line 80: module 'strict' not found.
  46. ↑ 46.0 46.1 46.2 Lua error in package.lua at line 80: module 'strict' not found.
  47. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  48. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  49. ↑ Interview section. Lua error in package.lua at line 80: module 'strict' not found.
  50. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  51. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  52. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  53. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  54. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  55. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  56. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  57. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  58. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  59. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  60. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  61. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  62. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  63. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  64. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  65. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  66. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  67. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  68. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  69. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  70. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  71. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  72. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  73. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  74. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  75. ↑ Lua error in package.lua at line 80: module 'strict' not found.

External links

  • No URL found. Please specify a URL here or add one to Wikidata. Script error: No such module "In lang".

Lua error in package.lua at line 80: module 'strict' not found.

Retrieved from "https://infogalactic.com/w/index.php?title=Sonic_Team&oldid=726788409"