Headbang Games's Recent Forum Activity

  • TheRealDannyyy I've noticed that Ashley mentions in the greenwork plugin post that the game's exe must be named nw.exe for it to work, I also notice you didn't write anything about it, my game and steam overlay seems to work fine for me with a different exe name, but I'm not sure what was the original problem that required this action, can you shade some light on the subject?

    I think what he meant was that even when porting you can do fishy things, intentionally or not, not to mention support and maintenance for the long term, official plugins are always safer than 3rd party, I've seen more than once that bug reports were dismissed because of 3rd party plugins.

    Now, if it was somehow officially supported by scirra as a trusted plugin, where they have a contract between them that makes sure the plugin will be supported and updated, that would be more reassuring.

    So I finally got the overlay to show up, but once it does it's not responsive to any clicks, it seems like the game is still in focus and it's receiving the keyboard input instead of the steam overlay, pressing shift+tab doesn't close it.

    I remembered the Big Roundup post mentioned adding --in-process-gpu if the overlay is not showing, though it did show I thought giving it a try and it works.

    Ashley did it work for you without it? you might want to add it to your installation instructions.

    Also it seems to work for me with badpad.exe and not just nw.exe, is there something specific I need to test that might not work and come back to bite me in the ass later?, or if it's showing up then it's all good?

  • NP, you can always use len() to get the length of the string, but seems unnecessary in your case.

  • Here's one way to do it

    http://headbangames.com/textbox.capx

  • I noticed you're using the old OBS and not the new "Studio" version, I thought that might help, but it doesn't work either

    When I switch out of the game window and it loses focus I can see the NW.js window frame with the game title in the recorder but the inside window is still black.

    My game is already live on Steam for a few days now, but it's in early access, so maybe they treat it differently.

  • Are you sure you're talking about window mode and not screen/display mode?

    That's the only one that works for me with --disable-direct-composition

    I have NVIDIA GeForce GTX 750

    Actually this was originally reported to me by a player who uses an ATI adapter.

    A long time ago when I tested it, it worked even in game mode (more than a year ago), but somewhere since then it got broken.

    What settings can cause this?

    I tried all the options available on OBS, none of them seemed to help.

    Personally I do my recordings with NVIDIA built-in game recorder, works better than anything else, but it also needs --disable-direct-composition to work, and not everyone got a GTX 600+ for that.

  • I was talking about windows capture, it still needs the --disable-direct-composition to work, I couldn't get game capture to work for quiet a while now regardless of version or args.

    Oh I didn't know Steam had it as a requirement, good to know, I was taking my time with it, I'll add it asap.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Quick question, why are you targeting 

    %LocalAppData%\GameName\User Data[/code:6flu62pg]
For the uninstall script and not [code:6flu62pg]%LocalAppData%\GameName[/code:6flu62pg]
Is there any reason to keep the other cache directories on the root directory of the game?

  • Oh sorry I missed that, here it is:

    --disable-plugins --disable-internal-flash --disable-popup-blocking --enable-gamepad --enable-html5-camera --allow-file-access-from-files --disable-software-rasterizer --ignore-gpu-blacklist

    using NW.js 0.19.2 on windows 10 64bit with obs studio 17.0.0

  • "How To: Workaround Recording Issues & Canvas Flickering (NW.js v0.14.0rc1 - v0.19.0)"

    It refers to both, maybe it just fixes the flickering.

  • > FYI, NW.js 0.19.2 still produce black screen on OBS without '--disable-direct-composition'.

    >

    Basically what BackendFreak said, this is a more technical bug that the Chromium team will hopefully take care of.

    You could try to use --single-process but I doubt that it will fix the bug. I'll do a post when the new update update goes live.

    tecbug I'm still waiting for a response from MadSpy, he seems to be rather busy right now.

    I'll add everything new to the roundup as soon as the fixes for Steam4C2 and Greenworks are done and ready to be released to public.

    As always, patience is the key.

    --disable-direct-composition fixes the bug, but it says in the post that from version 0.19.1 it should work without it, but it doesn't, waiting for Chromium 56.

    I've tried --single-process before, it didn't do anything besides causing the game to stop working.

Headbang Games's avatar

Headbang Games

Member since 5 Dec, 2012

Twitter
Headbang Games has 1 followers

Connect with Headbang Games

badpadgame.com

Trophy Case

  • 12-Year Club
  • Jupiter Mission Supports Gordon's mission to Jupiter
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Popular Game One of your games has over 1,000 players
  • Coach One of your tutorials has over 1,000 readers
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • RTFM Read the fabulous manual
  • Email Verified

Progress

21/44
How to earn trophies