radar detection bug

[michaelm75au]

It may be part of the DATA patch (which was not originally going to be code, but this may change just for this one fix) when it comes up.

I have left it with Joe W to determine.

[castor troy]

ORIGINAL: michaelm

It may be part of the DATA patch (which was not originally going to be code, but this may change just for this one fix) when it comes up.

I have left it with Joe W to determine.

thanks for the info

[SuluSea]

ORIGINAL: michaelm

It may be part of the DATA patch (which was not originally going to be code, but this may change just for this one fix) when it comes up.

I have left it with Joe W to determine.

I'm confused with the terms code patch and data patch, would either of these require a restart?

Thanks for the help Micheal!

[witpqs]

ORIGINAL: michaelm

It may be part of the DATA patch (which was not originally going to be code, but this may change just for this one fix) when it comes up.

I have left it with Joe W to determine.

Honestly, Michael, the fact that a lot of us have many squadrons of Attack Bombers that don't work is pretty big, too.

[castor troy]

ORIGINAL: witpqs

ORIGINAL: michaelm

It may be part of the DATA patch (which was not originally going to be code, but this may change just for this one fix) when it comes up.

I have left it with Joe W to determine.

Honestly, Michael, the fact that a lot of us have many squadrons of Attack Bombers that don't work is pretty big, too.

mhm... and many of us are in mid 43 already in their PBEMs, have forgotten (or didn´t notice) to stop the B-25C factory to upgrade to the B-25D1 and are now stuck with more or less non working types of bombers... [:(]

[stuman]

Thanks as always Michael.

( But as one who usually plays the Japanese side, it is ok with me if the Attack Bombers still have some work to be done. No hurry there [;)] )

[CapAndGown]

ORIGINAL: stuman

Thanks as always Michael.

( But as one who usually plays the Japanese side, it is ok with me if the Attack Bombers still have some work to be done. No hurry there [;)] )

+1

(radar, OTOH . . . )

[;)]

[jwilkerson]

ORIGINAL: SuluSea

I'm confused with the terms code patch and data patch, would either of these require a restart?

Patches that REQUIRE a restart are very rare ... we've never done one for WITP or for AE ... and I don't think our predecessors did any for WITP either. And we have no intention of doing one either.

[castor troy]

ORIGINAL: jwilkerson

ORIGINAL: SuluSea

I'm confused with the terms code patch and data patch, would either of these require a restart?

Patches that REQUIRE a restart are very rare ... we've never done one for WITP or for AE ... and I don't think our predecessors did any for WITP either. And we have no intention of doing one either.

I guess he meant "require a restart to have the data base changes happening for an ongoing game". While it´s great how it´s done now, weren´t most WITP patches done in a way that required a restart to also have the db changes?

[SuluSea]

Thanks guys, I guess I could have been more specific. As I mentioned I'm kind of confused with the code and data patch terms. What I meant to say was something along the lines of , will the radar and attack bomber fixes require you to restart?

[castor troy]

ORIGINAL: SuluSea

Thanks guys, I guess I could have been more specific. As I mentioned I'm kind of confused with the code and data patch terms. What I meant to say was something along the lines of , will the radar and attack bomber fixes require you to restart?

AFAIK... no [:)]

[JWE]

ORIGINAL: castor troy

ORIGINAL: SuluSea
Thanks guys, I guess I could have been more specific. As I mentioned I'm kind of confused with the code and data patch terms. What I meant to say was something along the lines of , will the radar and attack bomber fixes require you to restart?

AFAIK... no [:)]

Don’t want to steal Joe or Michael’s thunder, but I just answered this question with regard to the Babes, and have the text handy, so …

2 kinds of patches – an EXE patch and a DATA patch. Exe patch just changes code (.exe and .dll) files. This was done for Patch 4 and all the hotfixes. Exe patch does NOT require restart. The update happens automatically and does not affect on-going games at all.

DATA patch is different. It changes values in the scenario data files. But these changes do NOT automatically get picked up by an on-going Savegame file. This requires some special update magic by the developers. It was done in Patch 2 (I think it was 2) and kinda worked, but many people had problems, so it’s iffy for it to be done again – up to the Boss.

So installing a DATA patch will not REQUIRE restart; you just won’t see the new data values in on-going games. If you DO want to see the new values, one of two things must happen; 1) special update magic, or 2) restart.

p.s., When (if) the patch comes out, Joe or Michael will make it expressly clear whether or not special update magic will happen. Till then, I respectfully suggest you ‘cover your brookies’ with Plan B.

[jwilkerson]

ORIGINAL: castor troy

I guess he meant "require a restart to have the data base changes happening for an ongoing game". While it´s great how it´s done now, weren´t most WITP patches done in a way that required a restart to also have the db changes?

The six WITP patches done by the AE team had no scenario data changes - they were all "EXE ONLY".

[witpqs]

But with one of the patches - maybe it was the second but I forget - there was data changed because we were asked by the game if we wanted to incorporate the OOB changes into the game in progress.

[jwilkerson]

ORIGINAL: witpqs

But with one of the patches - maybe it was the second but I forget - there was data changed because we were asked by the game if we wanted to incorporate the OOB changes into the game in progress.

Right there was one WITP patch - done by Michael Wood - not the AE team - that had scenario data changes in it - and there was an attempt to allow the option to port those changes into ongoing games. I don't know how successful the attempt was - in my ongoing games at that stage - I neither upgraded the EXE nor the data. I still really prefer finishing a given game on the game version I started in on - at least when playing "real" game - i.e. not testing.

Porting data changes over to onging games is not as easy to do as it is to say. The data in some scenario files like devices or aircraft or classes are easy because these are not changed during the game - but the data in other scenario files like airgroups, ships or land units are changed during the game. Bringing in changes to this second group is very problematic and I think we eventually decided not to try it. So for AE patch 02 we did a "partial" port of the data changes.

[witpqs]

To provide one data point, it worked fine for me.

[castor troy]

ORIGINAL: jwilkerson

ORIGINAL: castor troy

I guess he meant "require a restart to have the data base changes happening for an ongoing game". While it´s great how it´s done now, weren´t most WITP patches done in a way that required a restart to also have the db changes?

The six WITP patches done by the AE team had no scenario data changes - they were all "EXE ONLY".

wow, six patches? Hmm, wonder why I restarted two or three of my PBEMs. Must have been very early then. [&:] Or there have been some problem, can´t really remember anymore, been quite a while already [:D]

[Sardaukar]

Beta patches and hotfixes included into count, apparently.

[jwilkerson]

Wow - I'm surprised at the interest in "Patch History" should we add another CLASS to the Curriculum? [:D]

ORIGINAL: Sardaukar

Beta patches and hotfixes included into count, apparently.

We did six patches for WITP:

1.8.0.0
1.8.0.1
1.8.0.2
1.8.0.3
1.8.0.4
1.8.0.6

I think there was one hotfix for 1.8.0.4 but that was a brief update to the first version of 1.8.0.4 which was then replaced by the final version of 1.8.0.4. I don't recall any beta patches. So I think six patches is the count of what we did - not including beta or hotfix.

[Sardaukar]

My bad, I thought we were talking about AE patches. [8D]