Corona-cation (Day 2)

Git Commit: None


    Today I made a realization; I still don't understand some fundamental ideas of networking in UE4.

    I started out the day with little direction as the designers haven't updated any of the design documents or given me a task to work on after our meeting on monday. This turned out to be a blessing in disguise as it meant I found a huge bug with the core of the game. So since I don't necessarily have a deadline to meet I decided I would try to implement the reviving system I thought about yesterday. I started this out by making sure the healing from the cleric worked so that later I could use that as a reliable point of gaining health in case something went wrong with the new system. 
    But as I tested the heal aura I found it wasn't doing anything. I checked the blueprint and didn't see any logical error so I went to the output log to dig up errors or warnings. And indeed I found some. The first one that directly told me what was happening was: Warning: UNetDriver::ProcessRemoteFunction: No owning connection for actor BP_FPChar_Sharpshooter_C_0. Function ServerHeal will not be processed. Simple enough, I thought. Just do a quick google search to find all the other hundreds of people who have also come across this and job done. But not this time. Every answer seemed to point in a different direction, many telling me do things that I already had done. Things like not replicating the player controller, setting the owner of the character etc. I went back to the project to see if anything else was going wrong and I found another warning hidden at the time when the clients joined the game. Warning: OSS: No game present to join for session (GameSession)
    I went through the same routine and nothing that I knew of came up. There was lots of technical jargon I had never heard before like RPCs (although in reality I had been using them without knowing). I tried to do research on all this and implement it into the game but I have have had no luck yet. I will continue on this tomorrow and I hope to have it fixed before Friday. Or maybe it will magically fix itself just like it broke :)

Comments

Post a Comment

Popular posts from this blog

Polishing the Foundation

Image
     This sprint was relatively uneventful; mainly cleaning up the existing foundational elements of the game (the first person character and spell component) and continuing to improve the necessary elements of the game like the pause screen. Player Character & Spells      The improvements to the player character come in two parts; the ability to have, use, and change spells, as well as interaction via an interface. Both of theses are as simple as I could make them. Utilizing inheritance from USpellBase using the spells is only really a single line, and changing out the spells we can use the NewObject factory to make a new spell very simply. FirstPersonCharacter.h FirstPersonCharacter.cpp      As for the interaction interface, it only consists of two functions right now, one to fire an interaction event and one to check if the object can be interacted with. This second function is used mainly to show UI on the player's screen like...
Read more

Progress Update #13

Image
  Niagara Asteroids in UE4     These past few days I have continued work on asteroids. Only that now I have ditched instanced static meshes in favor of getting my hands on the new-ish Niagara particle system.  Learning Niagara     I have decided that since this is an entirely new subsystem of the engine I would do everything in blueprint first, then transition everything to C++ when I knew it was working reliably. Additionally, because Niagara is still relatively new, the official documentation is sparse if existent at all. So with most tutorials at this time geared towards blueprint implementation, starting in blueprint will give me the highest likelihood of finding a solution to any problems I may come across. The Niagara Workflow     The first thing I learned about Niagara is that the workflow has changed significantly from what cascade was. Where in cascade (to my limited knowledge) you worked in one particle system where e...
Read more

A New Chapter

Image
     This week has presented the biggest change probably since the release of Mini Solar System; I was offered a full-time position as a junior programmer at Studio 369 which I was happy to accept. I start on Monday and I couldn't be more excited to work with the team there! However, this did mean though that my priorities shifted quite instantaneously. I went from working full-time on "RPG_Game" to preparing for this new job. This mainly meant getting up to speed on networking as that is the one area of Unreal Engine I feel I have a lack of knowledge in (I'm already proficient in UI, AI, gameplay, materials, and general backend work), and since 369's specialty is networking I figured I would come prepared. I did do a little work on "RPG_Game" but it was minimal just to tie up some loose ends. Unreal's Multiplayer Framework      As explained by the Unreal Engine documentation, "multiplayer programming [is] inherently more complex than programmin...
Read more