Extra files in installation of 1.2.2??

[tg626]

I think I discovered something, so I'm looking for confirmation and perhaps some opinions on how important it is.

It seems to exist for other parts, but I've directly investigated the OscarB fuel tank so far...

The folder for the Oscar B tank ( \GameData\Squad\Parts\FuelTank\fuelTankOscarB ) contains

• fuelTankOscarB.cfg  
• model.mu            
• model000.dds
• model001.dds        
• tank.mbm            
• tank_n.mbm

Note the existence of both DDS and MBM textures?  Opening the model.mu in a hex editor shows textures named "tank" and "tank_n" being referenced.  If I remove model000.dds and model001.dds the game doesn't care (no errors in log, no issues in game)

So - exactly how much memory / time are we waisting loading textures we never need?  Or loading MBM textures which is supposed to be slower then DDS and was the reason for DDS being adopted in the first place IIRC...

For those who know enough to ask, there is no MODEL{} node in the config, therefore no reassignment to the DDS files.  

[OrbitalBuzzsaw]

In English, please - Not coder, I'm not fluent enough in that to understand.

Edited December 16, 2016 by OrbitalBuzzsaw

[Stone Blue]

hehe... yup... thats called leftover garbage...

Stuff like that ALL thru KSP.... leftover useless remnants of code, unused textures, .cfgs STILL using very old deprecated syntax....etc, etc...

I brought up rigidbody wheel collider errors (lots of them) I was getting, way back in 0.25, or maybe 0.90?, and I was told just ignore them, they are harmless... STILL getting them in 1.2.2

Its all good housekeeping stuff that Squad, obviously thought, since not game breaking, they werent gonna spend the time cleaning up things, "just because..."

[tg626]

I'd bye it was leftover garbage IF the model used the DDS and the MBM files were extraneous, but it's the other way around.  The model uses the MBMs and the DDS are ignored.  That's not bad housekeeping, that's a straight up... erm... loveup as this forum likes to say.

 

[Stone Blue]

Wait... I thought KSP just grabs the first useable textures for the mesh that it finds, regardless of name or extension...

So, when the .dds files are there, theyre first, so KSP uses THOSE, and ignores the "duplicate" mbms...
Remove the dds, and the mbms become first, so KSP uses those... In either case it has useable textures, so no complaints...

UNLESS, I really am clueless about it, which could highly likely be the case.... But I HAVE read up quite a bit on which file types are best to use, and pros/cons... but that was awhile ago, and my memory is basically CRS

 

[tg626]

My unstanding is that the file needs to have the same name.  So if we had tank.dds and tank.mbm what you say is true, but it's not and the log at least makes it appear that it loads every texture it can get it's hands on.  And if THATS true, the game may be stuffing textures it will never ever use into memory and therefore be using up memory pointlessly.

I know that's a lot of maybes, that's partly why I made the post.

[Stone Blue]

Well hopefully someone who knows better than either of us will chime in...

I would say it might be nice if someone were to go thru and update, optimize, and get all the textures/cfgs updated/cleaned up, so deprecated .cfg defs are all cleared out... But then how would they be "released" and distributed without running afoul of Squad's license on redistributing their assets?

[omelaw]

21 hours ago, Stone Blue said:

Well hopefully someone who knows better than either of us will chime in...

I would say it might be nice if someone were to go thru and update, optimize, and get all the textures/cfgs updated/cleaned up, so deprecated .cfg defs are all cleared out... But then how would they be "released" and distributed without running afoul of Squad's license on redistributing their assets?

make a list of unused files in ksp and write a tiny program that deletes thoses files.

some quick of parts that has mbm files in it.

Kerbal Space Program\GameData\Squad\Parts\Wheel\roverWheelM1

Kerbal Space Program\GameData\Squad\Parts\Wheel\roverWheelS2

Kerbal Space Program\GameData\Squad\Parts\Wheel\roverWheelXL3

Kerbal Space Program\GameData\Squad\Parts\Wheel\roverWheelTR-2L

Kerbal Space Program\GameData\Squad\Parts\FuelTank\fuelTankOscarB

I thinks rover wheels use mbm texture... is that intended?

Edited December 17, 2016 by omelaw

[Stone Blue]

Nice... But thats just part of what I'd like to see... :thumbs_up: tho

[tg626]

On 12/17/2016 at 1:15 PM, omelaw said:

make a list of unused files in ksp and write a tiny program that deletes thoses files.

some quick of parts that has mbm files in it.

Kerbal Space Program\GameData\Squad\Parts\Wheel\roverWheelM1

Kerbal Space Program\GameData\Squad\Parts\Wheel\roverWheelS2

Kerbal Space Program\GameData\Squad\Parts\Wheel\roverWheelXL3

Kerbal Space Program\GameData\Squad\Parts\Wheel\roverWheelTR-2L

Kerbal Space Program\GameData\Squad\Parts\FuelTank\fuelTankOscarB

I thinks rover wheels use mbm texture... is that intended?

That's part of my point, they made DDSs for the model but they are still using the MBMs.  Solution: delete mbm files, rename dds files to match.

Delete tank.mbm, tank_n.mbm

Rename model000.dds > tank.dds

Rename model001.dds > tank_n.dds

Edited December 20, 2016 by tg626