Torque 3D add DX11 - 10 support?

#1 its ok i found it :D

#2 it has been while since i have read some performance comparison between dx9 and dx11.
and it always said that dx11 has much better performance then dx9.
but dx11 support in t3d always was criticised .

" i have recreated the files in here but for directx 10 and 11 only it is gfxd3d11 and gfxd3d10 shader, queryfence,enumtranslate etc etc etc."

so,what about your performance gain ?
any side effects?

here is mustafakorkmaz's brance:

https://github.com/mustafakorkmaz/Torque3D/tree/Direct3D11

#3 so far i have only changed the graphics layer to use the same calls in direct x 11 and direct x 10, i haven't actually done anything in the main app to call one of them instead of direct x 9 yet. shouldnt be too hard to change i think its best to create a seperate exe file for each dx version

#4 also have to create a few dx 10 and 11 specific gfx funcions, dx 11 and 10 dont have the fixed function pipeline of dx9, this would handle lighting, clipping, also need to implement the geometry shader, this is what creates the tessellation i think and lets face it thats what all of us want the new direct x for lol

#5 " i think and lets face it thats what all of us want the new direct x for lol"

ya,that is what needed for t3d.i personally like to develop for mobile.
but we have to work on windows machine.so being testing machine,it needs performance boost.without getting better performance from rendering side t3d will always remain as an simulation only or hobbyist try out tool.

since DX is limited only to windows,so i am looking forward to luis's opengl port and personally have started to working on open glES.

looking forward to see your progress.

#6 Well if this works out properly then it will be a foundation for people to port in newer openGl versions to the engine. I don't know opengl all that well and wouldn't trust myself to even try lik but it should be the same process, define the functions available to the engine as enums of opengls/directxs, there are features even in DX9 that look like they have been left out of the grphics layer in torque in the spirit of cross platform compatibility, but now that opengl is sort of on the same level as dx and can do the same things these features should be implemented. Hell even some rudimentary input controls for the mouse were changed or not used (doubleclick) in the spirit of compatibility.

#7 Thomas,
What you're doing is some pretty fantastic work. Something I feel T3D needed for a long time. Plus it would extent the life of the engine. If things like OpenGL works out!
I know I personally will be following your progression. Hopefully it'll make it into the main branch in the near future.
Keep up the great work!

#8 if i get it working next on the hitlist is going to be this

https://github.com/kirillv/cpp-inverse-kinematics-library

#9 that would be great too!

#10 Thomas,
Did you start a development branch for what you are doing for Dx11?
Maybe some others could join in with development. Just asking.

#11 no i havnt created a development branch yet, all the files needed to use dx10 and dx11 are already in place anyway and sorted out, just need to actually test it out see if it works. Tho if anyone is wanting to give it a shot before i release what i have done, my advice would be to do dx10 because of the differences between dx9 and dx10 are huge but the differences between dx10 and 11 are very small.

#12 I will begin testing on this when i have all my other additions sorted out, things that i am working on that i believe torque should have as basic features in its arsenal.

to list a few:

AI:
NavGraphs - not nav meshes/ Recast has already got nav meshes
Finite State Machines
Fuzzy Logic
Obstacle Avoidance and Steering Behaviours

Game Features:
Iron Sights
Scopes - this will need some changes in dx9s functions anyway for better RTT
Minimap - same as scopes


InverseKinematics and Ragdoll but these will be done after dx10 and dx11

#13 Also might be worthwhile to add physical properties to cameras so they dont fly through things like terrain and buildings

#14 Sounds like a solid plan :)

#15 @Thomas
thats a pretty nasty 8as in good)
idea and the feature list is really nailed down.

All that stuff should be already in place but we all know that dx9 is limited so a dx10/11 renderer update would push many things forward.

Great to see a solid plan!
thumbs up

#16 true dx9 is limited but alot o games still being released today use dx9. anything u see in a game released recently you can do with dx9 just need to improve on torques implementation of it.

#17 Have a look at the gfxD3D9EnumTranslate.pc.cpp file for all the features dx9 has and their torque enumeration

#18 i do get that however you know by now that there is alot that was stripped out/ left out
and well am by all means no coder, it might be sad but i guess you wont get much attention from the real coders here.

Most of those either work for WLE or do their own thing, being left alone to work on something is one thing but being left in the dark when there are ppl who could speed up your work fro the benefit of all,
just by adding a sentence here and there is a shame.

Anyways am glad someone tackles dx10/11 support

#19 its clear tho when u read through the code that most of the features that were left out were due to compatibility with opengl, opengl back then wasnt what it is now and it was leagues behind direct x now both technologies are very much neck and neck.

#20 they are and tbh that is why am surprised that you are not tackling opengl?!
especially since for indie game developers a opengl engine is a should do thing.

And if you look at stuff like ouya and the upcoming steam os and ofc android
and linux ingeneral.

However more then cheer for you and donate something to the cause wont happen.

If you need beta testers
am in -
i7
Nvidia GTX 675m
16GB RAM