Known issues/2.0.16 - Revision history

82.77.240.44: fixed grammar on alpha

2026-03-30T09:33:35Z

fixed grammar on alpha

← Older revision		Revision as of 09:33, 30 March 2026
Line 1:		Line 1:
	{{Breadcrumbs\|Alpha Branch/{{SUBPAGENAME}}}}		{{Breadcrumbs\|Alpha Branch/{{SUBPAGENAME}}}}
	{{Early-access-version\|2\|0.16\|~~apha~~}}		{{Early-access-version\|2\|0.16\|alpha}}

	A number of levels in version are known to be broken, and require some workarounds to complete. Some of these issues affect multiple levels, I only give the first level you are likely to come across them.		A number of levels in version are known to be broken, and require some workarounds to complete. Some of these issues affect multiple levels, I only give the first level you are likely to come across them.

159.196.132.3: Update stale Known issues sections from Wire Spaghetti onward for current 2.1.48 Alpha files

2026-03-15T10:45:53Z

Update stale Known issues sections from Wire Spaghetti onward for current 2.1.48 Alpha files

← Older revision		Revision as of 10:45, 15 March 2026
Line 33:		Line 33:

	== Wire Spaghetti ==		== Wire Spaghetti ==
	~~API~~ test ~~marker~~.		This section is out of date for current 2.1.x alpha builds.

			In the current local 2.1.48 Alpha files, <code>campaign/symphony_1_nand/meta.txt</code> already:
			* uses the provided <code>Main Memory</code> and <code>Register File</code> components instead of asking the player to place their own RAM blocks;
			* explains that register addresses are byte-addressed and must be multiplied by 4; and
			* no longer tells the player to leave <code>zr</code> disconnected.

			The older RAM-width workarounds and the <code>zr</code> note below applied to older builds only and should not be followed on current builds.

			== Integrating ALU ==
			This section is out of date for current 2.1.x alpha builds.

			In the current local files, <code>campaign/symphony/test.si</code> implements opcode <code>11</code> as multiplication (<code>a_value * b_value</code>). The old workaround about deleting or disabling the multiply unit should not be followed on current builds.

			== RAM ==
			This section is out of date for current 2.1.x alpha builds.

			<code>campaign/symphony_6_ram/meta.txt</code> already documents:
			* <code>0 load_8</code>
			* <code>1 load_16</code>
			* <code>2 load_32</code>
			* <code>3 reserved</code>
			* <code>4 store_8</code>
			* <code>5 store_16</code>
			* <code>6 store_32</code>

			It also already explains that the load ports must be above the store ports to avoid a circular dependency. The older workaround in this section should be removed for current builds.

			== SSD ==
			This section is out of date for current 2.1.x alpha builds.

			<code>campaign/symphony_7_ssd/meta.txt</code> already documents:
			* <code>0 load_8</code>
			* <code>1 load_16</code>
			* <code>2 load_32</code>
			* <code>3 pload</code>
			* <code>4 store_8</code>
			* <code>5 store_16</code>
			* <code>6 store_32</code>
			* <code>7 pstore</code>

			Also, <code>campaign/symphony/test.si</code> reads <code>Main Memory</code> and <code>Persistent Memory</code> by name, so the older RAM/SSD mix-up workaround does not match the current local files.

			== Instruction aliases ==
			This section is out of date for current 2.1.x alpha builds.

			Current local files show:
			* <code>campaign/symphony_9_aliases/meta.txt</code> asks the player to add five aliases: <code>mov</code>, <code>neg</code>, <code>not</code>, <code>movt</code>, and <code>movb</code>;
			* <code>campaign/symphony_9_aliases/default.asm</code> uses only those five instructions; and
			* <code>campaign/symphony_9_aliases/test.si</code> validates the resulting register values for those instructions.

			The older workaround about editing four load/store lines or replacing <code>test.si</code> should be removed for current builds.

			== Various levels ==
			This section appears to describe older assembly-spec problems.

			Current local 2.1.48 Alpha files already ship separate <code>default.isa</code> assets for later Symphony levels, including:
			* <code>campaign/symphony_10_stack/default.isa</code>
			* <code>campaign/symphony_reg_use_check/default.isa</code>
			* <code>campaign/symphony_11_functions/default.isa</code>

			These files already include <code>movt</code>, <code>movb</code>, <code>push</code>, <code>pop</code>, <code>call</code>, and <code>ret</code>. The broad regex/workaround section should be treated as historical and should be removed unless someone can still reproduce it on a current build.

