Page 1 of 1

crash bug in 11.0.10, Set KeyStroke FX Stack (undo / redo)

Posted: 01 Sep 2021, 23:59
by Svengali
I'm not sure if this bug has survived into 11.5 or not, but...

Upon entering the following keystroke command in an action list, I am immediately crashed out of TVPaint:

Set KeyStroke Undo> FX Stack> Redo

sven

Re: crash bug in 11.0.10, Set KeyStroke FX Stack (undo / redo)

Posted: 03 Sep 2021, 13:39
by Xavier
Svengali wrote: 01 Sep 2021, 23:59 Upon entering the following keystroke command in an action list, I am immediately crashed out of TVPaint:

Set KeyStroke Undo> FX Stack> Redo
Hi, just tried on Linux using the 11.5.2, couldn't reproduce it.
Then tried from Windows using the 11.0.10, couldn't reproduce it either.

Sorry Sven, did it happen only once ? or are you able to reproduce it ?

Re: crash bug in 11.0.10, Set KeyStroke FX Stack (undo / redo)

Posted: 03 Sep 2021, 14:50
by Thierry
I don't have this either.
Can you share your action list?

Re: crash bug in 11.0.10, Set KeyStroke FX Stack (undo / redo)

Posted: 03 Sep 2021, 16:55
by Svengali
I guess its me and not a bug.

Something is messed up with my action commands creation: Set KeyStroke works as expected for adding new commands lines to the action until I get near the bottom of the option list starting with:
TVPaint Animation and the extended commands, where I pick any option and the action command line is assigned "Plugins:" but no crash afterwards???

Starting with Set KeyStroke> Twain> Acquire, ENTER ... I immediately crash out of TVPaint with this message:
message.png
message.png (39.6 KiB) Viewed 4487 times
And that crash out + message happens for the rest of the Set KeyStroke extended command list.

I'm going to try to isolate the problem and fix it if I can, and if I do, I'll post what I found in this thread... sorry for the premature bug report.
sven

Re: crash bug in 11.0.10, Set KeyStroke FX Stack (undo / redo)

Posted: 07 Sep 2021, 13:05
by Svengali
Pure and simple, the problem would seem to be low available storage on my C: drive. I'm moving to a new Windows 10 system very soon, which should solve the problem and other strangeness as well. I'll update this report afterwards.

sven