TheRealDannyyy's Recent Forum Activity

  • 1/ I managed to change all the icons EXCEPT the one of the top left corner once the game is launched on Steam.

    Probably caused by the old version of NWjs that you're using. Please update to a newer one. Read below for more info on how to get Greenworks working with newer versions.

    2/ I get weird artifacts when steam popups leave the screen in the black bars on the side of the game (if I have resized the window so that there are black bars). They leave a "trail".

    You are using Greenworks 0.33.3-r2. This is an ancient version of NWjs that you probably stay at because of the outdated Greenworks addon support. You can get up-to-date prebuilds, which make it possible to keep using the addon with newer versions of NWjs.

    (You can also check out: How To: Workaround Steam Overlay Issues With Letterbox Scaling)

  • I'd like to ask one more question regarding NWjs editor support after retirement. Will we still be able to report NWjs specific editor bugs or will those not be looked into anymore?

  • About the custom prebuilds I see that it enables support for more recent versions of nw.js (I'm currently using Greenworks + Nw.js 0.33.3), but could you explain the benefits to use more recent versions of nw.js ? I haven't seen this anywhere... I'm not really familiar with Node webkit updates and so far on this particular subject my position has been : "if it's not broken, don't fix it", but if I'm missing on something I might upgrade my game! ^^

    Software updates always contain important fixes and performance improvements. NWjs specifically got a complete overhaul of the window tech, which fixes a lot of issues with Steam and certain types of game recorders. I never tell people to use new or specific versions of NWjs because there can always be unexpected issues and downgrading can sometimes be problematic.

    I also felt quite restricted by the current official Greenworks ACEs so I'm considering updating to Greengrinds to support future DLCs for example.

    That's pretty much up to Scirra. There are TONS of features that could be supported but I guess there aren't enough Construct Desktop/Steam developers to justify Scirra to put the work into it. I don't know how Scirra prioritizes things so your best bet is to ask them directly, that's just my opinion.

  • CuL8R This issue has been worked around in the next NWjs release. It's going to be in NWjs v0.43.7 or v0.44.0 depending on how things go. I won't include it in the roundup, since it's Construct 3 specific but everyone who needs a workaround right now, can use the actions based on my example.

    (Ashley thanks for the additional help!)

  • Sounds pretty good!

    TheRealDannyyy do you think we'll still be able to use your launcher, the one that keeps things up to date?

    It will work fine but I'm not sure if the launcher will still be worth it. Technically all you'd have to do is get the json file from here, download NWjs and put it into the folder.

    Anothor thing I'd like to avoid after Scirra fully drops out, is providing support for NWjs specific editor bugs. I like helping people with NWjs specific bugs in their games but adding editor bugs into the mix, might be too much added work. I'm doing all of this for fun after all.

    If the demand is there I could keep supporting it but I'm currently thinking about deprecating it.

  • We can delete the vast majority of NW.js-specific code and stop having to maintain it with bug fixes and such.

    How significant is the mentioned code? Could it potentially corrupt projects or is it just minor stuff without any major impact?

    I generally like the plan and end goal. Posts about current progress would be great.

  • Tomycase One thing that came into my mind since you also reported the zoom issue. NWjs should save the zoom level after closing, did you make sure to reset it back to 100%? (Form size issue.)

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • The zooming issue and many more have been fixed in NW.js v0.43.4, I guess we'll get an official update next month when v0.44.0 is out.

    Please test the form issue again next month or upload something for me to reproduce. Screenshots aren't really useful and delay testing on my end.

  • Wow I was about to message you since I know you are qualified when it comes to NWjs, I'll make a post in your topic right now, thanks!

    It's alright, gonna do a heads up post when the stuff is fixed.

  • Hello everyone, I recently discovered that NWjs allows the user to zoom/unzoom during runtime with CTRL+Mouse wheel, however it can be incovenient for a user who toggle it by accident, and can screw the game display, so my question is, is it possible to disable this function with a chromium arg or something?

    Thanks ~

    Good catch! Next time please report it to Scirra directly or do a quick post inside my topic so I can look into it and create a bug report like this one.

  • I know the Text object is a Form control and I don't think Construct can do much there.. but with SpriteFonts you should be able to do anything you want having perfect pixels when scaling.

    https://drive.google.com/file/d/1mjEO_9pxkprzcZCn6BRJdVOdT6Z2tkX6/view?usp=sharing

    That's pretty much the same as it looks on my end. Downscaling is still an issue though and looks bad with Spritefonts. I'd really prefer to fix the text object instead of using spritefonts.

    If you for example scale down the window size, the text object is still readable (even with the blur issue) in comparison with the spritefont:

  • scaling SpriteFont "should" be okay as long as you have Point on.

    however, if you are upsizing the entire game this has many inherent issues.

    is your text doing any sort of movement or animated scaling?

    I have it on point but spritefont text scaling isn't the main issue. It's more an issue with the text object being blurry by default, inside the browser.

    Integer letterbox scaling works fine but I would still prefer non-letterbox scaling. It seems to be impossible to get it pixel perfect with Spritefonts, since that looks even more blurry in comparison with the text object when scaled.

TheRealDannyyy's avatar

TheRealDannyyy

Member since 30 Sep, 2014

Twitter
TheRealDannyyy has 18 followers

Trophy Case

  • 10-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
  • Forum Hero Made 1,000 posts in the forums
  • Regular Visitor Visited Construct.net 7 days in a row
  • RTFM Read the fabulous manual
  • Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

18/44
How to earn trophies

Blogs