Game Development Community

Major Bug Fixes submitted for Fluid Rendering...

by Melv May · in Torque Game Engine · 09/08/2002 (7:29 am) · 10 replies

Hi,

I have spent this morning resolving major and minor bugs that people have informed me about in the improved fluid rendering.

***** I would seriously recommend that you update your files with these fixes *****

I must thank Desmond Fletcher and Eric Hartman for the heads up on the serious "crash/disconnect on create waterblock" bug, thanks guys.

NOTES:-

- You do not need any "addField" entries in the "buildWater" function in "ObjectBuilderGui.gui" now. In-fact, mine is ...
function ObjectBuilderGui::buildWater(%this)
{
   %this.className = "WaterBlock";
   %this.process();
}
- Only the file "waterBlock.cc" has changed so you only really need to replace that as it will save building lots of files.

- Field grouping is included in the new "waterBlock.cc" file but I have commented the addGroup/endGroup lines out in the function "waterBlock::initPersistFields". If you have merged with the [HEAD] then you can uncomment these lines out to enable grouping.

Thanks for your help guys.

- Melv.
NextNext Thread
PrevPrevious Thread
More from Torque Game Engine


Torque Owner Sam Guffey
#1
09/08/2002 (10:24 am)
The new effects are great, however when the depthMask is enabled it seems to shrink the textures down and from a distance you can see where the textures meet, kinda like a grid. The water tex's im using are not seemless and Im assuming this is why they dont blend well.

Associate Melv May
#2
09/08/2002 (10:29 am)
Hmmmm ...

The depth mask option, as the instructions state, is a way to revert the waterBlock back into it it's previous state. It's just a way to see it with the new depth engine on or off and shows the improvements, it defaults to on and normally stays that way.

The previous waterblock never had a tesselate option so when you turn it on it uses the surface/shore tesselate options. Change them to what you require.

If you don't use seamless textures then you will see the seam!

- Melv.

Torque Owner Sam Guffey
#3
09/08/2002 (10:52 am)
The odd part is that I never had seen the seem before, just with this build. What do the Tess options do btw?

Associate Melv May
#4
09/08/2002 (10:57 am)
Exactly what the instructions say.

I'm not being funny but I did spend time typing them for a reason. ;)

- Melv.

Torque Owner Sam Guffey
#5
09/08/2002 (11:11 am)
I have always been the kinda person to just open the new entertainment center and just start putting it together without reading first. Guess it would help if I did huh =P.

Anyways Melv, great job look forward to your next work..
Did I hear you say new particle engine =)

Sam

Associate Melv May
#6
09/08/2002 (11:18 am)
No problem Sam.

I've been meaning to improve the "help files" as they are just crappy text files at the moment and they could do with being html files with nicer formatting at least.

I really wanted to start a new web page with all my stuff on it but I've been too busy doing the actual work
to get it done.

I'm sure I'll do it when the weather gets worse and I stay in more and more. ;)

- Melv.

Torque Owner Sam Guffey
#7
09/08/2002 (2:52 pm)
Did you update the waterBlock.h file? There are some varibles that are undefined in the .cc file.

-Update-

I just had to add..
StringTableEntry    mEnvMapName;

In the private section of the fluid rendering in the waterBlock.h file

Associate Melv May
#8
09/09/2002 (12:15 am)
Sam,

I think you've got something wrong here.

That variable is not used in my code at all and I've just download the latest fluid rendering from the GG site and it's not referenced anywhere.

That variable is from the old waterBlock from the codebase.

I renamed those variables ages ago to two seperate environment maps e.g.

mEnvMapOverName
mEnvMapUnderName

Not sure what you're doing here. I noticed you posted a problem with CVS, could this be related?

- Melv.

Torque Owner Tom Vogt
#9
09/09/2002 (12:24 am)
Thanks, Melv!

My lead coder and I have been hunting this bug for days. Never suspected it could've been your code. :-)

Anyways, not much time lost. We found a couple other bugs while hunting this one. Good to know you keep your snippets updated. Others are more of the fire-and-forget mind.

Associate Melv May
#10
09/09/2002 (12:29 am)
Yeah,

Sorry for the problem guys. I do try to fix problems as they come in but sometimes I need a kick up the butt to get me started.

As always, send any problems to melv.may@btinternet.com, that way I don't forget them.

- Melv.