(New!) Wick Editor Version 1.17.1 - New Clip Options, Editor Options, Onion Skinning, and More!

Actually, maybe the 4th one was already fixed. I did find something else that could be intentional or a bug, but if a multiframe clip has an empty first frame, the clip appears as a small plus sign. when run, there is no plus sign, and when stopped, the plus comes back. I think itā€™s supposed to be a fix so that you donā€™t have an invisible clip, which makes sense because the hitbox in the editor is the hitbox of the first frame.

2 Likes

@awc95014 yes this is intentional! (The plus sign).

1 Like

Iā€™ll be checking this out later today. Thanks for all your HARD WORK.

I guess the pen tool will get updated later (where you can use the handlesā€¦bezier)

If you change the position of text with code, it doesnā€™t revert back to what it was before it was run. dunno if thatā€™s the case with objects.

i had a semi-cursed project that i fixed, but hereā€™s what happened.
I wanted to make a scoring mechanism for Le Tingy 2, so i made a text box in the scoring frame called ā€œtvā€ and ā€œtpā€ (time value and time points) as well as death and life values and points. i have a long frame with an off-screen rectangle doing all the code starting on the second frame, and it changes the text when it leaves that frame and enters the scoring frame. if you play the game completely it would be fine, but if you exited it would take you to the first frame with the rectangle selected (itā€™s not even on the first frame) and if i go check it, it says that tv is not defined. many things are wrong with that.

  1. it doesnā€™t kick me out of the project to tell me
  2. it takes me to the first frame to explain the problem
  3. the program fully functions
  4. tv is defined

Iā€™m not sure what the problem is. I got rid of the ā€œcursednessā€ by getting rid of the score frame and the added code. Can anyone help me?

I really appreciate these updates! Especially the Clip options, the resolution option and the bug fixes. :smile:
Iā€™m using the test version 1.17 now for the jam, but Iā€™ve run into a lot of bugs. Iā€™ll upload details on all those soon after I get all my thoughts straight. (I currently have a sorta-messy document where I write down all these issues as I find them)

Colors are slightly off using test branch video Export. This is Mayruā€™s anim, where the one on the left is the exported version. Itā€™s more yellow and saturated overall. Itā€™s a big issue in serious projects when colors have to be carefully balanced.

Also exported that file as a gif and it caused the tongue color to flicker, I guess the algorithm couldnā€™t decide which shade to use:
tongue

Thatā€™s unfortunate, although your animation looks awesome anyway :star_struck:

Oh my god! Is there shape tweens?

That anim belongs to Mayru, and there arenā€™t shape tweens in this version.

Hey @HOTS Thanks for pointing out the contrast issue. Iā€™ll take a look and see if there are some color settings we can change.

Who has hidden my post?

1 bug and 3 suggestions for the ā€œcut frameā€ feature (shortcut shift + c).

Bug: when the playhead is over a frame which isnā€™t selected (see image), shift + c does nothing:
Wick Addframe bug
It should create a keyframe at the playhead.
The ā€œinsert blank keyframeā€ button and shortcut act correctly (they make a blank keyframe at the playhead).

Suggestion 1: Change the name of ā€œCut Frameā€ in the shortcut menu to ā€œInsert Keyframeā€ or ā€œInsert Frameā€, since the word Cut is deceptive (itā€™s associated with ctrl + x)

Suggestion 2: rename the current ā€œAdd Frameā€ button to ā€œBlank Frame (shift+8)ā€ since the button doesnā€™t really add a frame, but rather converts to blank keyframe.
add frame
Suggestion 3: Create a ā€œKeyframe (shift+c)ā€ button beside the ā€œBlank Frameā€ button so users can convert to non-blank keyframes without the shift+c shortcut.

3 Likes

this is epic i like it.

I see that youā€™ve edited the post today and I like all the new features
:exploding_head:
More bugā€™s are fixed! :bug:
Everythingā€™s turning out great! :+1:
Good job and thanks Wick editor! :clap:
:partying_face:

EDIT: EXPORT ISSUE FIXED, however a small bug remains; pressing the x-button still doesnā€™t cancel an export.

Click to see original bug

I canā€™t video export anything.

Iā€™m in chrome, test branch, tried exporting a 1-3 frame anim with just circles at all resolutions and it doesnā€™t progress. At least one other guy has the issue; he sat for an hour with no progress.
Also the x-button on the progress bar box should be made to cancel the export.

Hey @HOTS, could you please send me a screenshot of your developer console? There are some instructions here (My video wont finish rendering!) It will hopefully show an error I can use to fix the problem.

Sorry about the issue!

OMG YESSS THANK U omg i can finally export in .svg yesyesyesyes thank u so much if i start making money itā€™s going straight to your patreon

Hi,

small bug/feature request: if you hide the div that an animation is playing on, you get very ugly errors:

VM926:12607 Uncaught TypeError: Cannot read property ā€˜_transformBoundsā€™ of null
at CanvasView.getBounds (:12607:42)
at CanvasView.getCenter (:12662:15)
at CanvasView.setCenter (:12667:23)
at Wick.View.Project._renderSVGCanvas (:58819:28)
at Wick.View.Project.render (:58657:10)
at Wick.Project.tick (:49217:15)
at eval (:49276:24)

Is there any way to tell the wick-player to stop/destroy itselves?
Or, maybe, a way to surpress the errors :slight_smile:

regards,

Paul