RunClientOnWindows
Version 25 (molator, 05/23/2011 01:49 am)
| 1 | 1 | vl | h1. Run Client On Windows |
|---|---|---|---|
| 2 | 1 | vl | |
| 3 | 19 | kervala | We supposed you have finish the [[BuildForWindowsCmake|compilation]] and now you want to run your own client to connect on the open shard. |
| 4 | 1 | vl | |
| 5 | 20 | sambsp | NOTE: |
| 6 | 20 | sambsp | |
| 7 | 20 | sambsp | 1、You may want to check the known issues section at the bottom of the page before you proceed. |
| 8 | 20 | sambsp | 2、If you are using your own shard, before run your own client, you can use the pre-build client execute file to confirm whether your shard is okay. Then if your client meets problem, you know it isn't your shard's fault. Pre-build client here: |
| 9 | 25 | molator | https://docs.google.com/leaf?id=0B3LX3q7MsUEGOTJkZjM2YzMtZjRjNy00NDEyLTk4ODQtYmVkN2YwNTJmNGFl |
| 10 | 21 | molator | |
| 11 | 20 | sambsp | After download, launch ryzom_client_r.exe to test the shard. |
| 12 | 21 | molator | |
| 13 | 10 | sm3 | |
| 14 | 1 | vl | h2. Data |
| 15 | 1 | vl | |
| 16 | 15 | molator | The Mercurial repository doesn't contains all big data like textures, 3d objects... so you need first to "Download the client archive". |
| 17 | 1 | vl | |
| 18 | 18 | molator | Legacy client for old shards (such as open.ryzom): |
| 19 | 15 | molator | https://sourceforge.net/projects/ryzom/files/ryzom_client_open.7z/download. |
| 20 | 15 | molator | |
| 21 | 15 | molator | That client will work with open.ryzom. |
| 22 | 15 | molator | |
| 23 | 18 | molator | New client for recent shards: |
| 24 | 25 | molator | https://docs.google.com/leaf?id=0B3LX3q7MsUEGOTJkZjM2YzMtZjRjNy00NDEyLTk4ODQtYmVkN2YwNTJmNGFl |
| 25 | 15 | molator | |
| 26 | 15 | molator | That client won't work with open.ryzom. |
| 27 | 15 | molator | |
| 28 | 1 | vl | Extract the archive anywhere, for example in @c:\ryzom_client@. |
| 29 | 17 | molator | Then replace the binary and the drivers with your own. |
| 30 | 1 | vl | |
| 31 | 1 | vl | h2. Running under Visual studio |
| 32 | 1 | vl | |
| 33 | 1 | vl | Right click on @"client"@ project on the left tree then click on *Set as Startup Project* |
| 34 | 1 | vl | |
| 35 | 1 | vl | Right click on @"client"@ project on the left tree then click on *Properties* |
| 36 | 1 | vl | |
| 37 | 1 | vl | In @Configuration Properties->Debugging->Working Directory@ set the path to the client directory, for example @c:\ryzom_client@. Press "OK" |
| 38 | 1 | vl | |
| 39 | 1 | vl | Press *F5* to run the client. |
| 40 | 1 | vl | |
| 41 | 1 | vl | h2. Running outside Visual Studio |
| 42 | 2 | vl | |
| 43 | 5 | Xzereus | Create a shortcut @R:\code\ryzom\bin\client_ryzom_r.exe@ inside @c:\ryzom_client@. |
| 44 | 5 | Xzereus | |
| 45 | 6 | molator | Edit the properties of the shortcut and be sure "Start in" point to @c:\ryzom_client@. |
| 46 | 6 | molator | |
| 47 | 6 | molator | Double click on the shortcut. |
| 48 | 6 | molator | |
| 49 | 6 | molator | This step is extremely important. It is not an option to use the "client_ryzom_r.exe" packaged with the client archive, since this is often outdated, and can cause [[ClientConnectErrors#None-of-the-accountscharacters-you-create-show-up-in-the-database|an annoying problem]]. |
| 50 | 6 | molator | |
| 51 | 2 | vl | h2. Connect on another shard |
| 52 | 2 | vl | |
| 53 | 3 | vl | By default, the client will try to connect on @open.ryzom.com:40916@. But if you want to client to connect on another shard, add this line in @client.cfg@: |
| 54 | 2 | vl | |
| 55 | 1 | vl | <pre> |
| 56 | 3 | vl | StartupHost = "ip.of.your.server:40916"; |
| 57 | 1 | vl | </pre> |
| 58 | 1 | vl | |
| 59 | 1 | vl | So it'll override the @StartupHost in the @client_default.cfg that is : |
| 60 | 1 | vl | |
| 61 | 1 | vl | <pre> |
| 62 | 1 | vl | StartupHost = "open.ryzom.com:40916"; |
| 63 | 3 | vl | </pre> |
| 64 | 15 | molator | |
| 65 | 15 | molator | h2. Create a user account |
| 66 | 15 | molator | |
| 67 | 15 | molator | To create a user account, run the client, fill login/password and click 4 times on connect. |
| 68 | 15 | molator | Validate the popup you will get. |
| 69 | 15 | molator | The account is created. |
| 70 | 4 | Xzereus | |
| 71 | 9 | sm3 | h2. Client Errors and Known Issues |
| 72 | 4 | Xzereus | |
| 73 | 4 | Xzereus | There is a good chance you'll come across an error or two. If you find one, visit the Page detailing client connect errors [[ClientConnectErrors|client connect errors]]. |
| 74 | 7 | sm3 | |
| 75 | 16 | molator | NOTE for the legacy client: |
| 76 | 1 | vl | |
| 77 | 9 | sm3 | 1) You'll need to add the following lines to your client cfg for now: |
| 78 | 9 | sm3 | <pre> |
| 79 | 9 | sm3 | TexturesInterface = "texture_interfaces_v3"; |
| 80 | 9 | sm3 | TexturesInterfaceDXTC = "texture_interfaces_dxtc"; |
| 81 | 9 | sm3 | </pre> |
| 82 | 1 | vl | |
| 83 | 9 | sm3 | If you have issues with icons missing in the game. This is the reason. |
| 84 | 9 | sm3 | |
| 85 | 9 | sm3 | 2) There are missing textures in the current client archive related to the login screen. You'll notice a grey screen at 2 points while running the client. This should be remedied eventually with update of the client archive. |
| 86 | 9 | sm3 | |
| 87 | 14 | molator | You can unpack client\data\interface.bnp, copy launcher_bg.dds to launcher_bg_0.dds and launcher_bg_1.dds and repack using bnp_make. |
| 88 | 11 | molator | |
| 89 | 9 | sm3 | 3) Before your client will connect to your newly built server, you'll need to update 2 XML files that it uses for communication. |
| 90 | 7 | sm3 | |
| 91 | 7 | sm3 | In your c:\ryzom_client\data directory create a new directory called data_common |
| 92 | 7 | sm3 | |
| 93 | 7 | sm3 | Copy database.xml and msg.xml from \ryzom\code\ryzom\common\data_common\ and place into your c:\ryzom_client\data\data_common directory. |
| 94 | 7 | sm3 | |
| 95 | 1 | vl | You can unpack client\data\data_common.bnp instead, replace the two files and repack using bnp_make. |
| 96 | 13 | molator | |
| 97 | 13 | molator | These steps will not be needed eventually. |