Corona-cation (Day 26)

Utter Confusion


Top-down game:
    So as I said yesterday, I worked on making the Plague Doctor's poison attack better. I wanted a physical poison vial of some kind that would splash an area instead of just immediately poisoning everyone in range. However, I was not able to get this done today.
    For some reason this was way harder than I thought. My initial plan was for the Plague Doctor to spawn this vial actor which would then launch itself, and upon hitting something would incur the poison effect upon any players within range. I got all the way through to the part where it would launch before I found the problem that I would spend the rest of my time on without solving. The vial wasn't showing up. It was working, I think, just not rendering. When the AI would choose the AOE attack it would spawn the actor successfully and some time later (presumably when the thing landed) the player would get poisoned but I saw nothing appear on the client or the server.
    I checked everything I knew that would prevent it from rendering the simple sphere I had as a placeholder, but none of it worked. I will try again tomorrow with renewed patience.

UE Source Compilation:
    Recently I also tried to compile the Unreal Engine from source, but I also had no success with this. I seem to be on a roll with these defeats. I patiently went through the process of re-downloading the project through git before opening VS to try to compile. I made sure I had all dependencies and .NET Frameworks that it required then compiled. 
    I watched task manager while it started up and about ten minutes in the compiler ran my computer to 100% ram usage then proceed to crash. It somehow managed to fill up whatever remaining 16GB of ram I had. On the next attempt I closed everything that wasn't needed for the compile and ran again. This time it got through the process without maxing out ram so that was good, but the thing still failed. I got "Fatal Error C1076 compiler limit : internal heap limit reached". 
    The possible fixes I found were to use a 64-bit platform toolset in VS (which I think I was) or to increase the /Zm parameter which specifies the memory costs it should plan for during compilation. I have not verified either of these yet but I really hope that at least one of them will work. 
    

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