InsaneHawk's Recent Forum Activity

  • Update: Topic has been updated to better reflect the state of the game

  • Hey!

    Little update on the project!

    We're now in a private alpha state, and we're also looking for people that are interested by that type of game to join this alpha and help us test out everything!

    You'll find all information here: twitter.com/GameRhythmy/status/1102944913421991936

    Thanks!

  • Thanks for the link, very useful, I will certainly give it a try!

    I see in the documentation that it is also using the same greenwork plugin, which currently support NWjs up to 33.3 and electron up to 4.0 beta 7, which is also not the latest version available, you still depend on greenheart updates, which comes about twice a year.

    I'm working with NWjs 33.3 with the latest greenwork plugin and I have no issues with steam overlay, achievements or window capture in OBS, though game capture doesn't work.

    But i'm more intrigued by your statement "I've got better performances according to my tests" this enough is a good reason to switch.

    Did you test it on linux as well?

    I didn't test on linux, mainly windows to be honest, as I'm more focusing on that now, rather than linux.

    Yea, seems like some people don't have issues with it, but I'm one of those that had some, for some reasons, you know, magic's happening sometimes.

    You'll quickly see why it's better I suspect, because of many little improvement, and the progress being made by Armaldio, there's a lot of QoL things/features in it, even if building isn't as "fast" as the built-in editor nw.js but still, I think it's relevant :)

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • Hi, can you please share what other issues using electron over NWjs solved for you?

    How did you get the steam overlay and achievements working on electron without greenworks?

    Well, I had 2 major issues with NW.js, plus a side one that isn't really an issue but something that could be improved:

    - Greenworks plugin, not working as it should even if you followed every single step from the documentation, Overlay broken, lack of features/functionnalities etc.. (and the fact that you were forced to use an old version of NW.js ... Sshhhh)

    - The fact that you couldn't catch the window with a lot of recording softwares/streaming softwares.

    - When you build your game, you have to "hack" your .exe to add your game's icon, numeric signature & credits attached to it, which isn't something you want to do on every single release...

    The last 2 points where just fixed by using Electron instead on NW.js, and the first point, thanks to Armaldio + MikalDev from the Community Discord, that found solutions for Electron, working.

    You may find all the information you want here: electronforconstruct.armaldio.xyz

  • InsaneHawk Would you mind trying out the new window implementation of NWjs?

    All you have to do is, use a more recent version and add the mentioned Chromium arg to your package manifest file. You will know that it works, if it displays native Chrome stuff after pressing "F11" to go into fullscreen mode. (This is currently a bug and will get patched out soon.)

    As a side note, the mentioned multi-process architecture isn't the issue. I've done tests in the past when single processing was still working and it didn't help with the capture at all. Main reason for why I removed it from the Roundup, besides every 2nd update breaking the feature. It's something on the GPU side of NWjs that some, especially free recording software doesn't like.

    I've had success with receiving an answer from the OBS team in the past and they pretty much just told me that, it's the user's responsibility to pick a working mode for recording/streaming and so on.

    Well, I've switched to Electron and I'm happy with it, I'll most likely don't go ever back on NW.js now.

    Thing is, that I was stuck using an old version of NW.js because of their Greenworks plugin, which is forcing you to use a specific version of NW.js, in order to make it work (which obviously didn't work, since I had to find an alternative to it, being Electron (Overlay issues)

  • It's absolutely, 100% a problem with the screen recording software. It's not Construct's or NW.js's fault. If screen recording software can't record the screen, it's not doing what it says on the tin. Their software is broken. If they claim it's not their fault, they are being negligent.

    and I do agree with you that some part are being so, we both know it's not Construct's fault but still, I'm not wrong I assume saying, having more build options can also help finding better ways of doing things, and it will suit more some people.

    As right now, I'm more about compiling and only using Electron rather than Nw.js, since they won't probably do anything about it, I needed to figure out somehow a way to counter this.

  • Electron uses the same browser engine as NW.js. I don't know why it would work differently with screen recorders - perhaps they disable the GPU process, which might degrade performance. You can do that with NW.js anyway if you pass the --in-process-gpu flag. Still, as I said before, it's a bug in the screen recording software if it can't record your screen.

    BTW the latest C3 releases include the Game Recorder object which has a built-in screen recording feature... which always works!

    I don't understand how you still can't understand the issue... I'll try to make myself even more clear (let's hope)

    - NW.js had several issues for capture the window with STREAMING softwares, such as OBS, XSplit etc..

    - So now maybe you may get why, I don't care about this "built it Recording" whatever that is. Why the hell should I force Streamers and youtubers to record with that thing, when they're used to do the same with their tools, do you really think they would even bother trying to find a solution as it's not on their end? I don't think so.

    - I've contacted support, here, for OBS, XSplit, and even forwarded that to the NW.js team, no one seems to care at all.

    - Issue is, that window can't be capture, doesn't matter what you try to do, yes, "--disable-gpu-compositing" was working but it's also heavyly reducing performance of the game itself (the arg you mentioned didn't work on my end) to a point that's, it's absolutely unplayable for the type of game I'm making (which is a rhythm game, and every frame is god damn important)

    - I see you coming, no, there's no optimization problem, since I made a test batch on my game with more than 25+ different PC configurations, from very low end hardware / refresh rate to the highest ones, absolutely 0 problems noticed so far.

    - I'm sorry but Electron seems to be different somehow as, without doing anything, I've got better performances according to my tests and this issue is gone, alongside the other one linked to your official Greenworks plugin, working yes, to unlock achievements, but also absolutely incomplete in term of features (you just have to look at the documentation to see how much features it's missing). But my main problem with Greenworks wasn't the lack of features and such, as I could have workaround, what I couldn't workaround was the Overlay absolutely not working at all, switched to Electron, stopped using your plugin and magic, it's all working again.

    So yes, as I'm saying, I'm pretty sure having a secondary option to build on Windows won't be luxury.

    The more choice you'll give to people, happier they'll be (and I know how much work it does represent, but why don't you come over the Community Discord and ask "Armaldio" which is the guy working on that Electron builder for Construct 2/3? I'm pretty sure he'd be happy to help)

    Sorry if my message sounds harsh, but I'm tired of explaining the same thing over and over, when it's absolutely clear that there's an issue, somewhere in NW.js, and it's not recording software's fault as it's working god damn fine with Electron, which according to you "is the same".

  • For future notes, I solved this issue by just not using NW.js anymore.

    I'm now compiling using Electron, which is way better than NW.js on many points and solving two major issues I had with NW.js one being the topic's subject. I still don't understand why Construct isn't offering the Electron option.. but well

    I'm afraid no one is ever going to work on that problem, so if you want somehow to fix this kind of issue, it's fairly simple, don't use NW.js, try to see Electron

  • Wow, I like this style.

    Thanks! Glad you like it! :) We wanted to go with something between minimalist and a little detailed graphics, each levels will have his own "art style" but the artistic direction will stay like this :)

  • Looks great, good luck with it!

    Thank you very much for your comment! We really hope people will like it as much as we do!

  • Hello everyone,

    "Rhythmy" is a new arcade-style rhythm bullet hell game, out now in Early Access on PC, Mac & Linux.

    Steam: https://store.steampowered.com/app/1001970/Rhythmy/

    Try to dodge and survive many levels while listening to Thaehan, F-777, Boom Kitty and more, that are part of the game's soundtrack. If you're seeking for some hardcore bullet hell challenge, while listening to some epic music, you're at the right place!

    Subscribe to Construct videos now

    As the game is slowly but surely getting closer to the official release, we'll be adding more levels, modes and features to the game! But until then, here's what you can expect from the early access build on the day it launches:

    • 2 Chapters - Which will have their own design and music style!
    • 7 Levels - Splitted across these chapters!
    • 4 Mutators - Mutators are level modifiers that will power-up your experience, making everything even harder!
    • All Mutators Challenge - This is the ultimate challenge for people seeking real difficulty, you'll have to complete the level with all mutators enabled at once, are you ready for this?
    • Level Editor - Express your creativity with the Level Editor, create, share your creations with the community!

    The game in its final form will be much different, and with your input, we really hope to make it even better! Here's what you can expect from the release of the game:

    This is what you can expect from the final release:

    • 4 Colorful chapters - with their own art style!
    • 16 Levels - including bosses!
    • Level mutators - to power up your experience (and make it harder, always harder)
    • More game modes! (that we'll tell you update in later stages..! let's keep some surprises!)

    We'll also be featuring exclusive songs made for the game, here's two of them!

    soundcloud.com/rhythmygame/soundstorm-dead-or-alive-rhythmy-exclusive

    soundcloud.com/rhythmygame/soundstorm-pinball-rhythmy-exclusive

    Links

  • I used OBS to record games I built for my twitch stream. I used display capture instead of game capture and it worked fine.

    twitch.tv/vila4480

    Of course it works, since it's not about targeting the screen of the game itself, but rather the whole screen, which isn't this topic's subject :)

    The problem we're talking about is about Game capture or Window capture, and a lot of users won't ever go for the solution you've mentioned since it's really not optimal at all on the streamer's end.

InsaneHawk's avatar

InsaneHawk

Member since 15 Mar, 2016

Twitter
InsaneHawk has 2 followers

Connect with InsaneHawk

Trophy Case

  • 8-Year Club
  • RTFM Read the fabulous manual
  • Email Verified

Progress

10/44
How to earn trophies