rothers

Members
  • Content Count

    38
  • Joined

  • Last visited

About rothers

  • Rank
    Advanced Member

Recent Profile Visitors

774 profile views
  1. Electron is the worst choice as far as I can see, no cookie support, poor performance (jerky unpredictable frame rate), riddled with issues, performance does not match Chrome, cross platform issues.
  2. That's interesting but I may have found something better. What I did last night and this morning was try nw.js which is an alternative to electron. AND... It's much better. Firstly the performance is 'right' no difference between it and Chrome... secondly you don't have to 'build' anything with nw.js. Just download it, test your game by dragging your game folder on to nw.exe (on PC) and if the game runs then just zip it up in the nw.exe folder and THAT'S IT. Cookies work, sound works, no judder or performance issues, everything can be set from a text file (screen res etc.) Wow. NW.JS is the answer.
  3. This might explain the performance issues, seems it has been on going since V1.8 https://github.com/electron/electron/issues/12042 Looks like they have turned off hardware acceleration on 2D canvas! Crazy...
  4. So cookies don't work. Forget trying to make them work. However localstorage DOES work so convert any cookies over to localstorage. But as for the poor performance (scrolling jumpy, lag) I can't find a solution, it just seems Electrum does *something* every 6-7 second which causes the app to stutter. I'll test it on the PC tomorrow but as far as I can see this is a dead end. I might just have to go back to C++. Boy... converting this back to C will be a nightmare.
  5. So it turns out electron does not support cookies... which is a total disaster if you think about it. There is apparently a solution which I'm trying now: https://www.npmjs.com/package/electron-cookies (forget this, I've no idea what it does but it does not make cookies work) However further testing has shown a weird bug with electron - my game seems to freeze up for a split second every 5-6 seconds. It obviously makes it jumpy to play. Sigh. Is there ever going to be a solution to this?
  6. I've tested all 3 builds it produces on the mac (and via Wine) and they work Finally a set up which produces 3 exes for Mac, Linux and Windows from one command!
  7. Thanks! I'm glad you enjoyed it. The second and third parts are 90% done I just needed to make sure the engine worked on everything before pushing out the other two chapters. Seems the main issues are sound which is probably because I coded most of it from scratch a few years ago before the latest standards were locked down. I shall try to replicate the repeating sound. Oh and I did throw in some ZX Spectrum references later in the game
  8. *EDIT* Could you try it again, I've literally added some code to say if for some reason longvolume can't be defined to ignore the code around it. I'd be curious to know what happens. Remember to properly reload the page (dev mode). --- That's so weird, I have the same Chrome and it works fine. What OS? I'll try to replicate it. You will be able to continue in the game until almost the end where the sound panning is used again for fire. I'm going to try to fix it. It's a weird one.
  9. This is a really easy guide to installing Wine: https://www.davidbaumgold.com/tutorials/wine-mac/ Saves all the nightmare!
  10. Audio seems fine with it (so far). I've now got it building Linux and Windows builds too. Going to set up my spare PC tomorrow and make sure it works. You need to have wine installed for it to build the windows exes.
  11. Interesting, what browser and set up? I'm using extensive audio tricks which it seems some browsers don't quite support yet which I didn't know Wondering if it's gain.value which might work differently in some browsers. I've tried a hack of just making longvolume window.longvolume... usually solves these issues.
  12. This is really fun but it's quite difficult to play on a laptop with the touch pad, can't really think of a way around that, really need to plug a mouse in. Might find my steam controller and see how it plays with that. I like how the games are over quickly, no messing about, it's just war!
  13. Hello, I've been working on this on and off for years. Intended to be free to enjoy for everyone. No adverts/spam etc. This is the first version I've been happy with for a while, feedback appreciated. Bugs or issues I've missed please let me know! http://boozegames.com/wizzley/wizzley.html Not sure how robust my host is, it's 15MB. Oh CHROME ONLY AFAIK, I'll deal with the little errors in firefox etc. once I know everything is good with the game itself. It's in the style of the Dizzy (etc.) games with added gore and weapons. If you want to use a controller like the Steam controller just 'redefine keys'. Default keys are: Space jump, Arrow keys move, Z = 'inventory', X = fire. Number keys can also access inventory/change weapons.
  14. OK to update: I've now managed to make a stand alone exe on the mac with Electrum. It was like some DOS based nightmare from the 1990s. Here is what I did: Follow the Electrum quick start guide until you get something to run in a window. What you get to run is of NO USE as it isn't an exe. Then Electrum sort of just trail off about how to make that an exe. Really weird. However someone on stackoverflow pointed to: https://www.npmjs.com/package/electron-packager Which is another command line nightmare but it DOES make an exe for Mac, Linux and Windows in one go. Here is the install process (it needs admin/root access): ---- npm install electron-packager --save-dev Then the following as sudo, you will need admin password: sudo npm install electron-packager -g Then follow the guide WITHIN YOUR electron-quick-start dir: Rename the dir from 'electron-quick-start' to your app name. Make sure electron-packager is installed globally (sudo npm install electron-packager -g should have done that) productName in package.json has been set to your app name (edit it with a text editor) The electron module is in the devDependencies section of package.json, and set to the exact version of 1.4.15. (edit it with a text editor) npm install for the Foo Bar app has been run at least once (I just ran 'npm install' from the command line once) Now run: electron-packager . (with the full stop) ----- AND BEHOLD an exe which runs and compresses to 44MB. Wow. Just wow. There is serious room for a desktop one click app for this, because I don't think any newbie is going to be able to do all that.
  15. I managed to get Electrum working last night but it's working in that way where I don't know HOW I got it to work in the end. I end up with a folder which will run the game as an app so I need to try zipping it up and seeing if it will run on another mac I guess. My main worry is the other mac might need loads of libs installed to run it. The bad news is the exe is >160MB for a 1.5MB html5 game!!! If you're using <audio> then FLUID is by far the best way to wrap up a mac version, you literally just give it a URL and it gives you an exe of the url. (but if you're using anything modern like proper sound it will die), Fluid also produces tiny exes, like just a little bigger than the webpage source.