Open illwieckz opened 10 months ago
It's totally OK to implement a feature with another codec that RoQ can't do.
The purpose of having videoMap RoQ support is to only have what Quake 3/Tremulous had, no less no more. We can see videoMap RoQ support as a kind of “GIF” to be applied on surfaces.
We don't need to extend RoQ support to other things even if one day we allow the engine to do more video things with other video codecs. If one day we have another video format that allows us to do things RoQ can't do, we would not be obligated to port the feature back to RoQ, and we would not be obligated to not implement the feature with the new codec because RoQ cant.
According to the Multimedia Wiki the RoQ format supports keyframes in RoQ_JPEG
chunk, but if Quake 3/Tremulous never implemented that we are not expected to implement it.
If one day we implement a keyframed video codec, we would be able to add a specific material keyword to control if the playback behavior would be the legacy one or be absolute in time, and we would document that the absolute time playback is only available with the supported codecs and not RoQ.
@slipher wrote in #954: