Ashley's Recent Forum Activity

  • I cannot put my project here because it's a professionnal work.

    The bug report guidelines tell you what to do in this situation.

  • It's only really a minor issue. Most games are not affected by it. It causes maybe something like +/- 2px difference. Given that dt has small random variations that can alter the game as well, you generally should design your game with enough tolerance anyway, so that this kind of offset does not meaningfully impact the gameplay. With Construct 2 being in widespread use for ~6 years, it has affected few games, and for the most part accuracy to within a few px is just fine.

    It was also a pretty complex change in the end, we basically ended up rewriting all the movement math used in behaviors, and it caused a few extra bugs while we got that right (like this and this, and would not be surprised if there are more since we only just fixed that second one). We're focusing on C3 for all new improvements, and that kind of maintenance overhead when making a new improvement is the kind of thing we only have the resources to put in to C3 going forward.

  • Nope, it's their fault. The error message clearly says what is wrong and even says what to do about it!

    We can't accept bugs in third-party addons, the addon developer must fix it.

  • The problem is WebGL 1 cannot tile non-power-of-two textures, so C2 stretches them to a power-of-two size (e.g. 32x32, 64x64, 128x128 etc) before making a tiling texture. This is lossy and causes a slightly distorted texture sometimes. However WebGL 2 can tile any size texture, so it doesn't happen if the system supports WebGL 2. NW.js should support WebGL 2, providing you're up-to-date and not sticking to an old version.

    Probably the best workaround is to make sure all your tiled backgrounds are a power-of-two size.

  • Yes, but after the beta period ends, so not for a while yet.

  • We don't have any current plans to add multiple preview windows. Maybe you should post a suggestion.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Did you get the correct Windows SDK version? IIRC if you get that wrong, VS2017 can't open it. It won't work in VS2015 either until you fix it.

  • Make sure you wait for the runtime to finish loading. That function won't exist on startup.

  • You should only have objects placed on the layout that the layout really does use. Don't place objects which are never used on that layout, since it will waste memory (C2 will preload them but they will never be used). Conversely, don't delete objects which really are used - the preloading system depends on using the initially placed objects. Even if you create them on Start of Layout, it is less efficient. If you change layouts and the previous layout used that object, if it's not initially placed on the next layout, C2 will unload it, and then reload it again in Start of Layout. This pointlessly unloads then reloads the textures for it. If it's initially placed, C2 knows to keep it in memory if the previous layout also used it.

    It's pretty simple really: just have the objects the layout uses initially placed on the layout, and everything is optimal.

  • I'm not sure, browser storage is handled by the browser. It's probably in a database somewhere in the user data folder.

  • Sketch works for me but Speedy looks like it has a bug in the minified code. If you use the Physics behavior it's a known bug, but if not please file a bug for it following all the guidelines.

  • The memory usage is based on objects initially placed in the layout. If you delete them and create them at runtime, then the runtime memory usage hasn't actually changed, but C2 will estimate the memory usage being less based on the initially placed objects. Basically the memory estimate assumes you don't create any objects at runtime.

    It's also a bad idea to delete objects you actually use from the layout, because if they are initially placed, C2 will pre-load them when the layout starts. If they're not initially placed in the layout, it will be forced to load them at the moment you create them, which can jank the game.

    tl;dr it will make things slightly worse.

Ashley's avatar

Ashley

Early Adopter

Member since 21 May, 2007

Twitter
Ashley has 1,831,266 followers

Connect with Ashley

Trophy Case

  • Jupiter Mission Supports Gordon's mission to Jupiter
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Forum Hero Made 1,000 posts in the forums
  • Forum Wizard Made 5,000 posts in the forums
  • Forum Unicorn Made 10,000 posts in the forums
  • Forum Mega Brain Made 20,000 posts in the forums
  • x126
    Coach One of your tutorials has over 1,000 readers
  • x74
    Educator One of your tutorials has over 10,000 readers
  • x6
    Teacher One of your tutorials has over 100,000 readers
  • Sensei One of your tutorials has over 1,000,000 readers
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • RTFM Read the fabulous manual
  • x44
    Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

32/44
How to earn trophies

Blogs