itch.io

On the capacitor, why did you remove the address input from the original design? The point was previously to be able to have variable clocks in simulation and since it had already been implemented I don’t see why it would have been removed :(

(I’m a bit biased: I was the one to suggest the capacitor object so I’m more asking for peace of mind, sorry!)

A friend of mine had the same error. Some devices aren’t compatible with one of the components which renders textures or something along those lines. They’re currently working on coding a compatability too to bypass this error but it’s not finished yet and they say there’s no guarantees it’ll work good luck x

I will be producing a video to submit to Sebastian Lague’s upcoming video! It will be a guide on how to operate this monitor! For now: Minimum Steps Per Clock Tick = 50

MONITOR DRIVER

FULL DIVIDER

SUB TST

PROC TEST

It’s complete :D

And of course, I’m operating on the community discord! You can find me there along with many other great logical minds! https://discord.gg/WDUyhVUM

Once I create the driver, I will be uploading the complete project to a github repository where it will be accessible and completely functional :)

Gaps in the line are not pixels being skipped over, but a trim around each RGB display. I have submitted a request for this trim to be toggleable, but as for right now it is unavoidable

COMPLETE!!!

The monitor project has been a short span of time where I have seen to try and create a monitor out of the new RGB displays, and I can confirm with certainty that it is completely functional.

I am in the process of creating a driver for the address, but other than that, the monitor is complete.

https://github.com/ItsIceyTime/DLS-PROJECTS/tree/main

I’ve created a repository with instructions on where to find the error. It appears to be locationality, but I haven’t given it any extra thought.

Thank you, and good luck with trouble-shoothing!

I’ve just discovered that the mechanics behind DLS are likely locational. Circuits which depend on timing to work will only correctly execute a portion of the time depending on their location in the world.

We have another suggestion:

• A lookup for all instances a subcomponent is used

Additional Request I have just encountered:

• The RGB display, when used in a subcomponent, has a border which would be better gone. If we could have a toggle (same way we can edit the contents of the ROM obj) to remove the display border, I would not have this issue above (these should all be adjacent)

Requests:
The community in the discord server has come together with ideas we may wish to see or appreciate being added! These are currently as follows:

• Modifiable Subcomponents/Subcomponent Switches - A device which allows you to input data into a subcomponent without having to place a switch in the world.
• Mod support for DLS
• Support for sharing Subcomponents and projects
• Buttons which turn off once click is released
• Descriptions for Subcomponents (Especially useful with Sharing Subcomponents.

Ongoing Projects:
Currently, two projects are being done in the server:

• A mod for 16BIT and 32BIT wires  (Maybe more in the future.)
• A subcomponent for a generalized RGB monitor, currently testing at 5x4 RGB displays [Done by yours truly].

Thank you very much to Sebastian Lague for the reboot of DLS, it's incredible and we could never appreciate your work enough!
And of course, the server link x
https://discord.gg/pXtPuwfg39

hit ctrl + g. To snap to grid, you hold ctrl while dragging an object

While clicking chips, hold the shift key. without letting go, you can then scroll up and down to space the chips

Occasionally when placing many busses, there will be phantom connections where many busses are synchronized while disconnected.
It can be solved by connecting an input to the black wire shown. this will cause one of the phantom wires to go black. toggling one of the signals on the input toggles it for all phantom busses.
Connecting the same input to the new black wire and repeating till all are connected seems to fix it. you can delete every bus connection to the input and it works fine, but once you delete the input block itself, the error arises again.
I am using the Linux version ran on a steamdeck for context.

as shown

I think I broke it
I got a number so big it doesn't display
Also got a score of 3*10^39,  highest I've seen so far, previous was 2*10^37 IIRC