Bon livre, bien structuré, avec des exemples de code fournis. Je le recommande.

It, s so hard to install the software, it took me 2-3 weeks to install the softwares like SFML, and also hard to understand, the game physics and concept to hard..

the link supplied both in the digital version and the hard copy have a bad link and can't find the images online...Update: You can however use the git link to download the samples and all the art assets are in each example

* By the end of the book, you will have programmed three graphical applications in C++ for the Windows operating system.* The programming language is C++11, compiled using the Visual Studio IDE for Windows.* The book was not written for multiple platforms, but the code does not make heavy use of Windows specific functionality, so it should work with a few minor adjustments.* The applications are simple games with limited functionality. This book focuses on the graphics and rendering, not the gameplay.* Each of the three applications are built upon a different graphics library: SFML, OpenGL, Vulkan.BEGINNERS BEWARE* I would recommend this book to advanced C++ programmers.* People with no knowledge of programming will struggle with this book. Read a beginner's guide book first.* Chapter 1 (C++ Concepts) is a good refresher, and may be suitable for beginner C++ programmers.* The majority of the book is advanced. I do not recommend this for beginner programmers, and it will probably go over the heads of intermediate programmers. To be a C++ developer, you need to know your stuff.MY SUCCESS WITH THIS BOOK* I (the reviewer) was able to follow this book and achieve all the results that the author achieved, with difficulty.* Here's my computer specs: * Windows 10.0.18362.0 * NVIDIA GeForce RTX 2070 Super * AMD Ryzen 7 3700X* Here's the tools I used: * Visual Studio Community 2019 version 16.8.4 * CMake 3.19.4 * Vulkan SDK 1.2.141.2 * and the C++ libraries mentioned in the book (URLs are included in the book).* I built the SFML game in x86 (32-bit) configuration, and I built the OpenGL and Vulkan games in x64 configuration.THE NITTY GRITTY* Important parts of the book require you to build third party libraries using CMake. The author expects you to know how, and assumes the libraries are already built. The libraries I had the most trouble with were for the OpenGL section: * Bullet (physics library) * Freetype* Throughout the book, the blocks of code have many minor spelling errors, which means that you cannot assume that the code is correct. If you copy and paste it, you need to fix the errors. I suppose this is to help you avoid plagiarizing. The overall architecture and program logic is correct, but there are a few parts of the program that are missing. Because of the format in which they sent me this book to review, I did not have access to the accompanying code repository of the final project files, but I managed to guess and fill in the blanks (and copy one or two bits from other tutorials).* The Vulkan section is the hardest and longest to produce a meaningful outcome (because Vulkan always takes long). One difference between this book and the online Vulkan Tutorial is that this book separates the logic into classes and methods, instead of one monolithic class of functions.* The author includes a constructor and destructor for every class, but they do nothing, so you should in fact remove the empty constructors and destructors from the headers and cpp files because they are not being used for proper RAII. The author's approach for lifetime semantics is member functions (e.g. init() and destroy()).* Because the author uses raw pointers (new and delete), it might be worth it to `=delete` the copy and move constructors and assignment operators, to avoid lifetime issues.* Unlike the author, I always group my includes in a specific order to prevent most issues. * #include <std-library-header> * #include <third-party-library-header> * #include "header-in-this-project" * #include "accompanying-header-of-this-cpp-file"* Instead of writing #define in the source code to configure headers, I add them as preprocessor definitions in the Project Properties. ( GLFW_INCLUDE_VULKAN;GLM_FORCE_RADIANS;GLM_FORCE_DEPTH_ZERO_TO_ONE ). This avoids the possibility of the header being compiled in a different file without the definition.* The author was not concerned about the safety of class invariants. Some member variables are public when they should be private. For a toy project such as this, it doesn't matter.CONCLUSIONThis is a book for intermediate-to-advanced C++ programmers looking for a challenge, willing to learn how to program graphical applications for Windows.

The general concepts in the book are solid. The problem are the mistakes, both grammatical and coding. There are examples that are supposed to return a particular result but do not work in the real world. There are basic C++ concepts explained in the start that have fundamental flaws and mistakes that would result in code that either won't compile or won't run the way the book explains. These aren't complicated examples, they are basics on how classes in C++ works, namespaces and how they are used, and the list goes on from there. The publisher's website lists no errata at all for the book. If someone would have taken the time to double-check the code and grammar, this book would be a solid four stars.