Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

TAXINAUT

An open-world exploration game where you are a taxi-driver in space. · By mosgrom

FIXED: Text cut-off and other possible display problems on Ultra-HD / Ultra-Wide displays.

A topic by mosgrom created Mar 06, 2020 Views: 237 Replies: 6
Viewing posts 1 to 6
(2 edits)

Ultra-HD display (e.g. 4K) reportedly starts with the screen only partly visible. Somebody reported setting text scaling back to 100% solved that problem but text, especially in dialogs, seems to be cut-off at times (probably text is displayed too large). Possibly playing with "Change high DPI settings" (right-click taxinaut.exe -> Properties -> Compatibility tab) might provide a work around. Try letting taxinaut manage the scaling. If you have an ultra-hd display and are willing to assist me to fix this let me know. I'll give you a free key for the game.

2020/03/06  update: Somebody mentioned not just setting the text-scaling back to 100% but also 'other' scaling? I don't know what/where that is in Windows but it might help you. Another thing you can try is in config.txt (in install directory where taxinaut.exe) is change 'uiscale=auto' to:

uiscale=no

I'm working on a way to detect the 150% scaling and do something automatically but this might take a while because as I said before I don't have a 4K monitor so I'm dependent on somebody with a 4K and patience to assist me with this.

2020/03/12 update: This should be fixed as of V0.7.3.

(1 edit)

Hi mosgrom, I have a 4K screen and so far everything is fine, but I have noticed times when chat text is cut short by a line or so. I'm happy to help test any updates or instances where you think this has occurred. Sorry I can't be more specific at this time, but like I saw it's rare and I've only noticed it once or twice.

(2 edits)

Hi Chris? (mrchrisgreen) do you mean by cut short that a word that's spelled out while a character is talking all of a sudden is placed on the next line. Or do you mean actual static text is only partly visible?

If you have the patience, what would really help me is the following:

1. Start taxinaut.exe

2. Go into "SETTINGS".

3. Click the white "TEST" button.

4. Taxinaut will glitch for about 20 seconds and then exit.

5. Send me the test.zip file that should now be in the taxinaut installation folder (where taxinaut.exe is) (send to bugs@mosgrom.net).

Either way thanks for reporting this!

I'm having an issue at 2560x1440 where occasionally a line of text will not be shown due to there being no room left in the box.  I'll send you that file momentarily.

I just send you an email (I'm assuming you just send me the test.zip). I'm looking to fix it of course but another work-around (besides what I mention in the email might be to change config.txt (in install folder where taxinaut.exe is) from:

uiscale=auto

To

uiscale=no

It should give you a smaller screen of 1920x1080 centered on your 2560x1440. I know this is not what we want but as a temporary work-around it might suit.

For anybody following this: I've made a little progress (I think) with this problem. First of all there are 3 things:

1. TAXINAUT is to big to fit the screen. This happens when windows scaling is set to more than 100% (right-click desktop -> Display settings).

2. When people talk to you and the text is animated, a word that was being typed out on one line suddenly appears on the next line. This is as intended (well it's as it's currently programmed but could of course be better but it's not a bug).

3. Text is actually cut-off or only partly visible (I have not been able to confirm this). This would be a bug that is probably also caused by windows scaling.

The current best work-around is still to set your windows-scaling setting to 100% But I'm looking into doing some automatic scaling to compensate. In that case users will still have to set taxinaut.exe's compatibility options, that is, High DPI settings to let TAXINAUT handle the DPI scaling because else it causes issues with text-rendering.

This should be fixed as of V0.7.3