brushfe's Forum Posts

  • You do not have permission to view this post

  • You do not have permission to view this post

  • Hey, thanks everyone. And thanks for the example mekonbekon — personally I think that should replace the one included in C3, the instructions and example were super clear!

    I see why the maps were created, but it still just seems to complicate the code (and the event sheet) more than it used to. Wouldn't this all be a lot simpler if you could just call a function by name/string?

    For an approachable dev platform like C3, it feels like something as fundamental as functions shouldn't be getting more complicated over time. Not that function maps shouldn't exist, as there's some super cool uses of them here like dialogue, but in addition to the basics like calling by string.

  • As a C2 user I've been trying to learn more about C3's new features. Maybe someone could help me see the value in Function Maps?

    I checked out the Function Map tutorial included in C3, but that only made things more puzzling. It seemed like it took 3x more work to do something you can make with one function and some if statements.

    For example: here's a picture of the C3 Function Map tutorial done without function maps. It's much less work and much simpler — but I'm sure I'm missing something valuable about these maps.

  • Just on the topic of redundancy -- in my experience designing UI/UX, it's not always a good thing to remove it. There's a difference between where something should logically be found, and giving people access to the most frequently used tools.

    The removal of the ribbon, in my view, is a big mistake. While a lot of things are tucked away logically, it takes more time/clicks to do certain tasks (the grid is a great example). I've seen this most often when engineering is the focus of the UI, versus productivity. Simplicity is good, but reduction is bad.

    I think we'll see more of this conversation at C3 gets more popular. Logic in UI is good for learning, but redundancy is good for productivity. I know the UI/UX is the reason I'm still in C2, despite the features.

    Voice of one, but I'd heavily suggest including a ribbon that's either based on the most used tools (C2 is a great start) or even customizable.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • You do not have permission to view this post

  • You do not have permission to view this post

  • You do not have permission to view this post

  • You do not have permission to view this post

    Thanks for the update and investigation Ashley! It's been a lot smoother going in/out of animation editor, but I've just had the same crash I've always encountered: after 4+ hours of work, last 30 mins were editing lots of sprites and collision boxes, and lots of previews to check the work, then it crashed pressing F4 to preview.

    Following WrathOfAbe, if the machine specs are important, I have an Intel i7-2670 2.20ghz with 12GB of memory. This is a heavy project in terms of events and layouts, with an average of 15 sprites/layout.

    I have created a project example that repeatedly demonstrates this crash.

    Here's what it looks like. If you've lost work to this then you might want to look away... ;)

    Click to play if it doesn't do so automatically:

    Here's the project caproj:

    Crash test .caproj project

    Steps to reproduce:

    1) Open the project. Be patient, it can take a minute...

    2) Edit any sprite using the "Animations: Edit" in the properties bar (note, the open layout has no sprites in it, so memory use for this project is at a minimum).

    3) Close the sprite editor. If you're prepared to wait a minute then it might recover, but if you click on anything / try to close it again / click anywhere else then it'll drag up the windows crash popup.

    Things to note. C2 is using approx 152 Mb of memory with this layout open in the editor. After the crash and selection of "wait for the program to respond" then the reported memory use goes down to 20 Mb. Although C2 appears to have recovered, clearly it is not working properly...

    What's with the cycling through 150 sprites or so after initially closing the sprite editor...?

    Anyway, Ashley, I hope that this is what you need and it'll repeatably crash on your super-computer.

    I also get the same crash following the instructions above. I'll take a look at the larger / sprite-heavy projects I have to see if anything similar happens when it crashes. Thanks for assembling that example Colludium!

    Just want to second the above experience — pressing alt-tab while a large project is saving, or just after, usually crashes here.

    Saving doesn't always show a progress bar for me, so I can't tell when the saving is complete, but if I just wait a few seconds after saving before running the preview or switching applications, it's all good.

    (using latest Construct beta 274, applies to last few versions as well)

  • Are you both working on large project?

    Another way to look at the problem is the undo list. Im working on a rather large project (lots of images, events, layers, etc), and the strangest version of this happened yesterday.

    After a couple of hours working without a crash, I held the alt key for a few seconds, and then it crashed. Just in the editor, looking at an event sheet. It may have been saving at the time, but that was it.

    I wasn't alt-tabbing or anything (I was going to but got lost in thought, hence the holding down the alt key).

    I'm certainly not qualified to figure this out, but maybe it's a memory problem that's triggered after a certain point, which is reached faster by projects with more assets?

  • You do not have permission to view this post

  • Solid game! I've really enjoyed playing it so far. I hope you can build on the world you've created - some more adventures in this fox land would be great (and if so, I'd only suggest finding a new goal besides "Save the girl").

    Great work!