Link opacity of all brushtypes to pressure etc.

[Kwadrope]

Right now only custombrushes can map opacity to pen specific input like pressure
I'd like this for all brushes

I know I could take any brush and make it into a custombrush but that is so counterproductive.
Also Step and lighting could do with more control like this




PS: + a reminder of my to most wanted features
->unlimited Canvas
->tabbed /FULLY customizable interface like blender, toonboom, photoshop...

[Fabrice]

Right now only custombrushes can map opacity to pen specific input like pressure
I'd like this for all brushes

I know I could take any brush and make it into a custombrush but that is so counterproductive.
Also Step and lighting could do with more control like this




PS: + a reminder of my to most wanted features
->unlimited Canvas
->tabbed /FULLY customizable interface like blender, toonboom, photoshop...

It's already in the TODO list, don't worry

[Kwadrope]

opacity ? or also UI and canvas?

if it's all,great
if it's some,still great ,but a bit less

Do all proposals get read? and who choses what gets implimented? is it a team effort? Does popularity count ;do posts with no answers get shunned for just being 1 persons' wish?
How many people ARE working on improving tvpaint anyway?


could we SEE the to do list?


just a bit curious
when I don't see any answers or only few I intend to think they will not get in TVP,ever.

[Paul Fierlinger]

when I don't see any answers or only few I intend to think they will not get in TVP,ever.

And then what? Will you break down and loose it, or will you become flexible and adapt to what is now? Show me any software which has such close and everyday access to its developers as this one. Which software has ever presented a list of features in development, in consideration, not in consideration and absolutely original which no one has ever thought of before and will blow the socks off of everyone once it comes out at noon on February 14th 2013?

[Kwadrope]

when I don't see any answers or only few I intend to think they will not get in TVP,ever.

And then what? Will you break down and loose it, or will you become flexible and adapt to what is now? Show me any software which has such close and everyday access to its developers as this one. Which software has ever presented a list of features in development, in consideration, not in consideration and absolutely original which no one has ever thought of before and will blow the socks off of everyone once it comes out at noon on February 14th 2013?

just asking

It's just that precisely because tvpaint is so open a developper ,which is refreshing, is why I ask this

They're free to answer or not,just as I am free to ask it ,or not.

Adaption is different then a thirst for evolution,making something even better then before. We/I can adapt,but we/I need not be content to remain working like this for the rest of our lives if it can get even better.

Also since it's rare that a developper has such an open community (except for open source programs,which are even more open,sometimes) i'd like to understand the rules or the ways the developpers work in, which the ideas are validated or not.

Perhaps a little introductory,locked,topic can present this information on top of the feature requests subforum

[Elodie]

i'd like to understand the rules or the ways the developpers work in, which the ideas are validated or not.

Well, as we wrote in the FAQ :

How do you decide how to improve the software ?

We look for recurring opinions about the software and take note of frequently asked features from our beta-testers and users. Many of our team members also come from graphical backgrounds, and this factors into many of our innovations. The best place to voice your suggestions is on the forum.

We have our own ideas and needs with the software and also listen our users' needs. For example, the peg-holes registration and the "line smoother" were requested on the forum. The storyboard tool was our idea and we improved it with our beta-testers needs.
Some ideas are very long to develop, so even if we say "it's in the TO DO list", don't think we mean "yeah, maybe we will add it...", we really mean this is in the TO DO list

Of course we don't show that TO DO list, because it's a secret list =)

[Kwadrope]

the FAQ is too obvious a place to hide such information
I demand more clarity!

but you're right
should've seen that XD

I know the secret handshake,can I see the list now?

I jest, thanks for the replies ,though ^^

[Fabrice]

It's a secret list only shared with our beta-tester team for obvious commercial reason.
Publishing a such list or giving it to someone who doesn't have a signed NDA could inform our concurrents about what is going to happen ...

Now, if you read carefully the forum, some posts clearly shows that if something is in the TO DO list, we are going to release it sooner or later. (the smoth of the lines, and images marks are good examples).

Stay confident, every post is read and noticed here

[Peter Wassink]

Perhaps a little introductory,locked,topic can present this information on top of the feature requests subforum

this seems like a good idea and fair request.

a clear formal explanation of what the purpose is of the feature request thread and what is done (or not done) with the posted requests.
You might even need(?) a statement claiming no rights can be derived when a request is actually implemented ....or something (one needs to cover one's ass these days....sigh )