Hidden Palace - User contributions [en]

Disney Universe (Debug prototype)

2026-07-21T04:46:31Z

Alepou: Formatting and clarification.

{{Prototype
|Page name=Disney Universe (Debug prototype)
|status=Released
|releasedby=Anonymous
|filereleasedate=November 9, 2022
|origin_type=4chan
|origin_files=DisneyUniverse.7z\DisneyUniverseDebug.gcm
|origin_lot=4chan Eurocom and THQ leak
|game=Disney Universe
|system=Nintendo Wii
|genre=Action Adventure
|release_date={{RegionDate|NA|Oct 25, 2011}} {{RegionDate|AU|Oct 27, 2011}} {{RegionDate|EU|Oct 28, 2011}}
|unreleased=No
}}
{{Download
|file=Disney Universe (Debug prototype).zip
}}
A prototype of '''Disney Universe''' for the Nintendo Wii.
==Notes==
* USA build.
* Unknown Build Date.
* The build does not work on Dolphin 2412.
* The build works on Dolphin 2603a.
* Going past the build's title screen on Dolphin 2603a brings up the error/warning "Invalid write to 0x00000010, PC = 0x805be64c; the game probably would have crashed on real hardware."
* The build's title screen error/warning can be skipped.
* Pressing 1 on the Wii Remote brings up the Debug Menu.
<gallery>
File:Disney Universe intro movie placeholder.png|Intro Movie Placeholder
File:Disney Universe Main Menu.png|The Main Menu (With Bonus Debug Text)
File:Disney Universe world select.png|The World Select Screen
File:Disney Universe Debug Menu.png|The Debug Menu
</gallery>{{Prototype Footer|{{Navbox prototype|Disney Universe}}}}

Disney Universe (Debug prototype)

2026-07-21T04:38:43Z

Alepou:

{{Prototype
|Page name=Disney Universe (Debug prototype)
|status=Released
|releasedby=Anonymous
|filereleasedate=November 9, 2022
|origin_type=4chan
|origin_files=DisneyUniverse.7z\DisneyUniverseDebug.gcm
|origin_lot=4chan Eurocom and THQ leak
|game=Disney Universe
|system=Nintendo Wii
|genre=Action Adventure
|release_date={{RegionDate|NA|Oct 25, 2011}} {{RegionDate|AU|Oct 27, 2011}} {{RegionDate|EU|Oct 28, 2011}}
|unreleased=No
}}
{{Download
|file=Disney Universe (Debug prototype).zip
}}
A prototype of '''Disney Universe''' for the Nintendo Wii.
==Notes==
* USA build.
* Unknown Build Date.
* The build does not work on Dolphin 2412.
* The build works on Dolphin 2603a.
* Going past the build's title screen on Dolphin 2603a brings up the error "Invalid write to 0x00000010, PC = 0x805be64c; the game probably would have crashed on real hardware."
* Pressing 1 on the Wii Remote brings up the Debug Menu.
<gallery>
File:Disney Universe intro movie placeholder.png|Intro Movie Placeholder
File:Disney Universe Main Menu.png|The Main Menu (With Bonus Debug Text)
File:Disney Universe world select.png|The World Select Screen
File:Disney Universe Debug Menu.png|The Debug Menu
</gallery>{{Prototype Footer|{{Navbox prototype|Disney Universe}}}}

File:Disney Universe Main Menu.png

2026-07-21T04:32:00Z

Alepou:

The main menu of the Disney Universe debug prototype

File:Disney Universe world select.png

2026-07-21T04:29:30Z

Alepou:

The world select menu in the Disney Universe debug prototype.

File:Disney Universe Debug Menu.png

2026-07-21T04:28:22Z

Alepou:

The debug menu in the Disney Universe debug prototype

File:Disney Universe intro movie placeholder.png

2026-07-21T04:26:47Z

Alepou:

The place holder to the Disney Universe debug prototype

File:Disney Universe (Debug prototype)-title.png

2026-07-21T04:21:42Z

Alepou: The Disney Universe (Debug Prototype) title screen

== Summary ==
The Disney Universe (Debug Prototype) title screen

User:Alepou

2026-07-19T14:29:09Z

Alepou:

== Guides ==
=== Running 3DO Demos and Prototypes on macOS and RetroArch ===
''''' This guide exists because macOS is very picky with its files. And because 3DO prototypes/games/demos were not signed, therefore they are unable to run. This is why most games haven't been documented as of now. This guide applies to most prototypes and demos in the 3DO game space.'''''

Unlike most people would think, the standard, original retail BIOS is actually stricter than a patched BIOS. It will reject any unsigned prototypes/demos before even running the game, despite the region the BIOS or game is from being correct.

The standard retail BIOS, <code>panafz10.bin</code>, or any 3DO BIOS for that matter, needs to be patched in order for most prototype games/demos to boot. You must use an RSA-patched / decrypted BIOS file. It needs to be non-region-locked, and it needs to not check for signatures.

