October 19, 2017, 01:50:18 AMLatest Member: jbaustin2017

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - Grimdoc

Pages: [1] 2
1
Translations / New lines to be translated before next release
« on: March 16, 2012, 02:31:17 PM »
There have been several updates and changes on the translation part of the game lately.
New lines have been added and others have been made obsolete.

If you want your language to be up to date for the next release, then you should consider updating it.

2
Translations / Don't be a ****!
« on: February 05, 2012, 11:35:43 PM »
After being tipped of this article, I decided to share it here: http://www.digitalspy.co.uk/gaming/news/a362679/minecraft-studio-apologises-over-racist-translation.html

This could happen with our project too, so please be alert and tell us if you find any swearing, racism, sexual content or offensive harassments in the language you play the game in.
Stuff like this is not tolerated at all.

Until now I have just checked the uploaded language files for common coding errors, but from now I will do some searches with Google translate for unwanted words and phrases before committing such files.
I encourage all other translation committers to do the same.

Since we cannot proof-read 100 % of the text (can't know every language), I strongly recommend that you report anything you might find offensive in your own language.

I don't think this is a big issue with our project, but better safe than sorry.

3
Hospital Café / What happened with this sub-forum name?
« on: January 21, 2012, 03:56:24 PM »
This sub-forum name used to be Hospital Café, but now the é is missing.
Did something go wrong when we switched hosts? :-)

4
Translations / CorsixTH Translation Guide
« on: September 05, 2011, 08:06:23 PM »
CorsixTH translation guide

If you want to contribute to this project by making a new (or improve a) translation, this guide could be of good use.


First of all
Before starting on a new translation you should be sure that it hasn’t been made already (or that someone else has started on it). You can check this by looking for a thread including your language name in the sub-forum called Translations.
You should also check the project’s Google Issue list first. Just go there and search for the name of your language.
If you don’t find your language in any of these two places, then you should be ready to start on your translation.

When you feel like you have a reasonable first draft or edition of your translation, then it’s time to let others know what you have made. This can be done either by posting in the forum or on the issue list.

It is recommended that you make a post in both places.
Take a look at "How to get your translation into the game (sharing it with others)" further down in this guide.

If you later on realize that someone else already have started a similar translation, then try to contact the other translator and find out how to help on his/hers translation, or maybe even merge these two translations.


Starting on a completely new translation
There are two ways to make a translation for a new language.
The easiest way is to simply copy an existing translation file and translate that one into your own language (assuming you know the language you are translating from).
You should (if possible) pick a translation that is built up logically (and not totally random), since this is much easier to work with. Both for you and those who might improve/continue your work in the future.

PS: One can not translate directly from the english.lua! How to translate from English is mentioned in “The hard way (translating directly from English)”.
The reason for this is that the english.lua doesn’t contain all of the text strings that needs to be translate. The english.lua contains about 400 lines, while a “full translation” can contain over 3000 lines.
The other English lines are taken from the original game’s data files.

PPS: A “fix” for this could easily be made if someone took the time to make a “dummy” language file for the English strings, so that translators could copy and translate from that one. But if someone takes this task, one should be extra careful to get a logical build of the file, so it’s easy for translators to work with afterwards.

The easy way (copying a finished translation)
Lets take the Norwegian translation as an example, since this is pretty logically built, and use this as an basis for how to build up the new language.
First get through these folders: main game folder, LUA, languages (e.g. on MS Windows: \Program files\CorsixTH\LUA\languages\).
Here you see all the languages for the game so far.

Now open norwegian.lua with your favorite text editor (I prefer Notepad++ on MS Windows).
First you will see about 60 lines on copyrights and how the text string categories are arranged, then you will see some global settings.
You should change the name/names in the top to your own name and/or nick name when you have copied the content from the language you prefer to translate from.

Now for the global settings. These should be changed to fit your language.
The best way to learn how to do this is to read “Implementing a new language” in the wiki.
PS: The copyrights and font settings can also be copied from there.

The hard way (translating directly from English)
A harder way to create a translation is to go through the english text.
The reason this is harder is because there is no "clean" language file with english strings like all the translations.


