Instal Steam
login
|
bahasa
简体中文 (Tionghoa Sederhana)
繁體中文 (Tionghoa Tradisional)
日本語 (Bahasa Jepang)
한국어 (Bahasa Korea)
ไทย (Bahasa Thai)
Български (Bahasa Bulgaria)
Čeština (Bahasa Ceko)
Dansk (Bahasa Denmark)
Deutsch (Bahasa Jerman)
English (Bahasa Inggris)
Español - España (Bahasa Spanyol - Spanyol)
Español - Latinoamérica (Bahasa Spanyol - Amerika Latin)
Ελληνικά (Bahasa Yunani)
Français (Bahasa Prancis)
Italiano (Bahasa Italia)
Magyar (Bahasa Hungaria)
Nederlands (Bahasa Belanda)
Norsk (Bahasa Norwegia)
Polski (Bahasa Polandia)
Português (Portugis - Portugal)
Português-Brasil (Bahasa Portugis-Brasil)
Română (Bahasa Rumania)
Русский (Bahasa Rusia)
Suomi (Bahasa Finlandia)
Svenska (Bahasa Swedia)
Türkçe (Bahasa Turki)
Tiếng Việt (Bahasa Vietnam)
Українська (Bahasa Ukraina)
Laporkan kesalahan penerjemahan
Gods sake Steam shows you a tooltip with the CD-Key at startup.
How are you suposed to run it as admin? Is there a Starup / console command for doing so?
The Saved password is loaded from UTGame.ini. ("The password you have entered has an invalid length. A valid user name and password must be entered to login" error issue)
These are normally loaded from \UTGame\Config (this will differ if -nohomedir was used). If another directory contains these files, say in \UTGame\Published\CookedPC\Config, they will be loaded after, and the settings from those configuration files will be used. Hence, where these issues are seen.
I can only hope there is a reason the developers allow the loading of, what should be unique, configuration files. And, honestly, they should have ONLY loaded the first one, not the last one. But I digress...
As we only want one to exist for configuration purposes, delete any that are not in expected directory.
On my system, \UTGame\Published\CookedPC\Config had many of the *unique* configuration files (UTEngine.ini, UTGame.ini, etc.). After removing them, I was able to save both the CD Key and the password without being prompted again after closing/opening the game several times.
As others have seen this issue, I can only assume we all used the same process to cause this. For example, there may be a tool we all used to perform maintenance in UT3.
It was a pain to discover/deal with so I hope this helps someone.
Additionally, keep in-mind that the UT3 generates and stores a unique encrypted key based on multiple factors (I don't know all of the factors). For example, the unique encrypted key is partially based on CD Key + Network Interface Card (NIC) Media Access Controller (MAC) address. This means that any time there is a network interface change (like adding a NIC or a VPN), there is a potential for the unique encrypted key to be regenerated and the CD Key will need to be entered again (but only once per factor change).