If you're on macOS (like [[Special:Contributions/Loukas|me]]) you're going to most likely need to <code>xattr</code> the .bin and .cue files for the game along with the BIOS file using <code>xattr -cr "/path/to/folder"</code> in order to bypass quarantine flags. You may also need to <code>xattr</code> ''The 3DO Company - 3DO (Opera)'' core on macOS after installing it. Then, it is the same as running any 3DO game on RetroArch. <code>xattr -cr "/path/to/folder"</code> de-quarantines the whole folder of all quarantines. Be careful on what you use it for. You never know what code might be executed on your machine. Alternatively, you can use <code>xattr -dr com.apple.quarantine "/path/to/file"</code> for each file in particular. [[User:Alepou|Alepou]] ([[User talk:Alepou|talk]]) 01:41, June 11, 2026 (UTC)

===Running 3DO demos/prototypes on Asahi Linux via RetroArch===
'''''This guide exists because SOMEONE had to document Asahi Linux. And since there is so little information on Asahi and very few people actually have it installed, I decided to be the test subject.'''''

Step 1. Install RetroArch via FlatPak

Step 2. Download the 3DO Core MANUALLY. if you download from the integrated download menu, RetroArch stops working

Download cores from https://github.com/christianhaitian/retroarch-cores/tree/master/aarch64/opera_libretro.so.zip (This is the only repository I found that works with Asahi Linux's ARM architecture.)

Step 3. Paste yout core into <code>~/.var/app/org.libretro.RetroArch/config/retroarch/cores/</code>

Step 4.Put your RSA patched 3DO BIOS in <code>~/.var/app/org.libretro.RetroArch/config/retroarch/system/</code> ''which in my case is a patched''' <code>panafz10.bin</code>''' BIOS''

Step 5. Run the <code>.cue</code> file (or whatever file format you have for your 3DO prototype)

Step 6. Have fun!

Guide by [[User:Alepou|Alepou]] ([[User talk:Alepou|talk]]) 02:34, June 27, 2026 (UTC)

{{User stats|{{PAGENAME}}}}

User:Alepou

2026-07-19T14:27:42Z

Alepou:

== Guides ==
=== Running 3DO Demos and Prototypes on macOS and RetroArch ===
''''' This guide exists because macOS is very picky with its files. And because 3DO prototypes/games/demos were not signed, therefore they are unable to run. This is why most games haven't been documented as of now. This guide applies to most prototypes and demos in the 3DO game space.'''''

Unlike most people would think, the standard, original retail BIOS is actually stricter than a patched BIOS. It will reject any unsigned prototypes/demos before even running the game, despite the region the BIOS or game is from being correct.

The standard retail BIOS, <code>panafz10.bin</code>, or any 3DO BIOS for that matter, needs to be patched in order for most prototype games/demos to boot. You must use an RSA-patched / decrypted BIOS file. It needs to be non-region-locked, and it needs to not check for signatures.

If you're on macOS (like [[Special:Contributions/Loukas|me]]) you're going to most likely need to <code>xattr</code> the .bin and .cue files for the game along with the BIOS file using <code>xattr -cr "/path/to/folder"</code> in order to bypass quarantine flags. You may also need to <code>xattr</code> ''The 3DO Company - 3DO (Opera)'' core on macOS after installing it. Then, it is the same as running any 3DO game on RetroArch. <code>xattr -cr "/path/to/folder"</code> de-quarantines the whole folder of all quarantines. Be careful on what you use it for. You never know what code might be executed on your machine. Alternatively, you can use <code>xattr -dr com.apple.quarantine "/path/to/file"</code> for each file in particular. [[User:Alepou|Loukas]] ([[User talk:Alepou|talk]]) 01:41, June 11, 2026 (UTC)

===Running 3DO demos/prototypes on Asahi Linux via RetroArch===
'''''This guide exists because SOMEONE had to document Asahi Linux. And since there is so little information on Asahi and very few people actually have it installed, I decided to be the test subject.'''''

Step 1. Install RetroArch via FlatPak

Step 2. Download the 3DO Core MANUALLY. if you download from the integrated download menu, RetroArch stops working

Download cores from https://github.com/christianhaitian/retroarch-cores/tree/master/aarch64/opera_libretro.so.zip (This is the only repository I found that works with Asahi Linux's ARM architecture.)

Step 3. Paste yout core into <code>~/.var/app/org.libretro.RetroArch/config/retroarch/cores/</code>

Step 4.Put your RSA patched 3DO BIOS in <code>~/.var/app/org.libretro.RetroArch/config/retroarch/system/</code> ''which in my case is a patched''' <code>panafz10.bin</code>''' BIOS''

Step 5. Run the <code>.cue</code> file (or whatever file format you have for your 3DO prototype)

Step 6. Have fun!

Guide by [[User:Alepou|Loukas]] ([[User talk:Alepou|talk]]) 02:34, June 27, 2026 (UTC)

{{User stats|{{PAGENAME}}}}

User:Alepou

