Here is a suggestion that I just submitted in case anyone didn't know this or wants to also send a suggestion:
Summary
When you variant a linked graphics template, the variant that you use at publish determines which location will be used for the linked graphics, but it does not use the fallback path if no file is found in that location.
Steps to Reproduce
Make two variant values, one the parent of the other. Variant a linked graphic template. Create a file object based on the template. Create a directory for each variant and put the graphic for the file object in the directory for the parent variant. Publish with the child variant.
Expected Behavior
I would expect that the publish would use the fallback path and use the graphic that is in the directory for the parent variant value, just like topics use the fallback path.
Actual Behavior
The output has a graphic that says "File not found" because there is not graphic for the file object in the directory for the child variant.
Does this affect a deadline that Support should know about?
No, but this significantly hinders the use of variants for managing releases. I have to have all of the graphics in the directory for each variant value, even if the graphics are all the same. I would rather be able to only keep the updated graphics files in the directory for the child variant so I don't have multiple copies of the same graphic.