So currently bg images have the following maximums
Maximum width: 2560px
Maximum height: 1440px
Maximum file size: 2.5MB
But storyboard images have this maximum
Storyboarded images must not exceed an area of 17,000,000 pixels to keep loading times of large images within reasonable ranges for most computers to handle.
This is a bit more than 4000x4000 for reference.
Which effectively means that if you have a map and want a zoomed in background in the storyboard, it either needs to follow background requirements - resulting in low quality when zoomed in, or you have to have... a copy of your background in higher resolution as a storyboard asset.
So either low quality or 2 copies of the same image. Both solutions are kind of dumb.
suggestion:
Backgrounds which are also used as storyboard images would follow the storyboard images rule for maximum dimensions instead.
or something as a bullet point in the requirements list.
this is kind of silly and I want to know if this makes sense since the current way it's done is a bit strange
Maximum width: 2560px
Maximum height: 1440px
Maximum file size: 2.5MB
But storyboard images have this maximum
Storyboarded images must not exceed an area of 17,000,000 pixels to keep loading times of large images within reasonable ranges for most computers to handle.
This is a bit more than 4000x4000 for reference.
Which effectively means that if you have a map and want a zoomed in background in the storyboard, it either needs to follow background requirements - resulting in low quality when zoomed in, or you have to have... a copy of your background in higher resolution as a storyboard asset.
So either low quality or 2 copies of the same image. Both solutions are kind of dumb.
suggestion:
Backgrounds which are also used as storyboard images would follow the storyboard images rule for maximum dimensions instead.
or something as a bullet point in the requirements list.
this is kind of silly and I want to know if this makes sense since the current way it's done is a bit strange