Finally, a DirectX 10 video driver for Irrlicht

3DModelerMan · Post by **3DModelerMan** » Thu Dec 09, 2010 1:57 am

Cool. I hope this gets into the Irrlicht core. DirectX11 is what I really want to use.

evandromillian · Post by **evandromillian** » Tue Jan 11, 2011 12:41 pm

Hi people.

New changes to this project:

- Implemented hardware buffers, created by IVideoDriver. Buffers can be created by DirectX 9 and 11 drivers, and draw using it is only enabled for DX 11. See drawHardwareBuffer and createHardwareBuffer methods

- Vertex declaration support started by registerVertexType method, that receives and array of vertex elements and returns and E_VERTEX_TYPE id (same way of shader materials). I decided to only expose an id, and let video drivers to implement in better way. DX 11 implements with vertex declaration class, but DX 9 can store FVF ids or can use DX 9 vertex declaration too (enabling instancing)

- The texture and render target creation methods now supports texture array and multisampling config, as well as a method to query multisample capabilities for video driver. See queryMultisampleLevels and addRenderTargetTexture methods

I'm working now in stream output support. I hope to finish soon.

3DModelerMan · Post by **3DModelerMan** » Tue Jan 11, 2011 2:04 pm

Are you going to provide binary packages anytime?

evandromillian · Post by **evandromillian** » Tue Jan 11, 2011 5:32 pm

Hi 3DModelerMan,

See in bin/Win32-VisualStudio folder of project. There are the examples and the Irrlicht.dll also. But it was compiled in debug mode, OK?

Contact me in case of doubt.

3DModelerMan · Post by **3DModelerMan** » Tue Jan 11, 2011 11:10 pm

Alright, thanks.Debug mode is fine for now anyways.

Mel · Post by **Mel** » Wed Jan 12, 2011 12:30 am

evandromillian wrote:Hi people.

New changes to this project:

- Implemented hardware buffers, created by IVideoDriver. Buffers can be created by DirectX 9 and 11 drivers, and draw using it is only enabled for DX 11. See drawHardwareBuffer and createHardwareBuffer methods

- Vertex declaration support started by registerVertexType method, that receives and array of vertex elements and returns and E_VERTEX_TYPE id (same way of shader materials). I decided to only expose an id, and let video drivers to implement in better way. DX 11 implements with vertex declaration class, but DX 9 can store FVF ids or can use DX 9 vertex declaration too (enabling instancing)

- The texture and render target creation methods now supports texture array and multisampling config, as well as a method to query multisample capabilities for video driver. See queryMultisampleLevels and addRenderTargetTexture methods

I'm working now in stream output support. I hope to finish soon.

That multisample bit sounds extremely great

And the solution for the flexible vertices is quite remarkable too. Good job!

evandromillian · Post by **evandromillian** » Wed Jan 12, 2011 10:36 am

Thanks Mel.

Ths is an example of how to create custom vertex types:

Code: Select all

struct ParticleVertex {
   core::vector3df Pos;
   core::vector3df Velocity;
   u32 Type;
};

core::array<SVertexElement> elements;
elements.push_back(SVertexElement(EVES_POSITION, EVET_FLOAT3, 0))
elements.push_back(SVertexElement(EVES_NORMAL, EVET_FLOAT3, 0))
elements.push_back(SVertexElement(EVES_TEXTURE_COORD, EVET_UINT1, 0))
E_VERTEX_TYPE particleType = driver->registerVertexType(elements);

So, in draw methods, you can use this vertex type:

Code: Select all

drawVertexPrimitiveList(0, vertexCount, 0, indexCount/3, particleType, scene::EPT_TRIANGLES, indexType);

3DModelerMan · Post by **3DModelerMan** » Wed Jan 12, 2011 2:03 pm

Does this allow passing extra per-vertex information into shaders?

hybrid · Post by **hybrid** » Wed Jan 12, 2011 2:09 pm

