1.5M ratings
277k ratings

See, that’s what the app is perfect for.

Sounds perfect Wahhhh, I don’t wanna
icetigris

8 of 365

icetigris

I added some debug logging code because if you have windowed application (i.e. not a console application), standard debug output just gets sent to a black hole. Because I need to be able to print rude words to the console for debugging, I’m used to UE4′s UE_LOG() API, and I needed to pick out a short prefix for my engine stuff, I went with MEGALOG(). It’s basically the same as std::cout(), but I can make it do more stuff as needed.

I used this to hook up the very first real input:

In action:

Whenever I hit any key, it will print a string to the console. Also im 12.

an Icetigris original daily gamedev daily gamedev 2018

More you might like

icetigris

77 of 365

icetigris

The triangle “bumps” around right now. That’s because I’m doing the barest minimum level of input handling possible.

I’m not making a distinction between KEYUP and KEYDOWN (or any) events at the moment cause I just wanted something vaguely working. Another weird side effect of this is that any other event stops the triangle moving. That means if I move the mouse or hit any other button. I think the reason the triangle KEEPS moving unless I trigger another event is because the last KEYUP event with an arrow key that gets caught keeps that key code, so the corresponding if statement is always true. 

The idea is to have the triangle move while a given key is down, like you would expect in a typical 2D game, so that’s one of the next things I’ll do.

an Icetigris original daily gamedev daily gamedev 2018 programming
icetigris

81 of 365

icetigris

I made kind of a small/wip change, but one that gives me a lot to talk about. When enumerating DXGI adapters (i.e. asking DirectX what GPUs we got on this system; I’m using EnumAdapterByGpuPreference()), I started making a temporary/fake/throwaway ID3D12Device so I can look at how many nodes it has. 

Basically what this means is I can see if I’m running a linked device adapter (LDA) (aka SLI/Crossfire) config or not.

So, I can ask DirectX for logical adapters, then I look at each logical adapter and see how many physical adapters it contains. For example, if I have a machine with 2 Geforce 970s in an SLI setup, I’ll get 1 DXGIAdapter back from DirectX, but if I make an ID3D12Device from that adapter and call GetNodeCount() on it (using D3D12CreateDevice()), it will tell me I have 2 nodes, i.e. 2 real actual physical GPUs.

an Icetigris original daily gamedev daily gamedev 2018 programming
icetigris

83 of 365

icetigris

It’s later, so now I’m gonna tell you about my bitfiddling intrinsics utility header. I knew about intrinsics before now but I’d never had to really write anything with them directly. Now I Understand. As usual, Microsoft is off doing its own thing and then there’s GCC and clang. I’m thinking I might use clang later because its code generation and speed are a lot better, but who tf knows when I’ll do that.

Also TIL apparently Intel processors didn’t have a leading zero count (LZCNT) instruction until Haswell???? Also no popcnt until Nehalem, which was just before Sandy Bridge are you shitting me???????

an Icetigris original daily gamedev daily gamedev 2018 programming
See this in the app Show more