I know this is really basic stuff to most of you but I'm just starting to get comfortable with the Doom 3 SDK so I wrote a tutorial on strings and text messages. I talk about idStr, colours, console messages, and HUD messages. Any comments?

http://www.planetdoom.com/d3cc/

This is great! Thanks.

If we need anything right now it's information people have gathered from the SDK. Kudos.

Good information. I'm still relatively new to the SDK, so I need all the help I can get

I've added a second tutorial. This one's on user input (buttons, impulses, and commands). I spent quite a bit of time working on it and even though it's still pretty basic stuff I ended up learning a lot about the engine. I'd appreciate any comments.

http://bnbt.go-dedicated.com/doom3/tut02.html

I don't really know much programming and I don't know much about the SDK, but, you should really keep these tutorials coming, as I know they will be a valued asset to the community. Well done

i wanna have your baby.

can we get a sticky for tutorials in this section?

Thanks for the positive comments everyone.

I've finished another tutorial, this time on tracelines because I saw the thread where people were confused about tracelines.

On a more serious note there's an error in my first tutorial. I said that you can only print to the HUD with the help of a GUI script but I've recently discovered some text rendering functions in idRenderSystem. Unfortunately I'm having a heck of a time trying to get them to work. They work fine with the "textures/bigchars" material but I don't know how to use the actual game fonts (an, bank, or micro). I've sent an e-mail to iddevnet so if I get an answer I'll write a tutorial on fonts and how to render to the HUD without using a GUI. I'll also put a correction notice in my first tutorial.

Alright, on to the tutorial. Tracelines! Comments welcome as usual.

http://bnbt.go-dedicated.com/doom3/tut03.html

Trevor wrote:

I've sent an e-mail to iddevnet so if I get an answer I'll write a tutorial on fonts and how to render to the HUD without using a GUI. I'll also put a correction notice in my first tutorial.

Yes, in fact Brian posted a response with info on the main page at iddev.net.

Tutorial 4 on Fonts & Text Messages Part 2.

http://bnbt.go-dedicated.com/doom3/tut04.html

Hey Trevor, I'm just gonna rename this thread so it suits this list of tutorials better.

Aw, man, this is too good. Thanks a lot!

Yeah, good work! And i hope several are on the way, it's very helpful.

Stickied until we create a SDK-tutorial listing thread and add it there.

Goliath

Another post about fonts again today on iddevnet.com

Trevor wrote:

I've finished another tutorial, this time on tracelines because I saw the thread where people were confused about tracelines.

Thanks for this tutorial. It really made my day!!!

Now my code works, because I noticed one essential thing in your tut. I used GetEyePosition() for the trace start and never put the player as the entity that has to be ignored, so I always got my player back as an answer. Now that i noticed that I could get my code to working within minutes.

One sidenote: I'm still confused as how the masks relate to the gameworld. For example. I wanted to trace to an backpack which is an idItem. So I put CONTENTS_RENDERMODEL because it sounded good to me and the comment says "used for render models for collision detection". It is not. a backpack is a CONTENTS_MOVEABLECLIP. Of course this is rather easy to figure out because I wrote a loop that tests all flags and writes it to alog, so I can look which one triggers it. The comments for the masks are not really helpful, but maybe it is only because I'm not an native english speaker?

Thanks for changing the name of the thread and making it sticky.

sparhawk - The trace masks are actually pretty confusing. I'd just go with experimentation like you've been doing.

Here's a new tutorial on weapon scripts. This is a general info tutorial - there are no specific examples and it just tries to explain how idWeapon interacts with the weapon scripts. I spent a lot of time tracing through the idWeapon class so it makes a lot of sense to me right now but after reading it over it sounds kind of confusing. Let me know what you think.

Weapon Scripts Part 1

http://bnbt.go-dedicated.com/doom3/tut05.html

I'll probably work on some specific examples for part 2 like alternate firing modes (I know it's already been done) and anything else I can think of. I'm considering modifying the plasma rifle to glow whenever you're aiming at an enemy.

Trevor wrote:

Here's a new tutorial on weapon scripts.

Thanks for the tutorials. They are really helpfull. But could you edit all your tutorials into the first posting? I think this way people will recignize if much better, because if they don't read the thread entirely they might never notice that there are several different tutorials in here.

