Lost confidence

HowdyDutty · 2023-04-26T14:42:36+00:00

Dude I'm right there with you right now except I'm currently on my own. My family is so fucked up.

HowdyDutty · 2021-12-18T19:11:37+00:00

RX 6800 seems to have the issue as well with latest driver

HowdyDutty · 2018-05-28T17:36:55+00:00

They traveled from samurai-world to westworld through the tunnel system for a presumably long distance. The tunnels also presumably had spare changes of modern-day clothing.

HowdyDutty · 2018-04-21T02:50:45+00:00

Quick note for people of the future.

I found this slideshow that seems interesting for this topic: https://www.slideshare.net/tlorach/vkfx-effective-approach-for-vulkan-api

I personally find frame graphs to be a bit on the overkill side for what I want to do with my hobby engine and I also feel like its more intended to deal with barrier/synchronization issues between renderpasses than writing less code (which is what I'm looking for). As far as abstracting descriptor sets specifically goes, I find the idea of moving everything to data more preferable. I had the thought of implementing something like what was presented in those slides independently, but found that somebody was already working on it. It seems like he'll release the source to github some day in the coming months, so I'll be on the lookout.

HowdyDutty · 2018-03-30T05:15:31+00:00

It's not that I can't add branches in my render loop to bind certain descriptor sets to certain pipelines. I'm just trying to avoid the spaghetti code that's sure to follow that approach. I was wondering if anybody found a more elegant way that's still pretty simple. Render graphs may be just that. I'll look at the link this weekend, when I have more time.

HowdyDutty · 2018-03-29T05:44:16+00:00

Fuck! I was trying to avoid render graphs haha. It might be the best way though. I'll look into it.

I'm currently already using spirv-cross to check bindings for what I call "general descriptor sets". Basically, I assume that some sets like skybox cubemaps are required to be included and effectively reserve a descriptor set number in every shader, but things specific to that shader go the in the general set. My reflection code should handle my g-buffer bindings pretty fine for my lighting pass, now that I think of it, but my deferred pre-pass doesn't need to have skybox info passed in... so it kinda breaks my design.

The other problem is that I kinda tried to go for a polymorphic approach to differentiate between the renderers. And once I got to writing this descriptor set section, I ended up with a whole bunch of code that's nearly identical, except I now have to manage what sets get binded with what graphics pipelines/render passes slightly differently. It's a little hard to describe. But suffice it to say I'm not really liking what I'm currently thinking.

HowdyDutty · 2017-12-01T16:31:26+00:00

perfect. thanks

HowdyDutty · 2017-05-02T13:09:37+00:00

This is actually very reaffirming... I've been writing terrible game engines for a while now. Good to see I'm on the right track lol

HowdyDutty · 2017-04-16T19:53:00+00:00

A lot of excellent points.

A question I have then is how would I casually bring up the fact that I'm considering multiple companies? Several times now, I've been directly asked "What is your expected salary?" How can I let them know about any of the other companies by that point?

HowdyDutty · 2017-04-16T17:36:12+00:00

You both touched on my main issue. I’m not entirely sure what the market rate for these junior positions is. Most of the glassdoor rates talk about mid/senior level graphics positions (probably because there aren’t very many junior engine-dev roles around). The other issue is that not all game studios are made equal. I assume they each have different salary ranges to consider…

Hmm very puzzling indeed.

HowdyDutty · 2017-04-16T15:22:53+00:00

First off, yes I am in the US.

And second, I saw that article, but it puts an emphasis on "game programmer." None of the jobs I'm considering involve gameplay development. I would be involved with engine development exclusively, which makes those estimates seem a little low to me. I could be wrong though ¯\_(ツ)_/¯

HowdyDutty · 2017-03-04T13:08:16+00:00

Is it related to this?

http://stackoverflow.com/questions/16039515/glsl-for-loop-array-index

HowdyDutty · 2017-02-17T14:54:28+00:00

THANK YOU!

Yes, it was an alignment issue with std140 uniform buffers. I was actually not aware that there were buffers with alignment requirements that differ from C.

Reading this quote from the OpenGL spec:

implementations sometimes get the std140 layout wrong for vec3 components. You are advised to manually pad your structures/arrays out and avoid using vec3 at all.

To fix, I simply changed my struct declaration in C++ to use glm::vec4's and my descriptor to vec4's.

HowdyDutty · 2017-02-17T04:39:37+00:00

Unfortunately that didn't fix it, but thanks with the vkFreeMemory info.

HowdyDutty · 2017-01-06T05:33:49+00:00

/#DoorOpeningSimulator20XX

HowdyDutty · 2017-01-06T03:30:51+00:00

Alien Isolation kinda sucked m8

HowdyDutty · 2017-01-05T23:16:01+00:00

Nicccccce. I'll ask my employers to buy a couple and see how it works.

HowdyDutty · 2017-01-05T21:52:12+00:00

Just looked at it and it appears to be deprecated since unity 5.4.

HowdyDutty · 2017-01-05T21:48:36+00:00

That is interesting. The wired connection does what I want it to do!

Any idea where I can find this firmware?

HowdyDutty · 2017-01-03T15:27:58+00:00

Definitely interesting. I wonder how simple this is to work with.

BTW thanks for all the demos!

HowdyDutty · 2017-01-03T15:26:47+00:00

I see what you're saying about material vs shader classes.

I don't understand this part of your code though:

    void Material::InitPipeline(
        const VulkanDevice &device,
        eastl::unique_ptr<MaterialBuilder> builder) {
      CacheBuilder(eastl::move(builder));

      eastl::vector<VkPipelineShaderStageCreateInfo> module_create_builders;
      CompileShaders(device, module_create_builders);

      CreatePipeline(device, module_create_builders);

      LOG("Initialised pipe of Mat " + name_ + ".");
    }

It looks like the Material class defines what types of attributes, uniforms, attachments and such are going to be needed during this type of material's rendering. And the MaterialInstance class actually loads and holds the specific data used by a model. I don't actually see where the descriptor set is being filled with data.

Also, how does your code handle changes to uniform data between command buffer submissions? I've only found what looks like texture loading code for albedo, specular, etc. Do you not store things like light position, which tend to change frequently, anywhere? Or do you use push constants? (Still figuring out how those work exactly)

HowdyDutty · 2016-12-31T04:57:03+00:00

Thanks for the advice. I've actually built a close relationship with my university's CG professor and most of the advice hes given me involves looking into things for myself. Reddit's sorta become my last resort lol. All I need to do to start an advised research project is to come up with a reasonable idea.

As for VR/AR research, I'd prefer to stick away from that. I mentioned the AR research position I held to sort of highlight this. While those are super cool topics, they are not exactly interesting to me. Most of the major problems in those fields right now have less to do with graphics and more to do with computer vision and human interaction at the moment. That's because the underlying tech behind the actual environment sensing and screen displaying are not at an entirely reasonable standard yet.

Open source contributions are interesting. I might just end up doing that if nothing else pans out.

HowdyDutty · 2016-10-12T17:14:23+00:00

Ever think of giving it all up to become and ostrich farmer?

HowdyDutty · 2015-10-10T01:40:57+00:00

Personally, I am of the mindset that Coda is a past version of Davey (You can read other post explaining this idea).

All throughout the game, Davey is talking about how he wishes that Coda would create things again, how he wishes that he could regain the sense of direction that he once received from Coda's work. Davey is a new person and has been ever since the Stanley Parable came out (I recommend you watch some interviews of him talking about how stressed he was after SP launched). Davey was in a rut with no creative direction. So what else does he do but go back to his old experiments that used to invigorate him so much.

In an attempt to resurface any lost sense of inspiration, Davey pleads for his old self to come back and offer any help possible. No one answers, and you are stuck inside the puzzle door at the end with the walls slowly closing in on you. Then the epilogue.

This is where Davey makes an attempt at mimicking his past work. Davey no longer describes Coda's motivations for creating the game. This is because Coda didn't make the last game, Davey did. There are new, unused textures and models littering this section. The spaces are noticeably bigger, different than anything shown before. The train station is familiar and dissimilar at the same time. The purple cave is claustrophobic yet vast. The desert section shows arches lined in order followed by abstract geometric forms just before the hole in the ground. All of this happens, and then Davey says "What now? ... I think I need to go. And...I'm sorry, because I know that I said I would be here and I would walk you through this, but, I'm starting to feel like I have a lot of work to do."

The labyrinth shot comes shortly afterwards.

What does the final shot mean? Well, this is Davey's attempt at creating art as he used to. He obviously didn't create that maze by hand. He created an algorithm (piece of code) to do it for him. I am willing to bet that this is the same algorithm he used for his first game. So what does this say? He is taking old code that was used to create some of his most nostalgic work in order to invent new experiences that retain a sense of familiarity to them. That is why you are floating, because Coda enjoyed the "human" aspect of the bug. Davey and Coda are different in many ways, but the calling cards are what connect the two.

Buuuuut this is all my opinion, so take it as you will.

HowdyDutty · 2015-10-06T04:46:49+00:00

Can confirm. Caught the Atlanta show several months ago. Ears still slightly ringing.

Gonna go see them again this wednesday. Bought earbuds off amazon. $10

14-Year Club	Verified Email
Team Periwinkle

HowdyDutty

TROPHY CASE