Taijian Posted January 19, 2017 Share Posted January 19, 2017 VICTORY!!!!! W000000T!!! At this point, is there anything another interested Linux user (me) could do to help? Link to comment
K4thos Posted January 19, 2017 Share Posted January 19, 2017 The font you are looking for is called Sherwood. Here is a quick render you are welcome to use. Tomorrow I'll either try a macOS install or play around with case-sensitivity. If you need help with the linux instructions, let me know. This was just an eet-only install. Going forward, I want to try adding some pre-eet mods to see how things go. thanks, it's now included in the package. It looks like this font is actually not the one used by Beamdog. All title texts are attached to this post in case someone will be able to recognize the font name. At this point, is there anything another interested Linux user (me) could do to help? nothing right now title text.zip Link to comment
corvias Posted January 21, 2017 Author Share Posted January 21, 2017 A note for any Penguins coming to this thread, I've written a guide for Linux that details how to set up a modding environment like I've used in this thread. Enjoy! I've also packaged Argent77's chitin.key fix into a separate mod in case you aren't using EET or any other mod that fixes it. Link to comment
corvias Posted January 24, 2017 Author Share Posted January 24, 2017 @K4thos you may want to consider moving Argent's chitin.key fix into _end rather than _core. While I was working on my mega-install today, I realized that having it in the _core install phase means it's done before other mods that could potentially edit chitin.key as well... And of course, that's exactly what happened! The standalone chitin.key fix I packaged from Argent77's code does indeed work when I installed it as my last mode. To anyone else reading, that fix is in the the Linux Guide that I linked in my post above. Link to comment
K4thos Posted January 24, 2017 Share Posted January 24, 2017 @K4thos you may want to consider moving Argent's chitin.key fix into _end rather than _core. While I was working on my mega-install today, I realized that having it in the _core install phase means it's done before other mods that could potentially edit chitin.key as well... And of course, that's exactly what happened! The standalone chitin.key fix I packaged from Argent77's code does indeed work when I installed it as my last mode. To anyone else reading, that fix is in the the Linux Guide that I linked in my post above. good idea. Link to comment
argent77 Posted January 24, 2017 Share Posted January 24, 2017 Just a small note: chitin.key in Enhanced Edition games is *always* using forward slashes as pathname separators, regardless of platform. Luckily backslashes are working on Windows as well, but that can change in any of the future patches. I would remove the IF condition completely that skips the fix on Windows systems. Link to comment
corvias Posted January 24, 2017 Author Share Posted January 24, 2017 I think I found another bug. Not sure if this is an issue with weidu or the installer, but in _end, the installer creates the stuff that is meant for the the user's profile folder in the root of the game folder instead, Including baldur.lua. This has the consequence of causing mods, in this case Lefreut's UI, to not detect that EET is installed, and thus not show the correct UI when starting the game. The linux version of the game puts the user-specific stuff in ~/.local/share/ ("~/" is the equivalent of "/home/name_of_user"). As you'll see in the log attached, Stuff is going into: ./Baldur's Gate - Enhanced Edition Trilogy/ when it should go into ~/.local/share/Baldur's Gate - Enhanced Edition Trilogy/ Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.