Just finished a tutorial on vertex and pixel shaders. This one's pretty basic and doesn't get a whole lot done but it covers a lot of ground for beginners. I'll be writing at least a part 2 and I imagine the series will go on for a long time. I'll be working on other tutorials in the meantime (like the weapon scripts series).

http://bnbt.go-dedicated.com/doom3/tut06.html

New tutorial on shaders part 2. This one covers shader parameters and rendering an entity twice for opaque post process pixel shaders.

http://bnbt.go-dedicated.com/doom3/tut07.html

Two very cool tuts there. I must start trying to think of something cool to do with shaders now. I haven't done any low level programming for over 10 years!

Wonderfull

- http://web.archive.org/web/200504031607 ... .com/d3cc/

Wonderfull

- http://web.archive.org/web/200504031607 ... .com/d3cc/

I know this is really basic stuff to most of you but I'm just starting to get comfortable with the Doom 3 SDK so I wrote a tutorial on strings and text messages. I talk about idStr, colours, console messages, and HUD messages. Any comments?

http://www.planetdoom.com/d3cc/

This is great! Thanks.

If we need anything right now it's information people have gathered from the SDK. Kudos.

Good information. I'm still relatively new to the SDK, so I need all the help I can get

I've added a second tutorial. This one's on user input (buttons, impulses, and commands). I spent quite a bit of time working on it and even though it's still pretty basic stuff I ended up learning a lot about the engine. I'd appreciate any comments.

http://bnbt.go-dedicated.com/doom3/tut02.html

I don't really know much programming and I don't know much about the SDK, but, you should really keep these tutorials coming, as I know they will be a valued asset to the community. Well done

i wanna have your baby.

can we get a sticky for tutorials in this section?

Thanks for the positive comments everyone.

I've finished another tutorial, this time on tracelines because I saw the thread where people were confused about tracelines.

On a more serious note there's an error in my first tutorial. I said that you can only print to the HUD with the help of a GUI script but I've recently discovered some text rendering functions in idRenderSystem. Unfortunately I'm having a heck of a time trying to get them to work. They work fine with the "textures/bigchars" material but I don't know how to use the actual game fonts (an, bank, or micro). I've sent an e-mail to iddevnet so if I get an answer I'll write a tutorial on fonts and how to render to the HUD without using a GUI. I'll also put a correction notice in my first tutorial.

Alright, on to the tutorial. Tracelines! Comments welcome as usual.

http://bnbt.go-dedicated.com/doom3/tut03.html

Trevor wrote:

I've sent an e-mail to iddevnet so if I get an answer I'll write a tutorial on fonts and how to render to the HUD without using a GUI. I'll also put a correction notice in my first tutorial.

Yes, in fact Brian posted a response with info on the main page at iddev.net.

Tutorial 4 on Fonts & Text Messages Part 2.

http://bnbt.go-dedicated.com/doom3/tut04.html

Hey Trevor, I'm just gonna rename this thread so it suits this list of tutorials better.

Aw, man, this is too good. Thanks a lot!

Yeah, good work! And i hope several are on the way, it's very helpful.

Stickied until we create a SDK-tutorial listing thread and add it there.

Goliath

Another post about fonts again today on iddevnet.com

Trevor wrote:

I've finished another tutorial, this time on tracelines because I saw the thread where people were confused about tracelines.

Thanks for this tutorial. It really made my day!!!

Now my code works, because I noticed one essential thing in your tut. I used GetEyePosition() for the trace start and never put the player as the entity that has to be ignored, so I always got my player back as an answer. Now that i noticed that I could get my code to working within minutes.

One sidenote: I'm still confused as how the masks relate to the gameworld. For example. I wanted to trace to an backpack which is an idItem. So I put CONTENTS_RENDERMODEL because it sounded good to me and the comment says "used for render models for collision detection". It is not. a backpack is a CONTENTS_MOVEABLECLIP. Of course this is rather easy to figure out because I wrote a loop that tests all flags and writes it to alog, so I can look which one triggers it. The comments for the masks are not really helpful, but maybe it is only because I'm not an native english speaker?

Thanks for changing the name of the thread and making it sticky.

sparhawk - The trace masks are actually pretty confusing. I'd just go with experimentation like you've been doing.

Here's a new tutorial on weapon scripts. This is a general info tutorial - there are no specific examples and it just tries to explain how idWeapon interacts with the weapon scripts. I spent a lot of time tracing through the idWeapon class so it makes a lot of sense to me right now but after reading it over it sounds kind of confusing. Let me know what you think.

