• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
cozzie

'Continue' statement usage?

7 posts in this topic

Hi,

 

A probably fairly simple question, but I seem to have usef the c++ 'continue' statement incorrect.

What I do is the following (pseudo code)

 

for(materials=0;materials<nrMaterials++materials)

{

    for(meshes=0;mesh<nrMeshes;++meshes)

    {

        if(materials[material].index[meshes].uses = false) continue;

        // otherwise do thing with this mesh

    }

}

 

What I try to achieve is that 'continue' stops the iteration for meshes[m] and goes to the next iteration in this for loop, meshes[m+1].

From debugging it looks like it's not doing that.

 

Any ideas/ suggestions on what I might be doing wrong?

 

0

Share this post


Link to post
Share on other sites
= should be ==? or is that just an error in your post?

Maybe you should post the full code i cant see anything wrong with the current one apart from the syntax errors... Edited by Waterlimon
1

Share this post


Link to post
Share on other sites
The problem here is that you are using = instead of == (unless this was a typo), so that materials[material].index[meshes].uses = false will actually evaluate to the expression on the right-hand side of the equals sign. This means that the if statement's condition will never evaluate as true and so the continue statement won't be executed.
2

Share this post


Link to post
Share on other sites

cozzie, on 28 Jan 2013 - 12:50, said:
for(materials=0;materials<nrMaterials++materials)

The for condition is invalid AFAIK.

cozzie, on 28 Jan 2013 - 12:50, said:
for(meshes=0;mesh<nrMeshes;++meshes)

There's no mesh mentioned earlier in your pseudocode.

cozzie, on 28 Jan 2013 - 12:50, said:
if(materials[material].index[meshes].uses = false) continue;

The = is an assignment, not an equality operator
There's no material mentioned earlier in your pseudocode.
materials is not an array

Please, even when posting pseudocode, be consistent.
We cannot see what the problem is if you obscure it in typos.
Also, when it's a small snippet of code which has flow errors, it's probably better just to post the code. Edited by SuperVGA
2

Share this post


Link to post
Share on other sites

Thanks, I'll check the real code to see if the '=' is OK in the real code.

Maybe it's also a good idea to do what nightcreature mentioned (also more readable).

0

Share this post


Link to post
Share on other sites

++ for NightCreature's post: don't test a boolean against true or false, just test the boolean. The boolean itself *is* true or false. If your bool variables are named sensibly the code is more readable without the comparison. Use the 'not' operator to test for false, i.e. if (!something.isDead()) ...

0

Share this post


Link to post
Share on other sites

Got it, it was not the continue statements causing all the unneccesary state changes, but me running the same function for blended mesh instances going through each effect, material and mesh.

 

The real code was/ is:

 

			for(mat=0;mat<mRenderQueue.mNrMaterials;++mat)
			{
				if(!mRenderQueue.MatUsesEffect(fx, mat)) continue;
				if(!pD3dscene->PreSelectMaterial(mat, fx)) return false;							// 2x SetFloatArray, 1x SetTexture									   							
				for(m=0;m<mRenderQueue.mMaterialData[mat].nrMeshes;++m)		
				{
					mesh = mRenderQueue.mMaterialData[mat].meshIds[m];
					if(!mRenderQueue.MeshUsesEffect(fx, mesh)) continue;
					if(!pD3dscene->mMeshes[mesh].SetBuffers(mD3ddev)) return false;					// 1x SetStreamSource, 1x SetIndices

I might change the 'continue' style by making it more readble

 

if(......)

{

    do stuff

}

 

instead of if(!...) continue;

 

Now off the fix my indices for going through blended mesh instances.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0