2026-07-19T14:20:00Z

Alepou: Request to have my username changed to Alepou

= Request to have my username changed to Alepou =
== Guides ==
=== Running 3DO Demos and Prototypes on macOS and RetroArch ===
''''' This guide exists because macOS is very picky with its files. And because 3DO prototypes/games/demos were not signed, therefore they are unable to run. This is why most games haven't been documented as of now. This guide applies to most prototypes and demos in the 3DO game space.'''''

Unlike most people would think, the standard, original retail BIOS is actually stricter than a patched BIOS. It will reject any unsigned prototypes/demos before even running the game, despite the region the BIOS or game is from being correct.

The standard retail BIOS, <code>panafz10.bin</code>, or any 3DO BIOS for that matter, needs to be patched in order for most prototype games/demos to boot. You must use an RSA-patched / decrypted BIOS file. It needs to be non-region-locked, and it needs to not check for signatures.

If you're on macOS (like [[Special:Contributions/Loukas|me]]) you're going to most likely need to <code>xattr</code> the .bin and .cue files for the game along with the BIOS file using <code>xattr -cr "/path/to/folder"</code> in order to bypass quarantine flags. You may also need to <code>xattr</code> ''The 3DO Company - 3DO (Opera)'' core on macOS after installing it. Then, it is the same as running any 3DO game on RetroArch. <code>xattr -cr "/path/to/folder"</code> de-quarantines the whole folder of all quarantines. Be careful on what you use it for. You never know what code might be executed on your machine. Alternatively, you can use <code>xattr -dr com.apple.quarantine "/path/to/file"</code> for each file in particular. [[User:Loukas|Loukas]] ([[User talk:Loukas|talk]]) 01:41, June 11, 2026 (UTC)

===Running 3DO demos/prototypes on Asahi Linux via RetroArch===
'''''This guide exists because SOMEONE had to document Asahi Linux. And since there is so little information on Asahi and very few people actually have it installed, I decided to be the test subject.'''''

Step 1. Install RetroArch via FlatPak

Step 2. Download the 3DO Core MANUALLY. if you download from the integrated download menu, RetroArch stops working

Download cores from https://github.com/christianhaitian/retroarch-cores/tree/master/aarch64/opera_libretro.so.zip (This is the only repository I found that works with Asahi Linux's ARM architecture.)

Step 3. Paste yout core into <code>~/.var/app/org.libretro.RetroArch/config/retroarch/cores/</code>

Step 4.Put your RSA patched 3DO BIOS in <code>~/.var/app/org.libretro.RetroArch/config/retroarch/system/</code> ''which in my case is a patched''' <code>panafz10.bin</code>''' BIOS''

Step 5. Run the <code>.cue</code> file (or whatever file format you have for your 3DO prototype)

Step 6. Have fun!

Guide by [[User:Loukas|Loukas]] ([[User talk:Loukas|talk]]) 02:34, June 27, 2026 (UTC)

{{User stats|{{PAGENAME}}}}

User:Alepou

2026-06-27T02:49:46Z

Alepou: formatting.

== Guides ==
=== Running 3DO Demos and Prototypes on macOS and RetroArch ===
''''' This guide exists because macOS is very picky with its files. And because 3DO prototypes/games/demos were not signed, therefore they are unable to run. This is why most games haven't been documented as of now. This guide applies to most prototypes and demos in the 3DO game space.'''''

Unlike most people would think, the standard, original retail BIOS is actually stricter than a patched BIOS. It will reject any unsigned prototypes/demos before even running the game, despite the region the BIOS or game is from being correct.

The standard retail BIOS, <code>panafz10.bin</code>, or any 3DO BIOS for that matter, needs to be patched in order for most prototype games/demos to boot. You must use an RSA-patched / decrypted BIOS file. It needs to be non-region-locked, and it needs to not check for signatures.

If you're on macOS (like [[Special:Contributions/Loukas|me]]) you're going to most likely need to <code>xattr</code> the .bin and .cue files for the game along with the BIOS file using <code>xattr -cr "/path/to/folder"</code> in order to bypass quarantine flags. You may also need to <code>xattr</code> ''The 3DO Company - 3DO (Opera)'' core on macOS after installing it. Then, it is the same as running any 3DO game on RetroArch. <code>xattr -cr "/path/to/folder"</code> de-quarantines the whole folder of all quarantines. Be careful on what you use it for. You never know what code might be executed on your machine. Alternatively, you can use <code>xattr -dr com.apple.quarantine "/path/to/file"</code> for each file in particular. [[User:Loukas|Loukas]] ([[User talk:Loukas|talk]]) 01:41, June 11, 2026 (UTC)

===Running 3DO demos/prototypes on Asahi Linux via RetroArch===
'''''This guide exists because SOMEONE had to document Asahi Linux. And since there is so little information on Asahi and very few people actually have it installed, I decided to be the test subject.'''''

Step 1. Install RetroArch via FlatPak

