Peacekeepr
Member
- Jan 25, 2023
- 122
- 275
- 81
You probably need to useat the moment if you drop a 4k image in it displays it in 4k through a 1080p window, so basically you only see the top left quarter of the image.
You must be registered to see the links
function in order to pull it off (I'm assuming each image is a full screen render, and you're not using moving sprites).Usually in the syntax of Frame("foobar.png") and let Ren'Py figure out the specifics.
If you're loading all images automatically (i.e. just drop them in images/ folder and use their filename) then you need to either use
You must be registered to see the links
or use a Python loop to go through every image and then calling renpy.image() similar to
You must be registered to see the links
.Something like "for fn in os.listdir("images"): renpy.image(fn.split('.')[0], Frame(fn))" or whatever.
Using Frame() function will work regardless of resolution; if you suddenly decide you need a 720p or 8K version for whatever reason, you can get away with changing the game window resolution, and Frame() will make sure all the images are properly adjusted. And if you keep at 1080p, the function will be happy in doing nothing. Likewise, oversampling will pick the "best fit", so it is also transparent if you use 1080p in the end.
If you're passing GUI arguments as relative values (e.g. "xpos 0.2") then it'll be smooth, but if you're passing GUI arguments as absolute numbers (e.g. "padding 16") then some GUI will look weird if you do that and it won't be a so quick'n'dirty implant as it sounds.
Oversampling is also useful in conjunction withYou must be registered to see the linksandYou must be registered to see the linksto allow a game to be remade with higher resolution graphics.