Irrlicht Engine

in vanilla irrlicht 1.8 no

On the Shader-Pipeline branch yes but you have to create your vertex format your self.

there is no dx10 driver as the dx11 driver can run on all hardware all the way down to dx9 and support all feature of dx 9 ,10 and 11 if you are using the dx11 driver on dx10 hardware you should be able to use vs_4.0 and ps_4.0 amd has some cards suporting dx10.1 so ps/vs_4.1 dx11 hardware can use p...

11 is mostly complete I debugged the transparency a while a go and all feature should work but since I got no feedback on my build I sorta got stuck there

I'm starting work on the dx12 one in hope we get a functional driver before dx13 happens

Ill update my dx11 work to the lates svn and publish a patch that fix transparency issue for good after i'm done with my session next week


also there is this hapening

Yes that's what i'm talking about the noise periode is to short (At least it was in my experimentation) to be sampled in integral you would need to sample it in float and divide the coordinate by something like 128 befor feeding it to your algorythm

Your simplex code seem fine but the devil is in the detail with these. Ill have more time to look at it next week Are you feeding your noise function with coordinates ? if so do you scale them ? In my usage i noted it was better to fill your equivalent of a whole chunk using values from 0 to 1 then ...

Well the shader pipeline work for OGL and DX9 to so if you wan to use the shader-pipeline with an other driver you can just disable the dx11 driver. Then you can compile the engine where ever you wan to if you wish to use dx11 you need to compile on vs for now with the sdk it might be possible witho...

1 well there would be a significant improvement in memory usage because instead of storing 8 vertice + 12 indices per cube so at least 60k * 8 vertice (assuming only half the faces on the cube are visible) * size of vertex+ 60k * 12 indices that's a whole lot of memory wasted there with instancing y...

well the water node call a draw all wich redraw the scene a second time every frame so maybe the grass did not enjoy beeing redrawn a second time without a end scene or something between

Alright I hope too ill naturaly devlop a dx12 driver to go with it and ill also add multithreaded rendering for dx11

Will we support the multi threaded rendering path on these drivers?

Because it kinda is a big part of dx12/vulkan

i started using YSE sadly there is a potential licensing issue with juice if you plan to go commercial And so far the performance is not constand and several issue arrise when trying to play sounds multiple times ohter wise the interphase for YSE is really nice and a proper implementation would be a...

If a thread drop the refcound under your feet then some one thier does while(true) x->drop(); or you didn't properly implement grabbin when using and dropping when done Also irrlicht igniored threading as long as it could with the next generation of API becoming natively threaded irrlicht will never...

it's on page 43 ... a dropbox link I posted

well there is a full download a couple pages back