shade.

[AriusEso]

I spent some time the other night writing the introductory overview for the tutorials. I've shown it to a couple people and on the whole they say it's good. With a few constructive criticisms for refining certain areas. I thank them for giving it a read.

I thought it might be a good idea to open it up to a wider audience - as the introduction is important I think. I don't want people getting bored or confused before they even start with the tutorials.

If people could read this over and tell me what they like, what they don't like and anything that is too confusing. Also, if any shader guru's can tell me where the information is incorrect( I'm sure some of it is ).

Thanks.

Read it here: http://www.azazeldev.org/shade/wias.txt 

[RuntimeError101]

Mmm, I feel like a master now. 

I'll be looking forward to seeing the rest of these.  As far as I can tell (I'm the targeted audience, aren't I?) they're great and I'm anxious to see more.

[newborn]

Well thats a good tuto... Why don't you add it to the Wiki? With Zak's tuto, it would make the whole thing complete I think.

[AriusEso]

Thanks for reading it guys.

Well thats a good tuto... Why don't you add it to the Wiki? With Zak's tuto, it would make the whole thing complete I think.

I would. But I intend to release this text and a lot of others with shade. A large part of shade is going to be it's tutorial base.

[Zaknafein]

Nice intro Arius!

Some comments/corrections/suggestions :

- Line 56 : Host/Game/App > Shader > Screen
I'm not sure if you want to go into that so early in the tutorial, but you could expand that to something like : Host/Game/App > Vertex Shader > Pixel Shader > Alpha/Stencil/Depth Testing > Screen

- Line 82 : How does one know that the end user has hardware capable of compiling your code? The answer is in checking device caps.
This is true, but it's so much simpler to make a shader with as many techniques as there are shader models and let TV3D fall back through them. I never check the device caps for shader compatibility, but I make sure that all my shader are SM2.0 compatible.

- Line 120 : declarion
Typo

- Line 182 : void FragmentProgram(in VertexToFragment IN, out FragmentToScreen)
Forgot the OUT variable identifier.

Also the bit about "spaces" is a bit hazy and feels unnecessary in an introduction, I thinks. But you could link to Wikipedia (coordinate space, ordered basis or linear map [what is used to go from one space to another]) for people who have a background in linear algebra. Or just skip it?

[AriusEso]

Nice intro Arius!

Some comments/corrections/suggestions :

- Line 56 : Host/Game/App > Shader > Screen
I'm not sure if you want to go into that so early in the tutorial, but you could expand that to something like : Host/Game/App > Vertex Shader > Pixel Shader > Alpha/Stencil/Depth Testing > Screen

- Line 82 : How does one know that the end user has hardware capable of compiling your code? The answer is in checking device caps.
This is true, but it's so much simpler to make a shader with as many techniques as there are shader models and let TV3D fall back through them. I never check the device caps for shader compatibility, but I make sure that all my shader are SM2.0 compatible.

- Line 120 : declarion
Typo

- Line 182 : void FragmentProgram(in VertexToFragment IN, out FragmentToScreen)
Forgot the OUT variable identifier.

Also the bit about "spaces" is a bit hazy and feels unnecessary in an introduction, I thinks. But you could link to Wikipedia (coordinate space, ordered basis or linear map [what is used to go from one space to another]) for people who have a background in linear algebra. Or just skip it?

Hehe, the typo/out has been fixed already.

Line 56: You're right, but I personally found it easier to get my head around shaders once I had a grasp of what was going on. I will try to clarify it a bit though.

The spaces, hehe, I had a hard time trying to explain that. Even now, I know it in my head but I can't put it into words. I will probably skip and then link to those urls later on.

Thanks.

[Zaknafein]

Some feature I just thought about for Shade and I don't think it was mentioned before.

It would be sweet if the errors found while compiling would be highlighted in the code somehow. Like red wavy underline, or when you click on an error line in the log, jump to the line causing the error...

[AriusEso]

Some feature I just thought about for Shade and I don't think it was mentioned before.

It would be sweet if the errors found while compiling would be highlighted in the code somehow. Like red wavy underline, or when you click on an error line in the log, jump to the line causing the error...

Yeap, that one is already on my list( highlighting a line that errors ). I have a few bugs that I'm currently working out - aswell as a contest/compo project that is due next Monday. After that my entire focus will be shade. But for this coming week it'll be secondary to my competition entry.

[adnanbobo]

Great application. Good luck in the work. Looking forward for it

[AriusEso]

Thanks adnan.

Just wanted to let people know that I've continued work on this - after winning the gamedev.org contest( by default, noone else entered ). I've been slowly doing things. The disassemble is in for example.

[sciophyte]

grats on the default win!

Glad to see u back on this, can't wait.

[sybixsus]

As Homer Simpson would say "The two best words in the English language. De fault! De fault! De fault!"

In all seriousness, it does look bloody great, and would certainly be a lot more fun than messing about with NotePad++ which is what I currently find myself doing.

[GD]

Yep, this is great. Me also waits for this to replace SciTE...

[AriusEso]

Just wanted to give a quick update. I'm still working on this, the reason it hasn't been released is because it's exceptionally buggy right now. I use it on a daily basis, but, my usage is avoiding the bugs( cause I know where they are etc etc ). Anyway, I'm still working on it and I apologise for it taking so long. In the mean time, heres a nice little shot of it in action. Sorry about not cropping the second monitor, but if you look at the time in the shot you'll understand why I was lazy .

[click for big]

[rootsage]

Hey, this definitely looks like a cool project. One question, how are you handeling the syntax highlighting? Are you using a custom solution or a 3rd party library for it? I tried my hand at writing my own for a PHP IDE, but it didn't work out to well, random lines would get cut short and stuff while typing

Anyway, your editor looks cool, love the transparency too, very techy looking. When I get to the point where I am writing HLSL shaders, I will certainly use your editor.

[AriusEso]

I'm using a third party lib called SynEdit( http://synedit.sourceforge.net/ ).

[rootsage]

Awesome, thank you, I am going to check it out. Again, your editor is looking great