Unfortunately I did not give it much attention when I first noticed it so I don't know what about my system changed. reQuiem gives me garbage like this on launch, playing maps works fine if I load them in the console, I cannot load them from the commandline. Any idea what might cause this? I am on Archlinux.
Other engines work fine. I tried with a clean Quake dir. Pak files are intact, no configs interfering.
looks like the console buffer is corrupt, hence the various commands getting spliced weirdly like that.
I've not looked at requiem, but if its cbuf was rewritten, try ensuring that there's a \n on the last line, and that there's no nulls mid-file or anything silly like that.
also, make sure its reading the default.cfg that you think it is.
Don't want to cause you to look for a problem that isn't there, but if this doesn't happen on Windows how are newlines being handled and are the files being read in text mode?
Windows terminates lines with /r/n (char 13, char 10) and Linux with just char 10.
(Generally I am of the opinion to neither read nor write files in text mode and just use binary mode manually adding newlines (/n) where appropriate so there is only one style of newlines regardless of the operating system. Then when you are reading them, look for the possibility of carriage returns (/r) and strip them since you cannot control what text editor or engine last touched a file.)
The night is young. How else can I annoy the world before sunsrise? Inquisitive minds want to know ! And if they don't -- well like that ever has stopped me before ..
I'd say either autoexec.cfg or config.cfg are corrupted. Maybe you opened one the files in some editor and accidentally changed the file encoding to/from ANSI to UTF-8 or something like that ?
I know FrikaC made a cgi-bin version of the quakec interpreter once and wrote part of his website in QuakeC (LordHavoc)
I am 99% sure all files are intact, I checked with strace what it reads. Deleted all cfgs. The pak files have proper md5sums. It must be something in the whole system that changed. :?
If you can point me to
1) the current source
2) a known source without the problem
I might be able to track down origin in mere minutes.
There aren't too many ways this problem could happen.
(Oh yeah, and any chance Quaddicted can allow http:// for download and not just https:// ... libcurl.dll for Quake engines doesn't support https. (Windows))
The night is young. How else can I annoy the world before sunsrise? Inquisitive minds want to know ! And if they don't -- well like that ever has stopped me before ..
If it was as easy as a code diff, I would have found it myself. The engine was not recompiled and all its versions I tried showed the same. I guess it must be some library?
These are used and were updated recently on my system:
Some obviously can't have anything to do with it but maybe one has encoding/unicode stuff?
PS: You can use (^Quakeinjector|^Java|DokuWiki HTTP Client) as user agent to avoid the http -> https redirection until I drop Dokuwiki and the QI gets a new release with SSL support. HTTPS is the future though.