# Making a doom clone would be (technically) possible

**URL:** <https://forum.makecode.com/t/making-a-doom-clone-would-be-technically-possible/12985>\
**Category:** Arcade\
**Created:** [April 6, 2022, 2:38pm UTC](https://forum.makecode.com/t/making-a-doom-clone-would-be-technically-possible/12985 "2022-04-06T14:38:45Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![hasanchik](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/hasanchik/32/5885_2.png) [@hasanchik](https://forum.makecode.com/u/hasanchik)\
**Post date:** [April 21, 2022, 4:38pm UTC](https://forum.makecode.com/t/making-a-doom-clone-would-be-technically-possible/12985/7 "2022-04-21T16:38:35Z")

</div>

Well…  
Just take a look, please…

> [@3D Renderer Demo](https://forum.makecode.com/t/3d-renderer-demo/2294):
>
> Hi all. I’m new here. I thought I would try making a 3d renderer for Arcade, and here’s what I came up with: [2020-06-02\_12-03-43] Controls: Joystick: Move camera A: Cycle the lighting model (None, Flat, Dither) B: Toggle wireframe overdraw The renderer has an optional depth buffer, but using it causes an out-of-memory error (err 22) on my PyGamer! I’m trying to think of a clever way to solve that. The depth buffer can be disabled in engine.ts, in case you wanted to try running this on yo…

Its people already did this. What im thinking of is a **raycast engine** , not a full on 3d renderer like you mentioned. Since hardware is very slow with actual 3d rendering i think raycast engines are the way to making good-looking 3d scenes.

---

_[View the full topic](https://forum.makecode.com/t/making-a-doom-clone-would-be-technically-possible/12985)._
