Limitation WebGL & Save Environment

Plugin-free alternative to the ShiVa Web Player and Flash

Limitation WebGL & Save Environment

Postby giggsy » 2018-04-13 14:27

Hi,

I'm currently doing some testing with WebGL and noticed weird behaviour, when saving data to the environment (and possibly saving alternative data into another environment).
Could you outline the limitations of environments in WebGL?

They somehow seem to work, but my test case (which includes the switching) doesn't always seem to work ... but on the other hand, sometimes it does.

Thanks!
giggsy
Platinum Boarder
Platinum Boarder
 
Posts: 1149
Joined: 2010-06-27 21:17
Location: Austria

Re: Limitation WebGL & Save Environment

Postby broozar » 2018-04-17 00:55

hi giggsy,

if it sometimes works and other times it doesn't, that sounds like a bug to me. i'd like to see a sample to reproduce some of your findings.
please also keep track of things like browsers and their versions, local vs remote server testing, etc.

not sure what you mean by "the switching" though.

I am not informed about any limitations with the environment. for engine specifics, you need to ask NiCoX through e-mail or slack. but let's find out together first if it's browser-related or a true bug.
User avatar
broozar
Administrator
Administrator
 
Posts: 4118
Joined: 2007-09-16 10:22
Location: Berlin - Germany

Re: Limitation WebGL & Save Environment

Postby giggsy » 2018-04-17 07:45

Hi,

by switching environments I mean we got the following enivronments (=STS files):
* config (keeps track of must current savegame)
* savegame A
* savegame B

So my current suspicion is, that saving genereally works, but switching might get messed up (e.g. if you quit the game when saving).
That's what I would try next (in the next few days) and then I can try to give you an example to reproduce.

Thanks so far for you offer!
giggsy
Platinum Boarder
Platinum Boarder
 
Posts: 1149
Joined: 2010-06-27 21:17
Location: Austria

Re: Limitation WebGL & Save Environment

Postby broozar » 2018-04-19 11:31

the games are run on the client in a browser sandbox. if you quite the game, i would be surprised if any of the information is carried over to the next run. at the very least you cannot rely on it. also file access in the browser sandbox, especially chrome, is quite painful. that's one of the reasons why local html5 websites like my "ports" for ChromeOS or FreeBSD have to run on a local microserver http://www.shiva-engine.com/html5-anywh ... localhost/ for details on how STS is affected by that, you would have to ask NiCoX.

i suppose if you want persistent saves, you will have to go the old "send xml to php script and store in a database" route that was necessary with the old webplayer.
User avatar
broozar
Administrator
Administrator
 
Posts: 4118
Joined: 2007-09-16 10:22
Location: Berlin - Germany


Return to HTML 5

Who is online

Users browsing this forum: No registered users and 4 guests

cron