can you use ogre with Torque 3d

#1 Melissa,

You can but good lord it will be a TON of work. You have access to the source codes for both but, in this instance that does not help a whole bunch. You will need someone that is VERY adept at render pipelines and integrating tools between engines. I am not saying that it can't be done, it would just be a HUGE project. I peeked at trying this and I stepped WAY back from the idea once I started digging. Granted I am not the greatest coder in the world but, I like to think I understand at least the T3D side pretty well.

Ron

#2 Would it be as complex by taking Torque 3d into Ogre?

I know people use Ogre for a graphic engine, but then use another game engine to make use of it for more then just a graphic engine

#3 I think it would be 6 of one or 1/2 dozen of another. Ogre is basically a really cool and nice render engine (even at this point in time) for all intents. So it would be a matter of linking and hooking the T3D core functions from it's native render pipeline to Ogre's. Not a small task. Again, not impossible but, a 'very healthy' bit of work for any team. (I say team because I really do not think a lone person could do it without a HUGE amount of time and frustration invested toward the goal.) I could be wrong but, from my 'initial' poking around.....what I stated first appears to be true.

Ron

#4 Then I wonder...the person I was talking to said that the Blender Engine wss easy to set up with Ogre. Wonder why Torque is so much differ?

#5 What is the use of making blender game engine use Ogre renderer? Blender renderer is already very good.

#6 I don't know, but it could be that Blender itself uses Python internally. Ogre has a Python module. So maybe they are using PyOgre? You should ask the other person what they are talking about.

Torque3D is a complete engine with way more to it than the Blender Game engine. I am with Ron on the complexity. It would take some time to understand how T3D works and translate the appropriate calls and interfaces for Ogre3D to work with it.

This is an interesting idea as it could significantly reduce the amount of effort to maintain rendering pipe lines in the long run. It could also make the engine much more cross platform. However, it won't happen overnight. I would say this is probably a 3 to 6 months of a really good programmer that already knows T3D and Ogre.

#7 I've replaced GFX with OGRE3D in TGEA.

It's a mess and it took a lot of time. In the end it wasn't worth it because you can't simply just translate calls and be done with it, as OGRE isn't as low level as D3D or OpenGL, it's a lot higher.

Our primary goal was to use the better (at the time) pipeline and tools, and to cut down on maintainance time for the renderer.

Today with Collada support (which OGRE still hasn't got stable yet) and the above mentioned problem, I can't see much of a reason to do it.

Edit: Or well, you can translate the calls directly.. but there's no point as you're not getting much of what OGRE offers.

#8 AH, well...thanks for all the feedback about this

#9 @Stefan,

I'd be very interest in seeing what it took. Do you think I could get a copy of the code?

Vince