Digital Art Community Forum for Artists & Creators

Username: Kell9
Post Date: 2026-09-12 10:00:28

With the latest built [COLOR=rgb(239, 239, 239)]R 8.3.3[/COLOR] [COLOR=rgb(44, 130, 201)]macOS[/COLOR], an older issue has returned again: When opening, [COLOR=rgb(209, 213, 216)]Pen Direction[/COLOR] on all brushes is ignored and [COLOR=rgb(209, 213, 216)]Follow Trajectory[/COLOR] is used instead. This is really annoying. Interestingly, it seems that there is no general cure. What works one time will fail the next. Can anybody confirm this, or what are your suggestions? Currently, I can't find the thread regarding that topic.

Username: flowdee
Post Date: 2026-09-13 15:37:53

[USER=156988]@Kell9[/USER] what do you mean by Pen-Direction? I can't find that term anywhere in the UI - maybe you mean Pen-Rotation? [ATTACH type="full"]3516[/ATTACH] I'm mostly on a Mac, so I can try to reproduce this if you show me your relevant settings and give me a "painting recipe" for a brushstroke, so I can see what you mean - though my pen / stylus doesn't have rotation. But hey, that's what Motion IO can also be used for ;), although because of bugs in Rebelle Pro's WebSockets API I'm not sure whether Pen-Rotation & Pen-Tilt actually arrive correctly in the brush from the input side right now. Back when I implemented the features (before Rebelle 8.3.3) it worked - which also means you have a real creative playground with Motion IO for how you map out your pen handling. Meaning: something you'd normally just do intuitively with your hand can turn into a design object of its own - and thus become part of the painting's creative process. That's the huge potential of Motion IO : it's all modularized ... reduced to the max: Lego for Rebelle Pro. If you could also post 2 brushstrokes that clearly show the wrong & the expected behavior, either with a default Rebelle / factory Brush Preset or by uploading a test brush, I can give it a try.

Username: Kell9
Post Date: 2026-09-13 16:32:34

Sorry, you are right: It is [B][COLOR=rgb(209, 213, 216)]Pen Rotation ? [/COLOR][/B][COLOR=rgb(204, 204, 204)]Oh man, I feel like a dumb, ashes on my head ... Yes, I'm using the same settings and never change this![/COLOR] [ATTACH type="full"]3517[/ATTACH] [ATTACH type="full"]3518[/ATTACH] [ATTACH type="full"]3519[/ATTACH] Here is my goto brush: It is a BB Flat just a bit modified. [ATTACH type="full"]3520[/ATTACH] As written above: About 4 of 5 times I open Rebelle, the brushes with "Pen Rotation" react like "Follow Trajectory". Sometimes switching from "Paint & Mix" (2) to "Paint & Blend" (3) solves the problem for the entire session, but this is not always the case. Not only BBs are affected, but also the Texture Brushes. The snippet below shows the "trajectory" stroke behavior: [ATTACH type="full" width="259px"]3522[/ATTACH] Reading your explanations, it makes me curious whatelse Motion IO can do for us ... :)

Username: flowdee
Post Date: 2026-09-13 17:45:41

A quick test with your Bristle-Solid brush using my Motion IO companion app (using WebSockets & Rebelle Pro 8.3.3. on MacOS) and the settings I posted above looks fine - this is was 1/1. Stroke at the top uses pen pressure only, the stroke at the button uses pen pressure & pen rotation, but no pen tilt. Before I think about some other constellations which might trigger the error / issue you experience - if you just look at the painting, can you imagine that some graphic tablet drive or macOS update OR you pen tilt performance might be the issue? [ATTACH type="full" alt="Rotation Test.png"]3523[/ATTACH]

Username: Kell9
Post Date: 2026-09-13 18:34:00

Those are the settings of Tip Tilt: [ATTACH type="full"]3524[/ATTACH][ATTACH type="full"]3525[/ATTACH] Hm, last week I installed the latest Wacom Driver for my PTH 660 and this week Tahoe to 26.6.2. I remember, around the OS update the trouble started. Maybe this correlates, but I'm not sure. My DAW (Studio One 8) and dozen of plugins work like a charm with the new versions. For editing inside, I also use my Wacom.

Username: flowdee
Post Date: 2026-09-13 19:40:52

I used straight lines in my first test to intentionally circumvented the possible interference of the strokes trajectory, just to see if the rotation works. Lets bring the strokes trajectory and your "pen performance" into the test scenario. Using a curved line as the stroke is no problem in my app, but there endless ways to rotate and tilt the pen during that stroke. What about if you paint a simple sine-wave for example (sub bass goodness ;)) and just rotate the pen along the path (trying not to tilt the pen) - does this come out on the canvas as expected or not? If this works for you as a clear & reproducible test case, I can do the same via my Motion IO companion app - I am also on MacOS 26.6.2, but don't have Wacom drives installed on my Mac ... so we can narrow down the issue a bit further.

Username: Kell9
Post Date: 2026-09-13 19:45:54

