Wave-Function-Collapse
Wave-Function-Collapse copied to clipboard
Bug?
for (let i = 0; i < 12; i++) { ... } We are assigning only 12 out of 13 tiles...
- Added a simple node server to ease loading of images - Reduced **DIM** for make it faster - Added some css to make it look better
Instead of going through all cells to get their tile options, we keep the grid (like a cache of options), and only modify cells that might have changed, leaving aside...
Hey, thank you very much for all your videos, I'm having a blast watching them! I made a Pull Request [here](https://github.com/CodingTrain/Wave-Function-Collapse/pull/40) to make grid updates more efficient. Instead of watching...
i was trying to draw a large grid (64x64) and it was slow, so i tweaked the `draw()` function to skip calculating validOptions for cells that weren't adjacent to any...
grid helper
made a small helper class for general grid layouts (partially copied from things i did previously) its currently still not integrated perfectly so its just here as an idea im...
I think you mentionned not wanting 5.png (for circuit) to connect to itself even if it was in the right orientation, probably because it would make for really thin chips....
We can validate near cells through the edge, that will give us seamless texture result
By this time, there are duplicated tiles, one as an image and one as graphic: ``` javascript const initialTileCount = tiles.length; for (let i = 0; i < initialTileCount; i++)...
At [22:24](https://youtu.be/rI_y2GAlQFM?t=1365) in the video Dan tries to use his constants as the keys in the object but it doesn't work for him. This is because he did it wrong....