The way to do it this way is to first make a new file with the *.lua ending. If you don’t get it right, just copy another language file, change the name and delete it’s contents to start from scratch.
Then you should copy the copyrights from “Implementing a new language” in the wiki (or an existing translation).
You should also copy the global settings (language settings), and edit this to the name/names of your own language (explained in the link above).

Now you should make sure that the debug menu is turned on in the game.
This can be done by finding your config.txt and change the debug setting to true, like this: debug = true
(read this to locate the config file)

When that is done, you should start up your game, go to options and change into your own language (the one you are translating to).
Now start up any level (example level is fine), move your mouse to the top of the screen to see the menu, go to the debug menu and choose "dump strings". Exit the game.

Go to your main game folder, and open the file debug-strings-diff.txt
Here you will see all the strings from the English language that isn't translated to your language (and at this time that is all of the strings).

You will have to categorize and copy these strings into your own language file, and then translate them.
It is smart to add these strings as you translate (and not just add them all at once), since you then can see what you have to add next (just update this list by going into the game and dump the strings again).


Some technical tips
You should only translate what is inside the quotation marks (" ").

A text string should always end with a comma after the last quotation mark.

If you want to add explaining messages for yourself or others, you can add a space after the text string, and then two minuses (like this: random = "random text string", --message or explanation).
The text after (and including) these minuses will not be shown in the game. This can only be seen from the text editor ( if you are using Notepad++, it will appear in green color when written correctly).
This is nice for strings that needs further work. Just mark them with this for example: --todo
And when you or someone else want to improve whatever string you have marked, they could just search for the text "todo", and find what needs to be done.

For convenience, another tip is to never use TAB as a space function (unless you reassign it to use separate spaces in your text editor).
Because different programs use different lengths for the TAB character your nice formatting will then be spoiled for others viewing your file.

Just have a look at some of the code used in the existing files, and you will soon see what you can and cannot do.


What is a .lua file?
A *.lua file is a file containing code for the game. In our case it contains the strings that are (or needs to be) translated.
It can be opened, read and edited by any standard text editor.


How to get your translation into the game (sharing it with others)
After you have translated some or all of the text, you should go to the project’s “issue list” (found here: https://code.google.com/p/corsix-th/issues/list).
1) Click the button “New Issue”.

a) change the template to “Patch from user”.
2) In the summary you should write “Language: <yourlanguage>” to make it easy to find (e.g. Language: Norwegian).
3) Remember to attach you language .lua file with the button “Attach a file”.


After you have made some submits through the Google Issue list, you might get privileges to add your translations directly to the subversion (SVN) file repository (without having to post it in the Issue list for others to add it).
If you get this permission, then you will need a SVN program (e.g. TortoiseSVN for MS Windows), but a more complete list can be found on Wikipedia.


Thanks to Lego3 and Froksen for contributing!

5
Research Department / REQ the ability to turn off help.
« on: August 28, 2011, 03:57:36 PM »
I would very much like an option where I could turn off this kind of help:
- The message you get every time you build a new room.
- The message that says you need a X kind of staff for using and maintaining Y kind of room.
- The message that says you cannot place patient/item here.

Generally an option that can turn off all help boxes and balloon-tips from the adviser.
PS: The briefing box when you start a new level should not be turned off.

6
I was just able to hire a consultant with all three abilities.
Should this be possible?

If you are lucky enough to get this super consultant, you just have to put him in a training room and he will produce new super consultants all the time.

7
Emergency Room / CorsixTH Newbie Guide
« on: July 28, 2011, 02:30:41 PM »
CorsixTH newbie guide

If you are completely new to CorsixTH, I recommend you to read this guide (or at least look at it if you have a question), since there is a lot of unnecessary questions asked by newcomers, that have already been answered.


Reporting bugs and errors:
Please read through these easy steps before reporting a bug, error or a question:

1.   You should always try the latest build (update/version) of the game, since the problem you are experiencing might be fixed already.
How to install the latest build is explained elsewhere in this post.

2.   Take a look in the "Emergency room" in the forum to see if someone reported the same problem or question before.