I reinstalled the older Driver Version again, but it remains the same. :coffee:?

Username: flowdee
Post Date: 2026-09-13 20:30:54

Another idea : if its an issue somehow related to the Wacom driver output (theoretically in conjunction with a macOS anomaly) respectively on the input side of Rebelle, the "Tablet Event Log" may help Escape Motion to understand what happens (or does not arrive in Rebelle), but in the end the new Realtime Log should do it : [ATTACH type="full"]3526[/ATTACH]

Username: Kell9
Post Date: 2026-09-13 21:22:46

Thank you so much flowdee, I will do so! I simply forgot about those new possibilities. For now, after starting Rebelle, I press various times the number keys until my brush works as intended. Maybe EM has a clue what causes that behavior. I'll send the log tomorrow. ?️

Username: flowdee
Post Date: 2026-09-14 14:42:11

[QUOTE="Kell9, post: 34436, member: 156988"] I press various times the number keys until my brush works as intended [/QUOTE] That is interesting and maybe a hint for a mystery I experience sending [URL='https://www.escapemotions.com/products/rebelle/motionio_doc/reference/json_events_reference#set_brush']SET_BRUSH[/URL] and [URL='https://www.escapemotions.com/products/rebelle/motionio_doc/reference/json_events_reference#set_paint_type']SET_PAINT_TYPE[/URL] Motion IO JSON Events via WebSockets to Rebelle Pro. There is something strange regarding paint-types ([B]paint modes[/B] which you [B]toggle[/B] with your [B]number keys[/B] right ?), when I paint via a Rebelle Remote-Test feature I am currently developing in my Motion IO companion app, to make bug hunting easier for the WebSockets workflow. It looks like the paint modes get mixed up - but currently I am not 100% sure, maybe its related to the brush presets design and only the somehow extreme painting parameter in some tests (send via WS) makes it look like its the wrong paint mode / type. Or in other words : is it a bug of the SET_BRUSH and SET_PAINT_TYPE events or is it by brush preset design. Hence it would be great if you could post the essence of EMs findings about the reasons for this strangeness here - sometimes every breadcrumb matters ;). +++ The Rebelle Remote-Test feature in a nutshell : the WebSockets API of Rebelle Pro still has some issues that have a "show stopper" quality - or in other words : the WebSockets API needs some extra care & attention & love on Escape Motions side ;). But testing this from a Motion IO users perspective is more than arduous (and I guess for EM too ;-), so implemented a half automated test that can be executed from the menu of my app and uses the current artwork project, makes screenshots of Rebelle Pro automatically uses OCR to scan the value of the brush properties & color panel and writes a markdown file as the test result, if all propetiers send via SET_Xyz were at least set as expected. I still wait for the [URL='https://www.escapemotions.com/products/rebelle/motionio_doc/reference/json_events_reference#save']save[/URL] event working in Rebelle Pro via WS, to make at least an approximated pixel based comparison, if that was painted is that what was expected. So far I have to look at the markdown files, which also embeds the screenshots and hence that what was painted, and viewed in the right app (I use Obsidian by the way) I can verify the result, respectively the remaining, visually ... which works quite nice. ... as you were curious what else Motion IO can do for us ... a lot ? & ?

Username: Kell9
Post Date: 2026-09-14 15:41:29

Simply: WOW, that is absolutely killer! (y) ☄️

Username: Kell9
Post Date: 2026-09-14 16:23:59

[I][B]Update[/B][/I] My latest finding about this subject is: It always happens, when opening Rebelle with a previously created file from Finder. BUT: If I open Rebelle directly and create a new document, after "zooming out", the brushes behave correctly. The log files [I][COLOR=rgb(209, 213, 216)]app_realtime.log[/COLOR][/I] and [I][COLOR=rgb(209, 213, 216)]tablet_events.log[/COLOR] [/I]have been sent to EM's support. ?

Username: flowdee
Post Date: 2026-09-14 21:18:24

Hmm ... smells like an initialization issue. From an abstract processing perspective there might be similarities to "open Rebelle with a specific artwork" & "SET_BRUSH / SET_PAINT_TYPE" vs. "open Rebelle in a fresh state". You mentioned "zooming out" the canvas - is this just your workflow or needed to let the brush paint as expected? Does Rebelle in the bad & good case select the same brush preset as the active tool? I'm asking this, as switching the tool or brush in the same category is part of the "bug path" in the WebSocket Motion IO scenario. Or in other words : does the same brush preset paint as it should in one case (from the dock), but not in the other (from finder)? Thinking in the world of a DAW : feels like if a macro (remote control modulation) that controls several audio fx in the track chain toggles bypass via a dice on startup and once the macro knob is twisted a bit, the bypass toggles are in sync again ... and the sound is back in its "designed state" ... a bit of randomness can make a sound come alive, but dices that wipes through the sound preset or track chain like a hurricane aren't to my taste :ROFLMAO:.

Username: Kell9
Post Date: 2026-09-15 09:34:20

