DaDonik
-
Content Count
376 -
Joined
-
Last visited
-
Those are just some predefined collision types. According to the docs (http://www.leadwerks.com/werkspace/page/documentation/_/command-reference/entity/entitysetcollisiontype-r35) you can choose any value between 0 and 99. LEt me remid you that i don't own the engine and just took a quick look at the documentation, so no guarantee ^^
-
Axis aligned means they won't rotate, which makes things faster to calculate. Normally they are aligned wo the world axis, but who knows what Josh implemented.
-
Of course it will be as good as that one! The fact that newton runs on the CPU and the demo you show runs on the GPU doesn't affect speed at all! Get a brain...or stop trolling... @ Shadmar Can't try that demo, as i don't have LE3 installed, sorry.
-
So you now even market LE3 through my Steam profile....O.o I just saw i have and advertisment on my wall....
-
Looks like some ppl here on the forum are confusing BSP with CSG ^^
-
I tend to do that since a compiled map generated a bsp, yet in past use people tend to use csg subtract as csg. Since the engines i've used didn't have that feature we would distinguish map files as bsp or csg (ie CoD map = bsp, or HL2 as CSG) came in handy when working on multiple mod projects cross game
-
-
-
At least you now accept that you have serious problems
-
I have a hard time figuring out why you posted that. Apart from posting way to much, you should also get some english lessons. Sometimes it's really hard for me to understand what you try to say. I'm sorry if you are dyslexic, but if thats the case you should simply not post that much...
-
It's a no for LE2 and LE3 doesn't even have dynamic shadows atm.
-
Here some facts (real facts, not Lumojaa style ): http://www.nvidia.com/object/tegra-4-processor.html http://www.nvidia.com/object/tegra-3-processor.html
-
Be patient guys, the more questions you ask, the longer it will take Josh to release LE3
-
I like 3D Coat, but i can't say that it is slow. Dunno about ZBrush, but with CUDA enabled, my PC can handle 127 million polygons relatively well. Not that that much polygons are neccessary, but it can do it!
-
The easiest way is to have two TPivot's that you use to get the desired rotation. Position one pivot right where your model is and the other at the place you want to look at. Let the first pivot point at the second one and then get the rotation from your first pivot. Now use that rotation in CalcBodyOmega and you are done.
-
All of these full screen post effects are working on a per pixel basis, which is why the number of pixels is the most important performance factor. In the case of DOF it is always working on all pixels, so it doesn't really matter what near and far distance you set. It might be that the per pixel calculation gets more or less complicated when you change near and far distance, but that would be not a huge factor.
-
Thats indeed good news. Now we just need a LE3 beta to play around with and get used to how things are done.
