CFG edits wont seem to apply!

[lekkimsm2500]

Whats going on? Yeah, modding the CFG files worked, AT FIRST! But now for some reason, alot of the time, changes wont seem to apply anymore!

whats that all about?

[Capt'n Skunky]

Can you be a little more specific as in what you're trying to edit, what you're expecting to get, and what you ultimately experienced?

Arrr!

Capt'n Skunky

[lekkimsm2500]

Can you be a little more specific as in what you're trying to edit, what you're expecting to get, and what you ultimately experienced?

Arrr!

Capt'n Skunky

Uhh, well, example: Liquid engine! Lets say, thrust from 200 to 800, and fuel consumption to one! save it, using notepad, start game - SEE THE GAME TELL ME THRUST IS 800, yet no apparent changes to anything.

[lekkimsm2500]

Help anyone?

[Capt'n Skunky]

I think you might be expecting a result different that what your tweak has made. Have you looked at the SDK docs or the wiki?

The fact that you are seeing the change of stats in game tells me your tweak is being applied, it's just that you may be expecting a bigger difference than you're actually getting.

Arrr!

Capt'n Skunky

[lekkimsm2500]

I think you might be expecting a result different that what your tweak has made. Have you looked at the SDK docs or the wiki?

The fact that you are seeing the change of stats in game tells me your tweak is being applied, it's just that you may be expecting a bigger difference than you're actually getting.

Arrr!

Capt'n Skunky

Not if i make the liquid engine only have a fuel consumption of 1, and fuel tanks have a hold of 500 units... it burns way to fast, way less than 500 seconds!

[lekkimsm2500]

Aherm, bump

[HarvesteR]

I'm going on a hunch here, maybe I'm on the right track:

Are you modding a copied part folder from the original liquid engine?

If so, did you change the new engine's name parameter on the cfg?

not changing the name is very likely to cause such weird issues.

Cheers

[lekkimsm2500]

I'm going on a hunch here, maybe I'm on the right track:

Are you modding a copied part folder from the original liquid engine?

If so, did you change the new engine's name parameter on the cfg?

not changing the name is very likely to cause such weird issues.

Cheers

I do just copy a folder, go in the copied one, change stuff here and there, AND THE NAME and yet - its only 50/50 or more like 30/70 chance it will actually work! Its not even a guarantee anymore to remove the game, and try over! This is actually starting to piss me off!

Is there an actual program specifically made for edits, or is that done absolutely the notepad way ... ?

[Capt'n Skunky]

Ah, you were working on a copied part. As HarvesteR pointed out, that might be the problem.

The next time you encounter this issue, could you post both the original part cfg and the modified part cfg so we can look at it?

And yes, notepad is the only editor for configuration files. I don't see what an editor would bring that can't be achieved already via notepad or other text editor.

Arrr!

Capt'n Skunky

[lekkimsm2500]

Ah, you were working on a copied part. As HarvesteR pointed out, that might be the problem.

The next time you encounter this issue, could you post both the original part cfg and the modified part cfg so we can look at it?

And yes, notepad is the only editor for configuration files. I don't see what an editor would bring that can't be achieved already via notepad or other text editor.

Arrr!

Capt'n Skunky

Okay, what are the basic workings if i copy, saaaay, liquid engine ... What in the CFG do i have to make different in order to prevent this copy-malfunction crap? ... or perhaps change in the entire folder. Is is ever single line that needs to differ or ... ?

[Capt'n Skunky]

Well, obviously you need to have a different name for the folder, but the most important thing is the name property in the config file. The only caveat to the name is you can't use an underscore followed by a number because that's how the program tracks multiple instances of the same part within a craft. The first LFT would be fuelTank_1, the second fuelTank_2 and so on (the game actually uses a much longer random number).

What we as a community have been doing is adding the abbreviation of our make believe companies to the front of the folder name, for example, mbr_fuelTank would be a fuel tank from my Monkey Business Rocketry. That would also work for the name property in the config.

What we are suspecting is happening to you is that when the game reads your part name and manipulates the name from the unique one in the craft file to the actual part name, it's reverting back to the original name after fixing it up. You can see how this works by looking at what the name does with the name property in a craft file.

Arrr!

Capt'n Skunky

[Killerhurtz]

I'm going on bad memory, but isn't that a bad example Monkey? Isn't it said to avoid underscores?

[Capt'n Skunky]

The underscore issue was fixed, they are now allowed characters. It used to cut the name at the first encountered underscore so a part named 'origname_myname' would appear in the craft file as 'origname_myname_234652394' and would translate to just 'origname' when read back. Harv changed that and it seems the code now works looking for an underscore followed by a number. This means 'name_1' will fail but 'name_one' won't.

Arrr!

Capt'n Skunky

[lekkimsm2500]

The underscore issue was fixed, they are now allowed characters. It used to cut the name at the first encountered underscore so a part named 'origname_myname' would appear in the craft file as 'origname_myname_234652394' and would translate to just 'origname' when read back. Harv changed that and it seems the code now works looking for an underscore followed by a number. This means 'name_1' will fail but 'name_one' won't.

Arrr!

Capt'n Skunky

So what about the .DAE file? Do i need to rename that accordingly?

[Capt'n Skunky]

So what about the .DAE file? Do i need to rename that accordingly?

Nope, the DAE and Texture files can stay the same.

Arrr!

Capt'n Skunky

[C7Studios]

I can confirm I've had this issue before. I had accidentally left the name the same in the part.cfg file. This is an example from my landing gear part. I've marked the part I think thats giving you trouble

In this case there is a folder /parts/C7LGear/

That contains my part.cfg file.

// --- general parameters ---

name = C7LGear <-- This should match exactly the name of the folder you created for the new part.

module = Strut

author = C7Studios

// --- asset parameters ---

mesh = landinggear.DAE

scale = 0.1

texture = landinggear.png

specPower = 0.1

rimFalloff = 3

alphaCutoff = 0.0

[Capt'n Skunky]

AFAIK, the folder name and the part name can be different. The folder is only used by the game when sorting parts in the VAB (it loads parts by folder alpha sort). As far as the game engine and craft files, the name property is used. The first releases of my part packs had folder names different from their name property.

Arrr!

Capt'n Skunky

[C7Studios]

It's just a good rule to follow. It prevents accidental creation of parts with the same name. Windows won't let you make two folders with the same name.

[Capt'n Skunky]

Well, yeah, obviously your folder name will have to be different as forced by the OS, but as far as the game is concerned, there is no link between the two. This wouldn't be the source of the OPs problems is what I am getting at.

Arrr!

Capt'n Skunky

[C7Studios]

Well if he copied the folder he may not have changed the name in the part.cfg file is what I was getting at. That would absolutely cause the issue. In hindsight I could of worded things a bit differently.

[lekkimsm2500]

Well if he copied the folder he may not have changed the name in the part.cfg file is what I was getting at. That would absolutely cause the issue. In hindsight I could of worded things a bit differently.

Thats probably why anything seemed to have changed at the chance of a 50% success. I did change the name of the folder i copied, but it did never occur to me that seemed like a necessary thing to do.

Either way, i tried as told before to change the name in the CFG as Skunky said, and that seems to have done the trick!

So thank you guys very much!