Ghost Input Output/Phantom Input Output Bug is a very common bug.
There is a way to fix it but to help you get rid of it, we need more information on what you did that you think caused the ghost/phantom pins to appear. It could be caused by many reasons such as Deleting a Chip that is used in other chips.
Sadly, You can't rearrange the Chips in the bottom bar. However, There is a way to do it by going to your Project Folder which is located at %appdata%>LocalLow>Digital_Logic_Sim_Sebastian_Lime_inc>Project. Then you have to select the chip you want to relocate and open it then, change the "creation_index": to anything you want.
The problem with Edit Chips has been fixed and you just have to wait for the next update now. The wire issue is probably caused because of how the collider for wires work. Copying and Pasting chips is a pretty unknown feature it's already in the game you can Copy, Paste groups of chips. They won't retain the connections but that may be added in a future update. The idea of having a grid system and Inputs at the top or bottom of the chips or workspace is very nice
Thanks for playing Digital Logic Sim 2. We appreciate your support!
The expansion of the Workspace is one of the most or if not the most needed and requested feature. You can zoom in and out but it does have some small issues such as Hit boxes not changing sizes correctly but we will fix it soon. We hope to be able to deliver this requested feature as soon as possible and maybe before version 2.0.
Thanks for playing Digital Logic Sim 2, We appreciate your support!
1. You can Zoom in and Out using Ctrl+ or Ctrl- Although it is a bit bugged as the Hitbox of the Chip doesn't scale down properly and the Rotating doesn't rotate the Hitbox. We do intend to fix these in the future.
2. Great Idea! Our team have never thought of it. It is quite a simple suggestion so We just Implemented it.
Its quite an easy Solution. Go to that Folder and Rename 'Digital Logic Sim_Data' to 'DigitalLogicSim_Data' and it should work. I tried it and it worked
I have a solution for the Bug that ruins a project when a chip used in other chips is deleted.
Instead of Deleting the chip, Only remove it from the menu bar in the bottom and keep it inside the project and Only remove it from the project if all usages of that "Deleted" chip are removed.
Also,
The Number that shows the Binary Input in Number is a bit wrong. I believe that It should be flipped and go from top to bottom instead of bottom to top. Because of that Issue I'm having to convert the Binary Input or Output to Number myself. Fixing that Issue will make Converting Binary to Decimal Very convenient.
There needs to be workspace's in this game. One of the workspace will have almost unlimited space, unlimited available inputs and outputs. It will be the place where the Main Project or the Computer is going to be built. Upon Exit, the chips in the main workspace should remain and they should retain the data, location, etc. The second workspace should be for building the chips. It will be the same as the Workspace we currently have access to. I believe that this Feature, If Implemented can change the Game. We would finally be able to Build Computers, and Many many other things. It will open up almost infinite possibilities. Personally, I want to build a 4-Bit Computer (4-Bit Because of the Limitations). I know that I cannot build a Computer here due to the Limitations. Because the Parts such as Control Logic which is the most important part of the computer cannot be built as it requires ROM or RAM. and we cannot just make a ROM with data coded in upon placing it. and another important part is the Layout. I could just put all the Parts in one Chip but I want it all placed down separately and witness the Creation working. I can't do it due to limited space, Limited Input, outputs, etc.
The pixel index is can be changed using the Address Pins. The Address is represented in Binary. So, For example, If we want to change the pixel in the top left which is the first pixel we can leave all the address pins empty which sets the address/pixel index to 0 in binary.
After we select the Address of your Choice. We have to choose a color. Unfortunately, There is only 8 available Colors. There are 3 Color pins - Red, Green Blue. We can combine these colors to create another color such as pink, yellow, cyan etc. After we select the color of our choice, We can Update or Change the Pixel we chose to the color we selected by pulsing or bringing the Store Pin High. The store pin isn't edge triggered so can keep it high and actively change pixels.
Ok, I will. But, unfortunately I have exams till 16th June and I'm not able to use my PC so I will send it Later. Also you should make it so that the project saves what is in the main window where we build the circuits. And also the chips must retain their data. Same for the inputs and outputs too.
Hello, There are some issues with Performance. I have built a 16 Byte RAM (Actully 8 Byte since it's 4-Bit). After I turned the RAM into a Chip, The project started taking way longer to load and the project lags when I grab it from the Chips in the Bottom. It lags because It's simulating 16 Registers and an Address Decoder. The 4-Bit Register had 4 1-Bit Registers Simulating inside it and the 4-Bit Address Decoder is simulating 16 4-Input AND Gate which is simulating 3 AND Gates. The 1-Bit Registers are Simulating 2 D Flip-Flops which is Simulating 1 D Latch which is Simulating 1 SR Latch and so on. You can see how performance expensive it is. I have a RTX 3080, Intel Core I7-10700 and 32 GBS of RAM so it isn't very hard for my computer to run but it will be very hard for a low-end computer. I think instead of Simulating basically an Entire Project, You could try instead use a different approach that will be more performance friendly. If this performance issue isn't fixed, then It might just become near impossible to make a entire computer or CPU in this Simulator because of very low performance. A single clock cycle might just take a few seconds or even a few minutes. It takes around 3 to 5 Clock Cycles to execute one Assembly Instruction. so, You can imagine how tedious it will be to run anything large.