159.196.132.3: api test

2026-03-15T10:45:32Z

api test

Show changes

Dr Lipton: /* Level fails to compile due to wrong meta.txt */

2025-09-22T16:01:37Z

Level fails to compile due to wrong meta.txt

← Older revision		Revision as of 16:01, 22 September 2025
Line 136:		Line 136:
	=== Level fails to compile due to wrong meta.txt ===		=== Level fails to compile due to wrong meta.txt ===

	The meta.txt for this level has 4 incorrect instructions, to fix do either one of A OR B, not both, they are mutually exclusive.		The meta.txt for this level has 4 incorrect instructions, to fix do either one of A XOR B, not both, they are mutually exclusive.

	WORKAROUND A:		WORKAROUND A:

95.157.36.93: Bad opcode

2025-08-25T05:07:57Z

Bad opcode

← Older revision		Revision as of 05:07, 25 August 2025
Line 290:		Line 290:
	00100100 aaaabbbb 00000000 00000000		00100100 aaaabbbb 00000000 00000000
	Copies from register %b to register %a		Copies from register %b to register %a

			mov %a(register), %b(immediate)
			00110100 aaaa0000 bbbbbbbb bbbbbbbb
			Copies immediate %b to register %a

	neg %a(register), %b(register)		neg %a(register), %b(register)

Gelthor: /* Level fails to compile due to wrong meta.txt */ Clarify either remove broken lines or replace them, not both

2025-08-09T12:18:37Z

Level fails to compile due to wrong meta.txt: Clarify either remove broken lines or replace them, not both

← Older revision		Revision as of 12:18, 9 August 2025
Line 135:		Line 135:

	=== Level fails to compile due to wrong meta.txt ===		=== Level fails to compile due to wrong meta.txt ===

			The meta.txt for this level has 4 incorrect instructions, to fix do either one of A OR B, not both, they are mutually exclusive.

	WORKAROUND A:		WORKAROUND A:
Line 147:		Line 149:
	`</pre>WORKAROUND B:		`</pre>WORKAROUND B:

	Replace ~~this~~ 4 lines with		Replace the 4 load/store lines with
	store_16 [r5], r3		store_16 [r5], r3
	load_16 r6, [r5]		load_16 r6, [r5]

95.10.1.66: /* Level fails to compile due to wrong meta.txt */

2025-08-08T13:26:50Z

Level fails to compile due to wrong meta.txt

← Older revision		Revision as of 13:26, 8 August 2025
Line 135:		Line 135:

	=== Level fails to compile due to wrong meta.txt ===		=== Level fails to compile due to wrong meta.txt ===

			WORKAROUND A:

	Edit <code>Turing Complete\campaign\symphony_9_aliases\meta.txt</code> (found in the game's install folder, not your save files) and delete the last 4 lines of default_assembly, so that the section reads		Edit <code>Turing Complete\campaign\symphony_9_aliases\meta.txt</code> (found in the game's install folder, not your save files) and delete the last 4 lines of default_assembly, so that the section reads
Line 143:		Line 145:
	neg r3, r2		neg r3, r2
	not r4, r2		not r4, r2
	`</pre>		`</pre>WORKAROUND B:

			Replace this 4 lines with
			store_16 [r5], r3
			load_16 r6, [r5]
			pstore_16 [r5], r3
			pload_16 r6, [r5]

	=== Level fails due to wrong test.si ===		=== Level fails due to wrong test.si ===

