All-Aircraft-Simulations
Inconsistant Mods - Printable Version

+- All-Aircraft-Simulations (https://allaircraftsimulations.com)
+-- Forum: IL2 MODS Download & Discussion (https://allaircraftsimulations.com/forumdisplay.php?fid=267)
+--- Forum: IL-2 4.09m (https://allaircraftsimulations.com/forumdisplay.php?fid=348)
+---- Forum: IL2 MODS Discussion Section 4.09m (https://allaircraftsimulations.com/forumdisplay.php?fid=292)
+---- Thread: Inconsistant Mods (/showthread.php?tid=52038)


Inconsistant Mods - VT51_Thud - 12.01.2008

I would like to begin my thread by first saying that I applaud all those who have contributed to these Mods which has taken IL2 to a much greater level. In no way am I attempting to throw dagers at anyone.

With that said, I think it has brought about some major problems as well. More specifically, each person has a different set of Mods and we all don't see the same thing in the coop sign-up board. While I see a TBF, someone else sees a B-17 for the same slot. Folks that aren't patched at all may even pick what he sees as an allied slot while those with Mods installed show an axis slot.

I suspect it has something to do with the filelist.txt file being updated differently since it is being overwritten with each upload. Just my guess.

Anyone experiencing this?

- Fisneaky - 13.01.2008

I dont think the filelist has anything to do with this.

If the regular flyables are added to FMB first , and the mods last; then those without the mods can select them without the order being changed. ( only works on allied list - unless only mods are Axis.)

Best to ensure everyone has the required planeset installed beforehand.

- Oilburner - 13.01.2008

I have spent some time figuring out this problem and here is what is going on:

This problem is caused by some people having "some" mods and others having other mods. Unless a mission builder specifically marks a plane as AI only it will appear in your flyable list IF YOU HAVE THE COCKPIT. The problem is that when signing up for a plane IL2 sorts people by slot #, NOT plane. So a lead zero is at the top of my list (but I don't have B5N installed) and you have B5N installed and IT is at the top of your list and the lead zero is 5 lines down, we can both pick the lead zero because I'm in slot 1 and you're in slot 5. However, when we spawn one of us will be kicked. In addition, you cannot pick the lead B5N because I'm using that slot (slot #1 in the list).

fyi - order of things showing up in flyable list is function of fmb and can be edited manually after the mission is created (just edit the mis file).


This is the main reason I wanted a AAA mod pack with ALL flyables in it (even flyables I don't care about) just so everybody will be on the same page. "Unfortunately" we have been given so many good mods at such a rapid pace it is hard to keep everybody synced up.


I think you and I were in the same seow campaign last night and I could see the "D's" but I had specifically added them (they are not part of the bomber pack). My squadmates couldn't see them. At this point the only thing to do is to go down the list and each pilot announce on TS which plane he is in (type, squadron, plane#) and everybody else listen and make sure they aren't in the same plane. This still leaves problems other problems such as one person using the SLOT for a plane another person wants to fly but if each person announces what he is flying it should stop people from being kicked.


FYI here is a copy of a post I did in another thread with a clearer example than my rambling above...

///////////////////////

Something I realized last night is I think you have to do one big update. The reason for this is that when you play coops if you have a plane installed but somebody doesn't, you and another player could both pick the same aircraft and one of you gets kicked on mission launch. Here is what I mean:

Player A has no planes installed
Player B has F156 Storch installed

Player A sees this planelist to choose from when coop starts:
BF109
BF109
BF109
BF109
P47
P47
P47
P47

Since there is a F156 in the mission, and player B has it installed, he sees this planelist to pick from:
BF109
BF109
BF109
BF109
F156 Storch
P47
P47
P47
P47

Now player A chooses the 1st P47 (5th plane in list) and player B chooses the first P47 which is the 6th plane in HIS list. However, to player A, it looks like player B picked the 2nd P47 because that is the 6th plane in HIS list. When mission starts one of them will be kicked to an observer role (basically the view you have in a coop after you have ejected/died). When you are picking planes, the game apparently doesn't look at which plane you're in, it just looks at which number in the roster you are.

The other screwed up part is that if Player B picks the F156 Storch it will show on player A's side that B picked the 1st P47. This makes it where player A has to pick another plane (say the 3rd P47) but when mission starts you will have an idiot AI in the lead P47.

This isn't as big a deal when your flying with friends but when you are trying to host coops it turns into a freakin' circus when 30% of the people get kicked on start (everybody always picks the lead or element lead for whatever plane they want to fly).

- VT51_Thud - 18.01.2008

It's been a busy two weeks so I apologies for the late reply.

Thanks for both replies. Yes Oilburner, that was me in the same game. I couldn't stick around much longer because of my work schedule. You are spot-on of what I was trying to say.

I think our side is pretty standardized now so I hope all goes well this week. 8)