PS: This place is only meant for the situation where you're having trouble installing or running Corsix TH, or if you have problems with the gameplay.
This is not the place to report bugs.

3.   Do a search in the project's Github issue list.
Type in a relevant word (or phrase/words) and press search. Also try using words/sentences from the error message in the "console window".
If you get a lot of matches for your search, then you probably should try to find a better word/phrase to get a more precise hit.

If you find a relevant post (or posts), then read through it to see if this really is the same as your problem (or relevant).
When you find your problem or a very relevant one, you should check what status the problem has.
If the status says it's fixed and you still get errors, please give some feedback in the issue page.
If the status says it isn't fixed and you have some new information, please give some detailed feedback (preferably with a screenshot, a savegame from before the error occurs and a copy of the error from the "console window" - it is described elsewhere in this post on how to copy it).

Scroll down in this post to learn where to find your savegames.

4.   If you don't find any similar issues, then make a new issue in Github (or in the "Emergency room" in the forum, if it fits the description in #2).
Both sites require that you have a registered user, but this is easy and fast to set up.

You should always include your error log, unless it's obvious what the case is (check the "How to copy error text from the "console window"" section to learn how).

The most important thing after posting an error, issue or a question, is that you check back on it often, so that you can give the developers any additional information if they need it.


What level you are on:
If you are wondering on how to find out what level the error occurred on (for error reporting), just change the language to English (go to options, then settings), open the town map and compare the town name to this list:

Level 1 = Toxicity
Level 2 = Sleepy Hollow
Level 3 = Largechester
Level 4 = Frimpton-on-Sea
Level 5 = Simpleton
Level 6 = Festering-on-the-Wold
Level 7 = Greenpool
Level 8 = Manquay
Level 9 = Eastville
Level 10 = Eggsenham
Level 11 = Croaking
Level 12 = Battenberg


Installing the latest build (update/version):
For Microsoft Windows:
If you are running an old Windows version, you will need an additional program to unpack the files. I recommend 7-zip (freeware), or you can use almost any other decompression program.
Newer versions of Windows have an integrated .zip reader, but you can still install the additional program.

Open/save this link: http://th.corsix.org/corsix-th-latest-win32.zip

When you have opened it, just copy all of it's contents and paste it into your main CorsixTH folder (e.g. C:\Program files\CorsixTH). You will be asked if you want to overwrite the files. Say yes to all (none of your savegames or settings will be lost).

Now you are done!


For other platforms/operating systems:
Follow the same progress as for Windows, but use this link instead: http://th.corsix.org/corsix-th-latest.tar.gz

Then you should navigate to the directory where you downloaded the file and use the command "tar -xf corsix-th-latest.tar.gz". This will unpack the files.


PS: The latest builds might be more unstable than clean beta installs, but so far this hasn't been a problem, and you will probably get more joy by updating.
And by using these builds, the developers get more feedback on errors and so on, which can make the game finished faster.

After you have updated to a build from a clean beta version, you might experience that your shortcut don't work anymore. The solution is to use CorsixTH.exe (which is found in the main game folder).
Just change the shortcut target to this file instead.


