Summer Work (Day 3)

Slow Progress


    Continuing on the "tutorial", I tried today to get the function calls working so that I could get the planets moving. I decided to do this in the gamemode. Basically I needed two functions to be called on tick that would update the velocity and position of all planets.
    The first challenge was getting a gamemode at all. When I first started trying to create a new gamemode, the editor would crash every other compile. I realized that there were some updated made to the source code, so I downloaded and built that. Immediately after that the editor was crashing every compile. I spent some time trying to debug this but eventually it managed to fix itself and I haven't had a crash since then. I created a CelestialGameMode and a blueprint child. The next challenge was to get a variable for the gravitational constant that all planets could access to calculate the force that should be applied to them. It took me some messing around but I got it working. This process also made me learn the casting syntax for C++. 
    After that, it was on to the functions. This is what stumped me. The first thing I had to do was get all planets in the scene; a simple task in blueprint. It turns out it was much harder than I thought. For whatever reason I could not make an array of type CelestialBody. No matter what I did it wouldn't compile. It kept giving me the error: "'ACelestialBody': undeclared identifier". I even #included the Celestial body script and still no change. As soon as I figure this out though I think it will be easy (but that's what I thought before this so who knows).

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