0002615: "con_scaletext" causes giant text and HUD.

Notes
(0014306) Dusk (developer) 2016-02-04 01:42 edited on: 2016-02-04 01:43	What are your con_virtualwidth and con_virtualheight set to? The screenshot suggests that they're very small. You can set them in the "text scaling" submenu. In fact I didn't realize that the "Scale text in high res" option existed. It appears to be a duplicate of the "enable text scaling" option in the "text scaling" submenu.

(0014307) jewellds (reporter) 2016-02-04 02:01 edited on: 2016-02-04 02:02	You're right, the con_virtualwidth and con_virtualeheight were both set to 32, and changing it fixed the problem. I deleted my config and started again, and it turns out that 32x32 are the default values for a new config, which is far too small. As for "Scale text in high res", it seems to be a more recent addition to Zdoom as it doesn't exist in Zandronum before the 3.0 alpha.

(0014308) Dusk (developer) 2016-02-04 02:08	These defaults have been present since forever. You can, for instance, Zandronum 2.1.2 with a clean INI and notice that the HUD scaling still defaults to 32x32 which causes the text to be ridiculously large when text scaling is enabled. I think 320x200 would make a better default.

(0014319) Dusk (developer) 2016-02-05 11:31	'https://bitbucket.org/Torr_Samaho/zandronum/pull-requests/58 [^]' Changed the default to 640x480.

(0014330) jewellds (reporter) 2016-02-06 04:57	Just tested this by building with the pull request change and wiping my old config. New defaults are a massive improvement!

(0014336) cobalt (updater) 2016-02-06 10:46	Issue addressed by commit 8120df9e279d: con_virtualwidth and con_virtualheight now default to 640 and 480, respectively, addresses 2615. Committed by Teemu Piippo [Dusk] on Wednesday 31 December 1969 23:59:57 Changes in files: docs/zandronum-history.txt \| 1 + src/c_console.cpp \| 4 ++-- 2 files changed, 3 insertions(+), 2 deletions(-)

(0014527) Ru5tK1ng (updater) 2016-03-01 21:45	I tested this as well and didn't see any issues.

**Issue Community Support**
This issue is already marked as resolved. If you feel that is not the case, please reopen it and explain why.
Supporters:	No one explicitly supports this issue yet.
Opponents:	No one explicitly opposes this issue yet.

Issue Community Support

This issue is already marked as resolved.
If you feel that is not the case, please reopen it and explain why.

Supporters:

No one explicitly supports this issue yet.

Opponents:

No one explicitly opposes this issue yet.

Issue History
Date Modified	Username	Field	Change
2016-02-04 01:20	jewellds	New Issue
2016-02-04 01:20	jewellds	File Added: Screenshot_Doom_20160203_224430.png
2016-02-04 01:42	Dusk	Note Added: 0014306
2016-02-04 01:42	Dusk	Status	new => feedback
2016-02-04 01:43	Dusk	Note Edited: 0014306	View Revisions
2016-02-04 01:43	Dusk	Note Edited: 0014306	View Revisions
2016-02-04 01:43	Dusk	Note Edited: 0014306	View Revisions
2016-02-04 02:01	jewellds	Note Added: 0014307
2016-02-04 02:01	jewellds	Status	feedback => new
2016-02-04 02:02	jewellds	Note Edited: 0014307	View Revisions
2016-02-04 02:08	Dusk	Note Added: 0014308
2016-02-05 11:31	Dusk	Note Added: 0014319
2016-02-05 11:31	Dusk	Assigned To	=> Dusk
2016-02-05 11:31	Dusk	Status	new => needs review
2016-02-06 04:57	jewellds	Note Added: 0014330
2016-02-06 10:46	cobalt	Status	needs review => needs testing
2016-02-06 10:46	cobalt	Target Version	=> 3.0
2016-02-06 10:46	cobalt	Steps to Reproduce Updated	View Revisions
2016-02-06 10:46	cobalt	Note Added: 0014336
2016-03-01 21:45	Ru5tK1ng	Note Added: 0014527
2016-03-01 21:46	Ru5tK1ng	Status	needs testing => resolved
2016-03-01 21:46	Ru5tK1ng	Resolution	open => fixed
2016-03-01 21:46	Ru5tK1ng	Fixed in Version	=> 3.0
2016-03-01 21:46	Ru5tK1ng	Steps to Reproduce Updated	View Revisions
2018-09-30 22:10	Blzut3	Status	resolved => closed

Relationships