[0.4.8.62~88] Emergency Bug: xray_resource__modelName causes the transport vehicle template to be unable to combine with the tank template

Game Mods
1

Since the test version partition in forum is hidden, I can only post another record here

empty value of xray_resource__modelName causes the transport vehicle template to be unable to combine with the tank template

test cases

entity{
  _template:t="base_ab_41+opel_blitz_kfz_305+paratrooper_plane_camera"
}

entity{
  _template:t="respawnChooser+respVehicle"

  "respbase__addTemplatesOnSpawn:list<t>"{
    item:t="vehicle_spawn_validation"
    item:t="vehicle_spawn_restriction"
    item:t="base_tgdgb_m40_lv"
    item:t="gmc_353_a"
    item:t="paratrooper_plane_camera"
    item:t="vehicle_display_marker_over_head"
    item:t="soft_ground_collision"
    item:t="destroyOnDamageWithoutCrew"
  }
}

These cases works fine in the just previous version.

And they are broken in version just updated today.

This ruins the functionality of the mobile rally truck I just made few days ago…

Solusion for official developer. (Since we players can’t fix this)

add a default value of xray_resource__modelName for base_damage_model.

example.

base_damage_model{
  //
  xray_resource__modelName:t="t_26_1940"
}

Another similar solusion is to provide an additional template to patch this value. There is no need to modify the basic template value.

this may be more appropriate

also need developer to add such template

xray_resource_model_default{
   xray_resource__modelName:t="t_26_1940"
}
2 Likes
2

Ouch
That’s unfortunate.

4

@106054965 @Enginya @QA_meerosch

Don’t lose this issue.

It just came out and now is the best time to fix it. The weekend is coming soon, which will affect whether we can play with friends on the weekend.

5

Did you try to swap A+B to B+A? Will be sufficient to add new template with xray_resource__modelName set to some default, so you can add +C where C is this new template?

2 Likes
6

Yes, Thx for reply.

vehicle+tank (have to manually edit the scene.blk)
image

tank+vehicle
missing resource.

test case for this issue

entity{
  _template:t="respawnChooser+respVehicle"

  "respbase__addTemplatesOnSpawn:list<t>"{
    item:t="vehicle_spawn_validation"
    item:t="vehicle_spawn_restriction"
    item:t="base_tgdgb_m40_lv"
    item:t="gmc_353_a"
    item:t="paratrooper_plane_camera"
    item:t="vehicle_display_marker_over_head"
    item:t="soft_ground_collision"
    item:t="destroyOnDamageWithoutCrew"
  }
}

they would works in local games after I set the default value of xray_resource__modelName in entities.blk.

I can also fix a single entity in scene.blk.

But I couldn’t fix the entities generated by the multiplayer game, so it’s currently not possible to spawn these vehicles from the multiplayer game.

I have diff compared the official blk between the last version and current version.

I notice that dev have added an empty xray_resource__modelName:t=“” value to base_damage_model in the latest big version update, which I believe is the reason change cause the problem.

Solution 1

To fix it, simple way is to add a default value for xray_resource__modelName to base_damage_model


base_damage_model{
  //
  xray_resource__modelName:t="t_26_1940"
}

Solution 1.1

Another potentially less influential approach is to define a default placehold value for this xray_resource__modelName property in the civil_vehicle_templ instead of base_damage_model.


civil_vehicle_templ{
  //
  xray_resource__modelName:t="t_26_1940"
}

Solution 2

define a new template (C) to patch this value

xray_resource_model_patch_default{
   xray_resource__modelName:t="t_26_1940"
}

But the new template defined by the ugm currently doesn’t be synchronized to the client yet, and xray_resource__modelName is not a replicated synchronized attribute. So I can’t change its value by entites.blk

then we players cant fix this for multiplayer game…

these solutions ,only dev can do this for now

not yet fix in tiny version .73, waiting for next patch :disappointed_relieved:

not yet fix in tiny version .75, waiting for next patch :disappointed_relieved:

seems not yet fix in tiny version .81, waiting for next patch :disappointed_relieved:

3 Likes