Maybe this sounds like a dumb question but I'm really at a loss of what to do.

Basically, I've got a common weapon odf with child odfs in two respective sides. But when I modify the common weapon odf, the modification is only reflected in one of the sides (ie, the change will apply to cis but not rep). I've tried a manual clean and I've of course check the parent-child relationships to assure that they are all properly called for. I'm at a loss of what to do.

Instead of a child ODF, why not make a "super" ODF that doesn't inherit anything from a parent ODF? May I ask what exactly are you trying to change?

The reason I'm using a parent is so that I don't have to keep hopping back and forth between both sides making sure both weapons' properties are identical (besides the visual stuff -- colors, sounds, muzzleflash, mesh, etc.).

It was just something simple like spreadrate.

Here's the rep odf.

[WeaponClass]
ClassParent = "com_weap_inf_auto_rifle"

[Properties]

AnimationBank = "rifle"

GeometryName = "rep_weap_inf_new_rifle"
HighResGeometry = "rep_weap_inf_new_rifle"
OrdnanceName = "com_weap_inf_auto_rifle_ord"
FirePointName = "hp_fire"

The only reason I mention any geometryname at all is because the parent didn't have one so that the SBD could remain without a weapon mesh. But that's irrelevant.

The CIS variation is the same minus the geometryname stuff.

[WeaponClass]
ClassParent = "com_weap_inf_auto_rifle"

[Properties]

AnimationBank = "rifle"

GeometryName = ""
HighResGeometry = ""

OrdnanceName = "cis_weap_inf_wrist_auto_rifle_ord"
//FirePointName = "hp_fire"

Hmm, I not sure why it isn't working. Is the CIS rifle's ClassParent also "com_weap_inf_auto_rifle"?

Yes, that's what it says in the post above.

[edit]

For the record, the ordnance for the rep rifle was supposed to be rep_weap, not com_weap, and as you would expect, changing that did not fix the problem.

Whoops, I must have not been looking. This is a hard one. I can't seem to find out what problem is, sorry.

I actually had similar difficulties modifying the CIS B-1's rifle. No matter what I put in it, how often I munged, etc. it would stubbornly refuse any of the values written in its own ODF. Maybe it's something about the way the CIS side is set up? IDK, thougn, it ought to be the same as the others.... Just spewing thoughts here, I have no real idea on how to fix this. In my case, even creating a master ODF as mentioned above didn't work; you could try and see if it works for you.

are you adding ALL of the req files and stuff into your side folder and are you LUAs complete?

myers73 wrote:are you adding ALL of the req files and stuff into your side folder and are you LUAs complete?

You realize that has no bearing on whether or not the weapon values are changing?

@Fiodis -- Yeah, I just tried taking out the parent altogether and I copied the values of the parent into the child to bypass the whole problem. For whatever reason, it still didn't work. So I'm trying a manual clean and munge now.

[edit]

It still appears to not be working.

trainmaster611 wrote:It still appears to not be working.

I sense a fellow sufferer. Those misbehaving files of mine are still sitting in my folders, unfixed. Out of curiosity, is your weapon localized? I realize that has most likely no affect upon its properties...but eh.

A different idea: create a new set of ODFs, different names, with the same values, and give your unit those.

If that fails, and you're really desperate, you could try creating a whole new custom side just for that one unit with the evil ODF. Both are things I meant to try myself but never got around to.

Edit: Silly me. I went off a tangent when I first posted.

I milled over this at work, and came up with an idea or two. The changes work for one unit and not the other, so I'm now thinking that either the rep unit using that weapon is not being loaded, there's a weapon with the same name being loaded into memory that's causing a conflict, or the rep unit's odf doesn't have the new weapon assigned to it. Even if it's a total waste of time, it couldn't hurt to double check.

Couple of questions, where is this common file residing? In one of the side folders or in the side common folder? What happens if you copy the common file to both side directories, I know it defeats the purpose slightly. Just playing (at work don't tell my boss) I changed something in the side/common directory and munged side common and it never created either a new side common or a new world common.lvl file so if you were doing it that way that may be why it is not showing up, which of course doesn't answer why it wouldn't work when they where all munched together without a common file.

MercuryNoodles wrote:Edit: Silly me. I went off a tangent when I first posted.

I milled over this at work, and came up with an idea or two. The changes work for one unit and not the other, so I'm now thinking that either the rep unit using that weapon is not being loaded, there's a weapon with the same name being loaded into memory that's causing a conflict, or the rep unit's odf doesn't have the new weapon assigned to it. Even if it's a total waste of time, it couldn't hurt to double check.

FragMe! wrote:Couple of questions, where is this common file residing? In one of the side folders or in the side common folder? What happens if you copy the common file to both side directories, I know it defeats the purpose slightly. Just playing (at work don't tell my boss) I changed something in the side/common directory and munged side common and it never created either a new side common or a new world common.lvl file so if you were doing it that way that may be why it is not showing up, which of course doesn't answer why it wouldn't work when they where all munched together without a common file.

@Noodles

1) I'm not sure why the unit would simply not load. I have the dc:SIDE thing applied, etc. I did in fact make an entire new side just for this unit which evidently failed also. I even changed the name of the unit's ODF and its references in the REQs and everything but still no change.
2) I just did a quick check through all the sides folders for ODFs with the same name, no result

@Frag

1) Its in data_***\Sides\Common\ODF
2) Did you have the dc:SIDE thing in the LUA for the opposing sides? Otherwise, changing anything in the common won't make any difference

Also, for the record, the unit did used to take changes I made to common. So the rifle is indeed modified but its still using the values I had a few weeks ago instead of the most recent munge.

I'm going to try modifying the thermal detonator in the common and see if anything changes. If not, it might have something to do with the rep side and/or the unit.

If at first you don't succeed, munge, munge again? *lightbulb* When you munge changes for this weapon, do the affected odf names appear in VM's little text window?

One more thing you could check is the "date modified" on that side's lvl, and compare it to the one in data_***/_LVL_PC/SIDE, to be sure it's being copied.

When you were using the common odf, what did you munge after the change?
As mentioned it doesn't create a side com.lvl as such but rather puts the common files in the side that called for them. What I did was copy and change a file name in the com directory to something that would be easy to search for in the .lvl file, then changed an odf in the all side to reference the recently changed com odf file. Munged all side and looked at it with a hex editor and did a search for what I changed and it was there.
So what I am rambling on about is if you we just munging common side it probably wasn't getting to where it needed to be but if you did Munge everything then it may just start cooperating.

Well I changed the common thermal detonator ODF and the change was reflected in the rep units' weapons so its obviously particular to the rifle ODFs we are concerned with, not the unit or the side.

@Noodles: I don't usually read that crap in the VM, my attention span is too short But looking through the _BUILD/Side common, rep, and crf (the side I moved the concerned unit to) folders, all the REQ and CLASS files indicate they were munged on May 19 whereas the changes stopped taking effect about 5 days or so earlier.

@Frag: I did munge 'everything'. I always do that when I edit a common ODF.

Frankly, I'm stumped.

So, we know the files are being munged, but I'd still like to know if the new lvl is being copied to the addon folder, just to be sure.

Yup it is. Besides, if it wasn't, it the grenade wouldn't have been affected.

I'm going to try moving the common files to the rep folder and see if it will take then since it will have been munged into the rep side.