HTML5 build succesfull but no game in browser (canvas is gray)

Development Platform & Builds
, ,
1

After following all the steps in listed here, I can successfully build/cook/package/deploy/launch my custom project (Minimal_Default map with some custom BSP blocks and one custom material). However when it launches Firefox Nightly 64bit (with a secondary profile) the canvas area is just gray. It seems the game is loaded though, because it’s using about 2GB’s of memory. I’ve tried running locally via file:/// and running through Apache via localhost, but it has the same result, no game.

In the error console it just shows

ReferenceError: tstart is not defined
Successfully compiled asm.js code (total compilation time 0ms; not stored in cache)
"pre-main prep time: 511 ms"

If I manually insert the following part just inside the body tag in TestProject.html

<script type="text/javascript">
  var tstart = Date.now();
</script>

I get the following console log:

Successfully compiled asm.js code (total compilation time 0ms; not stored in cache)
"Script load time: Data[js]: 1.00ms, code[js]: 9.00"
"pre-main prep time: 494 ms"
2

I have the same error too. I have successfully built the HTML file and I am using IIS to run the file on localhost. But I get tstart not defined!

When I commented out that one line that used tstart I got a 404 error that reported that it couldn’t get “MyProject.data”

Can some one please help?

3

same here, would be interesting to get a solution :slight_smile:

4

.data file is generated during the cooking process - Make sure thats being generated. You might want to look at HTM5Platform.Automation.cs file on how thats being packaged.

5

Tried again with the new 4.2 release, this time it loads :slight_smile:

6

Hello,

Thank you for your report. We were not able to investigate this on the engine version you reported, but there have been many version changes to UE4 since this question was first posted. With a new version of the Engine comes new fixes and it is possible that this issue has changed or may no longer occur. Due to timetable of when this issue was first posted, we are marking this post as resolved for tracking purposes. If you are still experiencing the issue you reported in the current engine version, then please respond to this message with additional information and we will investigate as soon as possible. If you are experiencing a similar, but different issue at this time, could you please submit a new report for it.

Thanks!