#126 posted by
Joel B on 2014/04/07 03:07:36
Yeah, setting "Quake Directory" to the steamapps\common\quake folder is the way to go, and things work pretty well. To tie it all up:
1) The warning message about not finding a localization file appears to be mostly harmless. The localizations won't even be used unless the Steam bootstrapper encounters some issue running Quake.
2) You can make the message go away by copying the relevant folder and file (Public\steambootstrapper_english.txt, or whichever is appropriate for your language settings) from the Steam folder down into the Quake folder. This is kind of ugly though, and might break if a later Steam update changes the file. Actually creating a shortcut might also work; didn't try that.
3) It's easy to change the Quake Injector code to be more tolerant of these situations where the exe is not in the basedir. In the case of this Steam hack, the change would make it run Steam from the right working directory so that it finds the localization file.
4) Even if I get rid of the localization problem, I also see another warning in the case where Steam hasn't been launched yet: "[0406/174210:ERROR:resource_bundle.cc(417)] Failed to load C:\Games\Steam\bin\chrome.pak". It turns out that the current version of Steam always generates this message when I start it; I just usually won't see it unless I dig through Steam logfiles. It's harmless.
So, because of 1) and 2) it's workable. As for 3), I don't know if a new release of QI will ever be in the cards, but I'll mail Spirit about the patch. Fixing 4) is above my pay grade.
#127 posted by
Spirit on 2015/08/08 13:19:44
There is some work going on at the moment and I would like to make a new release soonish. If you have some (small) issues that are not yet in
https://github.com/hrehfeld/QuakeInjector/issues , now is the time to speak.
#128 posted by
Spirit on 2015/08/08 13:44:42
Could someone test ze Quake Injector on Windows 10?
#129 posted by
Joel B on 2015/08/08 19:39:16
Works on Windows 10 for me. I've tried install, uninstall, and Quake-launching.
However there's currently a build error in the master branch. I have a proposed fix at
https://github.com/hrehfeld/QuakeInjector/pull/103 ... I know I can merge that myself, but I'll wait a bit just in case I'm missing something.
#130 posted by
Joel B on 2015/08/10 18:39:42
BTW, any opinions about issues that would be essential to take care of before the next release? Lots of ideas have been accumulated there on GitHub over the years... I'm not sure which (if any) are really jumping up and down for attention.
(Especially minor fixes as opposed to big new features.)
#131 posted by
Spirit on 2015/08/10 19:05:52
https://github.com/hrehfeld/QuakeInjector/issues/97 would be great for user-friendliness. Right now a failed download will require the user to notice/remember it and manually remove the file.
Error
#132 posted by
ptoing on 2015/08/20 22:56:22
Seems like atm I can not connect to the database.
This is what I get:
"Database parsing failed! org.xml.sax.SAXParseException; lineNumber: 7284; columnNumber: 44; The entity name must immediately follow the '&' in the entity reference."
Worked just fine a couple hours ago. Something wrong with the server?
#133 posted by
ptoing on 2015/08/20 23:06:39
Now it works again. Must have been some weird hickup