TheRealDannyyy's Forum Posts

  • Description

    The buttons to view the "Z Order Bar", "Bookmarks Bar" and "Configurations Bar" aren't working anymore. Toggling them doesn't show or hide the bars as expected.

    Also toggling any bars while the image editor is open leads to some weird results. I assume that this could be an unwanted side effect of the recent "edit button" crash fix.

    Reproduction

    1. Open Construct 2 r266 or r267 (cannot reproduce in r265)
    2. Try to toggle any of the mentioned bars
    3. Notice that the bars aren't appearing as expected
    4. [Optional] Repeat steps while the image editor is open

    Version

    Tested and could reproduce using Construct 2 r266 and r267 on Windows 7.

    Tagged:

  • After testing out some MacOSX custom builds with the help of Mikal and using a Virtual Machine, we've got some pretty bad results.

    Some of the bugs I experienced:

    • Invisible/broken buttons in several dialogs
    • Launching external image editor not working
    • Random glitches inside the image editor
    • Crash when opening large project (probably VM related but still)

    My VM results and Mikal's real-machine results were overall the same. Basic features like opening and saving projects as folders were working fine, some good news.

    In conclusion: I will not provide any custom builds, since I don't think that they're ready for use yet. I'll keep trying to iron out some of the issues if possible but most of them seem to be caused by Construct 3, simply not having the code to support OSX systems.

  • > Any news on a Mac version of the desktop build?

    We do need MAC version, please. I know a lot people still using C2 because it works on desktop, they're not into cloud app or something, Im kinda like this.

    Technically it should be possible right now but I think Construct 3 isn't ready for it, which is why Ashley probably doesn't provide those builds yet.

    If you're interested in experimenting around, I could provide custom MacOSX builds but they will require some workarounds. Since I don't own a Mac or have a VM ready, I would create the builds on my Win7 PC. This means that file permissions will be completely messed up and you guys have to deal with that on your end.

    I'm open to do it for you guys, if any MacOSX user is up for the task.

  • Hi Tom and/or Ashley

    I would like to request a Constuct.net port of the Construct 2 NWjs downloads webpage, if possible.

    While it's fully up to you guys on how to do it (if at all), I'd recommend setting up something similar to the current Construct 2 addon database. The old webpage could then also redirect to the new webpage, until it's eventually completely offline.

    Tagged:

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Does anyone happen to know of a previous version of NWJS where this bug was not present? scirra.com/nwjs

    Currently the download site seems to be down but I'd recommend trying out releases prior to v17. Keep in mind that older releases might come with other, potentially worse issues so downgrade at your own risk.

  • Worth mentioning that I personally wasn't for or against the current system, just curious about per-pixel collisions in HTML5. Thanks for the info!

    If anyone knows any edge cases for polygon collisions, feel free to post them.

  • Regarding the polygon object suggestion. Didn't Construct Classic support pixel based collisions, couldn't the code for that be ported?

    I know it was more of a "hack" back then but I guess if it works, it works.

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

  • Hey, do you guys know if gamepad vibration works on UWP exported projects?

    UWP currently still runs based on the "old" Edge browser, so it shouldn't support it. This might change when they update Edge with a Chromium base (preview builds were planned for early 2019).

    — Are you comment 5 on the Chromium Bugs issue?

  • FYI false positives in antivirus software should be reported to the antivirus company, not the makers of the software identified as a false positive. There's pretty much nothing you can do about a false positive unless you're the AV company.

    That's true but they tend to have experience with these and as a result better ways to get in contact with the antivirus companies. Also they might know a way to prevent the false positives from happening in the first place.

    Here are the submission forms for both, just in case:

  • Here's a picture of the BitDefender alert (in french, if you need translation, I'd post it)

    > What version of NWjs are you using?

    nw.js v0.33.3

    Great thanks for the info. I think it's clear enough that it detects NWjs as ransomware.

    SecondDimension Do you use the same version? I'm planning to report it to the NWjs dev's. Internal changes in newer versions, could cause certain antivirus software triggering false positives.

  • Just to clarify a bit, this isn't an issue with the Greenworks plugin (we're not using that) but it is a problem either with the later versions of NW.js or Chromium.

    I've cut everything out of the loop (so no Greenworks, no Steam, no overlay or Construct 2), and tried using a simple set up including Christywl's basic example (which was confirmed to be working) in this bug report https://github.com/nwjs/nw.js/issues/5871 and just running nw from the command line. I just get a completely white screen when --in-process-gpu is added to the package.json chromium-args, if it is using nw.js 0.34 or above, and it works fine on 0.33.3 and below. So that isn't related to the Steam overlay, it just doesn't render anything at all.

    We thought it probably best to give a heads up that some people might run into issues with that workaround and the current versions of nw.js for Construct 2. It may not be everybody that encounters this but it is certainly an issue on my system. I've not done any investigation into it at all, I'd guess probably a chromium issue, I'll try and spend some time on it when I get the chance and raise it as a bug report.

    I will give this another run using the latest version and check out what's going wrong.

    Did something happened recently with security softwares concerning NWjs ? A customer of our product reported us that Bitdefender is preventing our application to start...

    What version of NWjs are you using?

  • OK, understood on the antivirus. I'm sceptical that contacting Norton will achieve anything though if I'm honest, but I might see if I can find a few other Steam games using nw.js and see if the same thing happens (just to have some ammunition).

    There is unfortunately no other "easy trick" for this one. It's the same with certain types of game recording/streaming software not working properly with NWjs.

    If it passes Valve's testing process, there should be nothing to worry about anyway. Maybe creating a discussion topic, stating the issue to your customers could help a bit.

    With the overlay, if you don't add in --in-process-gpu on the latest version then it doesn't work at all, as in no Steam overlay shows. If you add in --in-process-gpu then all we got was a white screen when trying to view the overlay. It's all working fine on 0.33.3

    I have no experience with Greenworks at all, since I'm using Steam4C2. I guess Headbang Games is right and your version simply isn't supported yet.

    (PS we are not using any achievements or Steam features on our first release)

    Unless you are under pressure because of a publisher or something else, I'd personally really recommend doing things step by step and not rushing it out.

  • Firstly, the --in-process-gpu fix for the Steam overlay isn't working with the latest versions of nw.js (I guess a bug introduced in Chromium?). From our testing it seems to have stopped working some time around 0.34, the last version that it still works in is 0.33.3

    What exactly goes wrong? Does it work fine without it, using versions after 0.34?

    Secondly, when launching the game through Steam we get an issue with Norton raising a 'Suspicious Network Activity' warning, which makes it looks as though something bad is happening. In reality the connection is just the SSDP protocol for uPnP (Universal Plug & Play). This is really beyond me, so not sure what to do. Is there anything we can do to stop this? Screenshot below to illustrate, thanks for reading and any advice appreciated.

    Sorry there is nothing I can do for 3rd party antivirus software. The only thing that could be done is reporting it directly to them. I know it sucks but that's just how things work with Construct and NWjs.

    If you don't get any response from them for a while, I could try to report it to the NWjs team. They might have a way of their own, to reach out to them.

  • I can also reproduce this. Only floating windows seem to be affected.