Ashley's Forum Posts

  • Which export option are you using? Clipboard features should work in Chrome on Android. However if you're exporting an Android app there's a known issue that currently prevents copying to the clipboard from working.

  • I've been thinking about the future of the desktop exports, especially as I'd like to support other stores like the Epic Games Store too, but the current approach of relying on the current set of third-party tools isn't working out (as noted Greenworks is essentially abandoned and I don't believe any Epic Games equivalent exists).

    TBH I'd prefer to move everything over to the Windows WebView2 export option. I've been impressed with how well WebView2 works, and it has the official backing of Microsoft, who have a lot more resources than the NW.js team (who seem to have been struggling to fix even serious regressions lately). It would be more feasible to develop our own Steam/Epic integration for the WebView2 export option as we already have a custom container app around the WebView2 control.

    The only downsides are:

    • Currently WebView2 is Windows only, but:
      • their roadmap does say macOS and Linux support is planned
      • Our stats show the vast majority of NW.js exports are for Windows anyway, so maybe it doesn't matter
    • The Steam Overlay doesn't appear with WebView2 apps, and the command-line workarounds for NW.js don't seem to work for it. I already reported this to Valve, but there's been no progress yet (and my past efforts to get them to fix things have been fruitless, which is why there's a bunch of quirks with NW.js that Valve never fixed).

    So it's a bit of a mess, but so long as the existing stuff keeps working I don't think there's any major urgency. As ever it's also a lot of work whichever path we take and with our limited resources we'd have to delay or cancel some other planned features or tasks to work on this. I'd be interested in thoughts on using Windows WebView2 for Steam publishing, assuming we got it to work - would the lack of macOS or Linux support be significant?

    I'd add it should be possible for third-party developers to step in too - there's nothing stopping a third-party developer (or contracting someone to do the work if it's that important) to write the necessary integration for the existing NW.js export. That includes forking and updating the existing Greenworks code which should provide a fairly mature starting point.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • It's difficult to see how it could be implemented like that, as it doesn't necessarily know which object will be its parent, and its parent's image points could vary across different animations and frames. A good example of a feature that looks obvious but is in fact probably impossible in that form.

  • That's why the Pin behavior is still there and the manual terminology around it being superseded refers to most (not all) features being replaced by hierarchies.

  • Surely there has to be a better solution then reporting it to each individual vendor, specially if this is a general problem native to construct or nw js?

    I'm afraid there isn't. Everyone affected should report any false positives to their antivirus vendor. It's the only way things like this get sorted out.

    I'm pretty sure this is nothing to do with the icon updater, and the base files themselves are flagged as false positives. Perhaps the fact the icon updater tool modifies the files causes antivirus software to take note.

  • Check the 'Export file structure' setting in Project Properties. If it's 'Flat' then subfolders are not used after export. However if it's 'Folders' it should work.

  • Regardless though, you still need to submit such false positives to the antivirus vendor, so they can improve their detection and make sure they don't incorrectly flag files. I suspect there is a single change they can make to their detection that will avoid all false positive cases with NW.js, so long as they have some examples of false positives submitted by users.

  • That's not the case though - suppose you tween the angle of a child in a hierarchy while the parent also rotates. You'd expect the child to rotate relative to the parent. So it isn't going to end on the tween end value. It's cases like this that mean the Tween behavior can't just say "at the end set the exact finish value" - in fact it used to, but it broke cases like the one I just described, so it can't do that.

  • You need to report false positives like this to the antivirus vendor. Only they can change what is detected as malicious or not.

  • There's loads of things that can cause floating point precision errors. Pretty much any fractional math can end up with results that are close to but not exactly correct. It's just something you have to deal with in any kind of tool with any kind of software that uses floating point data types. A famous example is that 0.1 + 0.2 = 0.30000000000000004.

  • The EXE file always has the same content regardless of the project, but changes between each NW.js version. You only need to submit it once per NW.js version that you export with that is incorrectly detected as malicious.

  • IIRC, the tween behavior cannot be exact, because it has to make changes in small steps, in case anything else changes the thing that is being tweened. However changing things in small steps is subject to floating point precision errors. It's just part of how maths works on computers. I don't think it's possible to reliably work around it - the best approach is to avoid making exact comparisons and allow a small tolerance (e.g. is within 0.001 of a number instead of exactly equal).

  • Browsers block access to certain folders for security reasons. For example if you granted a web page access to your entire Documents folder, the web page can access everything there - and a malicious page could then try to steal it all. To mitigate that you can't select the entire folder for certain sensitive folders like Desktop, Documents etc., but you can select a subfolder within them.

    If you only need to open one file, then just use the open file picker anyway - the user can just choose themselves rather than having your project try to list all available files.

  • As ever the first thing to check is the browser console and see if any errors are logged there. I'm not sure how to check the browser console on Xbox - Microsoft might have some documentation on how to remotely debug it.

  • It seems that anything containing "On collision with: (object with the solid behavior)" is no longer working. This is a huge problem.

    I just tried it and it's working fine. I've also not seen anyone else reporting the same problem.

    As ever it's impossible to help unless you file an issue providing all the necessary information.