Bugs and fixes

Created lørdag 08 februar 2025

mining nodes

Created mandag 13 januar 2025

DROPBE4R har Crestfallen: Medieval Survival 21. dec. 2024 kl. 12:26
https://steamcommunity.com/app/2293680/discussions/0/601891362926764065/

Bugs and possible solutions - mining nodes and combat

I have been playing this over a few days, and noticed some glaring issues, especially with resource nodes. Combat has similar issues.

I have noticed a few different types of problem such as:
The node not updating when struck. It should reduce in size but does not.
Lagging through/into the node and "falling" through the mesh.
Rubber banding in combat - especially noticeable with large targets like the dragons (similar to above problem with nodes)
In some cases its as though the node is not there at all, pick passes right through it.
These same issues do not seem to happen with tree nodes.

Here are some possible causes and suggestions for these bugs:

buggy mineable nodes in the UE5 game could be caused by a variety of factors. These issues — where nodes are sometimes useless, don't react to mining, still give resources without diminishing in size, or cause lag and rubber-banding — suggest problems related to network synchronization, physics, or gameplay logic. Here's a breakdown of potential causes and solutions:

Physics and Collision Issues

Improper Collision Settings: If the collision shape for the nodes is not set up correctly or doesn't match the visual mesh, mining interactions may not trigger properly. For example, the mining tool might not register a collision or trigger area, leading to inconsistent behaviors like the node not reacting when mined.

Solution: Verify that the collision settings on the node mesh are correct and that the node has a proper collision box or sphere that matches the expected mining area. Consider using simple collision shapes like spheres or boxes to simplify the interaction.

Physics Not Updating: If the node's physics are not set to simulate or update properly when it’s mined (like shrinking or breaking apart), the node may appear as though it’s not responding, even though it still provides resources.

Solution:
Ensure that when a node is mined, it correctly updates its physics properties. If the node shrinks, ensure that the proper scaling or destruction logic is being triggered in sync with the resource output.

Network Synchronization / Replication Issues

Lag and Rubber Banding: If the game is multiplayer or has a server-client setup, lag or rubber-banding issues might arise due to poor network synchronization. This can cause players to experience the node as though it's not interacting with them properly, as it may not update or sync correctly across all clients.

Solution:
Check the node’s network replication settings. Make sure that when a node is mined, the event is properly replicated across the network. For instance, when the node's health or state changes, this should be reflected in all clients. Using RepNotify functions and ensuring the server controls the state can help with synchronization.

Animation or Material Handling Issues

Incorrect Animation Triggers: If the node uses an animation (e.g., shrinking or breaking apart) when mined, the animation might not trigger properly, leading to a scenario where it still provides resources but doesn’t visually change. The resource logic might be separate from the visual effects, causing an inconsistency.

Solution: Ensure that the mining action triggers the animation correctly. This can be done by checking if the animation is tied to the correct event, like the node being mined, and that the logic for diminishing the node in size or destroying it is working properly.

Material or Mesh Issues: The material applied to the node may not update properly, causing the visual feedback of the node's state to remain static, even though resources are still given. Sometimes, materials are not set up to dynamically change based on state (like reducing transparency or fading out as the node is mined).

Solution: Verify that the materials or meshes change appropriately when the node is mined. You may need to implement a dynamic material instance that reflects changes in the node’s health or mined state.

Gameplay Logic or Script Issues

Resource Logic Not Tied to Node State: The logic that gives resources when the node is mined might be handled separately from the logic that updates the node’s state (shrinking, breaking, etc.). If these systems aren’t synchronized properly, it can result in inconsistent behaviors where the node still gives resources even if it hasn’t visually changed.

Solution: Check the script or blueprint that handles the mining and resource-giving logic. Make sure the resource is only granted when the node’s state has appropriately changed (e.g., node health reaches zero or a destruction animation is triggered).

Mismatched Update Frequency: In cases where nodes are processed on a timer or in chunks (e.g., periodic updates for health or state changes), the update frequency might not match the player’s mining speed, causing issues with node behavior and resource delivery.

Solution: Use more responsive updates based on real-time events rather than periodic updates. Consider using event-driven triggers for state changes and resource delivery.

Performance Issues (Low FPS or Heavy Resource Load)

Lag or Rubberbanding: If the game is running on low frame rates or has performance bottlenecks, players may experience rubberbanding or delays in interactions. This could cause nodes to behave oddly or not update their state in time with the mining action.

Solution: Optimize the performance of the mining mechanics, especially if there are heavy resource loads when many nodes are active at once. Lower the complexity of the node's meshes and animations, or reduce the number of nodes in active areas. Test and profile the game for performance bottlenecks.

Unreal Engine 5 Specific Issues

UE5-specific Bugs: Sometimes, issues like these can stem from bugs or engine-specific behaviors, such as problems with the new Chaos physics engine or how the engine handles dynamic object interactions in large or complex worlds.

Solution: Ensure you’re using the latest stable version of UE5, as engine bugs are often patched in newer releases. You may also need to experiment with different physics or network settings (e.g., changing the collision handling, physics updates per tick, etc.).

Conclusion

To troubleshoot this issue, you should start by checking:

The physics and collision settings of the nodes.
The network replication settings, especially in multiplayer scenarios.
The animation and material updates when nodes are mined.
The mining logic in your scripts or blueprints.
Performance profiling to ensure frame rates are adequate.

By systematically reviewing these areas, you should be able to narrow down the cause and resolve the issues with the mineable nodes in your game.