Skip to content
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

Failing to open x64 game in a path with special characters #643

Open
h4knet opened this issue Feb 20, 2024 · 3 comments
Open

Failing to open x64 game in a path with special characters #643

h4knet opened this issue Feb 20, 2024 · 3 comments

Comments

@h4knet
Copy link

h4knet commented Feb 20, 2024

Hello,

It seems the x64 version of the game won't launch if the path of the executable contains special characters like "éèàç..".

Here is the log file :

ioq3 1.36_GIT_7d711f8-2024-02-17 win_mingw64-x86_64 Feb 17 2024
SSE instruction set enabled
----- FS_Startup -----
We are looking in the current search path:
C:\Users\Clément\AppData\Roaming\Quake3\baseq3
C:\Users\Clément\AppData\Roaming\Quake3\ioquake3\baseq3
c:/program files (x86)/steam\SteamApps\common\Quake 3 Arena\baseq3
C:\Program Files\ModifiableWindowsApps\Quake 3\EN\baseq3

----------------------
0 files in pk3 files

We can see on the first line that the é is read correctly, but not on the second line (where the game actually is on my PC..).

I've moved the folder somewhere else (without special chars) and everything works fine.

@h4knet
Copy link
Author

h4knet commented Feb 20, 2024

Here is the content of the folder as proof :
image

I guess the issue comes from the function :

static void FS_Startup( const char *gameName )

And some mis-encoding ?

@zturtleman
Copy link
Member

ioquake3 doesn't support non-ANSI characters in paths on Windows. (This affects all file access, not a single place.) It's also reported at #509.

@h4knet
Copy link
Author

h4knet commented Feb 20, 2024

Indeed; I guess it’s a duplicate then..

But it’s weird to see the others binaries working (dedicated x64 and x86 game) where the x64 game isn’t.

maybe there could be an « easy » fix somewhere as the first line of log was written correctly ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants