4 ms·
Didn't watch the video, but is the inner Doom using the same engine and resources as the outer one? Would be really cool if it did. In that case yes, you can ha
by mojuba 4y ago
Didn't watch the video, but is the inner Doom using the same engine and resources as the outer one? Would be really cool if it did. In that case yes, you can have infinitely nested Dooms within Dooms, though you'd probably see a slowdown too.
- vesinisa 4y agoYou should watch the video! It is really informative, well-made and even funny. But to answer your question: no, it boots a completely separate instance of Doom.
- Liquid_Fire 4y agoBut you could conceivably port the original Doom (instead of Chocolate Doom) to run via this exploit, and then you would be able to nest it.
- avianlyric 4y agoI don’t think you could do the nesting because it doesn’t look like the nested doom has anyway to request additional memory. The memory for the nested doom is allocated upfront as the exploit is loaded, which would put a hard cap on the number of nested doom instances. So if you tried to load the exploit in the exploit, it would probably SEGFAULT.
- causi 4y agoWhat a shame. I was looking forward to PC benchmarks that included the number of nested Dooms it can run.
- vesinisa 4y agoGiven that he recommends "at least 16MB" of RAM .. I would wager quite a few on a modern gaming PC :)
- causi 4y agoBut he's not nesting it. That's my point.
- yellowapple 4y agoStep 1: port Doom to WASM (in a way which preserves the exploit or an equivalent mechanism) Step 2: implement a WASM runtime for DOS and pack it up as a payload for this exploit Step 3: boot the DOS Doom Step 4: boot the WASM Doom in the DOS Doom Step 5: boot another WASM Doom in the most recently-booted WASM Doom Step 6: GOTO Step 5 Step 7: ??? Step 8: profit
- bilekas 4y agoIts running the Chocolate Doom engine inside the original. Quite clever, the video is really clear too!