Admin

This has been fixed, but we are not putting out a new build until after the GDC, because we will be unable to attend to the code for a week.

All CSG brushes work for navmesh pathfinding. There are no limits imposed. I am not sure what was being described here.

That's a wise approach. The Lua debugger will give you enough power to get through the game, and then you can offload the demanding parts of your code to C++. I'll be writing a series of tutorials for making an FPS game once we get back from the GDC. A couple of people have code for this already, and the default C++ example already provides code for a freelook camera.

This is one device we are very favorable on. I'll leave it at that for now.

$199 per platform: http://www.leadwerks.com/werkspace/store/

All entities can be either a rigid body or a character controller now. See the physics commands in the entity class.

The fix for the file dialog crash has been uploaded. Please run the updater to get the fix.

This should not happen, ever. Will test.

You need to generate a lightmapped material for lightmapping to occur.

The OBJ format is not supported at this time.

The file reloading system is some of the most complicated code in the editor, and may still have some errors. Thanks for the report.

When you purchase the Leadwerks 3 Beta, you are purchasing Leadwerks 3.0, just early. People new to Leadwerks will pay the full price. You do not have to pay anything else when the final version 3.0 is released.

In order to fix your problem, we need to be able to reproduce it. Create one forum thread per problem. Do not include multiple bugs or add new bugs in a thread, unless the problems are very closely related. Do not hijack topics or reply with additional bugs in a report. Once the initial topic is resolved your reply will not be noticed and the thread will be closed. Include a complete description of the steps we need to follow to produce the problem. If images are needed to describe the error, upload them as an attachment in your forum thread. If any files are necessary to produce the problem, add them as an attachment in your thread. If your report requires files to reproduce the problem, and you do not attach those files, it will be locked or ignored so that we can focus on those issues that do have complete reports. Incomplete bug reports may be locked without explanation. By following these guidelines, we can spend our time solving your problem instead of trying to guess and recreate it.

Since the original issue is solved, I am closing this report. If you can produce erratic behavior please file a new report.

What is your connection speed? A full install here takes about 20 minutes.

There's a couple ways to approach this: material hooks, shader hooks, or global shader variables. I will have to think about it and see which is most efficient. I don't want any real-time string comparisons to be used. Because this is highly repetitive code.

1, 2, and 4 are fixed for the next build. I can't understand #3 from your description. Please post a small sample showing the error.

http://www.leadwerks.com/werkspace/page/documentation/_/command-reference/entity/entitysetcolor-r162

Please post your map, or at least a screenshot with nav rendering turned on.

Faces with that material will be removed when the BSP brushes are collapsed on load.

It should work. If you can reliably produce the problem again, please file another report.

We don't really have control over this.

There's not enough space for them to pass through that area. The navmesh visualization lets us catch problems like that and easily fix them.

Select the View > Draw Navigation menu so you can see what the pathfinding is doing. Maybe that section is too narrow for a path to form.

This should all be fixed now.