Weapon Scripts Part 1

http://bnbt.go-dedicated.com/doom3/tut05.html

I'll probably work on some specific examples for part 2 like alternate firing modes (I know it's already been done) and anything else I can think of. I'm considering modifying the plasma rifle to glow whenever you're aiming at an enemy.

Trevor wrote:

Here's a new tutorial on weapon scripts.

Thanks for the tutorials. They are really helpfull. But could you edit all your tutorials into the first posting? I think this way people will recignize if much better, because if they don't read the thread entirely they might never notice that there are several different tutorials in here.

Just finished a tutorial on vertex and pixel shaders. This one's pretty basic and doesn't get a whole lot done but it covers a lot of ground for beginners. I'll be writing at least a part 2 and I imagine the series will go on for a long time. I'll be working on other tutorials in the meantime (like the weapon scripts series).

http://bnbt.go-dedicated.com/doom3/tut06.html

New tutorial on shaders part 2. This one covers shader parameters and rendering an entity twice for opaque post process pixel shaders.

http://bnbt.go-dedicated.com/doom3/tut07.html

Two very cool tuts there. I must start trying to think of something cool to do with shaders now. I haven't done any low level programming for over 10 years!

Added another tutorial and I may be getting some hosting at PlanetDoom shortly! This one's on collisions. I'm thinking of doing a tutorial on adding new entities soon.

http://bnbt.go-dedicated.com/doom3/tut08.html

Thanks again Trevor. Great stuff.

I'm now hosted at PlanetDoom. The new address is:

http://www.planetdoom.com/d3cc/

I've also added a new tutorial. This one is really cool. It goes through modifying the BFG ball so that it blows up into tons of plasma balls which ricochet around the room. I'm extremely happy with it. If you want the full effect try it out in testmaps/test_box. Also, I played around with the ricochet code on my own and as I mentioned in the tutorial if you apply a ricochet to the BFG ball it looks awesome.

I'd love any comments on this one in particular.

That looks really cool Trevor.

Pretty sweet. Great job on the tutorials. Keep them coming.

Tutorial site is down

is it going to be back up?

Are you trying the old site or the new PlanetDoom one?
'cause the PlanetDoom one's working fine for me.

http://www.planetdoom.com/d3cc/

i was trying the old one :oops:

thanks

Seems like he's not updating it anymore. :/

PLease update more tutorials there like the only code ones i can find on the net. :cry:

Site appears to be down.

Indeed, it's 404 error.
You can still grab the tutorials from the google cache.

parsonsbear uploaded these. Posted here for clarity.

http://a.parsons.edu/~evan/d3cc/tut01.html
http://a.parsons.edu/~evan/d3cc/tut02.html
http://a.parsons.edu/~evan/d3cc/tut03.html
http://a.parsons.edu/~evan/d3cc/tut05.html
http://a.parsons.edu/~evan/d3cc/tut08.html
http://a.parsons.edu/~evan/d3cc/tut09.html
http://a.parsons.edu/~evan/d3cc/Text%20 ... t%202.html

using the web archive wayback machine (one of coolest things i've ever seen), i found two more of trevor's tuts on pixel shaders

http://web.archive.org/web/200502060539 ... tut06.html

http://web.archive.org/web/200502060542 ... tut07.html

not sure how long those links will work, but you can always go the wayback machine and enter http://www.planetdoom.com/d3cc/

Ok, this is gonna sound stupid and it probably is, but I'm gonna ask anyway :-)

I just started today, cause I'm interested in modding... Never done it before, hope to do it a lot :-)

I tried tutorial 1's idStr example. Easy start. I put in the code common->Printf(...) in idPlayer::Think. Build it and place it in a subdirectory of my Doom3 installation dir...

Now to test it, I start doom, but my subdirectory doesn't show in the mods list. Fair enough, it's a test anyway, so I copy a pk4 file to my directory too. Now it's in the mod list, so I can load it. I create a game, but the message doesn't show up in console

Any ideas? Also tried the _button5 example, same result...

Another question:
Is it possible to start the dll in debug mode and use breakpoints? Using VS.NET 2003. Complains about no debug information in doom3.exe (duh), but still is there a way to do it?

Got it working.
Had to place gamex86.dll into a game00.pk4 in my mod directory. Otherwise the game would copy the default dll and hence overwrite my modified version :-)

http://web.archive.org/web/200502060535 ... tut04.html