Step 2. Download the 3DO Core MANUALLY. if you download from the integrated download menu, RetroArch stops working

Download cores from https://github.com/christianhaitian/retroarch-cores/tree/master/aarch64/opera_libretro.so.zip (This is the only repository I found that works with Asahi Linux's ARM architecture.)

Step 3. Paste yout core into <code>~/.var/app/org.libretro.RetroArch/config/retroarch/cores/</code>

Step 4.Put your RSA patched 3DO BIOS in <code>~/.var/app/org.libretro.RetroArch/config/retroarch/system/</code> ''which in my case is a patched''' <code>panafz10.bin</code>''' BIOS''

Step 5. Run the <code>.cue</code> file (or whatever file format you have for your 3DO prototype)

Step 6. Have fun!

Guide by [[User:Loukas|Loukas]] ([[User talk:Loukas|talk]]) 02:34, June 27, 2026 (UTC)

{{User stats|{{PAGENAME}}}}

User:Alepou

2026-06-27T02:34:31Z

Alepou:

== Guides ==
=== Running 3DO Demos and Prototypes on macOS and RetroArch ===
''''' This guide exists because macOS is very picky with its files. And because 3DO prototypes/games/demos were not signed, therefore they are unable to run. This is why most games haven't been documented as of now. This guide applies to most prototypes and demos in the 3DO game space.'''''

Unlike most people would think, the standard, original retail BIOS is actually stricter than a patched BIOS. It will reject any unsigned prototypes/demos before even running the game, despite the region the BIOS or game is from being correct.

The standard retail BIOS, <code>panafz10.bin</code>, or any 3DO BIOS for that matter, needs to be patched in order for most prototype games/demos to boot. You must use an RSA-patched / decrypted BIOS file. It needs to be non-region-locked, and it needs to not check for signatures.

If you're on macOS (like [[Special:Contributions/Loukas|me]]) you're going to most likely need to <code>xattr</code> the .bin and .cue files for the game along with the BIOS file using <code>xattr -cr "/path/to/folder"</code> in order to bypass quarantine flags. You may also need to <code>xattr</code> ''The 3DO Company - 3DO (Opera)'' core on macOS after installing it. Then, it is the same as running any 3DO game on RetroArch. <code>xattr -cr "/path/to/folder"</code> de-quarantines the whole folder of all quarantines. Be careful on what you use it for. You never know what code might be executed on your machine. Alternatively, you can use <code>xattr -dr com.apple.quarantine "/path/to/file"</code> for each file in particular. [[User:Loukas|Loukas]] ([[User talk:Loukas|talk]]) 01:41, June 11, 2026 (UTC)

===Running 3DO demos/prototypes on Asahi Linux via RetroArch===
'''''This guide exists because SOMEONE had to document Asahi Linux. And since there is so little information on Asahi and very few people actually have it installed, I decided to be the test subject.'''''

Step 1. Install RetroArch via FlatPak

Step 2. Download the 3DO Core MANUALLY. if you download from the integrated download menu, RetroArch stops working

Download cores from https://github.com/christianhaitian/retroarch-cores/tree/master/aarch64/opera_libretro.so.zip (This is the only repository I found that works with Asahi Linux's ARM architecture.)

Step 3. Paste yout core into <code>/home/[YOUR NAME]/.var/app/org.libretro.RetroArch/config/retroarch/cores/</code>

Step 4.Put your RSA patched 3DO BIOS in <code>/home/[YOUR NAME]/.var/app/org.libretro.RetroArch/config/retroarch/system/</code> ''which in my case is a patched'''' <code>panafz10.bin</code>''' BIOS''

Step 5. Run the <code>.cue</code> file (or whatever file format you have for your 3DO prototype)

Step 6. Have fun!

Guide by [[User:Loukas|Loukas]] ([[User talk:Loukas|talk]]) 02:34, June 27, 2026 (UTC)

{{User stats|{{PAGENAME}}}}

User:Alepou

2026-06-27T02:27:39Z

Alepou: Added an Asahi Linux guide on how to run 3DO prototypes

== Guides ==
=== Running 3DO Demos and Prototypes on macOS and RetroArch ===
''''' This guide exists because macOS is very picky with its files. And because 3DO prototypes/games/demos were not signed, therefore they are unable to run. This is why most games haven't been documented as of now. This guide applies to most prototypes and demos in the 3DO game space.'''''

Unlike most people would think, the standard, original retail BIOS is actually stricter than a patched BIOS. It will reject any unsigned prototypes/demos before even running the game, despite the region the BIOS or game is from being correct.

The standard retail BIOS, <code>panafz10.bin</code>, or any 3DO BIOS for that matter, needs to be patched in order for most prototype games/demos to boot. You must use an RSA-patched / decrypted BIOS file. It needs to be non-region-locked, and it needs to not check for signatures.

