Welcome to TVPaint Community forums !

Is this normal? That my set exposure value on the right click menu is disabled? When I am on the last instance, it grays out. But not always. Sometimes, for some strange reason, it starts to work. Is there any explanation for that? Why would it even be disabled, on the animation layer?
Thanks

Check if maybe the out marker is at the same frame.

The Set Exposure has been broken/changed at some point. (I would like to see it fixed to go back to the way it worked previously.)

Previously, on a single frame (instance) you could simply right-click on it and select Set Exposure to enter the number of frames you want to expose that instance on the timeline.

What has been changed is that now you can not Set Exposure on a single instance (exposed for only one frame) , the instance must be exposed for at least two frames on the timeline , then the Set Exposure function in the menu will be enabled. Why ? I have no idea. It worked fine the way it was before and I see no good reason to change it.


My workaround has been to assign a shortcut key for Set Exposure , so when I want to Set Exposure on a single instance I hit my shortcut key to bring up the Set Exposure box. But now that's adding yet another shortcut key to the long list I have to remember. I would rather have the original functionality of the Set Exposure restored to the right-click menu.


.

I also think it is broken and it has nothing to do with the out marker. So I am not the only one. Maybe it is a bug. In my case, only happens, so far, on the last instance in the layer.

Try this: start a new project and you have just a single frame/instance. Now right click on it and try to set exposure. You’ll notice it’s grayed out and you can’t set exposure. Now manually drag the handle to extend that instance by one frame and then click on the second frame of the instance and now you’ll see set exposure is active again. In previous versions of TVPaint you could just click on the single instance and set exposure was active. It’s not technically a bug because that change was made intentionally, but to me it is something that used to work better and now feels "broken".