Page MenuHomeFeedback Tracker

Official Capture and Hold scenario CAH_Castle is broken (JIP Error)
Closed, ResolvedPublic

Description

Starting it on a dedicated Server will bring up this error:

Details

Severity
None
Resolution
Open
Reproducibility
N/A
Operating System
Windows 11 x64
Category
General
Steps To Reproduce
  • start dedicated server with {F1A1BEA67132113E}Missions/CAH_Castle.conf
  • look at the JIP Error

Event Timeline

This happened after the update to 1.3

Geez closed this task as a duplicate of T188480: Offset Harbour Block.Apr 14 2025, 12:32 PM
Geez reopened this task as Awaiting internal Testing.
nielu added a subscriber: nielu.EditedApr 14 2025, 3:53 PM

I can confirm, I'm having the same errors. I am reusing prop work from this scenario in my own gamemode, it was working fine until version 1.3.0.125

Client log is full of error similar to these:

13:35:58.379 RPL          : rpl::Pip::ProcessNetToGame
13:35:58.379  RPL       (E): IReplication::JIPError: Inconsistent item table on Slave connection. Item is missing or different item was loaded in its place. (item=0x40032BBC layout=DamageManagerComponent)
13:35:58.379  RPL       (E):    Expected:
13:35:58.379  RPL       (E):      cpp_layout=_RegionalDestructionManager_Layout
13:35:58.379  RPL       (E):      s_layout=script::Game::SCR_RegionalDestructionManager
13:35:58.379  RPL       (E): IReplication::JIPError: Inconsistent item table on Slave connection. Item is missing or different item was loaded in its place. (item=0x40032BBE layout=ScriptComponent)
13:35:58.379  RPL       (E):    Expected:
13:35:58.379  RPL       (E):      cpp_layout=_DamageManagerComponent_Layout
13:35:58.379  RPL       (E):      s_layout=script::Game::SCR_DestructionMultiPhaseComponent
13:35:58.379  RPL       (E): IReplication::JIPError: Inconsistent item table on Slave connection. Item is missing or different item was loaded in its place. (item=0x40032BBF layout=FactionAffiliationComponent)
13:35:58.379  RPL       (E):    Expected:
13:35:58.379  RPL       (E):      cpp_layout=_RplComponent_Layout
13:35:58.379  RPL       (E):      s_layout=script::Game::RplComponent
13:35:58.379  RPL       (E): IReplication::JIPError: Inconsistent item table on Slave connection. Item is missing or different item was loaded in its place. (item=0x40032BC0 layout=ScriptComponent)
13:35:58.379  RPL       (E):    Expected:
13:35:58.379  RPL       (E):      cpp_layout=_ScriptComponent_Layout
13:35:58.379  RPL       (E):      s_layout=script::Game::SCR_ArsenalComponent
13:35:58.379  RPL       (E): IReplication::JIPError: Inconsistent item table on Slave connection. Item is missing or different item was loaded in its place. (item=0x40032BC1 layout=ScriptComponent)
13:35:58.379  RPL       (E):    Expected:
13:35:58.379  RPL       (E):      cpp_layout=_FactionAffiliationComponent_Layout
13:35:58.379  RPL       (E):      s_layout=script::Game::SCR_FactionAffiliationComponent

I don’t understand how this is related to the other ticket and why it got merged. Could you pls explain?

R34P3R added a subscriber: R34P3R.Apr 17 2025, 12:40 PM

we also see such issue on our servers, there should be one Prefab missing Rpl. Also, since the Update, some Composition Prefabs like Military Tents or Barbedwire roll have duplicated Hierarchy and RplComp. I had to disable the duplicated Components to make itr work again.

Geez changed the task status from Awaiting internal Testing to Confirmed Internally.Apr 23 2025, 1:12 PM
Geez closed this task as Resolved.Tue, Jun 3, 10:25 AM
Geez claimed this task.

I still don’t understand how this is related to the other ticket and why it got merged. Could you pls explain?
I am also working in support and see the need to handle a lot of tickets etc but some information / communication would be appreciated.

Geez added a comment.EditedTue, Jun 3, 1:59 PM

I still don’t understand how this is related to the other ticket and why it got merged. Could you pls explain?
I am also working in support and see the need to handle a lot of tickets etc but some information / communication would be appreciated.

Hello, that was a mistake merge, it does not relate to the other ticket at all. As you can notice it was immediately reopened after the accidental duplicate closure