Quote:
Originally Posted by Hebe Vollmaus
I'm not shure if i understand you correctly. The last paragraph makes no sense to me. "The escorts themselves[...]" Especialy the last part "vs. not doing this in other installs".
But the first paragraph "In a test with a late[...]" may or may not have something to do with the so called "Config Date Bug". About this pice of quirk was my first post on Subsim:
https://www.subsim.com/radioroom/sho...d.php?t=170485
And my Tool will face a user with this info before checking a Campaign-file:
"Hint1: When RadarWarningReceiver RWR is modified to longer Range on Sensors/Factor and one Class specified Ship (RndUnit) in RndGroup has an older CfgDate, the whole group may not seen by RWR on +=25km Nav-map.
Hint2: Sh3MissionEditor may set CfgDate= of RndUnits to Mission StartDate which result to "CfgDate-Bug" on Class= specified Units (not updated Eqp in late war)."
And let me say some about this "Anyone else ever notice this".
I'm shure everything on SH3 has been noticed so far.  |
Completely stock .14b and if I understand your info. correctly, it applies to modified items.