-
-
Notifications
You must be signed in to change notification settings - Fork 528
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If path has non-ascii chars the game won't be able to find pak0.pk3 #509
Comments
Quake 3 only supports ASCII paths as a whole. You should rename your username as a fix, or disable using the homepath in your user folder by manually adding the +set fs_homepath installationdir cvar to your launch parameters, provided you don't have it located in a protected folder. Unicode on Windows is very messy and even then if you want parity with Linux, utf8 codepage support requires a newish version of w10. |
Well there must be an easy way since apart from Q3 I have never cam across a software that can't handle unicode paths. |
Keep in Mind that unicode support wasn't very widespread in 1999. |
Indeed. Hence the bug report for a modern source port that is still maintained 22 years later. |
Of course it's possible, but that doesn't mean it's easy. |
I'm OK with it being not easy and the team not wanting to spend time on it. Feel free to close the bug report. |
This is only for Windows. Let's say you want to run your game from a folder in your Desktop and your Windows username has non ascii chars in it, then ioquake3 will not be able to find the pak0.pk3 file because the full path of the pak0.pk3 file will have those non ascii chars in it and it somehow messes up the file opening routine. I suspect something here is wrong: https://github.com/ioquake/ioq3/blob/main/code/sys/sys_win32.c
The text was updated successfully, but these errors were encountered: