Planet Chili

The original issue you were having means that the pixels were trying to be drawn beyond the Graphics::ScreenWidth boundary ( >= 800 ). This issue means that the pixels are trying to be drawn beyond the left side of the window ( < 0 ). You'll have to determine where the failure is in your logic. If t...

I have had this error or something similar, though I don't recall what the root cause was. However, more than likely the issue is writing past the end of an array or to some invalid memory area. You'll have to debug the program a bit to find where the issue lies, if you have problems finding it, sha...

Here's the problem I believe: if (x + 5 >= gfx.ScreenWidth) { x = gfx.ScreenWidth - 6; } if (x - 5 <= gfx.ScreenWidth) { x = gfx.ScreenWidth + 6; } Assuming Graphics::ScreenWidth is 800 If x + 5 is greater than or equal to 800, then x equals 794 if x - 5 is less than or equal to 800, then equals 806...

Shouldn't be a problem because once you build the project, the *.shh files will be built by Visual Studio using the *.hlsl files. Until you build the project, you will get the error that those files do not exist.

There are two modes of use for the mouse and keyboard. One is state and one is event driven. If you use if( mouse.LeftIsPressed() ) then for however many frames you hold the left mouse button down, this function returns true. If you want a single button press event, you must use mouse.Read() to get ...

There a funky one in the final project for Intermediate. It seems like box2d crew went and make a breaking change to the code, and it screws up the collision at the boundaries of the field. the boxes fly out and trigger an out-of-screen putpixel exception. At least, this is my surmise. I haven't cl...

I know this is a little late, but it seems like in one case you are trying to open the solution/project without actually extracting the ZIP file to a folder. The second part of the errors happen if you try opening the same solution more than once say from two instances of VS. If this is the case, ex...

With the 2016 tutorial series, I've really only come across one common issue and that's in the FartAnnoyed tutorials. In this series, chili initializes a RectF structure by calling one constructor from another. The common issue among first time watchers is missing the placement of the call, see belo...

This is a very common issue. The issue is in your two Rect constructors where you are trying to call other Rect constructors. What you have: Rect( const Vec2 topLeft, const Vec2 bottomRight ) { Rect( topLeft.x, topLeft.y, bottomRight.x, bottomRight.y ); } When it should be: Rect( const Vec2 topLeft,...