corlenbelspar's Forum Posts

  • Problem Description

    When point sampling is used and a spritefont is at a scale of 2, for example, it will have a bunch of incorrectly scaled pixels if you use letterbox integer scale and NWjs.

    Attach a Capx

    https://drive.google.com/file/d/0Bz86oQ ... sp=sharing

    Description of Capx

    Demonstrates a problem with the spritefont.

    Steps to Reproduce Bug

    • Make a spritefont at scale 2, for example.
    • Use point sampling and letterbox integer scale.
    • Run in NWjs and resize the window to various sizes and the text will look glitchy.

    Observed Result

    The spritefont does not render correctly.

    Expected Result

    All pixels to be correctly rendered.

    Affected Browsers

    • Chrome: NO
    • NWjs: YES

    Operating System and Service Pack

    Windows 7 Home Premium 64-bit

    Construct 2 Version ID

    r243

  • It's because I have a million things going on at once and need to order conditions very precisely or too much needless crap is being processed at once.

  • I actually have to be careful with my events in mine because they can drop the FPS to 20 if they are done wrong.

    EDIT: When done right, my game can run around 55-59 FPS during normal circumstances of an action-heavy area.

  • I was wondering if when I set things such as a variable value, is it less burden on the CPU if I use an expression to check another value or a condition?

  • I was having this issue at random just trying to export my game to NWJS. I'm using the Browser object, but it doesn't always complain about the minification. I wonder if this has anything to do with where sometimes, seemingly at random, when I export my game the package.nw file is way smaller than it should be and the NWJS exe won't open while the package.nw file is in its directory. Otherwise, it runs fine.

  • It runs just fine in preview mode, but when I export it to NWJS, the EXE just opens its processes in the background and no window ever shows up. Is there any well-known problem that could cause this?

    It has to be my package.nw file because when I remove that file from the NWJS folder, it opens. Also, my friend who is testing it is now running into the same problem when it worked fine 20 minutes ago until I changed a few things, but I don't see why they would make it hang.

  • Didn't work when the value was something like 5%. However, I took your idea and modified it where it does work, because I didn't think to use things like left.

    floor(percentile * 100) & "." & right(str(floor(percentile * 1000)), 1) & "%"

    Thanks for the nudge in the right direction.

  • How do I get a number to always show one place after the zero, even if it's going to be .0?

    I want a percentile text where it will show values like 10.3%, 18.8%, 50.0% etc. but I don't know how to get it to display this when the digit after the decimal point is 0.

  • It hasn't as far as I'm aware. Is there any way I can track down what causes them?

  • I have the latest version of NWJS that is available for download on this site.

  • I keep getting debug.log files put in my project's main folder. I was wondering what they meant, because they keep saying stuff like:

    [1001/013324:ERROR:process_info.cc(608)] range at 0xfffde000, size 0x230 fully unreadable

    [1001/013324:ERROR:process_info.cc(608)] range at 0xfffdd000, size 0xf84 fully unreadable

    [1001/013324:ERROR:process_info.cc(608)] range at 0xfffda000, size 0xf84 fully unreadable

    [1001/013324:ERROR:process_info.cc(608)] range at 0xfffd7000, size 0xf84 fully unreadable

    [1001/013324:ERROR:process_info.cc(608)] range at 0xfffaf000, size 0xf84 fully unreadable

    [1001/013324:ERROR:process_info.cc(608)] range at 0xfffac000, size 0xf84 fully unreadable

    [1001/013324:ERROR:process_info.cc(608)] range at 0xfffa9000, size 0xf84 fully unreadable

    [1001/013324:ERROR:process_info.cc(608)] range at 0xfffa6000, size 0xf84 fully unreadable

    [1001/013324:ERROR:process_info.cc(608)] range at 0xfffa3000, size 0xf84 fully unreadable

    [1001/013324:ERROR:process_info.cc(608)] range at 0xfffa0000, size 0xf84 fully unreadable

    [1001/013324:ERROR:process_info.cc(608)] range at 0xfff9d000, size 0xf84 fully unreadable

    [1001/013324:ERROR:process_info.cc(608)] range at 0xfff9a000, size 0xf84 fully unreadable

    [1001/013324:ERROR:process_info.cc(608)] range at 0xfff97000, size 0xf84 fully unreadable

    [1001/013324:ERROR:process_info.cc(608)] range at 0xfff94000, size 0xf84 fully unreadable

    [1001/013324:ERROR:process_info.cc(608)] range at 0xfff91000, size 0xf84 fully unreadable

    [1001/013324:ERROR:process_info.cc(608)] range at 0xfff8e000, size 0xf84 fully unreadable

    [1001/013324:ERROR:process_info.cc(608)] range at 0xfff8b000, size 0xf84 fully unreadable

    [1003/163302:ERROR:process_info.cc(608)] range at 0xfffde000, size 0x230 fully unreadable

    [1003/163302:ERROR:process_info.cc(608)] range at 0xfffdd000, size 0xf84 fully unreadable

    [1003/163302:ERROR:process_info.cc(608)] range at 0xfffda000, size 0xf84 fully unreadable

    [1003/163302:ERROR:process_info.cc(608)] range at 0xfffd7000, size 0xf84 fully unreadable

    [1003/163302:ERROR:process_info.cc(608)] range at 0xfffaf000, size 0xf84 fully unreadable

    [1003/163302:ERROR:process_info.cc(608)] range at 0xfffac000, size 0xf84 fully unreadable

    [1003/163302:ERROR:process_info.cc(608)] range at 0xfffa9000, size 0xf84 fully unreadable

    [1003/163302:ERROR:process_info.cc(608)] range at 0xfffa6000, size 0xf84 fully unreadable

    [1003/163302:ERROR:process_info.cc(608)] range at 0xfffa3000, size 0xf84 fully unreadable

    [1003/163302:ERROR:process_info.cc(608)] range at 0xfffa0000, size 0xf84 fully unreadable

    [1003/163302:ERROR:process_info.cc(608)] range at 0xfff9d000, size 0xf84 fully unreadable

    [1003/163302:ERROR:process_info.cc(608)] range at 0xfff9a000, size 0xf84 fully unreadable

    [1003/163302:ERROR:process_info.cc(608)] range at 0xfff97000, size 0xf84 fully unreadable

    [1003/163302:ERROR:process_info.cc(608)] range at 0xfff94000, size 0xf84 fully unreadable

    [1003/163302:ERROR:process_info.cc(608)] range at 0xfff91000, size 0xf84 fully unreadable

    [1003/163302:ERROR:process_info.cc(608)] range at 0xfff8e000, size 0xf84 fully unreadable

    [1003/163302:ERROR:process_info.cc(608)] range at 0xfff8b000, size 0xf84 fully unreadable

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • OK thanks. I knew there were some actions unaffected by conditions, so I wanted to make sure I wasn't just wasting processing time on conditions that do nothing. lol

  • I was wondering if Z sort is affected at all by conditions?

    Like if I put a condition that tests if object A is on the screen, will the Z sort action only affect object A's that are on screen and ignore the rest?

  • I put mine at 28 because the only objects that move super-fast that could screw up, use for loops to check collisions between points A and B, thus making this problem irrelevant.

  • Well yeah I read that, but I was wondering if the fastest object in my game moves 16px per frame in my game, if I should set that higher than 30 or lower than 30. The manual didn't really detail any calculations I can make to fine tune it.