Non-Euclidean Doom: what happens to a game when pi is not pi (2022) [video]
The YouTube video explores Doom's history, development, open-sourcing, and platform adaptations. It discusses altering pi in the source code, leading to network vulnerabilities, non-euclidean geometry, and gameplay changes. Collision detection in the game remains unchanged.
Read original article
The YouTube video delves into the history of the game Doom, covering its development, open-sourcing, and adaptation to different platforms. It highlights the consequences of altering the value of pi in the game's source code, resulting in network vulnerabilities, non-euclidean geometry, and altered gameplay experiences. Surprisingly, collision detection within the game remains unaffected by these modifications.
Related
Microsoft and Qualcomm – Blame for Broken Arm Promises? [video]
The YouTube video discusses Microsoft's role in the ARM platform and Windows OS, impacting users, developers, and ecosystem partners. It covers concerns about advertising, data mining, software development challenges, Nvidia's Arm acquisition bid, and the industry shift towards Arm architecture.
Eric Weinstein and Terrence Howard Debate 1 x 1 = 2 On The Joe Rogan Podcast [video]
The YouTube video covers mathematics, physics, and philosophy topics such as addition vs. multiplication correlation, theory inconsistencies, zero's philosophical importance, currency devaluation, risks of money printing, and partnership complexities.
Whose bug is this anyway?? (2012)
Patrick Wyatt shares bug experiences from game development, including issues in StarCraft and Guild Wars. Compiler problems caused bugs, emphasizing the need for consistent tools and work-life balance in development.
Brian Lunduke: "macOS Sucks" [video]
A YouTube video critiques Mac OS X for design flaws, limited multitasking, and game options. It discusses Macintosh history, highlighting Multifinder's introduction for multitasking and early good game availability despite high costs.
Moiré Error in Doom
The Moiré error in Doom versions pre-v1.4 affected tall rooms, causing a flashing screen pattern near walls. Fixed in v1.4 for normal heights, v1.9 still had severe issues in extreme heights. The bug stemmed from numeric overflow in linedefs, leading to infinite tiling of a neighboring sector's flat, resembling a large-scale slime trail.
3 commentsRelated
Microsoft and Qualcomm – Blame for Broken Arm Promises? [video]
The YouTube video discusses Microsoft's role in the ARM platform and Windows OS, impacting users, developers, and ecosystem partners. It covers concerns about advertising, data mining, software development challenges, Nvidia's Arm acquisition bid, and the industry shift towards Arm architecture.
Eric Weinstein and Terrence Howard Debate 1 x 1 = 2 On The Joe Rogan Podcast [video]
The YouTube video covers mathematics, physics, and philosophy topics such as addition vs. multiplication correlation, theory inconsistencies, zero's philosophical importance, currency devaluation, risks of money printing, and partnership complexities.
Whose bug is this anyway?? (2012)
Patrick Wyatt shares bug experiences from game development, including issues in StarCraft and Guild Wars. Compiler problems caused bugs, emphasizing the need for consistent tools and work-life balance in development.
Brian Lunduke: "macOS Sucks" [video]
A YouTube video critiques Mac OS X for design flaws, limited multitasking, and game options. It discusses Macintosh history, highlighting Multifinder's introduction for multitasking and early good game availability despite high costs.
Moiré Error in Doom
The Moiré error in Doom versions pre-v1.4 affected tall rooms, causing a flashing screen pattern near walls. Fixed in v1.4 for normal heights, v1.9 still had severe issues in extreme heights. The bug stemmed from numeric overflow in linedefs, leading to infinite tiling of a neighboring sector's flat, resembling a large-scale slime trail.