Slipstream Mod Manager v1.9.1 (2018-01-07)
-
- Posts: 24
- Joined: Sat Mar 10, 2018 11:28 pm
Re: Slipstream Mod Manager v1.9.1 (2018-01-07)
Boah I have no clue how to do that, stupid question but could you do that for me? XD
- bamalf
- Posts: 204
- Joined: Wed Dec 17, 2014 12:57 pm
-
- Posts: 24
- Joined: Sat Mar 10, 2018 11:28 pm
Re: Slipstream Mod Manager v1.9.1 (2018-01-07)
No problem mate
I have made an Interesting discovery, I have translated the Achievement text and the game view the letters ö, ä, ü, without problems. But there are 3 tasks where the game doesn´t view the letters properly. the German word for "Main Menu" (HAUPTMENÜ) and "Delete Profile" (PROFIL LÖSCHEN) are not shown right and the german texts where the controls are described, the letters are missing there. I can use other german words for Main Menu and Delete Profile but not for the translation from the controls.
I have made an Interesting discovery, I have translated the Achievement text and the game view the letters ö, ä, ü, without problems. But there are 3 tasks where the game doesn´t view the letters properly. the German word for "Main Menu" (HAUPTMENÜ) and "Delete Profile" (PROFIL LÖSCHEN) are not shown right and the german texts where the controls are described, the letters are missing there. I can use other german words for Main Menu and Delete Profile but not for the translation from the controls.
-
- Posts: 24
- Joined: Sat Mar 10, 2018 11:28 pm
Re: Slipstream Mod Manager v1.9.1 (2018-01-07)
I think i know the Problem,
in your pic you named the "HULL" "корпус", everything that uses this .font can´t view the letters "Ö","Ä","Ü". Every other text till now has no Problen with the letters.
in your pic you named the "HULL" "корпус", everything that uses this .font can´t view the letters "Ö","Ä","Ü". Every other text till now has no Problen with the letters.
- bamalf
- Posts: 204
- Joined: Wed Dec 17, 2014 12:57 pm
Re: Slipstream Mod Manager v1.9.1 (2018-01-07)
Obviously, this is the case. You need to change the HL2.font.
-
- Posts: 24
- Joined: Sat Mar 10, 2018 11:28 pm
Re: Slipstream Mod Manager v1.9.1 (2018-01-07)
So I tried to use your tool but it didnt work for me, i have created new .png and changen the parameter in the index.json and execute the reassemble.rb but i didn´t create the new font.
- bamalf
- Posts: 204
- Joined: Wed Dec 17, 2014 12:57 pm
-
- Posts: 24
- Joined: Sat Mar 10, 2018 11:28 pm
Re: Slipstream Mod Manager v1.9.1 (2018-01-07)
I have done that, step by step how you discribe it on github but it doesn´t create the new font file
-
- Posts: 24
- Joined: Sat Mar 10, 2018 11:28 pm
Re: Slipstream Mod Manager v1.9.1 (2018-01-07)
https://prnt.sc/is3mnb I have no idea why it doesn´t work, it even doesn´t work for hte example .json file in the folder
- D-side
- Posts: 4
- Joined: Tue Mar 20, 2018 6:24 pm
Re: Slipstream Mod Manager v1.9.1 (2018-01-07)
ObstRiegel wrote:https://prnt.sc/is3mnb I have no idea why it doesn´t work, it even doesn´t work for hte example .json file in the folder
Hi, I'm the actual author of the tool. Sorry for the delay, got less free time than I need lately
First of all, you seem to be running Ruby 2.5, not 2.4 (despite the warning on the RubyInstaller download page). I haven't tested it, it might work, but it currently has major compatibility issues with a lot of libraries out there.
I'll give it a go myself though. Just to rule it out. For now let's assume it's not the problem.
The place in the code it refers to suggests that the file in the font_templates contains not an object (in curlies, {}), but an array instead (in squares, []). The error indicates it cannot convert "source" into an integer, which is fair, I did not intend any conversion to happen there. There has to be a field with the name "source" in every .json file inside font_templates. Is this the case?
I specifically tested the example in the repository, and bamalf has been using this tool extensively with a bit of my guidance. We never faced an issue like yours. Let's track it down.
The tool is really rough around the edges, I'm aware of that and sorry about that. I was under the impression that this tool will not be in use by anyone once we're done with Russian fan localization mod.
Looks like I will have to allocate some more time to improve ease of use and error reporting.
UPD: no worries regarding Ruby 2.5, it works just as well as 2.4. Just tried this out.