Support Technique

I often experiences two problems post patch (Windows sytems); Here's some workarounds:

1. You launch Ryzom and see the program in system tray but not on screen:
Open "Ryzom_configuration_rd.exe", click on "Display" and set the x and y positions to 0 (mine seems to like -32000 after patch which would be 16 screen lengths to the left and 30 below the screen.

2. You launch ryzom and when ya get in game, you aare at 1024 x 768:
Ok when you are told to exit and relaunch, exit but do not relaunch. Follow directions above but instead of editing the x and y positions, enter 1920 x 1000 or whatever you like to use.

3. The patches also reset your GFX settings to default. AFAIK, these have to be reset in Game Config. / Graphics / Landscape - Characters - Special Effects

PS: I use 1920 x 1000 in window mode for 2 reasons:

1. It gives access to screen real estate allowing me access to custom launch bar and desktop.

2. It solves some Ryzom issues such as no pop up windows for decorating your apartment. If they don't appear just hit the "maximize" button in upper right twice (once takes you to 1920 x 1080 and twice takes me back to 1920 x 1000

i know another little trick to keep all your settings from being changed after a patch (or after when disconnected and you relog your account to force log your toon off the server)

this works in windows every time:

open the task manager
choose the processes tab
find the ryzom process (should be client_ryzom_rd.exe)
right click the process and choose "end"
when the conformation box comes up tell it yes.

ryzom will now be closed.

now you can restart ryzom and your settings will be the same as the last time you were in game playing your toon. (if you do this process because disconnected be sure to give it a little time after you do it or you'll just have to kill the process all over again.)

the reason for this seams to be that whenever the client is properly closed, the configuration of the active window is saved in the config file. the login screen and char select screen use the default x and y size of ryzom, and if you close it on either of these screens it will save that data as your last known setting, thus changing your normal settings.

this is simply a workaround for the strange way that ryzom updates it's config file everytime you close the program vs when you change a setting.

also, this will keep your exact window layout (all the stuff in game, chat, radar, action bars, ect in the place you like).

I don't know what you guys are doing, but I don't have any problems with settings whether I'm in windowed mode (with my storage alt) or in fullscreen mode (with Bittty).

There are things going on here besides just patches and OS, that's for sure.

Useful info there Fred but I have to agree with Bittty on this one, only time I've ever had a config problem was after a crash. Why I take regular back ups. I run in windowed mode because full screen caused crashes on one of my old PCs and I got used to it.

there is two versions of ryzom client floating around.

1. Official windows client (from 2012?)
2. Ryzom Core client for linux/mac and possibly for windows with patch disabled.

First updates client.cfg even when you exit at login/char selection phase and that messes up window size (and possible placement) and if you login to game with wrong screen size, ingame window placement is messed up aswell.

Second has that fixed.

i'm running the offical client on windows, so maybe that's it. i'll have to look into that 2nd option karu, thanks for the tip. (would be nice if the only time the config file was updated was when the user changed something related to it, vs it resetting to default settings)

I have the original client from 2004 (just updated all the time) and no problems with this stuff so I had a look at my client.cfg and found this line:

SaveConfig = 0;

same in client_default.cfg says this:

// If you set this variable to 1, your client.cfg will be overwritten when you quit the client. 
// You will loose all the comments and identation in this file.
SaveConfig = 1;

Maybe setting that option to 0 (as I seemingly have done ages ago) helps with the problems

I doubt that is the problem, Jarnys, since I have that variable set to 1 (by client_default.cfg) and have not changed it in my client.cfg file.

I'm running official Win client updated with every update but with history back to the last time I downloaded it from the site back in 2012.

It only updates client.cfg -- does not touch client_default, and only "messes up" on crash, and not often on that.

Well Im am glad that this doesn't affect some of you but that doesn't mean it doesn't happen to many others. It's been mentioned over and over for years in Uni but saw it so many times with all the Atysmas patches / repatches of late that I duplicated the post from bunnynet as best I cud from memory. My ryzom folder is dated january 2004.

Neela ... Zyroom eliminates the need for manual backups ..... however I'm not anxious to use these as any new flags I have might have planted that day go bye bye. I think I have the backup set to once a week.

Perhaps it's the fact that some of us have just updated from pre beta days.
I also have that variable set to 1 by client_default.cfg , that line does not exist in my client.cfg file.

I do notice that client_default.cfg is set to 1024 x 768 ..... so and this is just a guess, methinks that post patch it is looking at the client_default.cfg file after patch and all the rest of the time it's looking at client.cfg. Changed it to 1920 x 1000. See what happens.

On your machines for those w/o th eproblem, without the problem, is the resolution the same on both cfg files ?

BTW, I did also notice that Frequncy is set to 60 Hz in client_default.cfg, ..... client.cfg says 120.

Though I have a 144 hz monitor, I am using it at 120 Hz so as to be able to enable Lightboost.

I did not intend to come across in any way other than reporting and adding information, FF. The more data that is accumulated, the better the chance of happening upon the cause of the problem.

In my setup the client_default.cfg is 1024 x 768 resolution and none of my three instances of the client have that resolution. I am not, however, modifying the speed (set to 60Hz).

Bitty exactly this might be the problem then...
client_default.cfg is never overwritten (might only happen at patch time to change the default values) and if you edit it the game might not start or will get the right file from the server.
The comment in client_default states that IF the value is 1 client.cfg will be overwritten during quit.
As I have set it to 0 in my client.cfg it will NOT write the file during quit but only during changes done manually (client.cfg settings take precedence over client_default.cfg settings if it's a setting that's not blocked in the code)

Freddy if you don't have the line in client.cfg just add it (you just have to make sure it's on a single line and not sharing a line with something else)
If setting this to 0 doesn't help you can always return to the previous setting by deleting the line again.

And no, resolution's not the same in both files 1024x768 in client_default.cfg and 1920x1080 in client.cfg

This issue happens to me even on the linux client: After a patch, and closing the game at the character selection window for a required restart, the window size always is reset and all positions are messed up.

I've now changed the SaveConfig variable to 0 in the client_default.cfg and added it to the client.cfg as well. After Easter holidays I can confirm wether it worked or not ;-)

Use this updated client (with ryzomcore compatibility code) :64bits version & 32bits version

Well patched again yesterday .... let it happen just to see what would happen. Wound up again at 1024 x 768 w/ all settinsg reduced.... so setting the default config to 1920 x 1000 didn't chnage the behavior.