TheRealDannyyy's Forum Posts

  • Construct 3 - Launcher V2.1.0 Released!

    This release improves Launcher performance. Custom Construct 3 NWjs releases are now being delivered from NWjs.io. This makes it easier for me to one-click deploy updates in the future.

    Full Changelog

    To view it, go to the Main Post and click the Software Changelog tab.

    Cheers!

    That's why we need to make changes NOW !!!! Let's work together on an Exporter for the Nintendo Switch or the Ps4 cause we need to get onboard one way or another, NOW !!!

    Don't get me wrong but if it was that easy, Scirra with their years of experience would've done it already. It's much faster to just remake entire games inside another engine with the exporters you need, than going through the process of setting up a "native converter".

    You aren't the first one to ask for native exporters, it's been done so many times in the past and never really resulted in anything. Back then we didn't have services like Chowdren, so it might be worth politely asking them again for their support. They seem to specifically support Construct and have a compilation process going, while other 3rd party services mostly do line-by-line ports. If you're willing to invest a lot of money for a line-by-line port, you might as well put some work into switching the game engine and hire some freelancers to help you out.

    Who are those companies !?!?! and please don't mention Chowdren cause they are way busy and I ain't waiting for two years for a response. Why don't you try to get along with those companies instead and bring them to Construct in an official way.

    > I'd point out that as I mentioned, people can, and do, publish their Construct games to Switch and PS4 using third-party companies.

    It's not as easy as "getting along" with the Chowdren Team or any company that's willing to port your projects to a native environment. Business is complicated and cooperating on such a level would require a great amount of legal and set up work. Native ports of games often, if not always require specific changes to be made to the build process, assuming an automatic builder/compiler is used at all. This alone would require tons of work since most games use 3rd party addons and similar.

    (As a side note. Good luck getting Chowdren or other 3rd parties on board with sharing their profits with Scirra. Why should they, if they can just independently provide the service and get 100% for it?)

    I know it's frustrating but that's just how things are. Piracy prevention aside, Nintendo probably saw that there weren't a lot of HTML5 games on the WII U and decided to drop support for it. Unless there are thousands of developers requesting it, I don't see this happening anytime soon.

  • > Do not run it every tick, it will kill performance.

    Yeah it was just for testing purposes.

    I'll try the workaround for the overlay not refreshing, but I already have objects moving on and out of screen (namely one tiledbackgound looping infinitely), so I'm not expecting too much ^^

    I will see if that works and come back to share the results.

    Make sure you have the right chromium args as well. If nothing else works, you'd have up upload something for me to test with the given NWjs version.

  • Thank you so much for doing the reporting! Does it mean if I revert back to an older nw.js (say 0.43.1) it would "solve" the icon problem?

    You have to test it yourself, no clue.

    I tried your pluginless workaround. First, thanks for cobbling it together! I didn't know when to trigger this event since the steam popups do not trigger the "On Overlay Activated" condition, so I went ahead and let it run every tick for now. Unfortunately I didn't see any change regarding the trail that stayed as usual :/

    Do not run it every tick, it will kill performance. Check out "How To: Workaround Steam Overlay Not Refreshing" if nothing else is working. It's fine on my end so it's safe to assume the problem is from something on yours.

    Heads up, if you decide to stay on older versions, I won't be able to help you. Older versions might have issues like this that have already been fixed.

  • Sam Dimanche I've looked into the window bar icon and it's probably a regression, reported here.

    About the Steam Overlay trail issue. I made a "pluginless" example that you can download and test on your end. (IMPORTANT: This will not function in Construct 3 worker mode!)

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Just wanted to add that these are official node files based on the Greenworks repository, nothing is customized so they are as they come from GitHub. We'd fully allow Scirra to take advantage of this and update the addons accordingly.

    We won't create an idea since we've set all of this up already (kinda seems unnecessary at this point) but if some community members want to do it, feel free to do so and reference this topic.

  • Regarding the "trail" problem: it is still there.

    I didn't think to look at the particular workaround you're refering to, somehow I thought it was for Letterbox Integer Scale... But the plugin is aimed at construct 2 and I don't find it on the C3 plugin page :/

    (I realize we're in the C2 section of the forum but this topic seemed general enough)

    How would you go to try an equivalent workaround on C3 ?

    Thanks again for a much appreciated help.

    It's for any kind of letterbox. The trail issue is actually caused by Construct itself. The engine basically doesn't refresh the letterbox around the game canvas and since Steam requires a constantly refreshing canvas (including letterbox), it leaves trails behind.

    You could try and report it as a bug since it's caused by Construct but I already did in the past and it got denied because that's how it's supposed to work.

    Sorry no clue how C3 handles the letterbox stuff with the new runtime and such. I'll see what I can do.

  • Added support for NWjs v0.44.0+ as usual. See'ya next month!

  • 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.