this one was missing too

EDIT:
Last link "Text Messages 2" was this one =)

None of the new links are working...

All of them work for me, just downloaded.
EDIT: oops, seems to be too late. ^^

The first link is broken.

Edit: The reply link fix is broken as well.

Wonderfull

- http://web.archive.org/web/200504031607 ... .com/d3cc/

I know this is really basic stuff to most of you but I'm just starting to get comfortable with the Doom 3 SDK so I wrote a tutorial on strings and text messages. I talk about idStr, colours, console messages, and HUD messages. Any comments?

http://www.planetdoom.com/d3cc/

This is great! Thanks.

If we need anything right now it's information people have gathered from the SDK. Kudos.

Good information. I'm still relatively new to the SDK, so I need all the help I can get

I've added a second tutorial. This one's on user input (buttons, impulses, and commands). I spent quite a bit of time working on it and even though it's still pretty basic stuff I ended up learning a lot about the engine. I'd appreciate any comments.

http://bnbt.go-dedicated.com/doom3/tut02.html

I don't really know much programming and I don't know much about the SDK, but, you should really keep these tutorials coming, as I know they will be a valued asset to the community. Well done

i wanna have your baby.

can we get a sticky for tutorials in this section?

Thanks for the positive comments everyone.

I've finished another tutorial, this time on tracelines because I saw the thread where people were confused about tracelines.

On a more serious note there's an error in my first tutorial. I said that you can only print to the HUD with the help of a GUI script but I've recently discovered some text rendering functions in idRenderSystem. Unfortunately I'm having a heck of a time trying to get them to work. They work fine with the "textures/bigchars" material but I don't know how to use the actual game fonts (an, bank, or micro). I've sent an e-mail to iddevnet so if I get an answer I'll write a tutorial on fonts and how to render to the HUD without using a GUI. I'll also put a correction notice in my first tutorial.

Alright, on to the tutorial. Tracelines! Comments welcome as usual.

http://bnbt.go-dedicated.com/doom3/tut03.html

Trevor wrote:

I've sent an e-mail to iddevnet so if I get an answer I'll write a tutorial on fonts and how to render to the HUD without using a GUI. I'll also put a correction notice in my first tutorial.

Yes, in fact Brian posted a response with info on the main page at iddev.net.

Tutorial 4 on Fonts & Text Messages Part 2.

http://bnbt.go-dedicated.com/doom3/tut04.html

Hey Trevor, I'm just gonna rename this thread so it suits this list of tutorials better.

Aw, man, this is too good. Thanks a lot!

Yeah, good work! And i hope several are on the way, it's very helpful.

Stickied until we create a SDK-tutorial listing thread and add it there.

Goliath

Another post about fonts again today on iddevnet.com

Trevor wrote:

I've finished another tutorial, this time on tracelines because I saw the thread where people were confused about tracelines.

Thanks for this tutorial. It really made my day!!!

Now my code works, because I noticed one essential thing in your tut. I used GetEyePosition() for the trace start and never put the player as the entity that has to be ignored, so I always got my player back as an answer. Now that i noticed that I could get my code to working within minutes.

One sidenote: I'm still confused as how the masks relate to the gameworld. For example. I wanted to trace to an backpack which is an idItem. So I put CONTENTS_RENDERMODEL because it sounded good to me and the comment says "used for render models for collision detection". It is not. a backpack is a CONTENTS_MOVEABLECLIP. Of course this is rather easy to figure out because I wrote a loop that tests all flags and writes it to alog, so I can look which one triggers it. The comments for the masks are not really helpful, but maybe it is only because I'm not an native english speaker?

Thanks for changing the name of the thread and making it sticky.

sparhawk - The trace masks are actually pretty confusing. I'd just go with experimentation like you've been doing.

Here's a new tutorial on weapon scripts. This is a general info tutorial - there are no specific examples and it just tries to explain how idWeapon interacts with the weapon scripts. I spent a lot of time tracing through the idWeapon class so it makes a lot of sense to me right now but after reading it over it sounds kind of confusing. Let me know what you think.

Weapon Scripts Part 1

http://bnbt.go-dedicated.com/doom3/tut05.html

I'll probably work on some specific examples for part 2 like alternate firing modes (I know it's already been done) and anything else I can think of. I'm considering modifying the plasma rifle to glow whenever you're aiming at an enemy.

Trevor wrote:

