ConsoleGameEngine icon indicating copy to clipboard operation
ConsoleGameEngine copied to clipboard

Screen Resolution(?) causing issues with console window size initialization

Open WilliamPas opened this issue 5 years ago • 1 comments

(NEWB USER ALERT)

SO I found this package after spending weeks trying to draft up a design for my own engine and instantly fell in love. However I'm having some issues running some of the examples, and I feel this has to do with the desktop space set by windows. I am viewing the project through Visual Studio 2017 with all .Net SDK's up to 4.7

image

First time I ran into this issue was when I tried to run the CaveGenerator.cs example. (My newb self doesnt know how to run the project from different class files so this is how I've been testing the examples.) image

My desktop screen resolution is 720p (1366 * 768). I also had a friend who's screen resolution is 1080p (1920*1080) When I run the example, an exception is thrown stating that the max window size my console allows is 63, when it needs 65. image

Now if I try to edit the window height size directly within cmd properties to 65, it will force the window size back to 63. image image

HOWEVER, with this example, if I turn on "Hide taskbar in Desktop mode" within windows taskbar settings, windows allows me to set the height size property to 65. This results in the program running as intended. image

It seems Windows really cares how much space there is on the desktop is when launching a console. With this change to my taskbar I can run every example except for the 3D and Hello World example, which ends up being too big. image

Perhaps there's a way to set the console font size before console width and height?

WilliamPas avatar May 08 '19 16:05 WilliamPas

Good issue report, very clear! Yes, and this is the current major bug with my engine. Im typing this on my phone, i may reply later to clairify a bit. There is this dilemma because if you set the font after setting the window it sometimes work; at the same time, setting it before also causes problems. I got really weird I/O errors from the resize function. I searched around but there seems to be no other report, nor any solutions to the problem.

ollelogdahl avatar May 08 '19 20:05 ollelogdahl