If you're on macOS (like [[Special:Contributions/Loukas|me]]) you're going to most likely need to <code>xattr</code> the .bin and .cue files for the game along with the BIOS file using <code>xattr -cr "/path/to/folder"</code> in order to bypass quarantine flags. You may also need to <code>xattr</code> ''The 3DO Company - 3DO (Opera)'' core on macOS after installing it. Then, it is the same as running any 3DO game on RetroArch. <code>xattr -cr "/path/to/folder"</code> de-quarantines the whole folder of all quarantines. Be careful on what you use it for. You never know what code might be executed on your machine. Alternatively, you can use <code>xattr -dr com.apple.quarantine "/path/to/file"</code> for each file in particular. [[User:Loukas|Loukas]] ([[User talk:Loukas|talk]]) 01:41, June 11, 2026 (UTC)

===Running 3DO demos/prototypes on Asahi Linux via RetroArch===
'''''This guide exists because SOMEONE had to document Asahi Linux. And since there is so little information on Asahi and very few people actually have it installed, I decided to be the test subject.'''''

Step 1. Install RetroArch via FlatPak

Step 2. Download the 3DO Core MANUALLY. if you download from the integrated download menu, RetroArch stops working

Download cores from https://github.com/christianhaitian/retroarch-cores/tree/master/aarch64/opera_libretro.so.zip (This is the only repository I found that works with Asahi Linux's ARM architecture.)

Step 3. Paste yout core into <code>/home/[YOUR NAME]/.var/app/org.libretro.RetroArch/config/retroarch/cores/</code>

Step 4.Put your RSA patched 3DO BIOS in <code>/home/[YOUR NAME]/.var/app/org.libretro.RetroArch/config/retroarch/system/</code> ''which in my case is a patched'''' <code>panafz10.bin</code>''' BIOS''

Step 5. Run the <code>.cue</code> file (or whatever file format you have for your 3DO prototype)

Step 6. Have fun!

{{User stats|{{PAGENAME}}}}

File:3DO-Fictional-Developer-Presents-Bogus-Title.png

2026-06-11T16:02:13Z

Alepou:

The opening credits for most 3DO prototype and demos. Which are empty.

File:Wolfenstein 3D (1995-09-07 Pre-release)-Opening-Screen.png

2026-06-11T16:00:36Z

Alepou: Loukas moved page File:Wolfenstein 3D (1995-09-07 Pre-release)-Opening-Screen.png to File:3DO-Fictional-Developer-Presents-Bogus-Title.png: The image does not only apply to Wolfenstein 3D for the 3DO, but most 3DO prototypes and demos.

#REDIRECT [[File:3DO-Fictional-Developer-Presents-Bogus-Title.png]]

File:3DO-Fictional-Developer-Presents-Bogus-Title.png

2026-06-11T16:00:36Z

The opening credits for Wolfenstein 3D for the 3DO prototype. Which are empty.

Wolfenstein 3D (Sep 7, 1995 prototype)

2026-06-11T03:06:00Z

Alepou:

{{Prototype
|titlescreen=Wolfenstein 3D (1995-09-07 Pre-release)-260607-193903.png
|Page name=Wolfenstein 3D (Sep 7, 1995 prototype)
|builddate=Sep 7, 1995
|status=Released
|dumper=Anonymous
|releasedby=archive3DO
|origin_type=CD-R
|origin_labels=9/7/95<br>Wolf 3D - 3DO
|game=Wolfenstein 3D
|system=3DO
|genre=FPS
|release_date={{RegionDate|US|Oct 19, 1995}}
|unreleased=No
}}
{{Download
|file=Wolfenstein 3D (1995-09-07 Pre-release).zip
}}
A prototype of Wolfenstein 3D for the 3DO.

== Notes ==