95.157.36.93: /* Cmp descriptions mention r6 instead of r15*/

2025-08-07T12:23:28Z

Cmp descriptions mention r6 instead of r15

← Older revision		Revision as of 12:23, 7 August 2025
Line 204:		Line 204:
	* Call and return instructions		* Call and return instructions

	Several of these have the wrong Mode, wrong OPcode, or are simply outdated. Below shows the correct instructions for these functions. You can either change them in game or in the meta.txt file associated with the level.<syntaxhighlight lang="text">		Several of these have the wrong Mode, wrong OPcode, are simply outdated, or the description contains an error . Below shows the correct instructions for these functions. You can either change them in game or in the meta.txt file associated with the level.<syntaxhighlight lang="text">
	load8 %dest(register), %address(register)		load8 %dest(register), %address(register)
	01100000 dddd0000 0000aaaa 00000000		01100000 dddd0000 0000aaaa 00000000
Line 268:		Line 268:
	01110111 0000vvvv aaaaaaaa aaaaaaaa		01110111 0000vvvv aaaaaaaa aaaaaaaa
	Store %value to %address in SSD		Store %value to %address in SSD

			cmp %a(register), %b(register)
			00101001 1111aaaa 0000bbbb 00000000
			Compares %a and %b and store the resulting flags in r15.

			cmp %a(register), %b(immediate)
			00111001 1111aaaa bbbbbbbb bbbbbbbb
			Compares %a and %b and store the resulting flags in r15.

	mov %a(register), %b(register)		mov %a(register), %b(register)

Gelthor: /* Various levels */ Added program is all zeroes

2025-07-31T16:50:49Z

Various levels: Added program is all zeroes

← Older revision		Revision as of 16:50, 31 July 2025
Line 188:		Line 188:
	s/(^\| )([01][01])0/$10$2/g		s/(^\| )([01][01])0/$10$2/g
	</pre>		</pre>

			=== Program is all zeroes ===

			Sometimes the Assembler fails to compile code leaving the program RAM filled with zeroes. First double check you have no compilation errors shown in the bottom of the Assembler window. If no errors are reported then switching schematic or restarting that game has been reported to force a recompilation and fix this.

	=== Wrong assembly instructions ===		=== Wrong assembly instructions ===

			These are fixed in Eryk's patch mentioned above.

	The assembly instructions for various levels is incorrect, some instructions that are bugged include, but are not limited to:		The assembly instructions for various levels is incorrect, some instructions that are bugged include, but are not limited to:

Gelthor: /* RAM */ Arguments A and B are exactly the same as those for ALU instructions

2025-07-26T20:14:23Z

RAM: Arguments A and B are exactly the same as those for ALU instructions

← Older revision		Revision as of 20:14, 26 July 2025
Line 110:		Line 110:
	# a new 16-bit load port, and finally,		# a new 16-bit load port, and finally,
	# at the top, a new 8-bit load port.		# at the top, a new 8-bit load port.
	The level log also incorrectly states that the 'load' and 'store' instructions should use "argument B" as address parameter. However, for this level that is not relevant. Instead you should use the immediate value as an address to store and load data in the program RAM.

	As a further clarification, the 'store~~' instruction~~ should fetch data from the register file at the address determined by "argument A" and store that in program RAM. The level log ~~makes~~ it seem as though you should store the value of "argument A" itself in program RAM, but that is not the case.		The level log states that the <code>load</code> and <code>store</code> instructions should use "Argument B" as address parameter. For clarity this is exactly the same Argument B that the ALU uses. In other words: it is either the value in the register specified by the Argument B field in the instruction or the immediate in the instruction, depending on the <code>Is Immediate</code> flag.

			As a further clarification, the <code>store</code> instructions should fetch data from the register file at the address determined by "argument A" and store that in program RAM. The level log might make it seem as though you should store the raw value of "argument A" taken from the instruction itself in program RAM, but that is not the case. Again this is exactly the same Argument A as used in ALU operations.

	== SSD ==		== SSD ==