[TEC] How does "frequency" work for ship skins in the Roster?

elanaiba · 07-08-10, 09:47 AM

Skins or names?

sergei · 07-08-10, 10:04 AM

Sorry, I wasn't clear.
Skins.

tater · 07-31-10, 04:44 PM

Interesting.

I just loaded a single mission with a few ships in it with new skins.

I set the unit roster files for each texture such that one was good from 1901 til 1940, then the next from 40 to 41, 41 to 42, etc.

I put 3 in the single mission, with the cfg date for each merchant set such that 1 should have had skin 1, then another skin 2, and the last skin 3.

Even though the mission date was 1944, all showed up with the pre-1940 skin.

OK, then I make all the dates 1901-1999 and try again. This time I set the frequency for skin 1 = 0.3, skin 2 = 0.3, skin 3 = 0.4

And I got 2xskin 1, and 1xskin 3!

Frequency might well work. In fact, setting frequency = 1 might FORCE using the first skin with an available date... must test. The ability to have many many skins will become important soon

Nisgeis · 07-31-10, 05:05 PM

Did you change both Entry Date and Unit Version Date in the ME when you teated the different date versions?

tater · 07-31-10, 05:29 PM

No, the entry date has to be the same, otherwise I have to sit there for years (more than 20km away) and wait for them to spawn.

The unit cfg date is what I changed. Note that this works for eqp files---I have single test missions where one subchaser has radar, and the earlier cfg date version doesn't.

sergei · 08-01-10, 07:44 AM

Quote:

Originally Posted by tater

Frequency might well work. In fact, setting frequency = 1 might FORCE using the first skin with an available date... must test.

Which may explain why in my tests the game seemed to have a predilection for just picking the first available skin.
I had all my frequencies set to 1.

tater · 08-01-10, 09:03 AM

That's the default, and I've always left it as is, even with a few new skins. The stock skins are so bad that I never bothered much—one filthy, dirty skin look much like another

The devs should have made at least 1 "clean" O-map for every ship.

Dan, should you pop back into the thread:

is there a chance that date assignments for skins in the Roster only work in campaign mode?

Also, do ship skins need to be in a certain name format for that to work, or are arbitrary names fine as long as the path is selected properly in the unit.cfg in roster?

So I used whole numbers for frequency. No idea if it works.

I made a mission, I have one ship class with 3 units in a convoy. One has a 1938 date, another has a 1942 date, and another '44. The skins are set such that all the "new" skins start in 1941+, and all the pre-war skins END in 1941. The cfg date on the 1 ship is 1938, but it shows the same skin as the 1942 ship—and the 1944 gets an appropriate skin.

It's very confusing, the start and end dates WORK with the eqp files, I've done much testing on that. I can have one of these merchants get an EQP change that works based on the cfg date, but not the skins.

07-08-10, 09:47 AM	#1
elanaiba Ace of the Deep Join Date: Mar 2005 Location: Bucharest, Romania Posts: 1,058 Downloads: 3 Uploads: 3	Skins or names? __________________ With strength I burn...

07-31-10, 05:05 PM	#4
Nisgeis Ocean Warrior Join Date: Jan 2008 Posts: 2,909 Downloads: 77 Uploads: 11	Did you change both Entry Date and Unit Version Date in the ME when you teated the different date versions? __________________ -------------------------------- This space left intentionally blank.

08-01-10, 09:03 AM	#7
tater Navy Seal Join Date: Mar 2007 Location: New Mexico, USA Posts: 9,023 Downloads: 8 Uploads: 2	That's the default, and I've always left it as is, even with a few new skins. The stock skins are so bad that I never bothered much—one filthy, dirty skin look much like another The devs should have made at least 1 "clean" O-map for every ship. Dan, should you pop back into the thread: is there a chance that date assignments for skins in the Roster only work in campaign mode? Also, do ship skins need to be in a certain name format for that to work, or are arbitrary names fine as long as the path is selected properly in the unit.cfg in roster? So I used whole numbers for frequency. No idea if it works. I made a mission, I have one ship class with 3 units in a convoy. One has a 1938 date, another has a 1942 date, and another '44. The skins are set such that all the "new" skins start in 1941+, and all the pre-war skins END in 1941. The cfg date on the 1 ship is 1938, but it shows the same skin as the 1942 ship—and the 1944 gets an appropriate skin. It's very confusing, the start and end dates WORK with the eqp files, I've done much testing on that. I can have one of these merchants get an EQP change that works based on the cfg date, but not the skins. Last edited by tater; 08-01-10 at 08:37 PM.

Thread Tools
Show Printable Version Email this Page
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

07-08-10, 10:04 AM	#2
sergei Sea Lord Join Date: May 2008 Location: London UK Posts: 1,788 Downloads: 405 Uploads: 29	Sorry, I wasn't clear. Skins.

07-31-10, 04:44 PM	#3
tater Navy Seal Join Date: Mar 2007 Location: New Mexico, USA Posts: 9,023 Downloads: 8 Uploads: 2	Interesting. I just loaded a single mission with a few ships in it with new skins. I set the unit roster files for each texture such that one was good from 1901 til 1940, then the next from 40 to 41, 41 to 42, etc. I put 3 in the single mission, with the cfg date for each merchant set such that 1 should have had skin 1, then another skin 2, and the last skin 3. Even though the mission date was 1944, all showed up with the pre-1940 skin. OK, then I make all the dates 1901-1999 and try again. This time I set the frequency for skin 1 = 0.3, skin 2 = 0.3, skin 3 = 0.4 And I got 2xskin 1, and 1xskin 3! Frequency might well work. In fact, setting frequency = 1 might FORCE using the first skin with an available date... must test. The ability to have many many skins will become important soon

07-31-10, 05:29 PM	#5
tater Navy Seal Join Date: Mar 2007 Location: New Mexico, USA Posts: 9,023 Downloads: 8 Uploads: 2	No, the entry date has to be the same, otherwise I have to sit there for years (more than 20km away) and wait for them to spawn. The unit cfg date is what I changed. Note that this works for eqp files---I have single test missions where one subchaser has radar, and the earlier cfg date version doesn't.