Replication Issues

 Author: Jacob McLain

Posted: 2/1/24

Problem: When running multiple clients that connect to each other, some will conduct actions that aren't replicated on the others. Specifically, the host client shoots bullets that get replicated on the others while the rest of the clients are unable to provide any changes to the host or other clients. After research, the problem boils down to the ownership of the weapon used to shoot. The weapon that possessed the ability to create the bullets was created primarily in the scene of the host client. Due to this, the weapon was owned by the server but we were trying to access it from a client.

Solution: I have two major paths that I'm pursuing in order to fix the issue. The first doesn't require too much upheaval of the systems. The gist is that instead of transferring the actual gun to the each client, we create a copy of it that is owned by the client. That way, it belongs to the client and is therefore allowed to create the bullets on the server side as opposed to just the client side. The only problem is the method, which I'm working towards putting together.

The second solution being to rewrite the entire shooting system. Right now, it's based on the gun the player's holding. The gun has the ammo, damage, bullet type, model, etc. This solution would take all of that and put that instead in the player. This would result in a mass migration of functionality moving to the player. I would most likely create a separate component that would accept the functionality so that I don't block others from editing the player. Either way, this would result in all the shooting belonging to the player, which belongs to the client that controls it.

Comments

Post a Comment

Popular posts from this blog

Procedural Generation - Room NavMesh Spawning

Image
 Author: Najee Jackson Problem When generating rooms, enemies didn't spawn, so the player just walked around in an empty level. To fix this, I wanted to create a spawner in each room of a certain size, but the spawner only worked in areas with valid nav meshes. My level had none in it since it was procedurally generated, which resulted in the spawner not spawning enemies, and if it did, enemies would not move since they couldn't find a valid NavMesh. Solution To fix this, I wanted to spawn a Navmesh Bounds Volume whenever a room was created, but I soon learned that you couldn't spawn NavMesh Bounds in Unreal Engine 5. After learning this, I searched for ways to spawn a nav mesh in a procedurally generated map. I wanted to avoid creating a giant Nav Mesh encompassing the entire map. Since I feared that the spawner would spawn enemies far away from the player, it also would be a waste of processing power to have an active nav mesh in areas that enemies never use. One way that...
Read more

Powerups and Wall clipping

Image
  Author: Colyn Reed Problem          For this week, I continued working on having a working map for the player to navigate and explore. On this map, I added powerups for the player to pick up. The power ups I added was the Health boost powerup which gives the player more max health and a speed boost powerup which gives the player more max speed. Along with the powerups, I added wall clipping so that the player doesn't get lost behind any walls. Solution     Getting the players max health to change was the first issue I ran into. I had to create a whole new event inside the health component that changes the max health of the player instead of changing the current health of the player. The speed boost powerup was easier to manage except that its hard to notice at first when you pick it up, but once you get it stacked its noticeable. For the wall clipping, I had to create a whole new material for the walls and the hardest part with that was get...
Read more