Matrix Games Forums

Bill.... (or others).... Since the upgrade, I have had inconsistent defensive fire from artillery. Since I have had some 5,000 turns in SC games, I know how the artillery on auto (or silent) has been working for years.... but it is not now!

I first noticed it when Russian artillery in Prussia did not defend against attacks from Germans. I thought that maybe I had put on save... but that was not the case. anyway, i made sure it was on auto and made the rest of my moves. Once again it did not fire, when my opponent attacked on his next move.

UK artillery in middle east has been returning fire. UK artillery in France HAS NOT... THIS HAS CAUSED GERMANS TO OVERRUN THE FRONT, THEN ATTACK THE ARTILLERY....(Which sometimes doesn't even defend itself!!) .... this has already caused Brits and French to lose several artillery pieces.... completely changing the game.

French artillery sometimes has fired... sometimes not. It most recently has not defensively fired to help defend Italians.
It has also failed to support forts in France.
.... This change has completely messed up a good game that I have (had) going with long-time opponent. He has no explanation, either.... although he has been mostly on the attack, so he has not had the same effect.
.... just to make clear... In verifying that I am not crazy... I made sure that ALL my artillery was set on auto... all with lots of shells... all with HQ attachments.... and pretty much results (or lack of) was the same as described above.
Gary (gamerdude)

Thanks, we will investigate.

Interesting. In the new 1.16.00 patch game, a quick play-testing of my previously modded 1.15.00 version of 1914 Call to Arms had artillery seemingly working with defensive fire as expected.

When playing with the 1.16.00 default 1914 Call to Arms, I have noticed in the same play-testing conditions as before, that artillery does not work with defensive fire as it should. But this is not systematic, mind, only occasionally. Hmmm…

By the way, I should point out that the 1.16.00 version of default 1914 Call to Arms has an error at startup: Text/EN/resources requires lines #848 St. Petersburg and #849 Weij. Easily edited so no problem, just needs correction for the next hotfix or patch.

CaesarAug wrote: Wed Sep 24, 2025 2:25 pm

By the way, I should point out that the 1.16.00 version of default 1914 Call to Arms has an error at startup: Text/EN/resources requires lines #848 St. Petersburg and #849 Weij. Easily edited so no problem, just needs correction for the next hotfix or patch.

I'm not getting such errors, nor would I understand why they would be created as no map changes like that have been made. Have the text files been modded your side at all?

The artillery bug has been identified and fixed, so will be corrected in the next update (hopefully soon, but I cannot be more specific).

BillRunacre wrote: Wed Sep 24, 2025 9:12 pm

CaesarAug wrote: Wed Sep 24, 2025 2:25 pm

By the way, I should point out that the 1.16.00 version of default 1914 Call to Arms has an error at startup: Text/EN/resources requires lines #848 St. Petersburg and #849 Weij. Easily edited so no problem, just needs correction for the next hotfix or patch.

I'm not getting such errors, nor would I understand why they would be created as no map changes like that have been made. Have the text files been modded your side at all?

How odd. Yes, I was getting that error message. The game continued to start up so it wasn’t altogether game-breaking.

Yes, I added those two lines and the error message disappeared.

good you found the bug!! ... glad I brought it to your attention! ... and good job by CaesarAug to confirm..... but please make a patch asap as anyone playing the game will like be greatly impacted....

....and many of us love the game, btw!!

gamerdude
(Gary)

CaesarAug wrote: Wed Sep 24, 2025 9:59 pm
How odd. Yes, I was getting that error message. The game continued to start up so it wasn’t altogether game-breaking.

Yes, I added those two lines and the error message disappeared.

Yes, those messages are annoying rather than game breaking.

However, St. Petersburg doesn't exist in the map (it's Petrograd instead) and I don't know where Weij might be.

That neither exist in my developer's version, nor am I getting such messages is very odd indeed.

Is anyone else experiencing this with the latest patch when starting a new game of 1914 Call to Arms?

Ah, correction Bill! I'm sorry for this heads up. I've tried starting up a 1.16.00 game-default 1914 Call to Arms, and no such error message comes up.

I have just realised that it was my own modded version of the same scenario where I had changed Petrograd to St. Petersburg and added the settlement of Weij in Arabia, boardering the Red Sea, in hex 218,133. When I ported over the newer 1.16.00 1914 scenario to adapt it, the resources text needed those lines put in again.

So sorry for the mix-up and for occupying your valuable time in finding and correcting real bugs!
My humble apologies!

