We’ve been repeating for years now that printing critical feedback messages to the console is wildly unacceptable; it downplays the importance of them, hides them from the user, and causes accidents. Studio should have the capability to throw toasts or dialogs for information that absolutely needs to be seen by the user. Is this finally enough lost work to have a solution prioritized?
and
Yes, this, it’s also worth noting that many developers (especially non-scripters) do not enable the output in their view and hence will never see these errors.
We agree with you here and feedback is received. The solutions we are looking at are ways to elevate certain passive messages and also errors out of the console log.
For future reference should others come read this, here is a simple test I did. I yanked 252 tank models out of the toolbox and pasted them on a new baseplate, then exported the place file. Just with the default collision settings, the file size was nearly 3MB in size. Then I changed the collision to “box”, did an export, and wow, the file size is only 82 KB now.
Given the wording of that post, it doesn’t appear that the limit was actually 4MB but rather that the limit for OpenCloud was 4MB, while Studio (likely) allowed you to publish larger files. As mentioned in that post, OpenCloud was later increased to 100MB file size limit. Are you sure the manual publishing recommended max file size is somewhere around 100MB, or is there no official statement on recommended max file sizes other than max sizes for OpenCloud?