How to copy error text from the "console window":
When you get an error in-game, just press Alt+Tab to get out of the game window (don't close the game).
Now find the console window. It should have some error messages in it.
To mark the text you want to copy (the relevant part), just right click on the bar of the window and chose Edit and the Mark or Mark all.
After you are done marking, just right click on the bar again, but now you chose Copy.

You can now exit the game, and you are ready to post your error message at the Google Code site (or the forum, if it is fulfills the rules for posting, see #2 in Reporting bugs and errors).
If you are very unsure about what parts of the text is relevant and what is not, you can always just make a new .txt file and paste all of the text in it, and then just upload it as an attachment to your issue post.
I encourage this instead of posting a whole wall of text in your post. It just looks very messy and take a lot of space.

If the game closes before you get to copy the error log, you can always find the gamelog.txt (in the same folder as config.txt) - this will contain your latest error.


Where to find your savegames:
The location depends on your operating system.

Savegames can be found in an own folder from where you find the config.txt, and the directories for the config.txt can be found in the game wiki: https://code.google.com/p/corsix-th/wiki/ConfigurationFile

You have to change USERNAME / HOME into your own username / home name.
These directories are hidden by default, so just copy and paste the location into your address bar in a window, press enter and then just open up the “saves” folder.


DEMO version:
If you are running CorsixTH with the DEMO version of Theme Hospital, then you have very limited gameplay
It only includes only a modified level 1 and it has no dialogs. However, you can play custom levels (without dialogs).
What you could do is to get a hold of a Theme Hospital copy and use that when you install CorsixTH (buy it, borrow it or get it elsewhere, but I don't encourage illegal copying) - or you could wait for a long time until graphics, sounds and music have been replaced with open source contributions, so that the game is independent.


Turning on the DEBUG menu (for cheats, tweaks or research on game behavior):
This is almost the same operation as finding your savegames, so just go to the wiki and find the directory for your OS: https://code.google.com/p/corsix-th/wiki/ConfigurationFile
Open the config.txt file and scroll to the bottom. Change the debug setting to true, like this: debug = true
Now you can start up the game, and on the top bar (where saving, loading etc. are) you can now see the debug menu.

PS: In the config.txt you can also change your screen size, chose where to put your savegames folder, change the location of installation folder and so on. There is more about this in the wiki.


How to take a screenshot:
While in the game, just press Ctrl+S, and an image in the .bmp format is placed in your main CorsixTH folder (e.g. C:\Program files\CorsixTH).

This only works with the SDL version.


How to significantly increase/decrease values in game:
When you just left click to increase/decrease some values in game, you only change the value by 1, but if you hold down the Shift or Ctrl button while you left click, you change it by a lot more.

For example in the drug book you change the research percentage by 25 if you “Ctrl-click” and by 5 if you “Shift-click”, but it is changed by 1 if only the left mouse button is used.
Another place this is useful is in the furnish corridor menu, when you need to buy many benches. Here you increase by 10 on “Ctrl-click” and 5 on “Shift-click”.


Concentrate research on machines:
It might not be too obvious what the concentrated research on various machines actually improves. But what it does is to increase the durability (max uses before repair is needed) and lowers the cost (both the cost for a room and the replacement cost for a new machine is lowered).
When the Research Dept. has improved a machine, you won’t see any increase in durability until you either buy a new room or replace the old machine.
   

Heating (radiators):
The heat distribution in CorsixTH is a bit different from the original Theme Hospital.
CorsixTH has an ambient and slowly increasing temperature instead of Theme hospitals "instant" temperature.
So with CorsixTH it takes some time for the rooms to warm up.

A good tip is to place a radiator in every room, and a few spread around in the corridors.
Take a look at the hospital map after a while to see the heat distribution/coverage.

Handyman not cleaning up litter:
If your handyman never visit a special part of your hospital to clean up vomit, pee or trash, then just put up a plant nearby where the littering occurs, and he will hopefully clean it when he passes by to water the plant.
Be sure your handyman is set to water plants (by adjusting the markers when you click on him - standard setup is OK).

PS: This method might not be necessary if/when the handyman code is improved.


Too big queues (many patients):
On higher levels you will need 2-3 GP's Office and 2 pharmacies to keep up with the queues.
You normally just need 1 of all other treatment/diagnosis rooms.
It can be wise to spread some toilets and staff rooms around when your hospital gets bigger.

Try to educate most of your staff in the training room so that you get faster working doctors (consultants).
After the consultant status is achieved, the doctor can no longer be trained.
Only doctors can improve their skills in the training room (not receptionists, nurses or handymen).

You can also go to the Policy chart and slide the “diagnosis procedure” bar to maximum (guess at cure = 100%).
Now you reduce the chance for patients getting the wrong cure (which results in death).


Too small queues (few patients):
To get more people into your hospital you need to get a higher reputation.

This can be done by not killing patients (improve the drugs), don’t send home patients, don’t take emergencies you can’t handle, not getting your Auto-Autopsy Machine discovered (don’t examine too many patients in it) and try not to fire too much of your staff.

Anyhow, you can make patients stay in your hospital longer, by going to the Policy chart, and slide the “diagnosis termination” to max. Now your patients will use as many diagnosis options as they can - which keeps them longer in your hospital and gives you more money (but can be a problem if your hospital gets too crowded).

8
Research Department / Truetype
« on: July 16, 2011, 06:38:37 PM »
I know truetype is pretty new and untested, but I'll make this thread so you can look at it when you have the time to improve the use of truetype.

1. All of the illnesses in the drugbook is written in capital letters, but when using truetype the letter "

9
Research Department / 1 person / persons / people
« on: July 16, 2011, 06:14:51 PM »
In r1284 the issue 707 was fixed.

But I guess only the "accept/decline emergency fax" was changed, because if you take the emergency and succeed, you will get a fax with a similar problem in it (see attached image).

I don't think "you saved 1 people" is accepted, since "people" is plural.
And it is surely not accepted in norwegian.

So a string should be added for this too?

10
This was added in r1319.

But I guess the coder didn't think of that you can fire people when they want a raise too.
I just fired a member from that option to test => No options, he just got fired.
So I really think one should add the option yes/no here too :)

11
Research Department / Money (hiring, raise, bonus)
« on: June 21, 2011, 09:10:50 PM »
It has been implemented that you can't hire someone when you have zero or negative amounts of money in the bank.
But you still can give them a raise and even a bonus (your amount in the bank drops).
This should be change on the exact same principle as the feature implemented.


I also think you should get a notification when you have zero or negative amounts of money in the bank and tries to hire someone.
A newbie would appreciate to know why he can't hire someone.


On a sidenote: I don't think the system should be like it was implemented now.
In reality you CAN hire people with negative holdings in the bank. Like how it is in the game now, you give them money the first day at work.
I would like it to be like the heating bills. They don't tap you account the first day.
And my suggestions about the raise and bonus only applies if the system is to be like it is today (the staff get's money on their first day at work).

12
Research Department / Screenshot notification
« on: June 18, 2011, 11:33:56 PM »
As mentioned in this thread, it would be nice if the adviser would tell you that the screenshot has been saved when you press Ctrl+S.

Just something like this: "A screenshot has been saved to your game folder", to let the player know that the screenshot actually was taken.

13
I was playing the original TH, and noticed these two things:

1: The announcer popped up and told me: "Placing windows makes the rooms brighter and improves the spirits of your staff".
Is this a fact in the old game, or is it just something he says?

2: Before firing someone in the old game, you will get a warning (and asked if you are really sure).
This is something I miss. It's easy to click the wrong button.

14
Research Department / Sound file extraction
« on: April 03, 2011, 11:33:55 AM »
It seems no one has thought of the sound files yet, so I tried to find out how much work it would be.

I used Allmedia Grabber 5.1 (trial) to search through all the sound .dat files.
See the attachment to see all the files and their sizes.

Unfortunately I could not extract them, because I just have a trial version.
But I guess there should be some freeware programs for this cause, now that we know that the file type is .wav.

EDIT: One can't attach .html files, so here is a link:
http://www.sendspace.com/file/thmnso


I also found out how to convert the XMI files to MIDI (found in Sounds/midi).
1. Get Winamp (free) and install it normally.
2. Go to options, preferences, plug-ins, input, find "Nullsoft midi player", mark it, configure, file types, just mark XMI (or all of them).
3. Open up the midi files found in sounds/midi, right click on them in the play list, view file info, save... (and now you can save it as a regular midi).

15
This thread is for gathering all of the various graphical glitches (layering problems).
Since they appear various places, I thought it was best to put it here on the forum, and not in the tracker.

Please post graphical glitches that you have found too, and try attach a screenshot of it.

Here are the ones I have found so far:
1: The training chairs upper part disappears behind wall.
2: The "ambulance lamp" is lowered to the man's chest when standing in the machine.
3: The head of the doctor is missing at one point in the animation.
4: The training chairs wheel is showing outside the wall.
5: The paitent is "outside" the machine (this only happens if a handyman fixes the machine while in use).
6: The desk chairs wheel is showing outside the wall - and the radiator is "under" the bed.
7: The upper bench is a little "inside" the wall. The lower bench, which is being placed, shows how it should be.

Pages: [1] 2