Ashley's Forum Posts

  • Closing, please provide a .capx or we cannot do anything about your report. This type of issue usually turns out to be a mistake in your events, which is why we require a .capx reproducing the issue.

  • Closing as this is currently by design and all working correctly. We don't support rendering wrapped layouts yet, although the feature request is on the todo list.

  • Closing, please only report bugs in the latest version (currently r139) and ensure you have uploaded your game properly. Your link is now a 404 not found.

  • Can't reproduce on Windows 8. I'm left with anim1 selected and the image editor showing anim1 frame 0 as well.

  • This is currently by design; the target types apply to the behavior type. Since you have a family behavior it means all the objects in the family share the same target list. I can see how this isn't ideal, though - maybe we can change it for a future release.

  • Fixed for next build.

  • I received your .capx by email, but it uses third party plugins. Please read the guidelines; unfortunately we cannot accept .capx files using third party plugins in bug reports. I could not reproduce a problem in a new project using Chrome. Try to reproduce the problem in a new project then post the link here.

  • mercy - you can change the event sheet font size in Preferences, or by holding control and scrolling the mouse wheel in the event sheet view.

  • Closing as resolved. However it sounds like there was a bug in C2 that caused a sprite image to go missing. We'd like to fix that if possible, so if you can reproduce that and report a bug for it we can investigate further to try ensure it doesn't happen again.

  • Just made an edit to the OP. We might actually make a release this week, we'll see how it goes.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Hi all,

    Just a quick update. Due to taking time off for summer holidays, the next beta is currently already about a week late compared to our usual weekly cycle. It is likely to also be another 1-2 weeks before we release it due to some more time off and the fact we're working on something pretty significant for the next beta!

    I would estimate we will release the next beta around 14th-16th August, but don't hold me to that. Even so it would make it about a month since the last update, which is an unusually long time between updates, so I just wanted to say we're not dead - just taking some holiday and working on some cool stuff. I'm sure it will be worth the wait :)

    Edit: we might actually do a release this week - we'll see how things go.

    Ashley

  • I think there is already an open bug thread with an issue that sounds the same.

    FWIW you can post bug reports without a .capx file if it's an editor issue (we are reasonable), it's just if your report could in any way at all be improved by adding a .capx file, you should. We get a lot of bug reports which we can't deal with because they are missing a .capx file and the description is not sufficient for us to do anything about the report, which is why we state it's required.

  • Yes, collision checking is single threaded. Collisions are checked in the actual 'On collision' or 'Is overlapping' events themselves, and since the results are needed immediately, there's not much to gain by offloading to another core - the rest of the events could not continue until the results were known.

  • The rendering will utilise all available GPU cores. Most logic processing happens on a single CPU core, except for pathfinding as Arima notes, but depending on the browser engine it may be able to use additional CPU cores for other purposes. For example IIRC Chrome forwards all WebGL calls to another thread, so they can happen on another core. Other processes like audio and image decoding are likely to use other cores. However the details will probably vary depending on the particular engine you're using (including whether CocoonJS or browser-based). If you wanted to know more about CocoonJS specifically, it would be best to ask Ludei.

  • It is probably running out of memory. The iPad 1 has extremely limited memory IIRC. The image format/download size has no effect on memory use since all images are decompressed in memory (see remember not to waste your memory), so using PNG-8 will make no difference there. What does C2's estimated memory use in the status bar say?