-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace game scaling in gfx renderers with resolution & destination per scene node #980
Comments
The ability to specify a resolution for each camera would be helpful and make it possible to resize the viewport to different screens. We could remove the max round multiplier from setting and leave it to the game developer. |
Currently cameras are not allowed to be larger than room, because it's not defined what lies behind the room in current game logic.
|
Unfortunately I do not clearly understand following two paragraphs. Could you elaborate on each point?
|
I meant that once a camera viewport can individually set its own resolution and zoom then there's little stopping them from making the game fully adjustable at runtime, so it would be possible to set the proper ratio for 6:9, 6:10, 4:3 and resize the GUIs to the screen. As long as the game developer feels like it, In that case though, think of a resizable window, a target minimum resolution will prevent results that deviate from the game developer's expectations which may make the game unplayable. |
Oh right, adjusting viewport's/game's aspect ratio was another request that fits here. |
Currently IGraphicsDriver interface has a strict game scaling setup where you have to set "native game size" and "render frame size" to achieve game scaling. After this renderer expects everything drawn in the native game resolution and scales up or down to match the render frame.
This is simple, but may be too restrictive for future needs.
See: IGraphicsDriver declaration:
The proposal is to completely get rid of strict "native size"/"render frame" setup in the renderer interface, and instead allow to define Native Resolution and Target Destination (sample names) per each scene node/spritebatch.
Examples of why this will be useful:
Some thought should be put into deciding how it would be better to organize this data and its assignment so that game drawing functions would not be overloaded with unnecessary concepts, like image destination on final surface, etc.
Also must take the "Render sprites in screen resolution" option into consideration.
See Also: #967 , #969
The text was updated successfully, but these errors were encountered: