christina's Recent Forum Activity

  • in full screen? it's very jerky, yes. Performance is smooth, but lerp scrolling is jaggy.

  • thanks Tried it, it's even jerkier then! Try it?

  • 60 is too fast. Are we sure it can't work with smaller max speeds? If so, I should have thought twice about the tiny size

  • You're right. That might have to do with player.platform.maxSpeed

    Maybe she needs to move exactly a specific number of pixels for it to work. Hm

  • um putting it out there: I would never have thought of it, but someone on twitter told me to turn windows aero back on. Apparently windows disables vsync when aero is disabled? I'm so weirded out. Thanks for listening

  • Here's the capx: https://dl.dropboxusercontent.com/u/280 ... test5.capx

    Here's the exported game:

    https://dl.dropboxusercontent.com/u/280 ... index.html

    OK I know it's the usual problem:

    * pixelart game,

    * ultra small resolution 128x96

    * pixel rounding on (because I don't like sub-pixels showing whenever enemies are trying to find their footing on platforms).

    I've set fullscreen to letterbox integer, so you can see for yourselves. Just run the game and resize the window.

    When the game window is 640x480 or less, beautiful, smooth movement. Yes, it's 1 pixel at a time, but that's what's intended.

    When you resize the game window to be more than 640x480, or even worse Fullscreen, there's a ton of jerking which doesn't feel like 1 pixel at a time. It feels like the screen is tearing as well. In any case, it's suddenly not at all smooth, and it happens just a few pixels above 640x480.

    Can anyone help, this issue makes me want to seriously quit trying pixelart games on C2.

    Is it a timedelta thing? Is it a mistake on my part? I'm just using the standard platform movement.

    Is it a monitor thing? I'm noticing my second (older, crappier) monitor is almost unaffected, on chrome! Both my monitors are affected on nw.js.

    However both my monitors can play, for example, a mame-emulated version of Rainbow Islands with perfect full-scale frame rate and no jerking.

    Ashley I wish there was a way for Construct 2 to work in a mode that emulates an older processor chip, with a specific frame rate, and adjusts everything so that it looks good on modern monitors.

    thanks to anyone who takes the time, it means a lot to me.

    • Post link icon

    It is a nw.js bug, it was introduced in 0.13 beta 2 (grrrr) and fixed recently (don't run beta 2).

    It makes the game run off-screen, in distant coordinates.

    The fix is to delete your exported folder.

    https://github.com/nwjs/nw.js/issues/4265

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • R0J0hound avoiding canvas resize didn't help unfortunately. Or it wasn't noticeable anyway, and the cost was that the code became a lot less readable with all the coordinate transformations.

    But I did realize, I don't need continuous canvas redraws when I'm zooming! So I'm now only requesting a resize+redraw when layout scale is 1, 0.75 and 0.5. As you can imagine performance is stellar.

    Thanks for everything <3

  • Tetriser, hi. mine is from a pixel mockup I was making

    • Post link icon

    I dug around on the nw.js forums. Apparently, some file in the "manifest.json" ? or "package.json" ? (I'm not sure where these live in the filesystem, if you do, please tell us), can become corrupted, and can "blacklist" the name of your app.

    Changing the "Name ______ " of my project in "Project Properties" instantly solved the problem.

    Could you try and let us know?

  • zenox98 then I'm done for, because nothing above NW.js 0.12 works for me

    • Post link icon

    Windows 7 x64 and non-Steam Construct 2 here: Neither exports nor previews NW.js projects. For example the Savegames Tutorial project works fine. The ghostShooter tutorial does not. A totally empty New project also doesn't work!

    I cannot open the exported .exe files or preview, and NW.js *32 stays open in the task manager, hanging without opening a window like FraktalZero. Usually it's two instances of the NW.exe

    I've tried every version of nw.js after 0.12, but 0.12 is the last one that works. Seems the newer ones are completely broken for me

christina's avatar

christina

Member since 21 Aug, 2012

Twitter
christina has 5 followers

Connect with christina

Trophy Case

  • 13-Year Club
  • Forum Contributor Made 100 posts in the forums
  • Regular Visitor Visited Construct.net 7 days in a row
  • RTFM Read the fabulous manual
  • Email Verified

Progress

17/44
How to earn trophies