by Kinsie » Sun Jul 22, 2018 7:08 am
Now that the new devbuild is out I can confirm that vid_setsize works. However, I also noticed that since the old vid_defwidth/defheight settings no longer seem to be read or updated (beyond being set to defaults at startup if they don't exist), the window will still be tiny on first boot until a new size is setup, which likely won't please people who don't religiously browse the bugs forum and know what's up. Since these old CVars don't seem to be used anymore, there might be merit to checking the INI for their existence on startup, then using them as the base for a vid_setsize command so as to neatly transition the user's settings to the new system. That'd likely take a bit of twiddling to ensure it only happens once, though.
(Speaking of the new system, I couldn't see a place in the INI where the new settings are saved, and a quick glance over the commits didn't enlighten me. Is this a registry thing, or something more obvious that I'm somehow missing?)
Now that the new devbuild is out I can confirm that vid_setsize works. However, I also noticed that since the old vid_defwidth/defheight settings no longer seem to be read or updated (beyond being set to defaults at startup if they don't exist), the window will still be tiny on first boot until a new size is setup, which likely won't please people who [i]don't[/i] religiously browse the bugs forum and know what's up. Since these old CVars don't seem to be used anymore, there might be merit to checking the INI for their existence on startup, then using them as the base for a vid_setsize command so as to neatly transition the user's settings to the new system. That'd likely take a bit of twiddling to ensure it only happens once, though.
(Speaking of the new system, I couldn't see a place in the INI where the new settings are saved, and a quick glance over the commits didn't enlighten me. Is this a registry thing, or something more obvious that I'm somehow missing?)