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

Getting a weird shader error: error X3018: invalid subscript 'xyz'

4 posts in this topic

I get [b]error X3018: invalid subscript 'xyz' [/b]when I try to compile my vertex shader.Here is my shader code:

[CODE]
cbuffer PerFrameConstants : register(b0)
{
float4x4 worldViewProjectionMatrix;
float4x4 worldViewMatrix;
float4x4 viewProjectionMatrix;
float4x4 projectionMatrix;
float4 cameraNearFar;
uint4 framebufferDimensions;
float tessellationFactor;
float3 padding;
};

struct GeometryVSIn
{
float3 position : position;
float3 normal : normal;
float2 texCoord : texCoord;
float3 instancePosition : instancePosition;
float3 instanceRotation : instanceRotation;
};
struct GeometryVSOut
{
float4 position : SV_Position;
float3 positionView : positionView;
float3 normal : normal;
float2 texCoord : texCoord;
};


float4x4 RotateV2M(float3 rotation)
{
float4x4 rotateX = { 1.0f, 0.0f, 0.0f, 0.0f,
0.0f, cos(rotation.x), -sin(rotation.x), 0.0f,
0.0f, sin(rotation.x), cos(rotation.x), 0.0f,
0.0f, 0.0f, 0.0f, 1.0f };
float4x4 rotateY = { cos(rotation.y), 0.0, sin(rotation.y), 0.0f,
0.0f, 1.0f, 0.0f, 0.0f,
-sin(rotation.y), 0.0, cos(rotation.y), 0.0f,
0.0f, 0.0f, 0.0f, 1.0f };
float4x4 rotateZ = { cos(rotation.z), -sin(rotation.z), 0.0f, 0.0f,
sin(rotation.z), cos(rotation.z), 0.0f, 0.0f,
0.0f, 0.0f, 1.0f, 0.0f,
0.0f, 0.0f, 0.0f, 1.0f };
return mul(rotateY, mul(rotateX, rotateZ));
}

GeometryVSOut GeometryVS(GeometryVSIn input)
{
GeometryVSOut output;
output.position.x += input.instancePosition.x;
output.position.y += input.instancePosition.y;
output.position.z += input.instancePosition.z;
float4x4 rotationMatrix = RotateV2M(input.instanceRotation);
output.position = mul(float4(input.position, 1.0f), mul(worldViewProjectionMatrix, rotationMatrix));
output.positionView = mul(float4(input.position, 1.0f), mul(worldViewMatrix, rotationMatrix).xyz;
output.normal = mul(float4(input.normal, 0.0f), mul(worldViewMatrix, rotationMatrix)).xyz;
output.texCoord = input.texCoord;

return output;
}


[/CODE]



So the problem is in the last function(the main vertex shader one),it somehow has trouble converting from float3 to float4 I think,I'm actualy new to the .xyz functionality,I think it's called swizzling.Maybe I'm not implementing the swizzling properly?
0

Share this post


Link to post
Share on other sites
There is a syntax error in this row:

output.positionView = mul(float4(input.position, 1.0f), mul(worldViewMatrix, rotationMatrix).xyz;

As a hint, the error is not related to the swizzle itself. Edited by Nik02
0

Share this post


Link to post
Share on other sites
[quote name='Nik02' timestamp='1347384588' post='4978971']
There is a syntax error in this row:

output.positionView = mul(float4(input.position, 1.0f), mul(worldViewMatrix, rotationMatrix).xyz;

As a hint, the error is not related to the swizzle itself.
[/quote]

Thanks,I can't believe I missed that one,however I think there is still some problem with the actual vertex declaration,or I'm not doing the C++ side right:

[CODE]UINT shaderFlags = D3D10_SHADER_ENABLE_STRICTNESS | D3D10_SHADER_PACK_MATRIX_ROW_MAJOR;
ID3D10Blob *bytecode = 0;
HR(D3DX11CompileFromFile(L"GeometryVS.hlsl", defines, 0, "GeometryVS", "vs_5_0", shaderFlags, 0, 0, &bytecode, 0, 0));
const D3D11_INPUT_ELEMENT_DESC polygonLayout[] =
{
{"position", 0, DXGI_FORMAT_R32G32B32_FLOAT, 0, 0, D3D11_INPUT_PER_VERTEX_DATA, 0},
{"normal", 0, DXGI_FORMAT_R32G32B32_FLOAT, 0, 12, D3D11_INPUT_PER_VERTEX_DATA, 0},
{"texCoord", 0, DXGI_FORMAT_R32G32_FLOAT, 0, 24, D3D11_INPUT_PER_VERTEX_DATA, 0},
{"instancePosition", 0, DXGI_FORMAT_R32G32B32_FLOAT, 0, 0, D3D11_INPUT_PER_INSTANCE_DATA, 0},
{"instanceRotation", 0, DXGI_FORMAT_R32G32B32_FLOAT, 0, 12, D3D11_INPUT_PER_INSTANCE_DATA, 0},
};

HR(gD3DDevice->CreateInputLayout(polygonLayout, ARRAYSIZE(polygonLayout), bytecode->GetBufferPointer(), bytecode->GetBufferSize(), &vertexLayout));
gD3DImmediateContext->IASetInputLayout(vertexLayout);
SafeRelease(bytecode);
[/CODE]

I saw in a tutorial that you define the first 3 ones like this and the ''AlignedByteOffset'' was '0' for the first one, '12' for the second and '24' for the third,even tho the third(texcoord-2 elements) is smaller than the second(position-3 elements) and yet theyre both 12 bytes apart,so I'm confused-should I put the instance ones 12 bytes apart too for it to work with the above shader?
0

Share this post


Link to post
Share on other sites
The instance data is (likely) in a separate vertex stream. In the input element descriptions, you still say that they are in the first stream (the InputSlot field of the structure).

The offsets are correct. Edited by Nik02
0

Share this post


Link to post
Share on other sites
[quote name='mrheisenberg' timestamp='1347387402' post='4978984']
I saw in a tutorial that you define the first 3 ones like this and the ''AlignedByteOffset'' was '0' for the first one, '12' for the second and '24' for the third,even tho the third(texcoord-2 elements) is smaller than the second(position-3 elements) and yet theyre both 12 bytes apart,so I'm confused
[/quote]

Offset is calculated from the end of the previous element, it's not related to the current element you're declaring. If I have a 12 byte element, a 12 byte element, and an 8 byte element in that order:
- the first offset is 0 (since it's first in the list),
- the second is (previous offset ((0)) + length of previous element((12))), so 12,
- the third is (previous offset ((12)) + length of previous element ((12))), so 24.
if there had been a fourth element in the same stream, THEN you would have seen the 8-byte alignment make a difference in an offset value, as the next up would be 32.
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