SUBSIM Radio Room Forums - View Single Post

propbeanie · 11-07-21, 04:50 PM

You usually have to run Hebe's tool multiple times to clear issues. You might fix what his tool found, but there is another lurking behind that one. But yes, the internal names have to match throughout. Take just a stock asset though, and copy its naming conventions, other than, do NOT use Conte Verde or the Porpoise, and some merchant that I can see, but cannot remember... but if you use the Kate for an airplane example, it has errors in the loadouts - in the Stock game... even the devs had issues with load-outs...

But anyway, the Kate is "ADB_B5N2_Kate" folder name. "ADB_B5N2_Kate.cfg" in that folder (think of a single mission file, that has the file matching the folder name). Inside that config is "ClassName=B5N2Kate * 3DModelFileName=data/Air/ADB_B5N2_Kate/ADB_B5N2_Kate * UnitType=303". Now, in the Roster Air folder for Japan is "TB_B5N2_Kate.cfg" and in it is "ClassName=B5N2Kate * UnitType=303" So they name it "DB" for "DiveBomber" in the Air folder, yet number it 303 for "Torpedo Bomber", and name it that in the Roster folder... sigh - but it does work like that.

in the Air cfg file is

[Loadout 1]
Name=3x500Kg Bombs
Type=3

[Loadout 2]
Name=4x250Kg Bombs ** no matching entry in the eqp file
Type=2

[Loadout 3]
Name=Torpedo
Type=4

and the eqp file has

;Basic Loadout values
All OK, seemingly
;3x500Kg Bombs loadout definition
All OK, seemingly
;5x250Kg loadout definition
All OK, seemingly, other than no matching cfg listing...
;Torpedo
Seemingly OK also

... and then list all of the "pilots" at the end, outside the other "loadout" definitions... not confusing. But notice that the cfg file names do not match, but the ClassName and Type must, of course... Probably what happened with this plane, is Bob was working on the plane, while Pete was working on the configuration for the Roster and Air folders, based on Bob's plane. Bob quits, and Steve takes over. He looks at the plane and goes "it be nice to have another bomb mount on this" and adds a B5 node, changing the Air folder, yet neglects to tell Pete for changes to the Roster. whatever - it actually only has four mounts, so it might just be someone got their finger in the wrong hole when typing a number four, and got "5" instead...

11-07-21, 04:50 PM	#1151
propbeanie CTD - it's not just a job Join Date: May 2016 Location: One hour from Music City USA! Posts: 9,749 Downloads: 440 Uploads: 2	You usually have to run Hebe's tool multiple times to clear issues. You might fix what his tool found, but there is another lurking behind that one. But yes, the internal names have to match throughout. Take just a stock asset though, and copy its naming conventions, other than, do NOT use Conte Verde or the Porpoise, and some merchant that I can see, but cannot remember... but if you use the Kate for an airplane example, it has errors in the loadouts - in the Stock game... even the devs had issues with load-outs... But anyway, the Kate is "ADB_B5N2_Kate" folder name. "ADB_B5N2_Kate.cfg" in that folder (think of a single mission file, that has the file matching the folder name). Inside that config is "ClassName=B5N2Kate * 3DModelFileName=data/Air/ADB_B5N2_Kate/ADB_B5N2_Kate * UnitType=303". Now, in the Roster Air folder for Japan is "TB_B5N2_Kate.cfg" and in it is "ClassName=B5N2Kate * UnitType=303" So they name it "DB" for "DiveBomber" in the Air folder, yet number it 303 for "Torpedo Bomber", and name it that in the Roster folder... sigh - but it does work like that. in the Air cfg file is [Loadout 1] Name=3x500Kg Bombs Type=3 [Loadout 2] Name=4x250Kg Bombs ** no matching entry in the eqp file Type=2 [Loadout 3] Name=Torpedo Type=4 and the eqp file has ;Basic Loadout values All OK, seemingly ;3x500Kg Bombs loadout definition All OK, seemingly ;5x250Kg loadout definition All OK, seemingly, other than no matching cfg listing... ;Torpedo Seemingly OK also ... and then list all of the "pilots" at the end, outside the other "loadout" definitions... not confusing. But notice that the cfg file names do not match, but the ClassName and Type must, of course... Probably what happened with this plane, is Bob was working on the plane, while Pete was working on the configuration for the Roster and Air folders, based on Bob's plane. Bob quits, and Steve takes over. He looks at the plane and goes "it be nice to have another bomb mount on this" and adds a B5 node, changing the Air folder, yet neglects to tell Pete for changes to the Roster. whatever - it actually only has four mounts, so it might just be someone got their finger in the wrong hole when typing a number four, and got "5" instead... __________________ "...and bollocks to the naysayer/s" - Jimbuna Last edited by propbeanie; 11-07-21 at 04:59 PM. Reason: TYPO ALERT!!!