So far, your complaint about downloading maps is the only one in years. I tested downloading from this servers, they do not have fastdl enabled, so this is not related to it.
Warband Script Enhancer 2 (v1.1.2.7)
- Thread starter K700
- Start date
Users who are viewing this thread
Pentagathoos
Squire
Would an operation such as set_agent_weapon_speed_modifier similar to damage and movement modifiers be a difficult thing to add or fairly straight forward?
Pentagathoos
Squire
happy valentines day cos i luv u <3
Pentagathoos
Squire
Hi! 
How does all_enemies_defeated interact with slot_agent_is_running_away?
How does all_enemies_defeated interact with slot_agent_is_running_away?Questions about scripts are not in this topic. This has nothing to do with the engine, because operations don't work with slots.Hi!
Got it, thanks
Pentagathoos
Squire
I know this has been partially answered already, but do the performance warnings given when using native assets matter much? If so, has anyone shared a version of Native files with these already fixed?
Why are the map_flags giving me these warnings? Surely they aren't skinned anyway?
17:17:31 - PERFORMANCE WARNING: Mesh map_flag_f14 with material banners_f and shader tex_mul_color_mul_factor_alpha uses CPU skinning
Why are the map_flags giving me these warnings? Surely they aren't skinned anyway?
17:17:31 - PERFORMANCE WARNING: Mesh map_flag_f14 with material banners_f and shader tex_mul_color_mul_factor_alpha uses CPU skinning
Last edited:
Is there a way to make gunners and other low-accuracy ranged aim for the body rather than the head?
This won't make shots more accurate, just lower. Try agent_set_look_target_position
mesh map_flag_f14 rigged
Thank you for your continual support of WSE
Hello, WSE2 seems to mess with the fixed point multiplier in certain circumstances, or it computes distances differently.
In TLD, I created a prop that fades out agents within a certain range: https://github.com/tldmod/tldmod/bl...stem/module_mission_templates_TLD_wb.py#L4447
Players reported agents fading out even outside the specified ranges, in conjunction with using WSE.
Here's a savegame of a siege. With WSE, it's reported that agents fade out when crossing the bridge. Without WSE, it works correctly (fadeout only underneath the bridge): https://drive.google.com/open?id=1g_h7VC-uOgvA7i7rat46lg9sgWjCO-Ef&usp=drive_fs
In TLD, I created a prop that fades out agents within a certain range: https://github.com/tldmod/tldmod/bl...stem/module_mission_templates_TLD_wb.py#L4447
Players reported agents fading out even outside the specified ranges, in conjunction with using WSE.
Here's a savegame of a siege. With WSE, it's reported that agents fade out when crossing the bridge. Without WSE, it works correctly (fadeout only underneath the bridge): https://drive.google.com/open?id=1g_h7VC-uOgvA7i7rat46lg9sgWjCO-Ef&usp=drive_fs
Hello. I don't think fixed point multiplier has anything to do with it.
It's a matter of different implementations of try_for_agents.
Warband directly iterates through all agents and compares distances - what you can do yourself with scripts.
WSE and WSE2 uses the mission grid for optimized iterate between agents already placed on the grid.
This is much better in terms of performance, but the problem is that the mission grid only have x and y coordinates, not z.
Therefore, in this case it works not only under the bridge, but also on it.
I will make the optimized behavior of try_for_agents optional, but for now, as a temporary solution, you can additionally compare distance using scripts, which will still be faster than searching through all the agents on the scene.
It's a matter of different implementations of try_for_agents.
Warband directly iterates through all agents and compares distances - what you can do yourself with scripts.
WSE and WSE2 uses the mission grid for optimized iterate between agents already placed on the grid.
This is much better in terms of performance, but the problem is that the mission grid only have x and y coordinates, not z.
Therefore, in this case it works not only under the bridge, but also on it.
I will make the optimized behavior of try_for_agents optional, but for now, as a temporary solution, you can additionally compare distance using scripts, which will still be faster than searching through all the agents on the scene.
Thank you! If you like WSE2, you can support the development on Patreon or Boosty.
