About Monkey 2 › Forums › Monkey 2 Development › V009 now up!
This topic contains 33 replies, has 8 voices, and was last updated by
peterigz
2 years, 10 months ago.
-
AuthorPosts
-
June 6, 2016 at 1:08 pm #924
wiebow:
Mollusk is for Windows and Mac OS X. Don’t know why not Linux.June 7, 2016 at 8:53 am #937[quote]Don’t know why not Linux.[/quote]
Is it like an operating system or something?
June 7, 2016 at 12:27 pm #939No, Linux is a kernel.
June 8, 2016 at 6:33 am #968
Hi,
Above is an image of monkeyroids built with Emscripten running on Firefox. The text is not right as you can see but the game will play. If I launch the monkeyroids.html file from a file manager it will crash the browser, but then work on the second try. It will not work in Chrome. All of this is on my Linux Mint 17.2 system.
My own framework will not work either. It will run much in the same way as monkeyroids but all of the non-imported (not using build system) assets are not displayed. So it appears that if I use the file system to load assets they are not accessed. This probably makes sense in Emscripten and I am not sure how to include assets that are loaded at runtime.
Just FYI.
June 8, 2016 at 7:00 am #969Are you using the latest emscripten? Latest GL drivers etc?
I’m on 1.36 here and all is OK, but to be honest, problems with emscripten on linux don’t surprise me all that much.
If I launch the monkeyroids.html file from a file manager it will crash the browser
You wont be able to run emscripten apps from the file manager reliably – they need to be served, hence the use of mserver. Any crashes here are definitely the browser’s fault – it’s just a web page with some javascript in it after all!
To load ‘non-assets’ at runtime in emscripten will require the use of a httprequest, possibly via an eventual http:: stream.
June 8, 2016 at 7:20 am #972Mark beat me to it. With the msever.
Running from the file manager would throw an exception as assets wouldn’t be loaded.
What works with a browser still depends on whats been implement within that browser. Chrome would be that better choice as always. So far the only thing that doesn’t work properly if the grid demo.
June 8, 2016 at 7:29 am #973@Mark Sibly: There appears to be an issue with loading audio in Linux Desktop (so far). The Load function in the Sound Class is loading data into the data buffer and SDL_RWFromMem appears to doing something. But Mix_LoadWAV_RW is returning Null.
Try the spacechimps mojo demo.
June 8, 2016 at 8:01 am #974“Are you using the latest emscripten? Latest GL drivers etc?”
I am using SDK version 1.36.5. I have the latest open source driver for my Radeon card so as far as I know I’m good. My other dependencies should also be current. But, I’ll double check it. I was also thinking maybe without mserver the fonts were not loaded?
“they need to be served, hence the use of mserver”
That I am sure is the case but so far I do not see a way to build mserver. Is there a script to build it? So far using rebuildall.sh and emrebuildmods.sh do not get mserver built.
“To load ‘non-assets’ at runtime in emscripten will require the use of a httprequest, possibly via an eventual http:: stream.”
Good to know.
June 8, 2016 at 8:27 am #975So in reference to above if I read this Java console output from Chrome right (testing mojotest sample) it’s not working because it can’t load requested data. This is because of no mserver (just trying to understand the issue)?
Java console output from Chrome when testing sample mojotest.
- mojotest.html:1310 XMLHttpRequest cannot load file:///home/moonbasealpha/Programming/monkey2/modules/mojo/bananas/mojotest/mojotest.buildv009/emscripten_release_linux/mojotest.html.mem. Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-extension, https, chrome-extension-resource.(anonymous function) @ mojotest.html:1310
mojotest.js:1 XMLHttpRequest cannot load file:///home/moonbasealpha/Programming/monkey2/modules/mojo/bananas/mojotest/mojotest.buildv009/emscripten_release_linux/mojotest.data. Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-extension, https, chrome-extension-resource.fetchRemotePackage @ mojotest.js:1
mojotest.js:1 Uncaught Error: NetworkError for: mojotest.datafetchRemotePackage @ mojotest.js:1
mojotest.html:1249 [post-exception status] Preparing… (0/1)Module.printErr @ mojotest.html:1249
June 8, 2016 at 8:29 am #976@Richard Betson: If you have MonkeyX installed then you already have it. Make a link to your MonkeyX directory in Monkey2/devtools. Name this link MonkeyXFree86c.
As for the Firefox font issue.
What works with a browser still depends on whats been implement within that browser.
June 8, 2016 at 8:38 am #977If you have MonkeyX installed then you already have it. Make a link to your MonkeyX directory in Monkey2/devtools. Name this link MonkeyXFree86c.
Awww. Got it thanks.
June 8, 2016 at 8:49 am #978As I suspected the lack of mserver running was not allowing it to work in Chrome. With mserver running monkeyroids works awesomely so far. The only wiggle is the arrow keys up/down are scrolling the screen. Firefox must be having issues.
So thanks for the help! Mark and dawlane.
June 9, 2016 at 8:16 pm #1013Hey Wiebow, will your sublime text language highlighter be available as a package at any point?
June 9, 2016 at 8:52 pm #1014Hi Pete,
I guess it will be! I’m heavily testing it right now, but i’ve put a copy on google drive if you want to try it. I’m using ST3 btw. Put it in your packages/user folder.
https://drive.google.com/file/d/0B808ULgYyi5FM1FjUlA5MW5uZ2M/view?usp=sharing
Still working on snippets, etc…
June 9, 2016 at 11:23 pm #1016Great thanks! Will give it a try tomorrow
- mojotest.html:1310 XMLHttpRequest cannot load file:///home/moonbasealpha/Programming/monkey2/modules/mojo/bananas/mojotest/mojotest.buildv009/emscripten_release_linux/mojotest.html.mem. Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-extension, https, chrome-extension-resource.(anonymous function) @ mojotest.html:1310
-
AuthorPosts
You must be logged in to reply to this topic.