Summer Work (Day 13)

Procedural Terrain Generation pt.2

    So yesterday I implemented the most sloppy multi-layer noise system ever created by man. I tried to stick to the tutorial as much as I could, but some things just wouldn't cooperate.
    The main thing that Unreal didn't agree with was a nested class. The basic idea behind the need for the nested class was it was to be a container for some modifiers to the noise settings. The problem was that I was unable to make an array of this class into a UPROPERTY. This is because, quite understandably, UPROPERTY's require the variable type to be derived from an unreal class, struct, or enum. But these things require special things that a nested class is unable to have (eg. GENERATED_BODY(), .generated.h). To get around this I just created another data asset that would hold the same information. The problem with this is that is adds lots of unnecessary clutter to the details panel in Unreal. I will continue looking for a fix for this, but for now it works so whatever.
    The rest of the tutorial went well with almost no hiccups. The only other major problem I found was with the layered noise that I had implemented last time. The problem was that the sublayers of noise were supposed to have a higher frequency to add more detail, but they weren't. The system was generating the same noise pattern every time, resulting in really smooth but exaggerated terrain features. I will work on changing this and possibly giving the sublayers an offset to make it feel more random from the base generated noise.

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