This topic contains 10 replies, has 8 voices, and was last updated by 
Sub_Zero 2 years ago.
-
Posts
-
new v1.1.04 are now up here for windows/macos:
https://blitzresearch.itch.io/monkey2
Also, there’s a new emscripten-v1.37.9 build tools package available from the ‘files’ package.
You should theoretically be able to extract this into your monkey2 ‘devtools’ dir (and mserver, also available from files page) and emscripten and wasm should/might ‘just work’. Does it for you?!? Not holding my breath…but emscripten/wasm HAS come a long way, wasm in partcular which is now supported by both chrome/firefox, and produces significantly smaller apps that load much faster.
Mostly working!
When I try Wasm or Emscripten it successfully compiles, but when I try to launch the page I get this window requesting input popping endlessly. If I cancel it, I get this error:
12345Could not create canvas: Could not create a WebGL context, VENDOR = 0x1002, DEVICE = 0x6821, Sandboxed = no, Optimus = no, AMD switchable = no, Reset notification strategy = 0x0000, GPU process crash count = 0, ErrorMessage = bindToCurrentThread failed: Failed to collect gpu information, GLSurface or GLContext creation failed.,:(,{"antialias":true,"alpha":false,"depth":true,"stencil":true,"majorVersion":1,"minorVersion":0}SDL_GetError=Could not create EGL contextFATAL ERROR: SDL_GL_CreateContext failed{{!DEBUG!}}On MacOS. Tested with Mserver and a simple Python server. Desktop target seems to be working fine.
Cheers.Attachments:
What browser? OS version? Googling suggests it may be a chrome thang.
I can’t actually get emscripten working here at home on a windows 10 laptop, guess there’s still some magic files missing from the emscripten-1.37.9.exe package so probably not worth trying if you haven’t got emscripten going already.
Howdy Mark, is there a README for the new build? I’m trying to understand the differences between v1104 and v1103. Thanks.
I am currently following portable sdk instructions here for initial attempt at an emscripten install on windows 10.
123456PATH=${MX2_HOME}\devtools\emsdk-1.35.0-portable-64bit;${PATH}PATH=${MX2_HOME}\devtools\emsdk-1.35.0-portable-64bit\clang\e1.37.9_64bit;${PATH}PATH=${MX2_HOME}\devtools\emsdk-1.35.0-portable-64bit\node\4.1.1_64bit\bin;${PATH}PATH=${MX2_HOME}\devtools\emsdk-1.35.0-portable-64bit\python\2.7.5.3_64bit;${PATH}PATH=${MX2_HOME}\devtools\emsdk-1.35.0-portable-64bit\java\7.45_64bit\bin;${PATH}PATH=${MX2_HOME}\devtools\emsdk-1.35.0-portable-64bit\emscripten\1.37.9;${PATH}Success! I have Wasm build of VPaint running happily in Chrome.
Downloaded and installing it right now. And I donated a couple of dollars to blitz research for this release.
Can someone provide steps to install emscripten target?
is there a README for the new build?
No, it’s really just a snapshot of the github repository. I’ll try to work out some way to attach a github changelog to future releases.
This release at least is mainly just bugfixes, but there’s a lot in there so I’d recommend ‘upgrading’ anyway.
Can someone provide steps to install emscripten target?
…this might be a bit more recent…
https://github.com/juj/emsdk/blob/master/README.md
What browser? OS version? Googling suggests it may be a chrome thang.
I’m seeing this problem on both Chrome and Safari, MacOS Sierra 10.12.4.
I also tested several of the “bananas” examples, same thing. I thought it could be a script blocker extension, but I have disabled it.<edit> Testing again, the bananas examples now work on Safari, but not on Chrome. My own project gives the same error on both. Will investigate more tomorrow, need some sleep.
Nice work!
Nice!
I’ve put up monthly donations!
You must be logged in to reply to this topic.