.RDP is not working

[maxios]

Just a FYI that .RDP is not working atm.

I belive it still thinks we're in tier 3 or 4 .

[DOC]

yes it does but we're not .... a value in the DB needs to be zero'd but it isn't affecting reality, it just thinks it is.

Will be corrected.

[maxios]

yes it does but we're not .... a value in the DB needs to be zero'd but it isn't affecting reality, it just thinks it is.

Will be corrected.

Copy, thanks for the reply DOC.

[maxios]

Just a heads up, might be same issue now for C105.

[DOC]

It's working as a function, but the reporting is not (that's what you see when you use .rdp) ... we know about it and Gadget is working on a fix, just not this weekend.

[i11cef]

It's working as a function' date=' but the reporting is not (that's what you see when you use .rdp) ... we know about it and Gadget is working on a fix, just not this weekend.[/quote']

Well as long as when it is fixed it doesn't nerf the effort of Allied RDP on Axis factories - which I note it didn't.

Though I must say, when the .rdp cycle reporting issue was fixed on day 3 of the 105 campaign, I guess the correct progress value was not calculated and applied until day 6 - I have screen pix of .rdp reports at 11:57:00 CDT reporting "cycle 1 at 50%", then some 40 minutes later at 12:36:47 CDT reporting "cycle 1 at 99%."

Without getting into the minutia, what is it exactly that you do to reset the server for a new campaign?

Is it simply a matter of replacing (re-writing / copying over) a game-server initialization file (or files) or swapping out a complete drive image?

It seems sometimes (with these initialization quirks) like you're re-inventing the wheel every reset rather than having a master file(s) ready to copy over to the server OR a server drive image ready on a fresh swappable drive.

You've been doing this long enough that these reset quirks should not be happening and yet they do.

[SNIPER62]

it would be interesting to see a list of steps to reset a campaign

[DOC]

You've been doing this long enough that these reset quirks should not be happening and yet they do.

You're right, but there's more to it than that. We're writing a whole new bunch of stuff into our infrastructure which will do this in an automated fashion, which has to be new because it's all (our network and server architecture) virtually new now, although some of the old remains and this is why for the time being, we have to re-invent the wheel every time we do it, because the system that should do it instead, is not completed.

Doing this with 2 contract coders and semi-literate poodle is making it a slow program because we need at least 8 full time coders and a bundle of money to do it if we were any other company, but we're not.

[DOC]

.rdp reporting (in game) should now be fixed (Campaign 106)