Search results for query: *

Dictionary<CharacterAttribute, TextObject> dictionary1 = new Dictionary<CharacterAttribute, TextObject>()
{
{
DefaultCharacterAttributes.Vigor,
new TextObject("{=h7aX2GOw}This child is quite strong, grabbing whatever {?CHILD.GENDER}she{?}he{\\?} likes climbing out of {?CHILD.GENDER}her{?}his{\\?} cradle whenever {?CHILD.GENDER}her{?}his{\\?} caretaker's back is turned.")
},
{
DefaultCharacterAttributes.Control,
new TextObject("{=pQSBdHC7}The child has exceptional coordination for someone {?CHILD.GENDER}her{?}his{\\?} age, and can catch a tossed ball and eat by {?CHILD.GENDER}herself{?}himself{\\?}.")
},
{
DefaultCharacterAttributes.Endurance,
new TextObject("{=xaNpQsjh}The child seems to never tire, running {?CHILD.GENDER}her{?}his{\\?} caretakers ragged, and is rarely cranky.")
},
{
DefaultCharacterAttributes.Cunning,
new TextObject("{=lF41sN5r}You see the glint of mischief on {?CHILD.GENDER}her{?}his{\\?} smiling face. Any sweet left unattended in the kitchen for even a few minutes is quickly stolen.")
},
{
DefaultCharacterAttributes.Intelligence,
new TextObject("{=KVDMVbT1}This child started speaking earlier than most of {?CHILD.GENDER}her{?}his{\\?} peers and can even string together simple sentences.")
},
{
DefaultCharacterAttributes.Social,
new TextObject("{=xXJnW5w0}The child pays close attention to anyone talking to {?CHILD.GENDER}her{?}him{\\?} and sometimes tries to comfort playmates in distress.")
}
};

Click to expand...

Dictionary<CharacterAttribute, TextObject> dictionary1 = Attributes.All.Select(x =>
new KeyValuePair<CharacterAttribute, TextObject>(x, x.EducationDescription))
.ToDictionary(key => key.Key, value => value.Value);

Click to expand...

Dejan said:

There's a behaviour called MissionCombatantsLogic. This is the mission behaviour that sets up the teams and sets mission type to siege battle. Mission.IsSiegeBattle is set only after the execution of this code section. So if you haven't included this behaviour in your modded mission or if you haven't written your own, then IsSiegeBattle won't be set. For the campaign side, you can check MapEvent.IsSiegeAssault.

Click to expand...

MArdA TaleWorlds said:

What is your games overall graphics settings? Could you set it to maximum and see if the issue still happening?

Click to expand...

bfoo75 said:

@Cephas, As annoying as it is to see things like this, I wouldn't call this a game breaking bug. It is a visual annoyance, but likely doesn't have any effect on your ability to play the game - such as a crash, softlock, or logic bug would.

Click to expand...

CaptainFracas said:

This bug is in the game since the 1.9.0. It's urgent to fix it as smithing is allmost unusable since the release as it is.

Click to expand...

SupaNinjaMan said:

If you want to adjust the prop to the ground normal, the best method I have found is to use a weird quirk of the cast_ray operation.

cast_ray casts a ray from a position (Y+ forward) until it collides with the ground or a prop, and then stores that collision position into a pos# register with the rotation storing the collided face's normal y+ outward. So something like:

Python:

(set_fixed_point_multiplier, 100), # This sets the units to centimeters
(init_position, pos11), # clear all data on pos10 register, we want this for the (0,0,0) rotational data.
(position_copy_origin, pos11, pos12), # pos12 is on the terrain you want to place the prop, this will give us the position while leaving the rotation (0, 0, 0)
(position_move_z, pos11, 100, 1), # move on the global z axis 100 cm, 1 m
(position_rotate_x, pos11, 90), # pitches the positional register forward to face the ground.
(cast_ray, reg0, pos10, pos11, 150), # this will cast a ray from pos11 150cm and store the collision in pos10, now that it is successful, pos10 should now be a duplicate of pos12 with the terrain normal! Reg0 is unused, but would store a prop_instance_id in the event of hitting a prop.
(copy_position_origin, pos10, pos12), # but I am a cautious man.
(position_rotate_x, pos10, 90), # you'll need to rotate the register 90 degrees again since props are typically +Z out instead of the +Y out that cast_ray returns. I am not sure this rotation is correct
(set_spawn_position, pos10), # now spawn the prop!

You'll want to do this before spawning the prop as to keep the ray from colliding with the prop.

Also, I did this on my phone so check the rotations are correct and that the cast_ray operation variables are all in the correct order.

Click to expand...

Veledentella said:

The game has been finished in development since 2016. The engine is from the 2000s and has been finished in development since then.

Click to expand...