Canardia

It wasn't my vote, I voted right now. So unpredictable!

Yeah, put cullface=0 in the mat file.

I think rather that Fortran will rule the world, because it's faster than .NET, and works on all platforms, while .NET works only on Windows and Linux, but not on AIX, zOS, PS3, Android, BlackBerry, MacIntosh, Amiga, iOS, BSD, etc....

That's indeed quite ridiculous. You could have like 1000 real 3D models as decals with higher FPS.

I just finished the first phase of my verlet water test. First I tried it with BlitzMax (since got the source code as BlitzMax code), then I tried it as C++ version, and finally as Fortran version. Performance results will follow. So far it's only 2D, but the ascension to 3D should be trivial, as I read on some plasma physics article ( http://www.plasmaphysics.org.uk/collision3d.htm ) that verlet forces and collisions happen individually per dimension. Furthermore, I found out that OpenGL can draw big round pixels using hardware acceleration and additive alpha blending ( http://www.opengl.org/resources/code/samples/mjktips/particles/index.html ), this is one way to make very fast rendering of a lot of particles. Now I can see if I can make a custom version of LE 2.43 which has 2 additional commands: mesh=GetWaterMesh() and SetWaterMesh(mesh), but first I have to finish a forum software for Fortran 2008 first.

It has nothing to do with VS 2008, but it's a general Windows console window things. Every console window has this.

I would just make pivots which are placed at each cockpit view spot. The rotation and position of the pivot determines how many surrounding instruments are seen, and it is completely aspect ratio independant, as you wouldn't ever have such aspect ratio that you couldn't even see 2 instruments. The pivot should be a bit further away anyway, since else the instruments would be too big on some screens, and that would make them as unreadable as if they were to small.

Click on the top-left corner for the System menu, and there you have properties from where you can set the scroll buffer size.

You could check how many EntityVisibile(camera,entity)==1 there are, and move the camera backwards if less than wanted are visible.

I could make a special LE 2.43 version which adds access to the waterplane. According to Josh I am allowed to do that and put it in the member downloads. Meanwhile I am also playing around with a 3D verlet based water for LE2, but it won't look as good as your 3D water, because everything will be big OpenGL points, but it will perhaps be more dynamic, so you can make a game like where Moses splits the ocean

Set the parent to 0.

I would use CreateSphere and paint it with a semi-transparent material, or make a ring mesh if it must be flat and hollow.

Newest BlitzMax works with newest LE always.

In the SDK/Tools folder you will find oalinst.exe. Run that, and it will install OpenAL drivers.

I managed to get transparent buffers somehow by painting the buffer with an alpha value. You can see the complete code in GameLib's AddNameTag() function: http://www.leadwerks.com/wiki/index.php?title=GameLib#AddNameTag

I get a huge FPS loss also when going closer to any texture. It might be related to the decal FPS loss problem.

Yeah, exactly the same problem as I had. I attached hair to a model, and after that only the pelvis moved, making a nasty animation

I don't know if it's fixed, or was it ever broken, or did I do something wrong, but it just didn't work for me, so I had to use SetEntityMatrix(model,GetEntityMatrix(bone)) instead. But if your animation suddenly doesn't work anymore, try unparenting models from the bones first.

For my taste too humanoid, why not let your imagination flow!

In the feature comparison list it doesn't mention PolyReduce, so it should be in the standard version too, or then they forgot to add it on the pro list.

Sculptris creates by default somewhat high poly models, which is good for normal mapping, so my asdasd monster had 58k vertices. Then I loaded the obj file which I exported from sculptris into UU3D, and chose the "3D/PolyReduce Model..." which is an awesome feature, because you can use a slider to see in realtime how your model looks with lesser polys. So I ended up with the slider set at 8k polys and it still looks very high poly and smooth. So I saved it as gmf and now it's only a 600k gmf which loads very fast in LE2. Very nice and easy pipeline from sculptris to LE2!

Small correction: PositionEntity is faster than EntityMatrix, so only if you use both Position+Rotation, or Rotation only, then EntityMatrix is faster: http://www.leadwerks.com/werkspace/topic/2411-entity-commands-speed-test/page__p__22232__hl__entitymatrix__fromsearch__1#entry22232

I made a list how fast each LE2 command is, and EntityMatrix was faster than PositionEntity and RotateEntity each alone, so it's a lot faster than doing both PositionEntity and RotateEntity.

In the BlitzMax help under "Help/Language/Advanced topics/Interfacing with C" there is an example how to import a C++ class into BlitzMax. Using this example you could expand it so that the cpp file loads the actual DLL where the actual C++ code is, so that the imported cpp file acts only as a interface header to the dll. However, you could as well just write the whole C++ code in the cpp file which is imported by BlitzMax, since it would be faster code than if you compiled the DLL with Visual Studio, because BlitzMax uses MinGW C++. Or if you want it even faster, you could write the DLL in MinGW Fortran, then load it with C++, and then import it in BlitzMax, and it would still be OOP through the whole chain

I think it's like "~/le3files". The "~" is like on Linux, which refers to the user's home directory.