Getting a weird warning when I compile this. Can't make sense of it, any ideas?

\main.cpp(321): warning C4239: nonstandard extension used: 'argument': conversion from 'matrix' to 'matrix &'\main.cpp(321): note: A non-const reference may only be bound to an lvalue

Line 321 for reference:
constants->Transform = rotateX * rotateY * rotateZ * scale * translate;

Thanks again for sharing this.

are you compiling with/W4? try/W3. alternatively, change both occurrences of

matrix operator*(matrix& m1, matrix& m2)

to

matrix operator*(const matrix& m1, const matrix& m2)

Thanks a million, both of those solutions silence the warning.

If you add#pragma comment(lib, "user32") it compiles for me by just typingcl code.cpp (Visual studio 2019, cl version 19.27.29112). Thanks for sharing the code!

If you add#pragma comment(lib, "user32") it compiles for me by just typingcl code.cpp (Visual studio 2019, cl version 19.27.29112). Thanks for sharing the code!

done :)

I get the following errors when I try to run this code, I am not sure what I'm missing.

..\directxhello.cpp(31): error C2065: 'wndClassEx': undeclared identifier
..\directxhello.cpp(32): error C2065: 'wndClassEx': undeclared identifier
..\directxhello.cpp(33): error C2065: 'wndClassEx': undeclared identifier
..\directxhello.cpp(35): error C2065: 'wndClassEx': undeclared identifier
..\directxhello.cpp(297): error C2678: binary '*': no operator found which takes a left-hand operand of type 'matrix' (or there is no acceptable conversion)
..\directxhello.cpp(25): note: could be 'matrix operator *(matrix &,matrix &)'

Is that all the errors the compiler gives? Try changing thematrix operator*() to take const arguments like d7samurai says above (23 May 2019)

Thanks a lot! That fixes the error in line 25, and 297. The first set of errors in line 33, and 35 still stand, I just started learning about windows api so I am not sure what these errors indicate.

Changing wndClassEx to wndClassExA in lines 33-35 fixed that error for me.

i have now updated the code to statematrix operator*(const matrix& m1, const matrix& m2) in both relevant places to avoid people having to manually do that (i.e. add theconsts) in the future. it's just that i never useconst myself, so i hesitated to make my original version "impure" in that way ;) ..

i also changedWNDCLASSEX toWNDCLASSEXA on line 31 (the type, not the variable namewndClassEx, as i don't see why that would matter).

Sure, makes sense :D

The program runs smoothly in Visual Studio but when I launch the compiled .exe (debug or release makes no difference) nothing happens, how comes? Do you have any tips for me? Thank you.
EDIT: I also tried with "Minimal D3D11 pt2", same thing happened. I'm very puzzled.

@boios check the .hlsl file path - L"shaders.hlsl", try to change it to something like - L"D:\Shaders\LineShader.hlsl"; where D:\Shaders\ is a file path to .hlsl source file. It this is not it, try to debug and come back :)

The program runs smoothly in Visual Studio but when I launch the compiled .exe (debug or release makes no difference) nothing happens, how comes? Do you have any tips for me? Thank you. EDIT: I also tried with "Minimal D3D11 pt2", same thing happened. I'm very puzzled.

like@CptBishop89 said, it's most likely due to the program not finding the shaders.hlsl file. an easy fix is to copy shaders.hlsl to the same folder as the .exe (edit: in a recent update, shaders.hlsl got renamed to gpu.hlsl. same thing applies)

Thanks for making this. Question: Why set theWS_POPUP window flag?

Thanks for making this. Question: Why set theWS_POPUP window flag?

just an easy way to get rid of title bar / window chrome

Thanks for this great snippet, this really helped me get up to speed! :-)
One strange thing, though: when I run the program, then close it, the window disappears but the process keeps running with 100% GPU utilization, according to the Task Manager.
Addingdevice->Release() at the end of theWinmain fixes this issue for me.

when I run the program, then close it, the window disappears but the process keeps running with 100% GPU utilization

how are you closing the window?

when I run the program, then close it, the window disappears but the process keeps running with 100% GPU utilization

how are you closing the window?

Not at all :-)
I just copied your code as is. Maybe a call toCloseWindow might also help, but as I said,device->Release() after the main loop will fix the issue for me.

when I run the program, then close it, the window disappears but the process keeps running with 100% GPU utilization

how are you closing the app, i mean. if you close it by pressing a key, then it should end the process normally. it's a minimal example intended to showcase the d3d11 aspect with as little tangential code as possible so it cuts corners on the surrounding app framework.

Oh right, I see. I used Alt+F4, you are right. Thanks!

You might still want to add that oneRelease line, it fixes the issue and may point people to not forget the clean-up code in their real app.

... may point people to not forget the clean-up code in their real app.

you never need to manually clean up / release any resources when exiting an app - that is handled by the operating system (and faster).

the issue in this case is that alt-f4 doesn't exit the process becauseWM_DESTROY isn't handled. and it isn't handled because it would require a customWindowProc (in the name of minimalism i simply supply the baselineDefWindowProc), which in turn means adding another function and extra clutter to the code.

device->Release() after the main loop will fix the issue for me.

device->Release() shouldn't have any bearing on the problem (unless causing the app to crash, thus ending the process).

so i'm not sure what's going on for you there, as nothing after the main loop will ever get executed. the only exit condition is onWM_KEYDOWN and that exits the process altogether.

Oh yeah, you are right, I did not notice there was no custom window proc. I am glad I know now, thanks for pointing it out! :-)