Coder Diary #30 -- The Adaptive A/I

Jafele · Post by **Jafele** » Sat Jan 30, 2016 4:57 pm

They´re not going to add more changes to JTCS, probably only bug fixes and other minor issues.

Warhorse · Post by **Warhorse** » Sat Jan 30, 2016 5:14 pm

Well, Berto would have to speak further on this, as I am not the programmer, but it is not as easy as just back porting all the new changes into the older engines. ME is not just a reworked DG engine, there are a lot of changes behind the scenes that particularly because each game is different oob's etc., would be all but impossible. This is why even my Korean War game is being delayed, it will also be using our new engine, and no longer the Rising Sun engine, so ALL scenario's will need to be redone, the new platoon id format, the list goes on...

berto · Post by **berto** » Sat Jan 30, 2016 7:52 pm

ORIGINAL: carl11

I am not trying to be obtuse here, but if you're not going to back port, then the debate over at JTCS re: the unbundling, where in some have surmised there will not be updates to those games any longer ( ef,wf, rs), BUT, I believe one of you have said there will be updates to them(?), or back porting to keep them viable, even in the unbundled form; would this not be...an update worth making?

Some people would be all too happy it seems if we leave the old, bundled JTCS entirely unchanged. Done.

Would this (back porting features to the old, bundled JTCS) be an update worth making? Maybe from the players' perspectives, but not from ours. Other than as a labor of love, there is effectively zero incentive for us to continue updating the old JTCS.

A new series of unbundled Campaign Series WWII titles? Yes, we plan to go forward with that. Note that these will not be mere facelifts of the old JTCS series. Much will remain the same (game play will be essentially unchanged), but so much will be new.

Over the past several years, has our tune changed? Have we spoken in the past about "mega patch" and updating the old JTCS indefinitely into the future? Yes, we have.

But circumstances change, we come to new realizations. We now realize that the old (bundled) JTCS has no future, except on a as-is, end of the line basis. (Matrix will likely continue to sell it, much like WITP:AE did not retire WITP; Matrix continues to sell both.) The planned new CS series -- WWII (standalone EF, WF & RS) and others -- has a very bright future, however.

berto · Post by **berto** » Sat Jan 30, 2016 8:11 pm

ORIGINAL: Jafele

They´re not going to add more changes to JTCS, probably only bug fixes and other minor issues.

No. JTCS 2.02 is the end of the (bundled, legacy Series) line. No more bug fixes, no more releases. Period.

(There are plenty of older games in Matrix' lineup where bug and minor issues fixing has effectively, and absolutely, ceased.)

Legacy JTCS has had a good long run. After Matrix revived it c. 2007, it was actively supported, bug fixed, and enhanced through several update releases, culminating in 2014's JTCS 2.02. That's seven years. Time to move on.

Note: But the older JTCS bundle is not exactly abandonware. Nothing precludes the Dev Team's participating in JTCS forum discussions and answering tech support questions. You will note also that new mods and scenarios continue to be offered. But new game releases, official or unofficial? No, no more.

Any new sequel games (including the proposed new unbundled WWII ones) -- that's a different story, however. As we keep retelling.

berto · Post by **berto** » Sat Jan 30, 2016 8:19 pm

ORIGINAL: Warhorse

Well, Berto would have to speak further on this, as I am not the programmer, but it is not as easy as just back porting all the new changes into the older engines. ME is not just a reworked DG engine, there are a lot of changes behind the scenes that particularly because each game is different oob's etc., would be all but impossible. This is why even my Korean War game is being delayed, it will also be using our new engine, and no longer the Rising Sun engine, so ALL scenario's will need to be redone, the new platoon id format, the list goes on...

Warhorse has put his finger on the biggest issue: The data formats have changed, in big ways and small, so it's no easy task to back port "modern" CS improvements and new features to the older, legacy JTCS. (Not to mention the graphics overhaul in the making.) No easy task? With bundled JTCS, it would be a herculean task! Which is one reason why we plan to redo the unbundled CS WWII games over several years, one game at a time.

carll11 · Post by **carll11** » Sat Jan 30, 2016 9:58 pm

fair enough. it is what it is...thx for the explanation.

Warhorse · Post by **Warhorse** » Sat Jan 30, 2016 10:38 pm

I know it sucks, we thought long and hard about it, but this is what has to be, I think in the long run, folks are going to be thrilled, please bear with us! This is all a ways down the pike though, much to do before-hand!

Jafele · Post by **Jafele** » Sun Jan 31, 2016 3:20 am

Being realistic it´s smarter to spend time working on new games with a 21st century engine than trying to artificially rejuvenate JTCS. We all love the grandfather, sooner or later he deserved a retirement. I know it´s for the better. [;)]

Big Ivan · Post by **Big Ivan** » Sun Jan 31, 2016 7:39 am

ORIGINAL: Jafele

Being realistic it´s smarter to spend time working on new games with a 21st century engine than trying to artificially rejuvenate JTCS. We all love the grandfather, sooner or later he deserved a retirement. I know it´s for the better. [;)]

+1

Warhorse · Post by **Warhorse** » Sun Jan 31, 2016 10:39 am

Thanks for understanding, fellahs!![:)]

Coder Diary #30 -- The Adaptive A/I

RE: Coder Diary #30 -- The Adaptive A/I

RE: Coder Diary #30 -- The Adaptive A/I

RE: Coder Diary #30 -- The Adaptive A/I

RE: Coder Diary #30 -- The Adaptive A/I

RE: Coder Diary #30 -- The Adaptive A/I

RE: Coder Diary #30 -- The Adaptive A/I

RE: Coder Diary #30 -- The Adaptive A/I

RE: Coder Diary #30 -- The Adaptive A/I

RE: Coder Diary #30 -- The Adaptive A/I

RE: Coder Diary #30 -- The Adaptive A/I