brushfe's Forum Posts

  • Awesome, thanks for the insight! I thought I was going nuts. And the shared drive folder is a great idea, I'll definitely get that set up. Appreciate it!

  • This may be a stupid question: my project file is getting quite large, and I thought saving it as a folder would speed things up when saving to Dropbox.

    But when I try to save as a project folder, it only points to my hard drive. And if I copy a project folder into my C3 Dropbox folder, C3 doesn't see the c3proj file.

    Am I doing something wrong? Or are project files not supported in cloud saves?

    Thanks very much!

  • I tried these files in a new project and it worked. Opened in PS, copied, and then pasted into the C3 image editor.

    I've attached a project with these images as tilemaps with transparency, if it helps.

    drive.google.com/file/d/1j1cZrwx9KaA-Zk6U2FPj3govN-_sd7a5/view

  • Hey, it should stop rotating if you set "Set Angle" to "No" (in the 8-Direction behaviour properties).

  • I know my preview stops working when I close the browser tab/window after it opens but before the preview loads. I think there was a discussion about this recently. Is that the problem you're having?

  • dop2000

    Maybe I don't understand something, but if Ashley is going to pick 5 most upvoted ideas, why does it matter how many people voted on them? Limited or unlimited votes - in both cases some ideas will get more votes than others, so just pick 5 from the top!

    I totally see your point – though I suppose, if for no other reason, limited votes draw a line between what's interesting to me (as an individual) and what's important right now (as a user). With only a few votes, we're forced to prioritize the most urgently-useful suggestions. It stops us voters from saying "I like this one, this one, etc" and keeps us focused on which ideas we think Scirra should do next.

  • I think we need to be careful not to confuse what's best for ourselves with what's right for the suggestion platform.

    If the goal of voting is to figure out what the collective user base believe is most important, and only a handful of those features can be explored/developed at once, there's no point in having unlimited votes. 10-15 votes each will give Scirra a manageable list to consider. Hopefully a few of them work out. And hopefully we know why the rejected ones get rejected. Then we do it all again, and over time we've achieved the goal of allowing the collective user base to shape the program.

    We've all got our lists of personal priorities, but they're based on our individual skill levels, workflows, etc. If my priorities aren't something you all would want, then you won't vote on them, and tough cookies for me :( It's vital to include user input in software development, but ultimately it's just input. Scirra has the most objective position to judge what's possible and what's right for C3.

    Above all, I'm glad we're trying something more manageable. It's been fantastic to have this discussion, and I hope it makes all our suggestions more useful and applicable!

  • The new system Ashley proposed sounds great to me; definitely worth a try! Keeping the ideas manageable for Scirra to be review, explore, and implement is priority one - otherwise there's no point to any of it.

    The number of votes question is interesting. Having unlimited votes swings it all in favour of users who take the time to review every idea, or constantly check in on the ideas. But too few votes means we can't support everything we believe in, or have to spend time vote-managing, which likely drives people away. That might take some testing. Or maybe there's a voting window, say the last month, where everyone gets invited to vote for any number of ideas they like.

    Anyway, super interesting conversation and I'm excited to see this progress!

  • Perhaps one approach is 'seasons' or limited windows of time. For example, at the end of every six months or every year, the ideas with the most votes are reviewed, discussed, and decisions are made by Scirra on implementation. Then the slate gets wiped clean: votes are cleared, and a new list of ideas is generated over the next window of time.

    This allows for a few things in this discussion to be true: fixed, predictable investment and minimal community management for Scirra; managed expectations for users and voters; a reason to post new ideas and vote for others; suggestions kept modern (i.e. in line with new features like 3D); and it gives us all a recurring reason to stay engaged with the ideas platform.

    The time frame, categories, and requirements for a suggestion is of course determined by the Scirra team. Unlimited votes per user allow us to vote without vote management, and wiping them each 'season' prevents that from causing problems.

    Food for thought!

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • As a heavy C3 user who used to contribute to the Suggestions page, I've had the same experience and share the same view as dop2000.

    To add to newt's comments, a huge flaw with the limited vote system is that you're expecting people to keep their votes current with what they think is important. I'm not sure how many people are constantly going back to that site and aligning their votes with the ever-growing list of ideas.

    So at this point, I'd wager it's a mistake to judge the ideas by votes. The longer the site goes on without rewarding those votes, the less people bother with voting. Instead, or at least in the case of people I know, they're likely just adding ideas to the pile, not voting, and hoping your team notices them.

    Gathering input from users is obviously important, but this current system combined with a thorough lack of feedback could certainly be rethought.

    EDIT: Sorry Ashley, I missed your bottom paragraph. I'll certainly have a think and dig around for alternatives

  • Had some fun with the new 3D shapes, and made this procedurally generated voxel terrain.

    Subscribe to Construct videos now

    This is fantastic! Great use of the tool. And I love the detail you put into the colour variations.

  • There's something going on at event #13; when you change that TileMovement action from "Animate" to"Instant", the guards do move to the next waypoints (way too fast, of course).

    I don't have enough experience with this behaviour to figure out what's stopping the Animate mode from continuing.

  • Try using the Timer behaviour. When the ctrl key is down and the timer is not running, launch the volley and start the timer to whatever delay you'd like. Once it's done, using the ctrl key would launch the volley again.

  • You might not be picking the specific enemies that have LOS. You can use "for each enemy" and "enemy has LOS" conditions before your shooting actions to make sure only those ones fire.

  • Are on a laptop? I keep accidentally shrinking the type by holding Command/Ctrl and scrolling on the trackpad (2-finger on Mac). You could try that shortcut to scale things back up.