• 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

Creating worldmatrix for renderables

1 post in this topic

Hi,

I'm moving from rendering whole mesh instances to renderables (submeshes of the mesh instance).

While doing this I can't figure out what's wrong with my world matrices of the renderables.

 

Here's a part of the code I use:

bool CD3dmeshInst::SetupBVWorldSpace(const CD3dmesh &pMesh)
{
	// resize vectors for renderables
	mRenderables.resize(pMesh.mSubMeshSize);

	TVERTEX *verticesPointer;
	TVERTEX *vertices = new TVERTEX[pMesh.mMesh->GetNumVertices()];

	pMesh.mVtxBuffer->Lock(0, 0, (void**)&verticesPointer, D3DLOCK_READONLY);		// ,0 = default
	memcpy(vertices, verticesPointer, pMesh.mMesh->GetNumVertices()*D3DXGetDeclVertexSize(vtxdecl, 0)); 
	pMesh.mVtxBuffer->Unlock();
	// VERTICES ARE NOT SCALED/ROTATED/TRANSLATED, AND ARE IN MODEL SPACE

	// CREATE BOUNDING VOLUMES (SPHERE & AABB) FOR FULL MESH, MODEL SPACE
	if(!SUCCEEDED(D3DXComputeBoundingSphere(&vertices[0].position, pMesh.mMesh->GetNumVertices(), D3DXGetDeclVertexSize(vtxdecl, 0), &mSphereCenterModelspace, &mSphereBoundingRadiusBase))) return false;	
	CreateAABB(vertices, 0, pMesh.mMesh->GetNumVertices(), &mBoundingBox);

	// CREATE BOUNDING VOLUMES (SPHERE & AABB) FOR RENDERABLES, MODEL SPACE
	for(size_t obj=0;obj<GetNrRenderables();++obj)
	{
		D3DXVECTOR3 sphereCenterModelspace;
		float sphereBoundingRadiusBase;
		if(!SUCCEEDED(D3DXComputeBoundingSphere(&vertices[pMesh.mSubMeshTable[obj].VertexStart].position, (DWORD)pMesh.mSubMeshTable[obj].VertexCount, D3DXGetDeclVertexSize(vtxdecl, 0), 
												&sphereCenterModelspace, &sphereBoundingRadiusBase))) return false; 
		
		mRenderables[obj].SetupBoundingSphere(sphereCenterModelspace, sphereBoundingRadiusBase);

		Crealysm_dxmath::BOUNDINGBOX bBox;
		CreateAABB(vertices, pMesh.mSubMeshTable[obj].VertexStart, pMesh.mSubMeshTable[obj].VertexCount, &bBox);

		mRenderables[obj].SetBoundingBox(bBox);
	}
	delete[] vertices;

	// CREATE WORLD MATRIX AND TRANFORM BOUNDING VOLUMES TO WORLDSPACE (SPHERE, AABB/OBB): FULL MESH
	CreateWorldMatrix(); 

	mSphereBoundingRadius = mSphereBoundingRadiusBase * mScale;

	for(int i=0;i<8;++i) D3DXVec3TransformCoord(&mBoundingBox.OBBcorners[i], &mBoundingBox.AABBcorners[i], &mMatWorld);
	UpdateAABBWorld(&mBoundingBox);

	D3DXVec3TransformCoord(&mBoundingBox.OBBcenter, &mBoundingBox.AABBcenter, &mMatWorld);
	mBoundingBox.OBBsize = mBoundingBox.AABBsize;

	// RENDERABLES: SETUP (i.e. CREATE WORLD MATRIX + BOUNDING VOLUMES TO WORLDSPACE)
	for(size_t obj=0;obj<GetNrRenderables();++obj)
	{
		mRenderables[obj].SetWorldPosParent(mWorldPos);			// mesh instance's world pos
		mRenderables[obj].SetRotParent(mRot);					// uses mesh instance's rotation as base
		
		mRenderables[obj].SetScale(mScale);
		mRenderables[obj].SetDynamic(mDynamic);					// for now all renderables take over mDynamic from the mesh instance!!

		if(!mRenderables[obj].Setup()) return false;
	}
	return true;
}


// setting up the renderable

bool CD3drenderable::Setup()
{
	if(mScale == 0.0f) return false;
	if(!mBoundingBox.created) return false;
	
	mWorldPos = mWorldPosParent + mSphereCenterModelspace;

	CreateWorldMatrix();

	mSphereBoundingRadius = mSphereBoundingRadiusBase * mScale;

	for(int i=0;i<8;++i) D3DXVec3TransformCoord(&mBoundingBox.OBBcorners[i], &mBoundingBox.AABBcorners[i], &mMatWorld);
	UpdateAABBWorld(&mBoundingBox);

	D3DXVec3TransformCoord(&mBoundingBox.OBBcenter, &mBoundingBox.AABBcenter, &mMatWorld);
	mBoundingBox.OBBsize = mBoundingBox.AABBsize;

	mAffectedLightIds.reserve(10);
	return true;
}

The result is this, there's a distance between the individual renderables:

 

renderable_nok.jpg

 

 

When I make the worldspace position of the renderables the same as the world pos of the whole instance, the result looks as expected. But that doesn't match up the theory and doesn't give me correct results for light culling, because the world position is then used to check the distance to point lights, which gives incorrect large distances for renderables that are far away from the center of the complete mesh instance.

//	mWorldPos = mWorldPosParent + mSphereCenterModelspace;
	mWorldPos = mWorldPosParent;

This is the result with this 'hack':

 

renderable_ok.jpg

 

 

My preliminary conclusion is that somehow the renderables vertices are handled like they are based around the origin of the whole mesh instance instead of their own origin (world matrix).

 

Any idea what's I'm not seeing?

0

Share this post


Link to post
Share on other sites

I've been thinking about it and think I've made a fundemental mistake. Even it the above approach would work it wouldn't give much flexibility.

Should te approach be:

 

- mesh instance has it's own world matrix

- renderable has it's separate own matrix, with all offsets in relation to the parent

(i.e. worldpos = difference of center of the renderable to worldpos of mesh instance and in my case 0 rot and scale 1.0)

- the rendable class should have 2 functions for returning it's matrix: 1 = local, 2 = local multiplied * parent

- that way I don't have to save relations on transformations just multiply the parent with renderable matrix if something changes

 

What do you think?

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