Stencyl 4.1 beta b10658

[LetsPlay2020]

I upgraded from Stencyl 4.0.4 to Stencyl 4.1.0 beta b10658 and I ran into publishing problems for HTML5 format. The Stencyl 4.1.0 version does not package all of my assets of my video game. I have been going back to Stencyl 4.0.4 just to publish my game for HTML5. Stencyl 4.1.0 also adds an extra unwanted loading white to blue bar before my loading page. I get a warning alert when I try to publish in Stencyl 4.0.4 because backwards compatibility.

[Justin]

I upgraded from Stencyl 4.0.4 to Stencyl 4.1.0 beta b10658 and I ran into publishing problems for HTML5 format. The Stencyl 4.1.0 version does not package all of my assets of my video game. I have been going back to Stencyl 4.0.4 just to publish my game for HTML5.

b10658 is quite old. Could you try with the latest private build?

If you still have the same issue, try this:
1. Clean out the output from previous builds (Tools > Game > Clean Project)
2. Publish your game for HTML5
3. Check that the problem persists
4. Generate logs (Tools > Logs > Generate Logs)
5. Upload your logs here

It would also be helpful if you can provide more details, like what exactly is missing when you publish? Is it always the same assets or is it random?

Stencyl 4.1.0 also adds an extra unwanted loading white to blue bar before my loading page.

I don't have any immediate plans to modify this, but you can change it if you'd like. It was added to show loading progress of the game code itself, which has to be loaded before the main preloader is shown. This was included at the request of a game portal for their users on slower internet connections (think, 3g cellular connection), who might otherwise think that nothing is loading at first.

1. Go to your Stencyl Install, and find "plaf/lime-templates/html5/template". In it is index.html and progress.js.
2. Go to your game folder (Tools > View Folder > View Folder for this Game) and create a lime-templates folder inside there.
3. Copy [stencyl install]/plaf/lime-templates/html5 to [game folder]/lime-templates/html5.
4. Any changes you make to the index.html and progress.js files will show up in your compiled game.

To just remove the progress bar, you could change the body of the page in index.html to this:

Code: [Select]

<noscript>This webpage makes extensive use of JavaScript. Please enable JavaScript in your web browser to view this page.</noscript>

<div id="openfl-content"></div>

<script>

var __filesToLoad = {::if linkedLibraries::::foreach (linkedLibraries)::
"::__current__.name::": {total: ::__current__.size::},::end::::end::
"./::APP_FILE::.js": {total: APP_FILE_SIZE}
}

var __progressListener = function __progressListener(progress) {};

var __completionCallback = function __completionCallback() {
lime.embed ("::APP_FILE::", "openfl-content", ::WIN_WIDTH::, ::WIN_HEIGHT::, { parameters: {} });
};

__loadWithProgress(__filesToLoad, __progressListener, __completionCallback);

</script>


[LetsPlay2020]

The only assets that copy over are my sound files. There is a default.pak file that is around 28MB or so that is located in the "lib" folder after my game is packaged. After the default loading screen appears, then my loading screen appears, when my loading screen is completed loading, nothing happens, my video game just stops after that. Thanks for showing me how to remove the extra loading bar. I will upload my log files shortly.

[Justin]

All of your assets (except the sounds) are found inside the default.pak file. This was another change made as a request by an HTML5 game portal, because it's faster to download a single asset pack file rather than hundreds or thousands of individual asset files, because of the overhead associated with all of the individual downloads.


When you try to test your HTML5 game, are you testing it from within Stencyl (using the built-in web server), or are you exporting it and then opening the index.html file? If you're opening the local index.html file in a web browser, that's not supported. Otherwise, please try looking at the developer console of your web browser for errors being printed from the game.

[LetsPlay2020]

I upload my files to my web server, the 4.0.4 version runs fine, the version 4.1.0 will not do anything after my loading screen is completed. It's not being run locally after I publish for HTML5. I have been publishing from version 4.0.4 when I make any updates to my video game to upload to my web server and my video game runs fine. Do the ".pak" need to be extracted or something like the .zip file after publishing in 4.1.0? The browsers I use are Chrome, Microsoft Edge, and Safari.

[Justin]

No, nothing needs to be done. The zip file Stencyl exports contains everything you need to play the game as-is. You'll just need to look at your web browser's developer console for errors when you play your game to see what's happening.

[LetsPlay2020]

It's running ok now, when I published my video game on October 1, 2022 in 4.1.0 it wasn't running after my loading screen. I will do a couple more publishing for HTML5 in 4.1.0. Thanks for your assistance on this.

[Justin]

Ok. It may have been an error that only sometimes occurs then. If it ever happens again, please try grabbing the logs from your browser so we can see what's wrong and file a new issue here. Thanks.

• Status changed from New to Closed

 log-2022-10-19.zip (147.63 kB - downloaded 63 times.)