Ashley's Forum Posts

  • pixelSize is the size of a pixel on the source surface. AFAICT it is working correctly. I guess you actually want the size of a pixel on the destination surface? There isn't a uniform specified for that yet.

  • It shouldn't take long to make a quick test project and verify this yourself.

    FWIW deactivating a group deactivates all sub-groups within it too. You cannot have an active group inside a deactivated group, it will still count as deactivated because deactivated groups deactivate everything inside them.

  • This is really difficult and also will be really slow since readback from the GPU is slow and complicated, and base64 strings are inefficient. What are you trying to achieve? It would probably be better to find a different way to do it.

  • There is an SVG Picture object in the latest beta release. You can just drag-and-drop an SVG file in to a layout to create it.

  • It's just a warning, you should still be able to skip it. If you can't publish, it is probably for a different reason.

  • It's not clear what you are actually doing. Are you using the new SVG Picture object in beta releases? Or rasterizing it in the Animations editor? Or something else?

  • FYI, this is fixed in the C3 runtime.

  • int and random are not built-in global functions in JavaScript. It looks like you're confusing Construct expressions with JS. In JS the correct code is Math.floor(Math.random() * 100) (for a random integer in the range 0-99 inclusive). See documentation on the Math object.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
    • Post link icon

    terence - I'm afraid not: once again, without providing a project and reliable steps to follow to demonstrate the issue, it is unlikely any progress will be made on this. Also the debug log you provided appears to be for the NW.js runtime, which has nothing to do with the C2 editor.

  • I can't think of any technical reason it would work differently. The desktop download uses the same browser engine as Chrome.

  • You can save a project as a folder (or with .c3p files, rename them to .zip and extract it). Then all the images are separate files, so you could use an external tool that can batch-resize image files. Zip the files and rename it back to .c3p and it's a C3 project again.

  • Use Project Files. Text files aren't really a good format - an array, dictionary or JSON would probably be more suitable.

  • Most systems have 2-4 GB of memory. A difference of 50-100mb isn't much really. It could come from browser extensions in Chrome which you could remove or disable if you really want to save 3-5% of system memory.

    • Post link icon

    I'm not sure you understood about updates: it's the NW.js version that does not automatically update, in neither the C3 desktop download, nor the NW.js previewer I just provided. With C3 desktop, to update the NW.js version we have to release an update, and then everyone has to go and download it again. With the NW.js previewer, there's not the step of waiting for us to release an update, so it's better: you can download updates directly from nwjs.io as soon as they're available, including nightly and minor updates. So it is an improvement over how the C3 desktop downloads worked. The C3 desktop download could update the C3 version automatically, because it's just new content on the server that gets downloaded, which I think is the source of the confusion.

    There's already options to keep a Remote Preview going. You can leave the dialog open - including in its own popup window so you can move it elsewhere on your display - and then a normal preview (including pressing F5) updates Remote Preview.

  • You do not have permission to view this post