Here it is in all its glory, straight from the netlist of the original chip itself. A lot of layout work went into this. Enjoy!
>>3653000
>>3653001
>>3653003
>>3653007
>>3653009
>>3653012
>>3653014
>>3653016
>>3653021
>>3653000
Am I supposed to know what this shit is?
Holy shit is this Robot Oddysey
This game literally got me into electronics.
>>3653050
Me too.
I've been playing it since the mid 80s.
This is just a small taste of the guide I am half way done putting together.
Complete walkthrough with schematics and maps for all 5 levels.
>>3653000
So like what does this actually do
>>3653070
You are correct.
The predecessor to this was Rocky's Boots, another logic-based graphical puzzle game.
This was the first one I've ever came across where it acted as a functional logic simulator. It was released for the Tandy and Apple II in 3 different versions.
>>3653075
It propels a robot until it makes contact with a wall, and continues to follow the wall using its bumpers as sensors.
My younger brothers told me about Rocky's Boots when they were in elementary school but the school didn't have it when I was there a year prior so I missed it. Always sounded interesting.
>>3653050
THAT'S what this fucking shit is called I'd thought about it for years
>>3653027
No. And a thread full of hipstershit won't change that.
UPDATE:
Revised the nested chip schematic to eliminate the crossed gate, and added in OR16 which seemed to have been left out.
A few minor graphical glitches touched up also.
Updating with some revised pages. (Page 1, no changes)
>>3656576
>>3656583
>>3656585
Added labels.
(Pages 5 & 6, no changes)
>>3656586
>>3656591
>>3656597
Last page, minor graphical glitches fixed.
This is fascinating to me, but i'm old enough that gravediggers keep scowling at me and poniting at their watches.
UPDATE:
Was able to get the IBM version of the game (v1.1) patched to remove copy protection & configured to run under MS-DOS 3.3 on a 1.44MB floppy disk image under DOSBox.
The game can be run right from the disk image, or you can boot to a HDD image and start the program on the floppy image from the command prompt (recommended).
The only (very minor) quirk with this is, the setup program fixes Drive A to load/save all Innovation Lab and Chip Library files, and Drive B for all saved game files - Pressing ESC to change disks does nothing.
While the extra space on the 1.44MB disks is useful, there are only so many saved files that can appear on the menu so the use of a small HDD image as a swap drive gets around this limitation for those with large libraries.
TLC logo splash screen
Game title screen
Menu
Game - opening animation
Game - start room in the sewers
Innovation Lab
Tutorial -
Robot Anatomy
Tutorial -
Robot Wiring
Tutorial -
Sensors
Tutorial -
The Toolkit
Tutorial -
Robot Circuits
Tutorial -
Robot Teamwork
Tutorial -
Chip Design
Load screen -
Game files
(Note: Fixed to Drive B)
The screen for saving game files is similar
Game Directory - Load
Drive B data disk
The screen for saving game files is similar
Load screen -
Lab files
(Note: Fixed to Drive A)
The screen for saving lab files is similar
Lab Directory - Load
Drive A game disk
The screen for saving lab files is similar
Load screen -
Chip files
(Note: Fixed to Drive A)
The screen for saving chip files is similar
Chip Directory - Load
Drive A game disk
The screen for saving chip files is similar
DOSBox startup screen
Command prompt in MS-DOS 3.3
Game disk in Drive A
Data disk in Drive B
Small 10MB HDD image Boot Drive C
Directory of all files on the game disk in Drive A with patches applied and system files transferred.
Setup utility needs to be run first before playing the game for the first time (or after any configuration changes) if you are putting this together yourself.
Nested Chip -
IBM Version
Outer Chip Build -
IBM Version
Prototype Chip wired in -
IBM Version
Successful test -
IBM Version
Red robot (Sparky) - Prototype Chip
Blue robot (Scanner) - Library Chip
Both run through the test room exactly the same -
IBM Version
Saved Lab files -
IBM Version
Saved Chip (WHNESTED) -
IBM Version
Modified code (Python) taking into account the difference in length of Short JMP and Near JMP instructions (one byte) - without this modification the patcher would fail with an Assertion Error:
def asmPadToLength(str, length):
padLen = length - len(str)
if padLen < 0:
raise ValueError("Code block is too long (%d bytes), must fit in %d bytes!"
% (len(str), length))
elif padLen <= 3:
# Short JMP (EB) impractical - just fill with NOPs (90)
result = str + asm("nop") * padLen
elif padLen <= 127:
# Fill with NOPs (90) using Short JMP (EB) - 2 bytes
result = str + asm("jmp end\n" +
"nop\n" * (padLen - 2) +
"end:\n")
else:
# Fill with NOPs (90) using Near JMP (E9) - 3 bytes
result = str + asm("jmp end\n" +
"nop\n" * (padLen - 3) +
"end:\n")
assert len(result) == length
return result