Here's a new tutorial on weapon scripts.

Thanks for the tutorials. They are really helpfull. But could you edit all your tutorials into the first posting? I think this way people will recignize if much better, because if they don't read the thread entirely they might never notice that there are several different tutorials in here.

Just finished a tutorial on vertex and pixel shaders. This one's pretty basic and doesn't get a whole lot done but it covers a lot of ground for beginners. I'll be writing at least a part 2 and I imagine the series will go on for a long time. I'll be working on other tutorials in the meantime (like the weapon scripts series).

http://bnbt.go-dedicated.com/doom3/tut06.html

New tutorial on shaders part 2. This one covers shader parameters and rendering an entity twice for opaque post process pixel shaders.

http://bnbt.go-dedicated.com/doom3/tut07.html

Two very cool tuts there. I must start trying to think of something cool to do with shaders now. I haven't done any low level programming for over 10 years!

Added another tutorial and I may be getting some hosting at PlanetDoom shortly! This one's on collisions. I'm thinking of doing a tutorial on adding new entities soon.

http://bnbt.go-dedicated.com/doom3/tut08.html

Thanks again Trevor. Great stuff.

I'm now hosted at PlanetDoom. The new address is:

http://www.planetdoom.com/d3cc/

I've also added a new tutorial. This one is really cool. It goes through modifying the BFG ball so that it blows up into tons of plasma balls which ricochet around the room. I'm extremely happy with it. If you want the full effect try it out in testmaps/test_box. Also, I played around with the ricochet code on my own and as I mentioned in the tutorial if you apply a ricochet to the BFG ball it looks awesome.

I'd love any comments on this one in particular.

That looks really cool Trevor.

Pretty sweet. Great job on the tutorials. Keep them coming.

Tutorial site is down

is it going to be back up?

Are you trying the old site or the new PlanetDoom one?
'cause the PlanetDoom one's working fine for me.

http://www.planetdoom.com/d3cc/

i was trying the old one :oops:

thanks

Seems like he's not updating it anymore. :/

PLease update more tutorials there like the only code ones i can find on the net. :cry:

Site appears to be down.

Indeed, it's 404 error.
You can still grab the tutorials from the google cache.

parsonsbear uploaded these. Posted here for clarity.

http://a.parsons.edu/~evan/d3cc/tut01.html
http://a.parsons.edu/~evan/d3cc/tut02.html
http://a.parsons.edu/~evan/d3cc/tut03.html
http://a.parsons.edu/~evan/d3cc/tut05.html
http://a.parsons.edu/~evan/d3cc/tut08.html
http://a.parsons.edu/~evan/d3cc/tut09.html
http://a.parsons.edu/~evan/d3cc/Text%20 ... t%202.html

using the web archive wayback machine (one of coolest things i've ever seen), i found two more of trevor's tuts on pixel shaders

http://web.archive.org/web/200502060539 ... tut06.html

http://web.archive.org/web/200502060542 ... tut07.html

not sure how long those links will work, but you can always go the wayback machine and enter http://www.planetdoom.com/d3cc/

Ok, this is gonna sound stupid and it probably is, but I'm gonna ask anyway :-)

I just started today, cause I'm interested in modding... Never done it before, hope to do it a lot :-)

I tried tutorial 1's idStr example. Easy start. I put in the code common->Printf(...) in idPlayer::Think. Build it and place it in a subdirectory of my Doom3 installation dir...

Now to test it, I start doom, but my subdirectory doesn't show in the mods list. Fair enough, it's a test anyway, so I copy a pk4 file to my directory too. Now it's in the mod list, so I can load it. I create a game, but the message doesn't show up in console

Any ideas? Also tried the _button5 example, same result...

Another question:
Is it possible to start the dll in debug mode and use breakpoints? Using VS.NET 2003. Complains about no debug information in doom3.exe (duh), but still is there a way to do it?

Got it working.
Had to place gamex86.dll into a game00.pk4 in my mod directory. Otherwise the game would copy the default dll and hence overwrite my modified version :-)

http://web.archive.org/web/200502060535 ... tut04.html

this one was missing too

EDIT:
Last link "Text Messages 2" was this one =)

None of the new links are working...

All of them work for me, just downloaded.
EDIT: oops, seems to be too late. ^^

The first link is broken.

Edit: The reply link fix is broken as well.

Wonderfull

- http://web.archive.org/web/200504031607 ... .com/d3cc/