Bug #266

fs_game does not recognize profile

Added by lottin over 6 years ago. Updated over 2 years ago.

Status:New% Done:

70%

Priority:LowSpent time:-
Assignee:-
Category:Client
Target version:2.78
OS: Arch:

Description

see this forum thread for details:
http://www.dev.etlegacy.com/boards/3/topics/349


Related issues

Related to ET: Legacy Development - Bug #1023: Loading profile overwrites cvars / fix CVAR_ROM flagged c... In Progress 20.03.2017
Related to ET: Legacy Development - Bug #415: ET:L is creating two different etconfig.cfgs Fixed 09.12.2013

History

#1 Updated by RaFaL over 6 years ago

  • Subject changed from fs_game does not do what it's supposed to do to fs_game does not recognize profile
  • Target version set to 2.71rc2

#2 Updated by IR4T4 over 6 years ago

  • Category set to Client

lottin wrote:

...
If I start etl with "etl +set fs_game etpub" I’m asked to create a new profile, so I’m afraid this is not it.

This is exactly the way it should work - this isn’t a bug. Each mod has got it’s own profile. If you start a new mod the first time you have to create a profile for the running mod. When you connect to a server with a new mod the profile is created w/o the profile create dialog automaticallly.

Profiles are stored in fs_homepath/<MOD>/profile/<profilename>

Different mods have different CVARS so you are able to set CVAR values per modification! On the other hand you don’t mess up a mod’s profile with CVARS of other mods.

#3 Updated by IR4T4 over 6 years ago

  • Status changed from New to Invalid

#4 Updated by lottin over 6 years ago

I had a profile but I was lacking a "defaultprofile.dat" file, that was what was causing the problem.

#5 Updated by Radegast over 6 years ago

  • Status changed from Invalid to New

IR4T4, this bug is not invalid. It happens because we changed the default mod from etmain to legacy. Since legacy is not in the search path, defaultprofile.dat is not found even if a profile was already created. I was going to add legacy mod as the last search path, but I wanted to test first if it could bring any unwanted effects.

#6 Updated by IR4T4 over 6 years ago

I would keep it as it is. A defaultprofile.dat file is created per mod path. In case the legacy profile cfg is read you may also collect CVARS of legacy mod the 'loaded’ mod doesn’t use (which is a vanilla bug fix beside the not known side effects if you add legacy to the search path) ...

#7 Updated by Radegast over 6 years ago

OK, I will add a top-level defaultprofile.dat in fs_homepath

#8 Updated by Radegast over 6 years ago

  • Assignee set to Radegast

#9 Updated by Radegast over 6 years ago

  • Assignee deleted (Radegast)

I can’t fix it that way and we can’t add Legacy to the default search paths.

#10 Updated by IR4T4 over 6 years ago

We might do this:
If fs_game is set and != "legacy" and profile name is our default value try to read the name of player directly from fs_homepath/legacy/defaultprofile.dat.

#11 Updated by IR4T4 over 6 years ago

  • % Done changed from 0 to 100

I’ve had a closer look: A defaultprofile.dat file is created with the UI createProfile command/process which is the way to go for running a mod the very first time.

lottin wrote:

If I start etl with "etl +set fs_game etpub" I’m asked to create a new profile, so I’m afraid this is not it.

This is it. Done once we keep the mod config clean with mod only used cvars - this fixes genuine behaviour of importing etmain (or in our case legacy) cvars into the mod.

Write defaultprofile.dat on disconnect and on ETL exit if there is no dat in path for given fs_game (should fix direct connect to mod case w/o exec createProfile before)

#12 Updated by IR4T4 over 6 years ago

  • % Done changed from 100 to 70

#13 Updated by IR4T4 about 6 years ago

  • Target version changed from 2.71rc2 to 2.78

#14 Updated by IR4T4 about 6 years ago

  • Description updated (diff)

#15 Updated by Spyhawk almost 3 years ago

  • Target version changed from 2.78 to 2.76

This should be solved once and for all.

#16 Updated by IR4T4 over 2 years ago

  • Priority changed from Normal to Low

#17 Updated by IR4T4 over 2 years ago

  • Target version changed from 2.76 to 2.78

#18 Updated by Spyhawk over 2 years ago

  • Related to Bug #1023: Loading profile overwrites cvars / fix CVAR_ROM flagged cvars behaviour added

#19 Updated by Spyhawk over 2 years ago

  • Related to Bug #415: ET:L is creating two different etconfig.cfgs added

Also available in: Atom PDF