SUBSIM Radio Room Forums - View Single Post

areo16 · 07-05-14, 02:06 PM

Hi DW,

For SH3...
I do have one suggestion for a hotfix. Perhaps when it is searching for Campaign errors and looking for unit class and unittype combinations, it will iterate through all classes of the same classname before it posts error.

Here is example. I have a mod soup that I am trying to incorporate many large mods together (GWX, WAC, War Elite, IJM, etc...) so I have classes that are duplicate but have different unittypes, in order to make the compatible with the various mods. Like I have in my Land folder a "LCD_SearchLight" folder, and then also an "LCD_SearchLight_2" folder.

LCD_SearchLight has this in the LCD_SearchLight.cfg file:

Code:

[Unit]
ClassName=CDSearchLight
UnitType=408
MaxSpeed=0.000000
MinSpeed=0.000000
Length=11.5
Width=13.8
RenownAwarded=10

the latter (LCD_SearchLight_2) has this in LCD_SearchLight_2.cfg:

Code:

[Unit]
ClassName=CDSearchLight
UnitType=403
MaxSpeed=0.000000
MinSpeed=0.000000
Length=11.5
Width=13.8
RenownAwarded=10

Notice that they both have the same classname but different UnitTypes (408 and 403). This is for mod compatibility. Perhaps you could add to your iteration in your program that it searches for all of a particular classname, to search for various unittypes of that classname before it spits out error. Because I am getting this error:

Code:

     Type 403 not defined for CDSearchLight

I of course do have CDSearchLight class with unitType 403 (as you can see above), but I'm sure your program just found the first CDSearchLight folder and saw 408 UnitType, and therefore spit out the error.

Could you perhaps fix this? I realize this is a special request but it should be an easy fix. Just loop until all of a particular ClassName are found, then compare UnitTypes. Don't just search for the first one.
Thanks.

Ask if you have questions.

If you don't have the time, I might just throw together a .bat file that searches for this error in the .log output and then searches my directories to see if it really is a legit error. So let me know if your up for the fix, otherwise I'll throw a .bat together.

07-05-14, 02:06 PM	#7
areo16 Sonar Guy Join Date: Oct 2013 Posts: 382 Downloads: 64 Uploads: 0	Hi DW, For SH3... I do have one suggestion for a hotfix. Perhaps when it is searching for Campaign errors and looking for unit class and unittype combinations, it will iterate through all classes of the same classname before it posts error. Here is example. I have a mod soup that I am trying to incorporate many large mods together (GWX, WAC, War Elite, IJM, etc...) so I have classes that are duplicate but have different unittypes, in order to make the compatible with the various mods. Like I have in my Land folder a "LCD_SearchLight" folder, and then also an "LCD_SearchLight_2" folder. LCD_SearchLight has this in the LCD_SearchLight.cfg file: Code: [Unit] ClassName=CDSearchLight UnitType=408 MaxSpeed=0.000000 MinSpeed=0.000000 Length=11.5 Width=13.8 RenownAwarded=10 the latter (LCD_SearchLight_2) has this in LCD_SearchLight_2.cfg: Code: [Unit] ClassName=CDSearchLight UnitType=403 MaxSpeed=0.000000 MinSpeed=0.000000 Length=11.5 Width=13.8 RenownAwarded=10 Notice that they both have the same classname but different UnitTypes (408 and 403). This is for mod compatibility. Perhaps you could add to your iteration in your program that it searches for all of a particular classname, to search for various unittypes of that classname before it spits out error. Because I am getting this error: Code: Type 403 not defined for CDSearchLight I of course do have CDSearchLight class with unitType 403 (as you can see above), but I'm sure your program just found the first CDSearchLight folder and saw 408 UnitType, and therefore spit out the error. Could you perhaps fix this? I realize this is a special request but it should be an easy fix. Just loop until all of a particular ClassName are found, then compare UnitTypes. Don't just search for the first one. Thanks. Ask if you have questions. If you don't have the time, I might just throw together a .bat file that searches for this error in the .log output and then searches my directories to see if it really is a legit error. So let me know if your up for the fix, otherwise I'll throw a .bat together. Last edited by areo16; 07-05-14 at 02:34 PM.