• 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

Easier way then 'GetParameterElement'?

4 posts in this topic

Hi,

 

I'm trying to set float arrays to my HLSL parameter arrays.

Example:

 

The fx/effect file:

#define MaxPointLights 2

float3		PointLightPos[MaxPointLights];

In my code (C++) I achieve the expected resulted one of these 2 ways:

 

// one way

mEffect->SetFloatArray("PointLightPos[0]", myfloatarray, 3);

// another way

D3DXHANDLE param = mEffect->GetParameterElement("PointLightPos", 0);
mEffect->SetFloatArray(param, myfloatarray, 3);


Both ways work, where the 2nd is the most flexible (in the 1st one I need for hard code "PointLightPos[0]", [1] etc (or make a D3DXHANDLE adding strings etc.).

 

My question;

Is the 2nd option I do the best one, or is there a better/ easier way to set the element of a parameter in a d3dxeffect?

 

0

Share this post


Link to post
Share on other sites

The second one is better as long as you cache the handle to the parameter.  You are essentially looking up the text based name of the parameter, so if you only do that once at startup, and then set the value with the handle thereafter, then you should be doing very well from an efficiency standpoint.

0

Share this post


Link to post
Share on other sites
Thanks.
What i could do then is use one and the same handle for static lights, set to the effect once at initial setup. And for dynamic lights save all d3dxhandles in my light class. Wouldn't the needed memory for that take away the advantage?

For example, one point light would need 5 different d3dxhandles.
On the other hand the number of dynamc lights is relatively low and i could do it with a dynamic array, only created for objects of my light class, where dynamic==true.
0

Share this post


Link to post
Share on other sites

IIRC, the handle is just a single integer value that maps easily to the handle.  You won't see any negative performance effects due to the usage of the handles - back in my D3D9 engine I did the exact same thing that we are discussing and it was perfectly fine.

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