🙈 Copy Past Visual Effect & Temporary Disable It

Helooooo everyone! :yum:

I’m using a lot of visual effects for my layers and I wish there could be copy/past one effect into another. There is a 3 dots next to effect and I wish there would be an option to “copy/past” it and likewise past one into existing one or with button.

AND on top of it to temporary disable it for preview, so often I just want to disable one particular effect that I have been tweaking for some time and deleting it is not really a lovely thought to just preview other effect or scene without it! :astonished:

I’m new to the engine so I might have missed or overlooked this! :eyes:

can you provide a mockup. I cant understand you.

You must test it with it. It will test every other action on how it behaves with effects.

@Jessica I don’t know that there’s a gui integrated feature to do what you ask, but you can do it with events - make events that modify a layer effect and copy/paste those, or use events to disable certain effects on a layer.

Thank you :two_hearts:

Yes, events are nice, but it’s for manipulating things while game running, I’d like to have it as a toggle on/off while in the editor :blush:

Hello, thank you for taking your time :relaxed:

Here is what I’m talking about.

456

Wish there would be a feature to disable particular effect (right now you only can delete it) or copy/past into another layer so that I do not need to type all the tweaks for the effect all over again and if it has many values to tweak, well I have to go back to look in previous effect to see if I have missed anything or not - time consuming. :no_good_woman: Not good.

I prefer not add this button for duplicate effects, because effects are expensives in term of resources on low devices and should be used carefully.
Overwise with lot of effects the game will freeze or lagging.

Hello :hugs:

Would be neat to have this very important explanation say next to EFFECTS name, when you open effect’s window, like you see on some other windows that give you tutorial or link to learn more.

However, does not really explains why I should suffer while developing the game or testing things out and should retype every number all the time.

I had yesterday a situation where I had to try best effect on a different layers and I had to manually do it for each layer, retyping every number, wasted a lot of time, made a few saves to just see different affects for different art styles.

If there is a concern that less advanced people will abuse it or over use it, like I said there should be a warning explicitly stating importance not to over use and may be after giving each layer more then say 3 effects there should be a pop up window that will remind about over use of effects and so on.

And Im not sure if I was clear enough, I am not talking about duplicating same effect on the same layer - one type of effect per layer does the job, what doesn’t is when you want to move this effect to another layer and you have to manually retype it on that new layer, while deleting old. Hope that clarifies.

In any way, thank you for your time & explanation :+1::two_hearts:

I agree that it could be a useful feature to copy/paste layers; for me it’s a matter of importance. As the same result can be achieved relatively easily using events, I wouldn’t place it as a high priority. It’s just my opinion, but I would prefer the developers work on adding new features and fixing bugs: the last update brought light layers and peer to peer, and I like these much better than the ability to copy and paste layers (again, just 1 persons opinion, we all have one).

I’ve done some of this testing myself lately, and I too quickly grew tired of putting in all those values on different layers with different effects every time. I understand your suffering; what I don’t understand is your resistance to using events as a workaround to achieve the same effect with more efficiency.

My recommendation if you’re testing/experimenting is to make an effect on whatever layers you want to test. Don’t worry about typing in the values - just keep track of what each effect is named. leave the other parameters at default. Then, use events to change the parameter values. The target layer can be changed very easily in the event editor, and events can already be copied/pasted. If you get used to using events to test your layer effects in this manner, I’m confident after a bit of practice you’ll learn as I did it’s actually much more efficient, as you can modify several layers/effects in a few moments without opening up a new editor box. Once the effect is set up in your events, you can enable/disable it literally with 2 clicks. When you’re satisfied with the results of your testing, input the final values into the effects editor and clean up your events sheet.

While we may disagree about the importance of this request, I do appreciate your desire to improve the engine we all use, and the time/effort you put into the request.

Cheers :slight_smile:

O I wouldn’t put it as a high priority and It’s rather simple to implement anyway compare to other things ( might be wrong tho who knows how they implemented it at first place lol) :slightly_smiling_face:

Its just this engine for ease access and easy start - that’s the selling feature so to speak. Imagine me using this engine in class teaching kids or young people and they all sitting there retyping values lol. Its one thing when you are familiar with what is what and another when you are beginning and you need to do a lot of testing - its just a simple thing to help you learn faster.

As you said " it’s a work around". Nothing wrong with work around when something is not created or broken. :relaxed: I just would like to have magical button, click and copy, click and past and tweak only what you need if anything at all :partying_face: Filling up Events tab with additional conditions that can be placed on layer may be better? :woman_shrugging:

I mean in general if we just thinking about it, if we ONLY meant to put/attach effect to specific layer and then go to events tab and modify it there, then WHY on earth even allow them to be modified right on the layer tab? You see what I’m talking about? You generally as a beginner expecting certain coherency as you go through IDE. Of course I can learn copy past in Events tab and copy past/modify on the fly - that’s ALL understandable :hugs:

Just my personal experience: I came as a newcomer to this IDE, I see layer, I see effects, Im adding effects and then it allows me to modify it and you look for simple copy/past - so one would naturally assume THIS IS where you do the modification OFFICIALLY - you see what Im saying? But turns out oh I better do it in events tab, so lets just forget about this feature that serves what purpose exactly now? :thinking: It simply IDE experience and efficiency.

Aye thank you for your input and suggestions.:+1: I just shared my personal experience and thoughts on it. Im IDE programmer and designer so I cannot stand when simple things are not done properly or ambiguity/duplicity in interface exist that serves no purpose haha :joy:

Also GDevelop is open source. I don’t have the technical skills necessary to implement anything like a change to the IDE - not without a lot of learning beforehand. However, if you, as a professional programmer and IDE designer think it would be easy to implement and have the necessary skill to do so, by all means, implement away. That’s what open source is all about… anyone can modify it as they see fit, and the entire community stands to benefit from your work. Just a little food for thought :slight_smile:

Your arguments convinced me and i just remembered that a message appears when there are more than 5 effects.

So I’m ok with the buttons now. If you open a pull request on github to do it or ask for help to make it, 4ian and I could guide you :wink:

The effect file to edit for add functions for copy paste duplicate:
newIDE\app\src\EffectsList\index.js

An example of file where the functions exist already:
newIDE\app\src\ProjectManager\index.js

Happy day everyone! :tulip:

Oh I did not know it was open source :open_mouth: How did I miss that? :face_with_monocle:

I will take a look definitely at it. Hope my JS level will be able to handle this. Thank you everyone for your help, thoughts and other useful information!:ghost:

Was fun :slightly_smiling_face:

1 Like