Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Issues with Twine
When in a tight deadline faulty systems are unnecessary, I understand that this is an open-source software, but if you are making an updated version of said software, at least make it as good or better than the last version of Twine. We are producing a Twine interactive fiction, and we do not have to materials necessary to produce said Twine on you current version (e.g: Embedding of multimedia) Thank you.
Comments
[opinion]
There have always been limitations with embedding multimedia data (image/font/audio/video) within a Twine Project created with either (Twine 1 or 2) of the Twine GUI based applications, and those limitations generally break down into three basic problems.
1. The story project becoming too large to be stored.
2. The story project becoming too large to be converted into a Story HTML file.
3. The Story HTML file becoming to large to be hosted-on / downloaded-from a web-server. This does not include downloading from a file hosting site.
The above three problems is why it is generally recommended to not embed multimedia data with either the Story Project or the generated Story HTML file if you plan to use a lot of MB's of multimedia.
notes:
1. The Twine 1 GUI application will start having "out of memory" error when building a Story HTML file once the total Story Project size (including child TWS files / external files referenced in StoryIncludes passage) grows to somewhere between 50-100MB.
2. The combined maximum size of all Story Projects allowed when using the web-browser based release of the Twine 2 GUI application is controlled by the web-browser's own default limit on the maximum size of it's local-storage cache, which is generally around 5-10MB depending on the brand of web-browser and if the Twine 2 GUI web-application being used is hosted remotely or stored on the local hard-drive.
3. The node-webkit release of the Twine 2 GUI application has had the default limit of it's local-storage cache increased to One Tera-byte which combined with the use of locally stored (on hard-drive) project files means that the Story Project files can be a lot larger but that does not solve the problem of a generated Story HTML file being too large to host on a web-server.
[/opinion]
I appreciate your response.