![]() Were made during the rush of Steam and aren’t well thought out. With this we also deprecate the HTTP file api and the visual studio extension. v0.22.0 - Major rebalancing, optimization, and favor system.v0.50.2 - Everyone asked for this one.v0.51.1 - Bugfixes because the author of the last patch sucks (it’s hydroflame).v0.51.3 - Y’all broke it on the first day (hydroflame).v0.51.4 - Manual hacking is fun (hydroflame).v0.51.6 - Backdoor! (hydroflame & community).v0.51.7 - n00dles (hydroflame & community).v0.51.8 - It was there all along (hydroflame & community).v0.51.9 - offline progress and exports! (hydroflame & community).v0.51.10 - Focus Mark, Focus! (hydroflame).v0.52.0 - Infiltration 2.0 (hydroflame & community).v0.52.1 - bugfixing (hydroflame & community).v0.52.2 - Oh yeah, BN11 is a thing (drunk hydroflame tbh).v0.52.4 - Bladeburner in React (hydroflame).v0.52.5 - CPU cores are useful!? (hydroflame).v0.52.6 - Logboxes and VS-code (hydroflame).v0.52.7 - Fixing the previous patch tbh (hydroflame).v0.52.8 - Fixing the previous patch tbh ROUND 2 (hydroflame). ![]() v0.52.9 - Less lag! (hydroflame & community).v0.54.0 - One big react node (hydroflame & community).v0.55.0 - Material UI (hydroflame & community).v0.56.0 - Trimming the backlog (hydroflame & community).v0.57.0 - It was too cheap! (hydroflame & community).v0.58.0 - Road to Steam (hydroflame & community).v1.0.0 - Breaking the API :( (blame hydroflame).v1.0.1 - New documentation (hydroflame).v1.0.2 - It’s the little things (hydroflame).v1.1.0 - BN13: They’re Lunatics (hydroflame & community).v1.1.0 - You guys are awesome (community because they’re god damn awesome).Speaking of which maybe I am missing something fundamental though I just hope this can be resolved one day without us / me getting mails from clients (also on PC using either Edge or Chrome and a small team of Mac users also using Chrome) reporting this issue. To me it seems like that when building a WebGL the outcome might vary regardless if changes have been made or not, which makes reliable development a hit or miss thing. Unfortunately this might not be as much help for others running into these problems but maybe the Unity team might get a better overall picture of this long standing issue. I have reverted all the above mentioned settings to the ones from yesterday and now everything works again (in Edge, Chrome and Firefox on PC) ![]() WTF?! Moment of the day Unity 2021.1.15f1: + Optimize Mesh Data "enabled" / "disabled" + Strip Engine Code "enabled" / "disabled" + Compression Fallback "enabled" / "disabled" + Api Compatibility Level ".Net Standard 2.0" Sorry to necro this thread ongoing since 2015 but I also do have jsStackTrace and wasm-function errors starting today. (in this point, I have not change anything in the files given from Unity) So this solution works well. ![]() In the iframe, i just open the Unity generated index file and it shows the game inside the iframe without problems. This all works perfectly in the game and via the index file created during conversion to WebGL platform game, I can send parameters to the game and it works with those "setups".However I have managed to encounter the above error when trying to integrate the game int to our system.įirst I tried to do it with by putting the tags in to our systems running init.js file which executes function creating the iframe in the html. The thing is that our game needs to take parameters as "setups" from our system and use them in the game and when game is done, send something back with callback function. Our team is trying to integrate Unity game in to our own system built and coded with Vaadin, Java and Javascript. I'm currently trying to solve above problem in our educational game project and I have come to a dead end with searching solutions all around internet.
0 Comments
Leave a Reply. |