* The opening credits mention no company developing the game (because the game wasn't finished yet to include company credits, so they used the 3DO placeholder).

== Screenshots ==
<gallery>
File:Wolfenstein 3D (1995-09-07 Pre-release)-Opening-Screen.png|Opening Credits (Classic 3DO Placeholder)
File:Wolfenstein 3D (1995-09-07 Pre-release)-Level-Select.png|Level Select screen.
File:Wolfenstein 3D (1995-09-07 Pre-release)-Difficulty-Select.png|Difficulty Select screen
</gallery>{{Prototype Footer|{{Navbox prototype|Wolfenstein 3D}}}}

File:Wolfenstein 3D (1995-09-07 Pre-release)-Difficulty-Select.png

2026-06-11T03:01:58Z

Alepou:

Wolfenstein 3D prototype's Difficulty Select screen for the 3DO. It contains "can I play daddy?" as an option.

File:Wolfenstein 3D (1995-09-07 Pre-release)-Level-Select.png

2026-06-11T03:00:57Z

Alepou:

Wolfenstein 3D prototype's level select screen for the 3DO

File:3DO-Fictional-Developer-Presents-Bogus-Title.png

2026-06-11T02:57:35Z

Alepou:

The opening credits for Wolfenstein 3D for the 3DO prototype. Which are empty.

User:Alepou

2026-06-11T01:41:37Z

Alepou: Formatting.

User:Alepou

2026-06-11T01:11:24Z

Alepou: Added a guide for 3DO Prototype/Demo running on RetroArch and macOS to my profile.

== Running 3DO Demos and Prototypes on macOS and RetroArch (a guide) ==

=== This guide exists because macOS is very picky with its files. And because 3DO prototypes/games/demos were not signed, therefore they are unable to run. This is why most games haven't been documented as of now. This guide applies to most prototypes and demos in the 3DO game space. ===
The standard retail BIOS, <code>panafz10.bin</code>, or any 3DO BIOS for that matter, needs to be patched in order for most prototype games/demos to boot. You must use an RSA-patched / decrypted BIOS file. It needs to be non-region-locked, and it needs to not check for signatures.

If you're on macOS (like [[Special:Contributions/Loukas|me]]) you're going to most likely need to <code>xattr</code> the .bin and .cue files for the game along with the BIOS file using <code>xattr -cr "/path/to/folder"</code> in order to bypass quarantine flags. You may also need to <code>xattr</code> ''The 3DO Company - 3DO (Opera)'' core on macOS after installing it. Then, it is the same as running any 3DO game on RetroArch. <code>xattr -cr "/path/to/folder"</code> de-quarantines the whole folder of all quarantines. Be careful on what you use it for. You never know what code might be executed on your machine. Alternatively, you can use <code>xattr -dr com.apple.quarantine "/path/to/file"</code> for each file in particular.{{User stats|{{PAGENAME}}}}

Invizimals: The Lost Kingdom (Aug 30, 2013 prototype)

2026-06-09T14:30:19Z

Alepou: Formatting.

{{Prototype
|titlescreen=Invizimals- The Lost Kingdom (Aug 30, 2013 prototype)-title.png
|Page name=Invizimals: The Lost Kingdom (Aug 30, 2013 prototype)
|builddate=Aug 30, 2013
|status=Released
|dumper=imagisphere
|releasedby=imagisphere
|filereleasedate=October 21, 2025
|origin_type=Playstation 3 DECHA00A HDD
|game=Invizimals: The Lost Kingdom
|system=PlayStation 3
|genre=Action-Adventure
|release_date={{RegionDate|EU|Oct 30, 2013}} {{RegionDate|US|Oct 30, 2014}}
|unreleased=No
}}
{{Download
|file=Invizimals The Lost Kingdom (Aug 30, 2013 prototype).zip
}}
A prototype of '''Invizimals: The Lost Kingdom''' for the Playstation 3.
==Origin Notes==
* The serial is NPEA00461 (EU Region).
* The build date was based on the most recent file modification date.
* It was found on the hdd <code>00-27450032-0055125-DECHA00A</code>.

== Game Notes ==
* An "Arrival Placeholder FMV" screen is present where a cinematic video would play, indicating the final FMV assets had not yet been produced at this build stage.
* A "Fly Cam" debug toggle is present in the pause menu alongside standard options, suggesting developer tools were not removed at this build stage.
* In the prototype, Ocelotl is introduced a little later than in the release. Specifically in the outside of the temple, while in the release Ocelotl is introduced inside of the temple.
* Enemies don’t show up at the intro’s very beginning. Only later on
* There's no tutorial on how to fight enemies at the beginning.
* When in a part of the game where the game instructs you to use your controller for balance, it says "SIXAXIS" instead of "use the wireless controller to balance."
* Camera is very buggy during gameplay.
* Most (if any) of the things that would cost Z-Sparks to unlock don’t cost anything at all.
* When selecting a special ability with the D-Pad, any ability apart from Ocelotl's two abilities show "PLACEHOLDER LOCKED"
* Levels are titled 'Temple1', 'Temple2', so on.

== Screenshots ==
<gallery>
File:Invizimals The Lost Kingdom (Prototype) Main Menu-level 1-2-Temple Bridge.png|Main Menu
File:Invizimals The Lost Kingdom (Aug 30, 2013 prototype) Arrival Placeholder FMV-Loading Screen.png|Arrival Movie Placeholder
File:Invizimals The Lost Kingdom (Aug 30, 2013 prototype) Pause Menu.png|Debug/Pause Menu
File:Invizimals The Lost Kingdom (Aug 30, 2013 prototype) Fly Cam.png|Fly Cam Example
File:Invizimals The Lost Kingdom Ocelotl.png|Ocelotl's appearance outside the Temple/Introduction area
File:Invizimals The Lost Kingdom SIXAXIS.png|"SIXAXIS" message instead of "use your wireless controller to balance" message
File:Invizimals The Lost Kingdom PLACEHOLDER LOCKED.png|When selecting a special ability with the D-Pad, any ability apart from Ocelotl's two abilities show "PLACEHOLDER LOCKED"
</gallery>{{Prototype Footer|{{Navbox prototype|Invizimals: The Lost Kingdom}}}}

Invizimals: The Lost Kingdom (Aug 30, 2013 prototype)

2026-06-09T13:39:44Z

Alepou: Fixed a piece of misinformation and added level structure.

{{Prototype
|titlescreen=Invizimals- The Lost Kingdom (Aug 30, 2013 prototype)-title.png
|Page name=Invizimals: The Lost Kingdom (Aug 30, 2013 prototype)
|builddate=Aug 30, 2013
|status=Released
|dumper=imagisphere
|releasedby=imagisphere
|filereleasedate=October 21, 2025
|origin_type=Playstation 3 DECHA00A HDD
|game=Invizimals: The Lost Kingdom
|system=PlayStation 3
|genre=Action-Adventure
|release_date={{RegionDate|EU|Oct 30, 2013}} {{RegionDate|US|Oct 30, 2014}}
|unreleased=No
}}
{{Download
|file=Invizimals The Lost Kingdom (Aug 30, 2013 prototype).zip
}}
A prototype of '''Invizimals: The Lost Kingdom''' for the Playstation 3.
==Notes==
* The serial is NPEA00461 (EU Region).
* The build date was based on the most recent file modification date.
* It was found on the hdd <code>00-27450032-0055125-DECHA00A</code>.
* An "Arrival Placeholder FMV" screen is present where a cinematic video would play, indicating the final FMV assets had not yet been produced at this build stage.
* A "Fly Cam" debug toggle is present in the pause menu alongside standard options, suggesting developer tools were not removed at this build stage.
* In the prototype, Ocelotl is introduced a little later than in the release. Specifically in the outside of the temple, while in the release Ocelotl is introduced inside of the temple.
* Enemies don’t show up at the intro’s very beginning. Only later on
* There's no tutorial on how to fight enemies at the beginning.
* When in a part of the game where the game instructs you to use your controller for balance, it says "SIXAXIS" instead of "use the wireless controller to balance."
* Camera is very buggy during gameplay.
* Most (if any) of the things that would cost Z-Sparks to unlock don’t cost anything at all.
* When selecting a special ability with the D-Pad, any ability apart from Ocelotl's two abilities show "PLACEHOLDER LOCKED"
* Levels are titled 'Temple1', 'Temple2', so on.

== Images ==
<gallery>
File:Invizimals The Lost Kingdom (Prototype) Main Menu-level 1-2-Temple Bridge.png|Main Menu
File:Invizimals The Lost Kingdom (Aug 30, 2013 prototype) Arrival Placeholder FMV-Loading Screen.png|Arrival Movie Placeholder
File:Invizimals The Lost Kingdom (Aug 30, 2013 prototype) Pause Menu.png|Debug/Pause Menu
File:Invizimals The Lost Kingdom (Aug 30, 2013 prototype) Fly Cam.png|Fly Cam Example
File:Invizimals The Lost Kingdom Ocelotl.png|Ocelotl's appearance outside the Temple/Introduction area
File:Invizimals The Lost Kingdom SIXAXIS.png|"SIXAXIS" message instead of "use your wireless controller to balance" message
File:Invizimals The Lost Kingdom PLACEHOLDER LOCKED.png|When selecting a special ability with the D-Pad, any ability apart from Ocelotl's two abilities show "PLACEHOLDER LOCKED"
</gallery>{{Prototype Footer|{{Navbox prototype|Invizimals: The Lost Kingdom}}}}

File:Invizimals The Lost Kingdom (Prototype) Main Menu-level 1-2-Temple Bridge.png

2026-06-09T13:35:08Z

Alepou:

Invizimals: The Lost Kingdom (Aug 30, 2013 prototype)

2026-06-09T09:54:44Z

Alepou: Added more images and some documentation on bugs.

{{Prototype
|titlescreen=Invizimals- The Lost Kingdom (Aug 30, 2013 prototype)-title.png
|Page name=Invizimals: The Lost Kingdom (Aug 30, 2013 prototype)
|builddate=Aug 30, 2013
|status=Released
|dumper=imagisphere
|releasedby=imagisphere
|filereleasedate=October 21, 2025
|origin_type=Playstation 3 DECHA00A HDD
|game=Invizimals: The Lost Kingdom
|system=PlayStation 3
|genre=Action-Adventure
|release_date={{RegionDate|EU|Oct 30, 2013}} {{RegionDate|US|Oct 30, 2014}}
|unreleased=No
}}
{{Download
|file=Invizimals The Lost Kingdom (Aug 30, 2013 prototype).zip
}}
A prototype of '''Invizimals: The Lost Kingdom''' for the Playstation 3.
==Notes==
* The serial is NPEA00461 (EU Region).
* The build date was based on the most recent file modification date.
* It was found on the hdd <code>00-27450032-0055125-DECHA00A</code>.
* An "Arrival Placeholder FMV" screen is present where a cinematic video would play, indicating the final FMV assets had not yet been produced at this build stage.
* A "Fly Cam" debug toggle is present in the pause menu alongside standard options, suggesting developer tools were not removed at this build stage.
* In the prototype, Ocelotl is introduced a little later than in the release. Specifically in the outside of the temple, while in the release Ocelotl is introduced inside of the temple.
* Enemies don’t show up at the intro’s very beginning. Only later on
* There's no tutorial on how to fight enemies at the beginning.
* Z-Sparks aren’t introduced in the prototype.
* When in a part of the game where the game instructs you to use your controller for balance, it says "SIXAXIS" instead of "use the wireless controller to balance."
* Camera is very buggy during gameplay.
* Most (if any) of the things that would cost Z-Sparks to unlock don’t cost anything at all.
* When selecting a special ability with the D-Pad, any ability apart from Ocelotl's two abilities show "PLACEHOLDER LOCKED"

== Images ==
<gallery>
File:Invizimals The Lost Kingdom (Aug 30, 2013 prototype) Pause Menu.png|Debug/Pause Menu
File:Invizimals The Lost Kingdom (Aug 30, 2013 prototype) Arrival Placeholder FMV-Loading Screen.png|Arrival Movie Placeholder
File:Invizimals The Lost Kingdom (Aug 30, 2013 prototype) Fly Cam.png|Fly Cam Example
File:Invizimals The Lost Kingdom Ocelotl.png|Ocelotl's appearance outside the Temple/Introduction area
File:Invizimals The Lost Kingdom SIXAXIS.png|"SIXAXIS" message instead of "use your wireless controller to balance" message
File:Invizimals The Lost Kingdom PLACEHOLDER LOCKED.png|When selecting a special ability with the D-Pad, any ability apart from Ocelotl's two abilities show "PLACEHOLDER LOCKED"
</gallery>{{Prototype Footer|{{Navbox prototype|Invizimals: The Lost Kingdom}}}}

File:Invizimals The Lost Kingdom PLACEHOLDER LOCKED.png

2026-06-09T09:27:10Z

Alepou:

File:Invizimals The Lost Kingdom SIXAXIS.png

2026-06-09T09:27:10Z

Alepou:

Invizimals: The Lost Kingdom (Aug 30, 2013 prototype)

2026-06-09T00:47:11Z

Alepou: Added Ocelotl's appearance notes and screenshot.

File:Invizimals The Lost Kingdom Ocelotl.png

2026-06-09T00:44:29Z

Alepou:

Invizimals: The Lost Kingdom (Aug 30, 2013 prototype)

2026-06-08T23:53:51Z

Alepou: Added prototype-specific screenshots to Images section.

File:Invizimals The Lost Kingdom (Aug 30, 2013 prototype) Fly Cam.png

2026-06-08T23:39:47Z

Alepou:

== Summary ==
Fly cam/Debug Mode in Invizimals: The Lost Kingdom

File:Invizimals The Lost Kingdom (Aug 30, 2013 prototype) Arrival Placeholder FMV-Loading Screen.png

2026-06-08T23:39:46Z

Alepou:

== Summary ==
A place holder for the intro movie in Invizimals: The Lost Kingdom

File:Invizimals The Lost Kingdom (Aug 30, 2013 prototype) Pause Menu.png

2026-06-08T23:39:46Z

Alepou:

== Summary ==
The pause menu in Invizimals: The lost Kingdom (Fly Cam is clearly visible.

Invizimals: The Lost Kingdom (Aug 30, 2013 prototype)

2026-06-08T23:01:27Z

Alepou: Added title screen image

File:Invizimals- The Lost Kingdom (Aug 30, 2013 prototype)-title.png

2026-06-08T22:59:32Z

Alepou:

Talk:Wolfenstein 3D (Sep 7, 1995 prototype)

2026-06-07T17:49:25Z

Alepou: Created page with "The standard retail BIOS (panafz10.bin) needs to be patched in order for the game to boot. You must use an RSA-patched / decrypted BIOS file. It needs to be non-region-locked, and it needs to not check for signatures. If you're on macOS (like Luca) you're going to most likely need to xattr the .bin and .cue files for the game along with the BIOS file using <code>xattr -cr "/path/to/folder"</code> in order to bypass quarantine flags. You may also need to x..."

The standard retail BIOS (panafz10.bin) needs to be patched in order for the game to boot. You must use an RSA-patched / decrypted BIOS file. It needs to be non-region-locked, and it needs to not check for signatures.
If you're on macOS (like [[User:Loukas|Luca]]) you're going to most likely need to xattr the .bin and .cue files for the game along with the BIOS file using <code>xattr -cr "/path/to/folder"</code> in order to bypass quarantine flags.
You may also need to xattr the Opera/3DO core on macOS.
Then, it is the same as running any 3DO game (if you're using RetroArch, that is).

Wolfenstein 3D (Sep 7, 1995 prototype)

2026-06-07T16:51:07Z

Alepou:

File:Wolfenstein 3D (1995-09-07 Pre-release)-260607-193903.png

2026-06-07T16:44:59Z

Alepou:

User:Alepou

2026-06-07T03:37:30Z

Alepou: create user page

{{User stats|{{PAGENAME}}}}