Irrlicht Engine

Yes, I very much do like the model quality in that screenshot. The shaders could be improved and reduced to be more subtle.

The speed increase would be minimal, but I don't think that core::round_ should be used. The behavior of a cast from a positive floating-point value to an unsigned integer is truncation i.e. floor . So I think an explicit addition of 0.5 should be added. core::round_ adds 0.5 to value, casts it to a ...

I guess you know what I mean
ehh..not really xD
Basically what he was saying is that this is screenshot of the month, not project of the month; implying that a development project that isn't graphically appealing isn't appropriate for this topic, and is in fact more appropriate for a thread such ...

Works fine over here in Google Chrome.

I don't mean to beat a dead horse. I'm fine with the current convention as it is defined; I'm just glad I know now for future reference. But http://msdn.microsoft.com/en-us/library/ee417304(VS.85).aspx (D3DXMatrixMultiply) is defined as "the transformation M1 followed by the transformation M2 (Out ...

At the end of the day you can push out the same pixels to the screen with Irrlicht as you can with Ogre. A number of things should contribute to your choice for which engine to use, including but not limited to: your experience with the engine, your experience with general graphics programming ...

hybrid wrote:Well, both orders are properly defined and just need to be used correctly.

Well yes. Shouldn't the documentation be updated then?

Hmm, you are correct. I guess that would explain why Irrlicht requires that you do:

core::matrix4 worldViewProj;
worldViewProj = driver->getTransform(video::ETS_PROJECTION);
worldViewProj *= driver->getTransform(video::ETS_VIEW);
worldViewProj *= driver->getTransform(video::ETS_WORLD);

instead ...

Probably because it's not a major development environment; furthermore, it would just increase the amount of projects that the developers would have to manage which is trivial but time consuming.

You have a multitude of options: UDKProgramming , Getting Started , UnrealScript Reference , etc. All the documentation is written by Epic Games themselves, or approved by them. It's cross-referenced as well, so feel free to click through as much information as possible. It will take a good bit of ...

Really, you're going to need to make your decision based on what is more cost-effective (or in your case time-effective). You don't want to waste your time. Thus if learning how to use the Unreal Engine 3 and producing your game will take 3 months, while producing the same game with your own ...

To get some conceptual information about it you could check out this page on octrees . Essentially they build the assertion that if a node isn't visible, then it's children are not visible. They can be used for other things as well besides just visibility algorithms. Furthermore, they are akin to ...

To draw lines you would use IVideoDriver::draw3DLine . Now when it comes to what equations you want to use there are a number of ways you can go about it. Have a look at Bezier curves and Cubic Hermite Splines . You can eventually venture into further areas, but those are the most widely used ...

That was pretty good, I liked the video. How'd you do the overhead pans while they were on the bed? I noticed the shadow, but I still couldn't tell how you did it.

I can't tell whether Ulf is being serious (given that joke about 12 year olds going around.)

Well essentially you would just solve the given equation(s) at a given step rate and output a list of lines to draw. You could vary the step rate based on how detailed you want the line to look and everything. That's how most people handle drawing any arc-based objects.