Could you point me to the AA code in the RTT generation? I did only find the feature support check for various AA modes, but no way to make an RTT anti-aliased or not. This was something which I wanted to approach for 1.8 or 1.9

evandromillian · Post by **evandromillian** » Wed Jan 12, 2011 9:24 pm

Hybrid,

I think that I didn't upload this implementation yet, sorry

I changed the method for addRenderTargetTexture, that now is:

Code: Select all

virtual ITexture* addRenderTargetTexture(const core::dimension2d<u32>& size,
				const io::path& name = "rt", const ECOLOR_FORMAT format = ECF_UNKNOWN,
				u32 sampleCount = 1, u32 sampleQuality = 0, u32 arraySlices = 1) =0;

And I removed the check for types of AA, because is implementation dependant. I don't know if is a good idea, cause DX9 handle this diferently from DX11 and from OpenGL.

3DModelerMan,

This allow not only passing extra information, but create a new type of vertex you need. But I keep this simple too, only exposing one method, the SVertexElement struct and returning a simple and well known E_VERTEX_TYPE enumeration.

But I just implemented this features for DX 11 driver for now, OK?

The repository is now updated, sorry for the delay.

3DModelerMan · Post by **3DModelerMan** » Wed Jan 12, 2011 11:05 pm

@Hybrid
Will you be integrating this with Irrlicht core soon?

hybrid · Post by **hybrid** » Wed Jan 12, 2011 11:10 pm

3DModelerMan wrote:@Hybrid
Will you be integrating this with Irrlicht core soon?

This means...?
The whole add-on? No, support for the new features are still WIP, needs better integration etc.
Just the AA feature? No, I will take a different approach.
Just the driver without the additional features? Depends on how complete it is, and how much additional changes in the basic engine it needs. the ogl-es 2.x driver is a good example for a real add-on (so far only in ogl-es branch). It just adds new files, a few changes to add the create functions and enum values, and exactly one change in the existing engine API.

evandromillian · Post by **evandromillian** » Thu Jan 13, 2011 1:02 am

Hybrid,

How do you think to integrate AA?I thought about using something like:

Code: Select all

driver->setTextureCreationFlag(video::ETCF_MSAA_8X, true);
// create texture
driver->setTextureCreationFlag(video::ETCF_MSAA_8X, false);

But I don't think that is good, cause MSAA only makes sense in render target texture.

I think that DX 11 driver is about 70% complete. But none of this features are strict necessary to this driver be delivered. I will do my best to integrate it without changes in the main engine interface.

But there is no doubt that these changes will be useful to use this new driver (and the others too) to release full potential.

Let's negociate this changes, I would be very happy to help.

amerthebest · Post by **amerthebest** » Thu Jan 13, 2011 1:25 pm

I think directx 11 support is very nice feature,i've tested it and it works well at moment with some leaks on 2d rendering,shadows and particle system.

There is small bug into the CD3D11Driver::queryMultisampleLevels(ECOLOR_FORMAT format, u32 numSamples) methods,you're always passing 4 instead of numSamples, should be:

Code: Select all

u32 CD3D11Driver::queryMultisampleLevels(ECOLOR_FORMAT format, u32 numSamples) const
{
	UINT quality = 0;
	if (SUCCEEDED(Device->CheckMultisampleQualityLevels(this->getD3DFormatFromColorFormat(format),
														numSamples, &quality)))
	{
		return quality;
	}

	return 0;
}

Anyway,nice work.

Keep you're work.

fmx · Post by **fmx** » Thu Jan 13, 2011 2:48 pm

Great work there evandromillian

You should post about your Flexible Vertex Format scheme in Nadro's topic:
http://irrlicht.sourceforge.net/phpBB2/ ... 57&start=0

Even if FVFs will not be implemented into the rest of irrlicht for a long while yet, its never too early to discuss implementation strategies