Playtesting WinSPMBT patch

[Listy]

wulfir said:I have, even in previous versions. And I like it, another justification for existance of the noble anti aircraft branch.

Oh don't worry I always have some Cloud-punchers and Rock Apes about... but I've never had the AI pull one like that on me, so I figuered I should mention it.

I feel kinda deprived now.

[Pyros]

feedback from Scott Littleton <[email protected]>


Hi Pyros,

Two scens have been effected by OOB changes it seems.

Scen 25: N Alliance T-54 SPA tanks have 107mm rockets and 130mm field
guns in weapon slots 2 and 3

Scen 39: Indian Centurion tanks have 30cal cmg in slot 1, 105mm L7 in slot 2

Actually, all the Indian tanks in Scen 39 are messed up, some have three
main tank guns in place of MGs.

Here's a couple more OOB screw ups:

Scen 21: US armor all messed up

Scen 22: Iraqi arty, SAMs, and some light armor are messed up.



Cheers
Scott

[DRG]

It is not possible to fix this for the patch without delaying the patch two weeks as I am leaving for a weeks vacation on Saturday. We have NO idea how this could have gotten this screwed up and I'll need to check the release verson and the CD release version to see if these errors are recent or old. I'm suspecting this may be an "old" problem

I had already considered releasing a "official" scenario package in a couple of months and if need be any corrections can go into that but we will check through the other scenarios and issue a mini patch on the forum if need be

Therefore, it would be helpful to have a bit nore detail about the problems than "some light armor are messed up" if that's possible

Don

[DRG]

OK we just discovered we DO have a big problem . This is not OOB related and it's not scenario related it's right in the EXE and how it's processing the info. We are debugging now and the patch release *IS* on hold

Don

[DRG]

Andy tells me the problems came from code which fixed weapons deleted on a unit in scenario editor, which some other code change had screwed up. This change buggered up some scenarios where the unit was marked as "changed" for some reason (the scenario designer had changed something not necessarily weapons and that's why some sceanrios were affected and others not. I'm testing this and so far it looks good . Good catch on Scotts part.

Don

[Double_Deuce]

DRG said:
OK we just discovered we DO have a big problem . This is not OOB related and it's not scenario related it's right in the EXE and how it's processing the info. We are debugging now and the patch release *IS* on hold

Can we maybe mention something to that effect in the public area of the forum? It appears a few of the natives are getting restless with at least 1 badmouthing Shrapnel. Bi#%@ing and moaning are 1 thing but making comments about Shrapnel or even Camo is another.

[DRG]

I am currently uploading a corrected version of the patch to Shrapnel. Right now that is all I'm prepared to say.

Don

[Double_Deuce]

No problem. Just wanted to make note of it before it snowballed. You know how some people run off at the mouth at the drop of a hat and with none of the facts.

[DRG]

I've posted a note as to why the patch was delayed yesterday and two of the guys who do indeed "run off at the mouth at the drop of a hat" and who have both, in the past, over reacted to remarks posted on the forum and been doing a rather spectacular job of doing what they do best including misquoting remarks made today

This time around we tried an experiement whereby we kept people informed virtually every step of the way the patch was being developed. Unfortunately some peoples overwheming sense of entitlement to information has proven what a complete PITA that approach can be. I doubt very much if we will follow the same path a second time. Next time, whatever we release, will come as a "surprise" to everyone and that will elliminate all the "are we there yet? crap that really REALLY gets on my nerves.


Don

[Pyros]

Don,

I hope you will enjoy your upcoming vacations!

cheers,
Pyros