You could always extract the c3p file to a folder. It's just a zip file.

I know that, but to have to go and manually unzip the .c3p file everytime you want to change something? Then rezip it (if that even works) to carry on working. Not the best workflow.

So basically, if a group were working on a project together using source control, would it be best for people to just use the same .c3p file and make sure their comments are good? Or should they unzip and rezip before/after they stage and push?

I can't possibly be the only one who's interested in this issue, can I?

I've tried searching the forums and can't find anything about this, which I must admit I find strange.

Maybe I need to page Ashley?

Hi there,

In C2, you could save out as a folder/file structure, which made things much easier for source control solutions like github.

Would there be any problem with using the single file format of C3 with github?

When will we be able to save out as a folder structure to help track changes etc.?

> Okay, thanks for the reply.

>

> How would I get a similar effect by hand coding it?

>

Here are all the current rex plugins for C3. MoveTo is available there

https://github.com/rexrainbow/C3RexDoc/ ... o/index.md

Mate that is amazeballs! I couldn't find a list like this, although I was sure there MUST be one! Thanks so much.

Okay, thanks for the reply.

How would I get a similar effect by hand coding it?

Hi there,

Interested in looking at an example capx/tutorial that uses rexrainbow 's moveTo plugin.

Can't open it in C3 because this plugin is a C2 plugin.

Searched around and found a C2toC3converter, but it only works on windows.

Is there an online utility available for this? I'm using a Mac.

Seems a shame to lose all that functionality in C3 that's been contributed over the years....

Thanks for the reply.

I also worked out an alternative....

Set Visible/Invisible doesn't really work because then your particles don't really behave properly and fade away nicely.

*However*, you can set the particle rate to 0 for when you're not holding the action button, and then set it to <a rate of your choice> when the action button *is* down.

e.g. If space is down, set particle rate to 'particleRate'

Else, set particle rate to 0.

Thanks, and hope this helps someone.

Hi there,

Using just a small particle emitter in a project. Notice that it can't be made inactive (it's engine flames, so only want to see it whilst a player presses a key).

I know that if there's more than a couple of hundred particles onscreen it might affect framerate (so the manual says).

So, is it better to make it invisible when unwanted, or to position it off-screen when unwanted? If those particles aren't visible, do they still affect framerate? I wasn't sure whether it was amount of objects in memory or time taken to render which is the bigger issue here.

Alternatively, is it better to destroy and recreate it each time? I doubt it, but thought I'd ask.

It doesn't affect this project very much really, but I'd like to know best practice for future. Thanks!

Hi there,

I'm not that user on github, so can't comment on that error I'm afraid!

Ashley - cloud is preferable because I have a number of computers that I use inbetween work and home settings - hence I love the browser move from C2, but am puzzled by VERY slow saving in Google Drive. Local is great whilst you're in the flow of doing something, but not to transfer of course. Yes save a local copy to USB etc., but thought I'd ask about cloud.

I *would* try to save to my Dropbox instead (in case it's a Google side problem), but I can't find the option to make it default to Dropbox instead of Google Drive. I'm stuck on the LOOONG sign in GDrive screen.

By 'haphazard', I mean I can't save into a neat file structure - it's all kind of hanging loose there. I like folders!

Did anyone find out how to solve this problem?

Is this plugin being worked on by anyone else? Would be really good to see the main team from Scirra give this some love. Ink is becoming a significant force in IF and it would massively increase the capabilities of C3 and its marketability.

Hi there,

Using C3 on latest MacOSX in Chrome, mainly.

I'm finding that saving to cloud takes an extremely long time - it takes forever to get a 'list of files' as the dialog states.

Saving to browser works quickly but retrieval is a bit haphazard.

Save to hard disk is clunky, slow and prone to easy duplication.

When will we just be able to save a file on the hard drive and work from it like in a normal desktop application?

On that note, when is the desktop version going to be available (which will no doubt make file saving easier).

Thanks.

(Incidentally, am a big fan and am using it for a BA Games Design course I run, so genuinely interested and not just complaining!).

No.