BillRunacre wrote: Thu Sep 25, 2025 7:48 am

CaesarAug wrote: Wed Sep 24, 2025 9:59 pm
How odd. Yes, I was getting that error message. The game continued to start up so it wasn’t altogether game-breaking.

Yes, I added those two lines and the error message disappeared.

Yes, those messages are annoying rather than game breaking.

However, St. Petersburg doesn't exist in the map (it's Petrograd instead) and I don't know where Weij might be.

That neither exist in my developer's version, nor am I getting such messages is very odd indeed.

Is anyone else experiencing this with the latest patch when starting a new game of 1914 Call to Arms?

Weij is on the Arabian Red Sea coast and a town that I asked mdsmall incorporate in his Icarus Mod a few years ago, as it was a base that Lawrence of Arabia used. It's a critical location in the redesign of the Arabian Revolt incorporated in the mod.

How on earth could it get mixed up with the vanilla campaign?

OldCrowBalthazor wrote: Thu Sep 25, 2025 8:34 am

BillRunacre wrote: Thu Sep 25, 2025 7:48 am

CaesarAug wrote: Wed Sep 24, 2025 9:59 pm
How odd. Yes, I was getting that error message. The game continued to start up so it wasn’t altogether game-breaking.

Yes, I added those two lines and the error message disappeared.

Yes, those messages are annoying rather than game breaking.

However, St. Petersburg doesn't exist in the map (it's Petrograd instead) and I don't know where Weij might be.

That neither exist in my developer's version, nor am I getting such messages is very odd indeed.

Is anyone else experiencing this with the latest patch when starting a new game of 1914 Call to Arms?

Weij is on the Arabian Red Sea coast and a town that I asked mdsmall incorporate in his Icarus Mod a few years ago, as it was a base that Lawrence of Arabia used. It's a critical location in the redesign of the Arabian Revolt incorporated in the mod.

How on earth could it get mixed up with the vanilla campaign?

Ah, you see, it was never mixed up with the vanilla campaign! You may not have read my earlier post: the error came up only on my end in a newly ported over 1.16.00 1914 scenario that was being adapted to the new patch and needed those two lines to be added again.

CaesarAug wrote: Thu Sep 25, 2025 8:03 am Ah, correction Bill! I'm sorry for this heads up. I've tried starting up a 1.16.00 game-default 1914 Call to Arms, and no such error message comes up.

I have just realised that it was my own modded version of the same scenario where I had changed Petrograd to St. Petersburg and added the settlement of Weij in Arabia, boardering the Red Sea, in hex 218,133. When I ported over the newer 1.16.00 1914 scenario to adapt it, the resources text needed those lines put in again.

So sorry for the mix-up and for occupying your valuable time in finding and correcting real bugs!
My humble apologies!

That is a relief, as that did have me rather confused!

CaesarAug wrote: Thu Sep 25, 2025 10:00 am

OldCrowBalthazor wrote: Thu Sep 25, 2025 8:34 am

BillRunacre wrote: Thu Sep 25, 2025 7:48 am

Yes, those messages are annoying rather than game breaking.

However, St. Petersburg doesn't exist in the map (it's Petrograd instead) and I don't know where Weij might be.

That neither exist in my developer's version, nor am I getting such messages is very odd indeed.

Is anyone else experiencing this with the latest patch when starting a new game of 1914 Call to Arms?

Weij is on the Arabian Red Sea coast and a town that I asked mdsmall incorporate in his Icarus Mod a few years ago, as it was a base that Lawrence of Arabia used. It's a critical location in the redesign of the Arabian Revolt incorporated in the mod.

How on earth could it get mixed up with the vanilla campaign?

Ah, you see, it was never mixed up with the vanilla campaign! You may not have read my earlier post: the error came up only on my end in a newly ported over 1.16.00 1914 scenario that was being adapted to the new patch and needed those two lines to be added again.

Funny. I was just speed reading this thread and saw 'Weij'. No one has ever heard of it unless your real familiar with the Arab Revolt or read Seven Pillars of Wisdom by T.E. Lawrence.
When mdsmall and I were talking in the early stages on how to implement a 3 stage Arab Revolt mechanicism, I though of Weij and asked mdsmall if it would be possible to place the town up the coast north of Yanbo. That's the place Lawrence and the Arabs took by marching north along the coast in the initial stage of the Revolt before heading into the Hejaz interior to start breaking rail lines and contacting more tribes to rise up against the Ottomans (Stage 2).

So anyways seeing an obscure name like Weij made me jump.