Search Home Members Contacts
About Us
Products
Downloads
Community
Support
Pages: 1 [2]
  Print  
Author Topic: Does anyone could give me their comments about OGRE vs TV?  (Read 10083 times)
Zaknafein
Customers
Community Member
*****
Posts: 2599


WWW
« Reply #20 on: May 29, 2008, 09:49:48 AM »

You want to add vectors just use vec1 + vec2, this is nice.

TV3D 6.5 also does that under .NET, I don't know about the other wrappers. All major TV_BLAH structures have their operators overloaded. Just thought I'd mention.
Logged

zaknafein.
>> the instruction limit : my blog & samples repository! <<
SylvainTV
Administrator
Community Member
*****
Posts: 4436


WWW
« Reply #21 on: May 30, 2008, 03:32:12 PM »

Unfortunately there is no operator overloading in VB6 and Delphi.
However it works for C++ and all .net languages Smiley
Logged

Regards

Sylvain Dupont
TrueVision3D Developer
sylvain@truevision3d.com

TV3D IRC at http://chat.truevision3d.com or on server irc.truevision3d.com #Truevision3D. Come talk with us !
petroz
Community Member
*
Posts: 603


WWW
« Reply #22 on: May 31, 2008, 12:15:51 AM »

Oh wow, i didn't not know that.
Logged

Happiness is found in your kindness.

Project: BattleSpace
Gallery URL:
http://s235.photobucket.com/albums/ee185/PeterStirling
AriusEso
Customers
Community Member
*****
Posts: 317

Esoteric


« Reply #23 on: May 31, 2008, 06:50:17 AM »

I liked OGRE when I used it, it is a fantastic engine. The reasons I use TV instead are 2-fold.

1: TV has a quicker cycle, it will take you one week to do something that in OGRE will take three.
2: I absolutely hated OGRE's material system. Writing shaders for shaders is pretty much absurd as far as I am concerned.

However, OGRE is a superb engine. Asides from the two above points I loved using it.
Logged

nullsquared
Community Member
*
Posts: 13


« Reply #24 on: June 15, 2008, 02:33:31 PM »

I liked OGRE when I used it, it is a fantastic engine. The reasons I use TV instead are 2-fold.

1: TV has a quicker cycle, it will take you one week to do something that in OGRE will take three.
Agreed, the higher level some library, the less time the client must take to write functional code.
Quote
2: I absolutely hated OGRE's material system. Writing shaders for shaders is pretty much absurd as far as I am concerned.
Shocked seriously?  I don't get it, what do you mean Undecided.  I find it so easy - write in your choice of language (GLSL/HLSL/CG), and write a .material script to bind shader parameters and what-not (all doable in-code, of course).  Ogre automatically bounds literally hundreds of shader parameters, from the current time to the current matrices in use:
Code:
// for example
param_named_auto worldViewProjectionMatrix worldviewproj_matrix
Oh well, each to their own, I guess.
Quote
However, OGRE is a superb engine. Asides from the two above points I loved using it.
Ogre is my main point of usage Grin

@ whoever said that the forums are unhelpful or not nice towards newbies: Are you serious  Wink?  I'm not particularly nice towards people who post questions like "hai, lol how use ogre make games? kthx", but I try my best to answer people's questions pretty much every day.  Besides, lots of others, including sinbad himself, tend to have "helping bursts" most days, answering pretty much any open questions Grin
Logged
AriusEso
Customers
Community Member
*****
Posts: 317

Esoteric


« Reply #25 on: June 15, 2008, 02:41:19 PM »

Hehe, yea, I could never get my head around the material files. Tongue

But as I said, OGRE is a superb engine and I always found the forum people there helpful. Cheesy
Logged

Pages: 1 [2]
  Print  
 
Jump to:  

Powered by SMF 1.1.3 | SMF © 2006-2007, Simple Machines LLC
Seo4Smf v0.2 © Webmaster's Talks