Melola Discovery

← Melola Discovery

Akses terbuka Jurnal SINTA 2

A Performance Comparison of Unity and Godot for First-Person Shooter Game Development

Decode: Jurnal Pendidikan Teknologi Informasi · Vol. 6 No. 2 (2026) · hlm. 592–598

DOI
10.51454/decode.v6i2.1804
ISSN
2775-1813, 2775-2984
Terbit
2026-07-31
Penerbit
Universitas Muhammadiyah Kendari
Lisensi
creativecommons.org/licenses/by-sa/4.0/

Abstrak

The paper presents the results of an investigation aimed at identifying the differences between the game engines Unity and Godot in terms of First-Person Shooter (FPS) development. Although the use of the two is widespread, there is a lack of research comparing their performance when subjected to similar experiments. The current study helps to address this gap by measuring the performance of these engines against six key indicators, namely RAM, CPU, frames per second (fps), installation size, export time, and exported build size. The former two engines were chosen since they are the most popular in the industry. Unity 6 and Godot 4.4.1 were put through a series of tests while running the same FPS test scenes on the same hardware (Intel Core i7-10870H, 16 GB RAM, Windows 10). RAM and CPU consumption were measured using Windows Task Manager and verified with the built-in profiler of the engines after three runs. The rest of the variables were measured directly. On average, Godot performed slightly better in terms of RAM (1,108 ± 60 MB), CPU (9.8 ± 0.4%), and fps (143 versus 36), while the installation size of Unity was found to be approximately 71 times larger (170 MB versus 12.1 GB). In addition, Godot took approximately five seconds to export, which is significantly faster than 130 seconds for Unity. The exported build sizes were similar, amounting to 114 MB and 110 MB for Godot and Unity, respectively. Overall, the findings contribute to a preliminary understanding of which engine may be more beneficial in specific conditions, which may be subject to further verification across multiple devices.

Jaringan kolaborasi para penulis

3 penulis · 3 tautan kepenulisan bersama

Arahkan kursor atau ketuk sebuah nama untuk menyorot rekan penulisnya. Klik dua kali untuk membuka halaman penulis.

  • Afiliasi tidak diketahui
  • Organisasi berbeda
  • Organisasi sama
  • Afiliasi tidak diketahui
  • Garis lebih tebal = lebih banyak artikel bersama · lingkaran lebih besar = lebih banyak artikel
Tampilkan sebagai tabel
Rekan penulisOrganisasiArtikel bersama

Afiliasi berasal dari OpenAlex; metadata OAI-PMH jurnal tidak memuatnya. Penulis tanpa ID OpenAlex dicocokkan berdasarkan nama, sehingga dua orang bisa tergabung atau satu orang bisa terpisah.

Data ini berasal dari Crossref (yang disetorkan penerbit), karena endpoint OAI-PMH milik jurnal tidak dapat di-harvest.

Sumber metadata: Crossref API (cadangan, berdasarkan ISSN) https://api.crossref.org/journals/2775-1813/works, pertama di-harvest 26 Okt 2026, terakhir terlihat 15 Nov 2026.
Metadata sebagai oai_dc, dikonversi dari Crossref
<oai_dc:dc xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"><dc:title>A Performance Comparison of Unity and Godot for First-Person Shooter Game Development</dc:title><dc:creator>Rashied, Faiz Azizan</dc:creator><dc:creator>Purbolaksono, Mahendra Dwifebri</dc:creator><dc:creator>Utama, Dody Qori</dc:creator><dc:description>&lt;jats:p&gt;The paper presents the results of an investigation aimed at identifying the differences between the game engines Unity and Godot in terms of First-Person Shooter (FPS) development. Although the use of the two is widespread, there is a lack of research comparing their performance when subjected to similar experiments. The current study helps to address this gap by measuring the performance of these engines against six key indicators, namely RAM, CPU, frames per second (fps), installation size, export time, and exported build size. The former two engines were chosen since they are the most popular in the industry. Unity 6 and Godot 4.4.1 were put through a series of tests while running the same FPS test scenes on the same hardware (Intel Core i7-10870H, 16 GB RAM, Windows 10). RAM and CPU consumption were measured using Windows Task Manager and verified with the built-in profiler of the engines after three runs. The rest of the variables were measured directly. On average, Godot performed slightly better in terms of RAM (1,108 ± 60 MB), CPU (9.8 ± 0.4%), and fps (143 versus 36), while the installation size of Unity was found to be approximately 71 times larger (170 MB versus 12.1 GB). In addition, Godot took approximately five seconds to export, which is significantly faster than 130 seconds for Unity. The exported build sizes were similar, amounting to 114 MB and 110 MB for Godot and Unity, respectively. Overall, the findings contribute to a preliminary understanding of which engine may be more beneficial in specific conditions, which may be subject to further verification across multiple devices.&lt;/jats:p&gt;</dc:description><dc:publisher>Universitas Muhammadiyah Kendari</dc:publisher><dc:date>2026-07-31</dc:date><dc:type>info:eu-repo/semantics/article</dc:type><dc:format>application/pdf</dc:format><dc:identifier>https://doi.org/10.51454/decode.v6i2.1804</dc:identifier><dc:identifier>10.51454/decode.v6i2.1804</dc:identifier><dc:source>Decode: Jurnal Pendidikan Teknologi Informasi; Vol 6 No 2 (2026); 592-598</dc:source><dc:source>2775-1813</dc:source><dc:source>2775-2984</dc:source><dc:relation>https://journal.umkendari.ac.id/decode/article/download/1804/956</dc:relation><dc:rights>https://creativecommons.org/licenses/by-sa/4.0/</dc:rights></oai_dc:dc>