[USER=73073]@flowdee[/USER]: [QUOTE] but dices that wipes through the sound preset or track chain like a hurricane aren't to my taste :ROFLMAO: [/QUOTE] Mine either! lol ... the die is cast. ? [QUOTE] ... smells like an[B][COLOR=rgb(209, 213, 216)] initialization issue[/COLOR][/B] [/QUOTE] YES, I totally agree with that, as it never happens during a longer painting session without closing Rebelle! So, I did some further PSI (Paint Scene Investigation). ;) My observations so far: [LIST] [*]With a new document, in most cases everything is fine [*]Reopen a previous document guarantees a miss behavior [*]It needs some actions to re- initialize the brush presets [/LIST] It is worth mentioning, that my goto brushes are organized in the Favorites category and I can easily change them with hotkeys. Actions for correction can be almost everything: [LIST] [*]Switching between the paint modes of a brush with or without changing to another brush preset [*]Changing the brush category and choosing another one [*]Before [I]closing[/I] Rebelle, brush category can be any but not my goto Favorites [/LIST] The easiest and by far the best cure is: Shift+Cmd to zoom out by dragging and then Shift+dragging to reposition the artwork on the screen – simple and effective. (I realized, this has become muscle memory when opening a document. The epic, cinemascope like size presentation is nice (if there were no other elements to hide parts), but I never start with painting details. For me zooming out is a must. Most of the time, especially in the beginning, I shrink the artwork to the size of an iPhone to get the whole picture. This mimics stepping back from the easel in real painting.) For now, having been found this, the sun returned. ?

Username: Veronika Escape Motions
Post Date: 2026-09-16 14:44:32

Thanks for the log files! Our team has analyzed them and found that there are no tablet events present. It is as if you painted with a mouse. So not only did pen rotation not work, but pen pressure did not work in that session either. I tested on my macOS with the brush you posted, but could not replicate the problem. Could you please do another test, but this time, do the fix during the session by trying the various shortcuts as you mentioned in this forum thread. Thanks in advance!

Username: Kell9
Post Date: 2026-09-16 17:39:48

[I]Update:[/I] I found the reason and as it seems – a [B][COLOR=rgb(209, 213, 216)]bug! [/COLOR][/B] ? But before, I made a complete uninstall of Rebelle 8.3.3., deep down into the system and NOTHING was left over – everything! I only saved the PNGs of some brushes, I can't live without. Of course my Artwork Folder wasn't included. ;) But the scenario remains the same! Nightmare on Elm Street ... :eek:? The game changer: All those more or less random actions before were not reliable solving the problem each time the problem occurs. And then, I found it by accident: As a strong believer in workflow, all that can be assigned has a shortcut. [B][COLOR=rgb(255, 255, 255)]––>[/COLOR][/B] Instead of switching the brushes with the hotkeys (6, 7, ...), [COLOR=rgb(84, 172, 210)][B]I [/B][/COLOR][B][I][COLOR=rgb(209, 213, 216)]MUST[/COLOR][/I][/B] [COLOR=rgb(84, 172, 210)]click it with the Pen – that's all[/COLOR][B][COLOR=rgb(255, 255, 255)]![/COLOR][/B] It doesn't need any further treatment! After opening dozens of files, I can confirm this for sure. I also remember that Rebelle version 8. xx when the Hotkeys for the Favorite Brushes folder were broken. (I reported this to EM at that time) But, as it seems there is still an issue. I'm using the smaller Apple keyboard [I]without[/I] the number block, maybe this might be a reason, but this is just guessing into the blue. [ATTACH type="full" width="244px"]3537[/ATTACH] ... with two pen clicks more when starting Rebelle, I can live ... :) [USER=6]@Veronika Escape Motions[/USER] : Sorry, but because of this, I couldn't reply earlier!

Username: Kell9
Post Date: 2026-09-17 06:56:54

[USER=6]@Veronika Escape Motions[/USER] : I sent another "tablet_events.log".

Username: Kell9
Post Date: 2026-09-17 13:48:51

Meanwhile, I tested my pen in [B]CLP[/B], too. Also in this program, I painted with brushes that use Pen Rotation and not Follow Trajectory. Whatever I do, creating new documents or opening existing ones after closing the app, this happens like in Rebelle. From the very beginning, the brushes behave correctly. So it is not my trusty old Wacom PTH 660 (2017) which I bought about 5 years ago. It is an initializing issue of Rebelle, whatever causes this under the hood. :)

Username: Kell9
Post Date: 2026-09-21 12:53:24

[USER=6]@Veronika Escape Motions[/USER] : Yes, I've got your mail but we can speed up the things! :) ? There is one important observation: The "miss behavior" occurs only when opening Rebelle and the pen is [B][I]hovering[/I][/B] over the tablet close enough to show the movement. That was the missing link! So now, regardless if I open the app from the program folder or double clicking an existing file, is to await the "opening procedure" to be finished and then start painting by picking up a color or changing the brush mode or something like this. Yeah!!! ??? Again, big thanks to all who chimed in and EM for their support. (y)