Masterxilo

Don't install LE to C:\Program Files\... .

If the TPick::triangle field works, I'd use that together with the surface mesh to find all the vertices of the hit triangle, and then do some math to find out the UV value at the hit position. I guess that what you had in mind. I wouldn't know another way.

While "major update" means that the old version will be discontinued.

++

If you create an le mesh/surface equivalent of it once you're happy with it and set it up as collision tree (http://www.leadwerks.com/wiki/index.php?title=Bodies#CreateBodyTree) then yes. A newton heightfield might be more efficient but there are no commands exposed for that. This will only make the physics work, the raycasting commands won't detect the mesh I suppose. Getting the rendering/lighting to look correct with a custom drawn object will be a pain...

xD Now it should not read but "40.9 kilometers"

??? 40960 meters = 40.96 km ... A km per grid point/heightmap pixel would be a way too low resolution, even for a flightsim.

It worked, but wasn't included as core functionality. You just need a vert shader and have to encode the vertex positions in a float-data texture.

I like it. But it's not better than the first version. Criticisms: The extreme video compression makes HD res useless and makes the whole thing look bad in general. LoD popping/sudden appearing of the bushes is still visible (I guess it's just the same video, but you managed to upload it in HD). Also the changes of the different shadow areas/resolutions is very visible. Music fits less and is not as good as the first one. Still, the map and artwork is great.

Try a size smaller than 100000.

The included ribbon framework is really cool:

Yes I know I could manually ad the new folder and delete the old one, but I want to use the variable. Nvm. I found and solved the problem. For some reason the variable updating batch file looks up the vars at HKCU (looks like it's not allowed to read from HKLM), but the installation only updated the values in HKLM. I copied those over and it works fine now.

I recently installed the latest windows sdk (7.0). But the environment variable/"macro" $(WindowsSdkDir) from msvc still points to the old location ("C:\Program Files\Microsoft SDKs\Windows\v6.1\" instead of "C:\Program Files\Microsoft SDKs\Windows\v7.0\"). I executed all C:\Program Files\Microsoft Visual Studio 9.0\Common7\Tools\vsvars32.bat, C:\Program Files\Microsoft Visual Studio 9.0\VC\bin\vcvars32.bat and C:\Program Files\Microsoft Visual Studio 9.0\VC\vcvarsall.bat (I think this should be the only one that has to be run.) with admin privileges. From what I know, these should update the variable from the registry "HKLM\SOFTWARE\Microsoft\Microsoft SDKs\Windows\CurrentInstallFolder", where the correct current install folder is stored (I checked). But even after running these the WindowsSdkDir variable still points to the old location. Any ideas?

FindWindow is not optimal either in the rare cases where there might exist another window with the same title.

It's quite difficult to use dlls in Java. You actually have to compile another wrapper dll: http://java.sun.com/developer/onlineTraining/Programming/JDCBook/jni.html http://www.javaworld.com/jw-10-1998/jw-10-apptowin32.html And I think it would not work/be allowed in an applet. Not unless you bought a security certificate. And even then it would still only work on the Windows platform. The entry for Leadwerks Engine on devmaster is quite old and contains wrong information.

That's not possible. You can't execute multiple leadwerks engine commands simultaneously.

++

glReadPixels might work.

To get the effect of the second image (which was in your case just a depth sorting effect/error), you'd put both the cube/unit and the marker to the transparency world, and render the cube solid. You'd need to apply a simple "see the last rendered image through me" material/shader to the cube.

k, that's true.

Why? It opens a resource that you specify with it's "name"/"address"/"Resource Locator" (with a uniform/unified notation). Hence the name...

And it'll only register input to the console window of the application, which one will want to disable in the release version.

This wasn't meant to flame a(nother) ati - nvidia argument. xD

Just got an e-mail from nVidia (the driver-newsletter) saying one shouldn't upgrade to 196.75 just yet (only hours after the "New 196.75 driver is here" message). They have removed that driver from their website, since there are obviously some problems with it. http://www.engadget.com/2010/03/05/nvidia-pulls-196-75-driver-amid-reports-its-frying-graphics-car/ Thought I'd share that info with people who didn't receive that mail/subscribe their driver newsletter.

You can use two cameras. Just make sure only one is visible when you render the scene (hide the other one with HideEnitity(), show with ShowEntity()).