TheRealDannyyy's Forum Posts

  • Introduction:

    Hey there, my name is as it says on the left and I've decided to do some research regarding UWP's.

    A group of people have run several tests on "background memory use" and we've got some interesting results out of it.

    The Problem:

    As people that read through this topic might already know, UWP's come with a set of restrictions.

    The most concerning restriction was clearly the following: The maximum memory available to an app running in the background is 128 MB. A lot of people (including myself) immediately came to the assumption based conclusion, that this restriction would make it impossible for C2/C3 to run and result in some sort of "crash".

    The Results:

    As mentioned before, a group of people inside the Construct Community Discord server, came together and found out something interesting. UWP's seem to have some kind of "technique", which greatly reduces the amount of memory when you suspend the game (e.g. open the main menu).

    TL;DR: In conclusion, memory use in the background is not an issue based on our test.

    The

    Actual Test:

    The test is fairly simple. UWP's, are as the name already implies "universal" and run pretty much exactly the same on all platforms (currently Win10 + XBone).

    So instead of doing assumption based complaints/accusations, we decided to do tests using an actual UWP game.

    (More details about the game can be found HERE.)

    Step 1:

    Install "Crystal Brawl" on a Windows 10 machine using the Windows Marketplace for UWP's.

    Step 2:

    Run the game and measure memory use, while the game is active and suspended.

    Memory Use (active): ~130mb | Memory Use (suspended): ~116kb

    Visual Proof (*):

    Our Conclusion:

    While limited use of CPU and memory in the foreground are still fairly impactful issues, memory use in the background doesn't seem to be a problem.

    Construct 2/3 games might not run with 60fps and require a lot of optimizations, it's not the fault of the engine though and rather the fault of Microsoft's deliberate hardware limitations for UWP's.

    It's recommended to submit further complaints about UWP's directly to Microsoft.

    We additionally recommend everyone do the test by themselves and give Crystal Brawl a play on Xbone or Windows 10!

    If there are any questions regarding this left, feel free to leave reply to this post or send us a PM in Discord.

    Cheers!

    *provided by

    skymen | ko = kilobyte

  • Ashley - wow, that's interesting. I love it! On another note, will C3 be able to ability to select an object in the debugger, by clicking on it directly in the viewport? instead of having to find it in the list

    Suggest it here: https://construct3.ideas.aha.io/ideas

    I'd personally like to see a complete overhaul of the debugger in Construct 3 to be honest, including enhancement like this one.

  • ...I am really not sure what to do at this point besides start over. There is literally 100+ of hours of work that just went poof into corrupt land. I am beside myself...like just cant imagine having to start over again and this is my second time having to start over on the same project in Construct 3. Construct 3 should not be used for production in anyones case, ever, until its fully stable and ready. I think I have learned my lesson now though. Cancel Construct 3, and stick with Construct 2 I guess. I cannot believe this.

    Complaining about it on the forums won't get you anywhere and I mean this in a sincere way.

    Report it as a bug (if possible) here: https://github.com/Scirra/Construct-3-bugs/issues

    If you cannot report + attach a c3p for reproduction, just hit Scirra up with an Email (support@scirra.com) and I'm sure they'll look into it and try to help you out with this.

  • Problem Description

    Construct 2 behaves in a weird way when selecting the rectangle tool inside the image editor.

    It even locks your mouse while importing sprite stips in certain cases.

    Attach a Capx

    Example Download

    Description of Capx

    Empty project a with single sprite on a layout (including sprite strip for testing).

    Steps to Reproduce Bug

    • Open example project
    • Doubleclick sprite and open image editor
    • Select the rectangle selection tool*
    • Rightclick the animation frames pane > import frames > from sprite strip
    • Click on import and notice that you cannot click anywhere

    *IMPORTANT STEP: I highly recommend to re-select the tool if it was already selected!

    Observed Result

    Any mouse interaction while importing a sprite strip is being blocked by Construct 2.

    There are also noticeable UI errors, which don't seem to be engine-breaking at the current time though.

    Rectangle selected:

    Other selected:

    Expected Result

    The rectangle tool shouldn't behave in this way and work just like any other tool. (No mouse locking and buggy UI.)

    Operating System and Service Pack

    Win 7 SP1

    Construct 2 Version ID

    r245+ (beta)

    Tagged:

  • Yeah I always forget that...

    Here it is: teleport me now!

  • I can further confirm that the rectangle selection tool might actually be at fault in this case.

    For some reason I've also noticed that parts of the right-click dialog get greyed out when the rectangle tool is selected (they still work though).

    Rectangle selected:

    Other selected:

  • Ashley & zenox98

    I can reproduce this as well. I think this issue is somehow caused by the file itself and the way that Construct 2 checks its validity.

    This is however not really a traditional "App-hang" but more Construct 2 locking you out, probably caused by an error during the importing process.

    Here is a reliable way to reproduce this issue (on my end):

    • Open an empty project.
    • Create a sprite object.
    • Choose the rectangle selection tool* > right click the animation frames pane > import frames > from sprite strip.
    • Select an image to import
    • Notice that you cannot click anywhere, however pressing escape still works (unnecessary mouse locking code?)

    *This step is very important! I highly recommend to re-select the tool if it was already selected. For some reason this also seems to be a part of the reproduction process.

  • Alright I finally found the issue and it's caused by the --in-process-gpu chromium arg. Removing that arg fixes all the "ghost process" problems.

    EDIT: I have reported this issue to the NW.js dev's and they have confirmed it: https://github.com/nwjs/nw.js/issues/6059

    This issue is not caused by Construct 2 and therefor can be closed.

  • No, that's just papering over the cracks rather than fixing the actual underlying issue. There is data being received but it's not resetting the kill timer for some reason. And the kill timer is important in case the destroy notification was lost in transit, ensuring it reaches an eventually-correct state rather than piling up zombie objects when packet loss occurs.

    Well then I guess it's all up to you Ashley.

    Is there any possible way to help you out with this? Is there something wrong with the samples that bjayfont provided you?

    (Sample 1 | Sample 2)

  • > In the multiplayer engine if an object does not receive data for ~3 seconds, it destroys it as presumably having timed out. So I think disappearing objects is caused by the timeout, and the real problem is being unable to read data.

    >

    So couldn't you disable the part that destroys objects when timed out? Or maybe add some sort of option for it? It seems that the timeout-destroy creates more issues than it solves, at least in this instance. The problem of reading data only ever seems to be momentary, anyway.

    I second that. I think a simple action to manually override the destroying timeout would be really useful for specific cases like this one.

    Ashley It would be amazing if you could add this to your todo list for the next C2/C3 beta update.

  • I'm with Silverforce and a couple of others in here.

    I think Scirra should really focus on the offline browser version of C3.

    Not because it's closer to native or something like that. It's more because I think that it would solve a lot of the current issues with certain limitations caused by browser security (e.g. local file access, creation and many more). Nonetheless I will keep on using both for now and fully switch over to C3, once it's stable and ready to use with bigger projects, even bigger than the ones which were used in order to demonstrate C3's current capabilities.

    I'd really like to support Scirra though but the lack of PayPal payment support makes it a bit difficult for me right now.

  • I've recently switched over to the 64bit version of Firefox and that pretty much "fixed" this issue.

    I have no clue what's wrong with my 32bit version but it doesn't really matter anyway, since this is clearly an issue on my end only.

    Thanks for all the responses in here again.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • With NW.js 0.23.0 I can't reproduce any problem, it always closes fine here.

    Hmm... might be an issue caused by something on my end. Is there a way to completely "reset" NW.js (e.g. registry values)?

    Please note that this only happens using C2 preview, the exported game runs and closes fine.

  • There is a way to force NW.js to use "hight performance" video card? (like new C3 do in Settings> GPU preferences (for multi GPU system)

    I think Ashley has already implemented this in the lastest stable release (R244).

    I'm not 100% sure if it works though. There is already a feature request for this one, if it for some reason doesn't work. (NW.js Issues)

  • linkman2004 Amazing work!

    I'd like to ask a short question regarding the "alpha" tag, if you don't mind. I'm working on a fairly large game and I'm a bit concerned about it.

    Are there any known game-breaking bugs that I should be concerned about or what is the reason behind the tag?

    (Also +1 on the Magicam for Construct 3 request! )