4A Engine: Difference between revisions
Content deleted Content added
mNo edit summary |
link added |
||
| (117 intermediate revisions by 84 users not shown) | |||
| Line 1: | Line 1: | ||
{{Short description|Graphics engine}} |
|||
The 4A Engine is a graphics middle-ware engine developed by [[4A Games]] for use in their video game [[Metro 2033]], published by [[THQ]]. It supports [[Direct3D]] APIs 9, 10, and 11, along with [[NVidia]]'s PhysX<ref>http://physxinfo.com/news/2017/metro-2033-4a-engine-specifications/</ref>, and also NVidia's 3D Vision. |
|||
{{For|the Toyota vehicle engine|Toyota A engine#4A }} |
|||
{{Infobox video game engine |
|||
| name = 4A Engine |
|||
| title = 4A Engine |
|||
| logo = 4A Engine logo.jpg |
|||
| logo caption = |
|||
| screenshot = Metro Last Light gameplay screenshot.jpg |
|||
| screenshot alt = ''[[Metro: Last Light]]'': the [[player character]], Artyom, pointing a shotgun at an enemy. |
|||
| caption = ''4A Engine'' in action on ''[[Metro: Last Light]]''. |
|||
| developer= [[4A Games]] |
|||
| released= {{Start date and age|2010|3|}} |
|||
| discontinued = |
|||
| latest release version = |
|||
| latest release date = <!-- {{Start date and age|YYYY|MM|DD|df=yes/no}} --> |
|||
| platform = [[Microsoft Windows]], [[macOS]], [[Linux]], [[PlayStation 3]], [[PlayStation 4]], [[PlayStation 5]], [[Xbox 360]], [[Xbox One]], [[Xbox Series X and Series S|Xbox Series X/S]], [[Nintendo Switch]], [[Amazon Luna|Luna]], [[Google Stadia|Stadia]] |
|||
| middleware = [[PhysX]] |
|||
| license = [[Proprietary software|Proprietary]] |
|||
| website = {{URL|https://www.4a-games.com.ua/}} |
|||
}} |
|||
The '''4A Engine''' is a [[Game engine|graphics middleware engine]] developed by [[4A Games]] for use in its video games ''[[Metro 2033 (video game)|Metro 2033]], [[Metro: Last Light]], [[Metro Exodus]]'', and ''[[Arktika.1]]''. It supports [[Direct3D]] APIs 9 through 12, [[OpenGL]] 3.2, [[Nvidia]] PhysX,<ref name=metrospecs>{{cite web|url=http://physxinfo.com/news/2017/metro-2033-4a-engine-specifications|title=Metro 2033: 4A Engine specifications|website=[[PhysX]]|date=February 20, 2010|access-date=December 29, 2017|archive-date=September 7, 2018|archive-url=https://web.archive.org/web/20180907032347/http://physxinfo.com/news/2017/metro-2033-4a-engine-specifications/|url-status=dead}}</ref> and Nvidia 3D Vision. |
|||
==Development== |
==Development== |
||
The engine was developed in [[Ukraine]] by a set of people who split off from [[GSC Game World]] a year before the release of [[S.T.A.L.K.E.R.: Shadow of Chernobyl]], notably Oles |
The engine was developed in [[Ukraine]] by a set of people who split off from [[GSC Game World]] a year before the release of ''[[S.T.A.L.K.E.R.: Shadow of Chernobyl]]'', notably Oles Shishkovtsov and Oleksandr Maksimchuk, the programmers who worked on the development of the [[X-Ray Engine|X-Ray]] engine used in the ''S.T.A.L.K.E.R.'' video game series. The engine itself is capable of running on PC, the [[Xbox 360]], and the [[PlayStation 3]].<ref name=metroeuro>{{Cite web|url=http://www.eurogamer.net/articles/digitalfoundry-metro2033-article|title=Metrospective: 4A Games vs. Digital Foundry|date=February 20, 2010|access-date=December 29, 2017|website=[[Eurogamer]]}}</ref> |
||
Shishkovtsov and his colleagues split from the development of S.T.A.L.K.E.R because that "its inherent inability to be multi-threaded, the weak and error-prone networking model, and simply awful resource and memory management which prohibited any kind of streaming or simply keeping the working set small enough for 'next-gen' consoles" along with its "terrible text-based scripting", which he explained led to the delays in the original game. |
Shishkovtsov and his colleagues split from the development of ''S.T.A.L.K.E.R'' because that "its inherent inability to be multi-threaded, the weak and error-prone networking model, and simply awful resource and memory management which prohibited any kind of streaming or simply keeping the working set small enough for 'next-gen' consoles" along with its "terrible text-based scripting", which he explained led to the delays in the original game.<ref name=metroeuro/> |
||
The |
The engine is multi-threaded such that only [[PhysX]] had a dedicated thread<ref name=metroeuro/> and uses a task-model without any pre-conditioning or pre/post-synchronising, allowing tasks to be done in parallel. When the Xbox 360 iteration had been measured during development, they were running it at "approximately 3,000 tasks per 30ms frame on Xbox 360 on [[CPU]]-intensive scenes with all hardware threads at 100 percent load". Shishkovtsov also said that the [[GeForce 6 series]] architecture of the [[RSX Reality Synthesizer]] in the PlayStation 3 proved to be very useful during development noted that there were many "wasted cycles". The engine can utilise a [[deferred shading]] pipeline, and uses tesselation for greater performance, and also has [[High dynamic range|HDR]] (complete with blue shift), real-time reflections, colour correction, film grain and noise, and the engine also supports multi-core rendering.<ref name=metroeuro2>{{cite web|url=http://www.eurogamer.net/articles/metro-2033-4a-engine-impresses-blog-entry|title=Metro 2033: 4A Engine impresses|date=February 19, 2010|access-date=December 29, 2017|website=[[Eurogamer]]}}</ref> |
||
[[Metro 2033]] |
The 4A Engine implementation of ''[[Metro 2033 (video game)|Metro 2033]]'' features volumetric fog, double PhysX precision, object blur, [[sub-surface scattering]] for skin shaders, [[parallax mapping]] on all surfaces and greater geometric detail with a less aggressive [[Level of detail (computer graphics)|LOD]](s). |
||
Using [[PhysX]], the engine uses many features such as destructible environments, and cloth and water simulations, and particles that can be fully affected by environmental factors.<ref |
Using [[PhysX]], the engine uses many features such as destructible environments, and cloth and water simulations, and particles that can be fully affected by environmental factors.<ref name=metrospecs/> The audio in the engine features [[3D audio effect|3D sound positioning]], [[Spatial music|spatialisation]] and [[attenuation]].<ref name=metroeuro2/> |
||
==Controversy== |
==Controversy== |
||
There |
There have been accusations that the 4A Engine is a modified version of the X-Ray engine used in the ''S.T.A.L.K.E.R'' series, instead of an original development. 4A denied the accusations.<ref name=shish>{{cite web|url=http://www.gamesindustry.biz/articles/4a-games-dismisses-metro-2033-engine-rumours|title=4A Games dismisses Metro 2033 engine rumours|date=February 18, 2010|access-date=December 29, 2017}}</ref> Shishkovtsov also noted that porting the original engine to consoles would have proved extremely difficult.<ref name=shish/> |
||
== |
==Games using 4A Engine== |
||
[[Metro 2033 |
* ''[[Metro 2033 (video game)|Metro 2033]]'' (2010) |
||
* ''[[Metro: Last Light]]'' (2013) |
|||
* ''[[Metro Redux]]'' (2014) |
|||
* ''[[Arktika.1]]'' (2017) |
|||
* ''[[Metro Exodus]]'' (2019) |
|||
==References== |
==References== |
||
{{reflist}} |
{{reflist}} |
||
==Further reading== |
|||
*{{Cite interview |last=Archard |first=Ben |interviewer=Alex Battaglia |title=Tech Interview: Metro Exodus, ray tracing and the 4A Engine's open world upgrades |last2=Shishkovstov |first2=Oles |url=https://www.eurogamer.net/digitalfoundry-2019-metro-exodus-tech-interview |archive-url=https://web.archive.org/web/20220929080046/https://www.eurogamer.net/digitalfoundry-2019-metro-exodus-tech-interview |archive-date=2022-09-29 |url-status=live |publisher=Eurogamer |date=February 17, 2019}} |
|||
{{Portal bar|Video games}} |
|||
{{Video game engines}} |
|||
{{DEFAULTSORT:4a Engine}} |
|||
[[Category:2010 software]] |
|||
[[Category:3D graphics software]] |
|||
[[Category:Game engines for Linux]] |
|||
[[Category:Global illumination software]] |
|||
[[Category:Metro 2033]] |
|||
[[Category:Proprietary software]] |
|||
[[Category:Video game engines]] |
|||
Latest revision as of 23:52, 15 December 2024
 | |
 4A Engine in action on Metro: Last Light. | |
| Developer(s) | 4A Games |
|---|---|
| Initial release | March 2010 |
| Middleware | PhysX |
| Platform | Microsoft Windows, macOS, Linux, PlayStation 3, PlayStation 4, PlayStation 5, Xbox 360, Xbox One, Xbox Series X/S, Nintendo Switch, Luna, Stadia |
| License | Proprietary |
| Website | www |
The 4A Engine is a graphics middleware engine developed by 4A Games for use in its video games Metro 2033, Metro: Last Light, Metro Exodus, and Arktika.1. It supports Direct3D APIs 9 through 12, OpenGL 3.2, Nvidia PhysX,[1] and Nvidia 3D Vision.
Development
[edit]The engine was developed in Ukraine by a set of people who split off from GSC Game World a year before the release of S.T.A.L.K.E.R.: Shadow of Chernobyl, notably Oles Shishkovtsov and Oleksandr Maksimchuk, the programmers who worked on the development of the X-Ray engine used in the S.T.A.L.K.E.R. video game series. The engine itself is capable of running on PC, the Xbox 360, and the PlayStation 3.[2]
Shishkovtsov and his colleagues split from the development of S.T.A.L.K.E.R because that "its inherent inability to be multi-threaded, the weak and error-prone networking model, and simply awful resource and memory management which prohibited any kind of streaming or simply keeping the working set small enough for 'next-gen' consoles" along with its "terrible text-based scripting", which he explained led to the delays in the original game.[2]
The engine is multi-threaded such that only PhysX had a dedicated thread[2] and uses a task-model without any pre-conditioning or pre/post-synchronising, allowing tasks to be done in parallel. When the Xbox 360 iteration had been measured during development, they were running it at "approximately 3,000 tasks per 30ms frame on Xbox 360 on CPU-intensive scenes with all hardware threads at 100 percent load". Shishkovtsov also said that the GeForce 6 series architecture of the RSX Reality Synthesizer in the PlayStation 3 proved to be very useful during development noted that there were many "wasted cycles". The engine can utilise a deferred shading pipeline, and uses tesselation for greater performance, and also has HDR (complete with blue shift), real-time reflections, colour correction, film grain and noise, and the engine also supports multi-core rendering.[3]
The 4A Engine implementation of Metro 2033 features volumetric fog, double PhysX precision, object blur, sub-surface scattering for skin shaders, parallax mapping on all surfaces and greater geometric detail with a less aggressive LOD(s).
Using PhysX, the engine uses many features such as destructible environments, and cloth and water simulations, and particles that can be fully affected by environmental factors.[1] The audio in the engine features 3D sound positioning, spatialisation and attenuation.[3]
Controversy
[edit]There have been accusations that the 4A Engine is a modified version of the X-Ray engine used in the S.T.A.L.K.E.R series, instead of an original development. 4A denied the accusations.[4] Shishkovtsov also noted that porting the original engine to consoles would have proved extremely difficult.[4]
Games using 4A Engine
[edit]- Metro 2033 (2010)
- Metro: Last Light (2013)
- Metro Redux (2014)
- Arktika.1 (2017)
- Metro Exodus (2019)
References
[edit]- ^ a b "Metro 2033: 4A Engine specifications". PhysX. February 20, 2010. Archived from the original on September 7, 2018. Retrieved December 29, 2017.
- ^ a b c "Metrospective: 4A Games vs. Digital Foundry". Eurogamer. February 20, 2010. Retrieved December 29, 2017.
- ^ a b "Metro 2033: 4A Engine impresses". Eurogamer. February 19, 2010. Retrieved December 29, 2017.
- ^ a b "4A Games dismisses Metro 2033 engine rumours". February 18, 2010. Retrieved December 29, 2017.
Further reading
[edit]- Archard, Ben; Shishkovstov, Oles (February 17, 2019). "Tech Interview: Metro Exodus, ray tracing and the 4A Engine's open world upgrades" (Interview). Interviewed by Alex Battaglia. Eurogamer. Archived from the original on 2022-09-29.
