Report this content
We want the Dreams coMmunity to be a safe, diverse and tolerant place for everyone, no matter their age, gender, race, sexual orientation or otherwise. If you believe this content to contradict these principles, you can file a report for our coMmunity teams to investigate.
Note that misuse of the reporting tool will not be tolerated.Item being reported:
This would be huge and amazing if it can be implemented in a good way. However, there is a problem with how the engine works: A Dream can load fast because it is small in data. The reason it is small in data, is because the only thing that is saved, is the instructions for how to make the Dream, and not 3D models etc. e.g. when the game has to show a house, it looks at a list of the steps that the creator took to make the house (like 1:add sphere, 2:subtract cube etc.) and recreates the house from those steps. This way, the only thing that needs to be saved, are the steps and not the house itself. The steps does not take much data at all, which is why a dream can be loaded so quickly.
Now how does this relate to the images? Since photos/screenshots cannot be made step by step in the same way as above, they have to be saved entirely as an image file. This means that a dream now has a potential of getting much larger file sizes, and as a result become much slower to load. To prevent this, you have to introduce restrictions to the number of images, or the quality of the images in a dream.
Another problem is how the images should interact with the lighting. As i understand, only flecks are affected by the lighting, which is why text gadgets don't get shadows etc. Although i am not sure about this one xD
But anyways, I hope the devs can figure a good way to implement this, as it could be awesome. And also i wouldn't mind some restrictions :)