• 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
lomateron

one variable for an intance

6 posts in this topic

The title is wrong, This is what i relly want, i have this in hlsl code

 

Texture2D Texture;

....

....

 

is there a way to take this Tex2Da.Load( uint3(0,0,0))

and Tex2Da.Load( uint3(1,0,0))

and Tex2Da.Load( uint3(2,0,0))

and transform it into a global effect vector variable so i don't have to Load() them every vertex shader or pixel shader.

Edited by lomateron
0

Share this post


Link to post
Share on other sites

I improved 1 original post question

How is that, i will like to see an example, code

the three texels are already on a 

 

Texture2D Tex2Da;

 

And I load them in the vertex shader but 64*1000*3 Load()s is too much, i want to know if there is a way to load them just onetime, and pass the 3 values to all the pixel shaders or vertex shaders that will run on all the intances.

If there could be something like that, for a complete drawIntanced()

Edited by lomateron
0

Share this post


Link to post
Share on other sites

I'm not 100% sure if I understand it correct, but it looks like you're doing it in the technique (function) itself.

Where do you use the l1, l2 and l3 variables in the effect/shader?

 

My 1st thought would be that you use them for each processed vertex or pixel, and that those 3 lines would be in your VS or PS function.

0

Share this post


Link to post
Share on other sites

read first post again

 

yes they are inside the vertex shader and passed to the pixel shader (the code that i showed is incorrect, but i want to know if there is something like that )

 

There are less vertices than pixels so its better to have the load() in the vertex shader and then pass them to the pixel shader

Edited by lomateron
0

Share this post


Link to post
Share on other sites

I think what you're asking is:

 

When rendering your frame, you render some data to a texture. Then you want to use this texture data in subsequent runs of a vertex shader (the same three texture samples for all runs of the vertex shader). Normally this would make sense to be a shader constant; but in your case it can't be because the data was generated on the GPU earlier in that frame and is never pulled back to the CPU. So you're basically searching for a way to use this data in your vertex shader, without having every vertex shader run have to take the 3 samples.

 

Is that correct?

 

 

I don't know of a way to do that, but:

1) Could you instead calculate this data on the CPU? Or do the calculations that go into those 3 pixels of interest in your texture come from something that has to be done on the GPU? Or,

2) Could you put up with a delay of a couple of frames, allowing you to pull this data back to the CPU when it's available and then set it as a shader constant?

 

 

Also, is doing the 3 samples in every VS run an actual a performance problem, or an imagined one?

0

Share this post


Link to post
Share on other sites

The 3 texels are inside a texture that indicates the position of spheres, the position changes in complex ways and the change is done inside the GPU.

I take those 3 or more spheres and transform into points of lights. Then when rendering the many spheres I need the 3 or more points of light positions to calculate how the other spheres shine.

The 3 Load() are very costly as the number of spheres increases, 3 Load() for every vertice of the many spheres i render (its better than for every pixel, in average there are more pixels than vertices)

Edited by lomateron
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