Profile of Sie_Sayoka

Avatar Area

Offline Unknown SteamID unknown
Posts: 103 | Subs: 1

General Information


Thread: Garrisoning AT guns in emplacements10 May 2022, 07:15 AM Garrisoning an AT gun within structures and other types of garrisons is possible. This post and this post within my guide covers a bit of the basics for garrisons. 1. Determine the type of markers the structure has. In most cases the "combat slot" markers will be able to hold units within the garrison. You may view these by using archive viewer and opening the .mua files with a text editor. 2. Match the ebps hold_ext and holdable_ext types. Both the garrison and the garrisoned entities need to have their types match up within these extensions. This should probably work. Note that the ABP of the garrisoned entity must have the default name, meaning you can't name it xyz.abp or something custom. Also note that the guide I linked is specifically for moving entities so you probably wont have to worry about a lot of the other things in there. This will only allow you to add an AT gun, or whatever other unit, into a garrison. It will not allow any crew to man it. I believe having a crew is possible but it's probably very difficult to do. In: Modding and Tools
Thread: (Attribute Editor) Scoped Garand as sniper+ 1 question20 Mar 2022, 22:46 PM This thread details where to find the sound files. If you know a sound that you want to use beforehand then it will be a simple process. Ensure that both the crew and action extensions do not have the crew in them. In: Modding and Tools
Thread: Wespe Creation Help Needed7 Feb 2022, 06:41 AM The flak halftrack, along with some other units, use a dummy weapon which complicates working with them. The dummy weapon is used so the unit may attack move. The stationary setup behavior for the flak halftrack is located within ebps\action_apply_ext and the weapons. If you look at the 3rd requirement_action in ebps you'll see that the enable_weapon_modifier for hardpoint_02 (its actual weapon) will be enabled if the unit is stationary. You can copy the 3rd requirement_actions to your cloned entity. The flak_ready animator_set_states can be deleted as only the flak halftrack blueprint has these states. It will probably be easier to clone the dummy flak weapon. For the actual weapon do these changes. disable_moving_firing: true non_moving_setup: true In your custom entity ensure that the dummy weapon is in hardpoint_01 and the real weapon is hardpoint_02. If your entity has other weapons you may add them after this. I believe setup and teardown are for team weapons only. This will probably work. In: Modding and Tools
Thread: Need help with AI threat perception6 Feb 2022, 19:31 PM I am stacking 5 on my HQ buildings as the AI will not attack it otherwise. I haven't tested to see if this will work with moving squads. Ai_settings\skirmish_settings\attack_importance\defensive_structure is set to 50, or 3rd highest, although these values are relative. Maybe not all of these extensions are required but most of them are. The weapon must do damage but you can set its aim time to some high number so it wont actually fire. Blueprint can be anything but is_visible_in_game must be true. Health can be invincible. Weapon_targeting can be no_targeting. Selection_type cannot be no_select. In: Modding and Tools
Thread: Need help with AI threat perception6 Feb 2022, 18:27 PM I'm also interested in learning more about AI. I believe I've found some relevant files although it would require knowledge of scar to correctly decipher them. They are all located within data.sga. data\ai\tactics.ai data\attribxml\templates\types\ai\ data\scar\systems\aimanager\ data\scar\systems\aimanager\goals\ There's so many god damn variables that its difficult to test exactly what each function does. It also seems that some functions are just broken or at least don't do what their description says. One thing that I did find helpful was using the defense_building entity type which made the AI consistently send a couple of squads to attack it. But even this is highly conditional as it requires certain extensions to work properly. In: Modding and Tools
Thread: Wespe Creation Help Needed6 Feb 2022, 04:06 AM It's recommended to learn how to use the NIS function in world builder as this will allow you to preview and test the states, variables, and actions of a blueprint. There are several reasons why simply moving a weapon from one thing may not apply correctly to another. weapon\anim_table The animation table controls what kind of animations a blueprint will use for its weapon. Most of the list is self explanatory in what its functions are. If you've use the sexton_dummy_mp anim_table you can see that most of the entries are blank whilst the su76_76mm_zis-3sh_gun_mp have them correctly filled out. weapon\fx_munition_name This is the action that will be played when the weapon hits something. weapon\projectile This is the projectile that is used by the weapon. The projectile in ebps must have the correct projectile_ext\launcher_marker otherwise the projectile will start from the 0, 0 point of the blueprint. weapon\tracking\normal This is how far and how fast the weapon can turn. You may view the extent of a weapon's tracking in world builder under the variables. Visually, a weapon may not exceed tracking degrees of its blueprint. The Sexton uses a different system than the su76. Whilst it is possible to replicate it with the su76 it's much easier to just work off of a su76 clone instead. 1. Clone weapon\soviet\ballistic_weapon\su76_76mm_zis-3sh_gun_mp 2. fx_munition_name: shell_artillery 3. Clone ebps\projectile\german_105cm_artillery_mp 4. Replace projectile_ext from su76_at_76mm_shell_mp These changes will visually have the su76 fire rounds like the lefh. If you would want the behavior to be more like that of an artillery, keep the projectile_ext and only change the launcher_marker. Weapon\tracking\normal\max_up will also have to be changed to the maximum limit the blueprint can use. Check in world builder to see what it is. In: Modding and Tools
Thread: Infantry Texture Swapping26 Jan 2022, 14:12 PM I'm unsure if these are actually texture swapping as its difficult to tell from the screenshots. They may just be clipping which also can lead to interesting combinations. They look good regardless. In: Modding and Tools
Thread: [Guide] Attaching to Moving Entities20 Jan 2022, 10:30 AM I believe that the stream has similar behavior to tracers in that it requires both origin and destination markers. This unfortunately makes it difficult to work with in this specific application. One more method that may work would be to spawn a dummy bren flamethrower on the hull MG muzzle when stationary. This will allow the dummy flamethrower to target and attack enemies while allowing the MG to do the actual killing. Possible issues would be the dummy weapon not firing at the same target and maybe some issues with tracking as well as attached entities do not update their position. In: Modding and Tools
Thread: [Guide] Attaching to Moving Entities19 Jan 2022, 21:22 PM Jump back to quoted post19 Jan 2022, 15:28 PMSneakEye Truly amazing what you achieved! Is it possible to attach that flamethrower (from the universal carrier I assume) to the hull mg of the Sherman and T34 with a working killcounter and veterancy? And have you experienced any impact on the performance with some many attached entities? Thanks! Having a tank with the bren flamethrower on its hull MG that has both the kill counters and veterancy of the tank is possible. If you're content with it having just the flamethrower muzzle fx and not the flame stream. `model = { "..\\..\\..\\common\\vehicles\\crew\\pintle_lmg_seated\\pintle_lmg_seated", "..\\..\\..\\Common\\base\\basemotion\\basemotion", }` Create an ABP. The above is assuming you're making it in a normal folder location. Create the entity and have it attach to the hull MG muzzle marker. Create another entity of the flamethrower and make it have both an attacking action and a delay to make_dead. Create the weapon based off the hull MG. With on_fire_action have it create the make_dead enitty. This system is similar to the one I've used for some of my own units. The make_dead action is required as on_fire_action doesn't undo spawned entities when the firing is finished. If you want the flamethrower to have a stream as well unfortunately I don't think it's possible. You could try adding the flamethrower directly to the tank's ABP but the stream will start from the ground level. In regards to lag, there's a split-second freeze in the game as soon as the unit spawns in. The duration of the freeze corresponds to how many entities the unit has. However, this only happens for the first unit of its type and subsequent units wont cause this. Overall impact on performance is negligible if you only account for the unit itself. The effects generated from its idle animation (tons of animator_actions) as well its attacks are much more performance heavy. In: Modding and Tools
Thread: [Guide] Attaching to Moving Entities19 Jan 2022, 14:59 PM Additional Attachment Examples The following units use all types of attaching systems previously discussed in the guide. In: Modding and Tools