dop2000's Forum Posts

  • You are using Local Storage events wrong. Check out the official example:

    editor.construct.net

  • Sorry, you are right, I didn't that there are different lists.

    Even in Russian I don't understand your problem.. Can you post a demo project?

  • If both sprites are rectangular, you can use this condition:

    SpriteA.BBoxLeft<=SpriteB.BBoxLeft & SpriteA.BBoxRight>=SpriteB.BBoxRight & SpriteA.BBoxTop<=SpriteB.BBoxTop & SpriteA.BBoxBottom>=SpriteB.BBoxBottom

  • As Ashley likes to say, Answer your own performance questions with measurements :)

    How much data are you talking about? If it's less than 1MB I wouldn't worry about it at all.

  • You have duplicate "кто_написал2 Add item" actions on your screenshot.

    Also, "stop loop" after a delay will have no effect.

  • You can do this with blend modes, see this demo:

    howtoconstructdemos.com/cut-an-image-into-pieces

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Noticed another mistake in the "For X" loop - it should be from 0 to tokencount(..)-1

    Other than that I don't know what else can cause duplicate entries in the list. Add console logging to double check that Photon sends the correct data, and that this event only runs once.

  • If you want to prevent adding empty strings to the list, the second cycle is not really needed. You can just add another condition to the first loop - that the tokenat(....) is not equal "".

    I don't know why there are duplicate people in the list. Either this data comes from Photon, or maybe added to the list somewhere else in your code.

  • 1.6GB is not that bad, this alone should not cause the crash.

    When the game crashes, what exactly happens? If the browser page remains open, try pressing F12 and check error messages in the console log.

  • Your two loops are nested one inside another, this is wrong. They need to be in separate sub-events.

    Also, never use "Trigger once" in loops.

    It's possible that duplicate player names are received from Photon, to check this you can add Browser Log action to the event.

    I suggest joining Russian C3 group on VK, there are lots of people who have experience with Photon.

  • The time should only matter if there were other random operations performed in between. If you set the seed immediately before generating the land terrain, it should always come out the same.

    I don't know your game, but you can probably prepare lots of random seeds for the entire level and store them in an array. When you need to generate or re-generate a chunk of land - get a seed for it from the array and run your land generation code with this seed.

  • I had Worker set to Auto in my project, seems like for some reason it defaults to No.. Can confirm that when I set it to Yes, the issue goes away.

    Still the debug view in System tab is really sluggish. Even though the FPS is 100, the mouse cursor lags, all actions are performed with a noticeable delay, the character continues moving for about a second after I release all keys on the keyboard.

  • No 3D features in my project either.

    I think maybe the amount of information on the System tab is somehow important. In my experiments removing a layer sometimes helped. But again I tried creating 50+ layers and hundreds of variables in a test project and couldn't reproduce this bug. The debug view became slower, but was still running at comfortable 30-50 fps.

    tarek2 As I mentioned, I had this problem in an empty layout with no event sheet attached and no object instances (except for a few arrays, jsons etc.)

  • Yeah, I'm on the same Chrome version. And I found two other users on another forum who have the same issue.

    I wanted to report this as a bug, but I couldn't reproduce it in a test project, it feels kind of random. One layout in the project may work well and another very similar layout may be terribly slow..

  • This issue started happening today, but I remember someone else mentioning it. When previewing a large project in Debug View, some layouts are extremely slow, running at 1-5 fps.

    Here is an example - the layout has 10 layers, but no sprites or other graphics. And even no event sheet!

    If I remove just any one layer, FPS immediately improves to 90-100.

    Also only the System page is slow, as soon as I click any object or any other tab, the FPS improves.

    Like I said, this started happening today. I have been developing this project for the past year and the debug was always working fine..

    Anyone knows how to fix this?