DiegoM's Forum Posts

  • The latest beta, r351, adds a new tag property to animation frames. The property is supported by the bulk importer. I will update the first post with information on that.

  • This might sound kind of obvious, but if you already have some grasp of how Construct works, just start trying to do what you want.

    Since you are trying to do something similar to something that already exists, look at it and decide what part you want to replicate first, this will likely be what you think is most important. Once you have decided were you want to start, it becomes much easier to find a solution for that particular problem.

    Once the initial small problem is solved, you build upon it. Decide what is the next bit that you want to add and find the solution for that... then it becomes a matter of adding small individual pieces until you have everything you want. This process can take a while, so try not to get discouraged if you start to notice it's taking a long time. The good thing is that with each small problem you solve you become more familiar with the tool, so adding further things slowly becomes easier.

    This approach will help you retain what you learn much better, because you will be solving problems you made up for yourself rather than the abstracts in a tutorial.

  • In your example the green square can not be set to be a replica because there aren't any other instances of the same object type which are set to be templates.

    You would need to add another instance of the blue square and that one would be able to be set to be a replica.

  • Unfortunately Admob is incredibly opaque about how it works, there is nothing we can do to help with these kind of cryptic behaviour on their part.

  • Anyone who is encountering this problem, how are you importing the images exactly? As in which of the options available are you using?

  • Ribis

    That looks like an error coming from an extension, the extension is probably ignoring it, but C3 catches it. There have been reports of the Last Pass extension causing it, but it could be any number of extensions. Try disabling your extensions one at a time to try and figure out which one is the problem or just turn all extensions off when using C3.

    jobel

    What kind of images are you using? As in size, amount of frames and format.

  • The way you have it set up the loops are executing every tick, so effectively all the time.

    If you want a loop to only happen after something else takes place, you should place it as a sub event of either:

    1) A block of conditions you want to be met before the loop executes

    2) A trigger condition

    In your example try placing the the loops you have as a sub event of the On start of layout trigger.

    Doing that will cause them to only run once, in this case, when the layout starts.

  • I think the problem you have is logical. For 16 unique answers, you can only have 4 different questions if each of them have only 2 answers, that would be 2 * 2 * 2 * 2 = 16.

    With 4 questions you guarantee to get a unique answer each time.

    Right now with 8 questions you have 256 possible results. That's 2 * 2 * 2 * 2 * 2 * 2 * 2 * 2 = 256. So if you have a catch all case, it makes sense that most people are getting the same result, only 16 combinations out of 256 have something! The probability is 16 / 256 = 0.0625 which is 6.25%. I think i got the math right... in any case, it's a pretty low chance.

    If you want more questions there are a couple of things I can think about that you can do.

    1) More unique answers. So for 5 questions with two possible answers, you would need 32 unique answers. 2 * 2 * 2 * 2 * 2 = 32. That might be a lot of work, but the results are guaranteed to be unique.

    2) You can have questions that decide the main result and questions that only wedge the main result a little bit. This will allow you to keep the answers you have and potentially have an infinite number of questions. This approach requires additional logic to decide exactly what it means to "wedge" the final result, and once that is decided, how big each wedge should be? The good thing is that you don't need to produce more unique results.

  • You have the "Open in Construct 3" option, so that means Construct is already installed as an app in Chrome. That's why you can't see the "Install" option.

    Have you tried opening it by clicking on "Open in Construct 3"?

    Edit: Sorry I missed that part of your original post.

    Try uninstalling C3 by opening it using the Open in Construct 3 option, and then going into the menu in the top right and choosing the Uninstall option. Then try installing it again.

  • Some browser extensions can cause problems with C3.

    Recently there have been a few reports of the error ResizeObserver loop limit exceeded. If that is the error you are seeing, try disabling your browser extensions to see if it makes a difference.

  • To answer the original question, there is no built in way to do what you want.

    The easiest thing I can think of is keeping track if the boss has been defeated in a given room, then with that information decide if it needs to be destroyed or not after recreating all the instances in the corresponding room.

    This falls in the domain of very specific game logic, so C3 doesn't provide a special way of doing it.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • This is 100% an issue with some extension.

    C3 does not use the ResizeObserver object anywhere. So if that is causing a crash, it's coming from somewhere else.

    Try disabling your extensions one by one until you notice the problem stops.

  • I just checked the feature support and it seems that Firefox and Safari are falling back to our custom resize algorithm.

    I will have yo try it out to be sure that is the case.

  • It makes sense that the problem is still present in Edge and Opera because much like Google's Chrome, they are based on the open source project, Chromium. So they pretty much have the same strengths and weaknesses.

    Firefox and Safari are both unique, so they have different strengths and weaknesses.

  • This seems to be related to this chromium issue. Where the maximum quality when resizing doesn't produce the expected result.

    bugs.chromium.org/p/chromium/issues/detail

    C3 is using a browser feature to produce resized images when it is available, if it is not available, it falls back to our own implementation of a resizing algorithm, which I have noticed produces better results, the problem is that it isn't as efficient as the browser and it is prone to run out of memory.

    For a while now the feature has been supported by browsers, so the custom resize logic isn't used. In any case, I prefer to not use that because the browser implementation will be way better, assuming it works. The problem is that there is no reasonable way to detect if the resizing is working properly or not to fallback to our resizing method.

    Is this a problem in other browsers? Namely Firefox and Safari.