AggrorJorn

You are correct. All buttons are placeholders for now, but they should definiteley have a better default style. It would sure would make it easier but I don't have that option at my disposal.. On the other hand, I would probably have to pay a percentage to Steam and/or Leadwerks. Adding buttons is easy and done within a few minutes. Adding the desired functionality to those buttons is more work. Still, its is a good idea and I will include it in the example.

I want to launch the beta version 0.9 of FlowGUI next week. It will be available for $5,00 during the beta stage and $10.00 on release. You will have always access to the latest version of the scripts, examples and documentation. FlowGUI is royalty free and does not require a back link or logo referring to its usage. Once I ironed out possible issues that users have found I will move on releasing the other elements. Beta will include: buttons checkboxes labels sliders (horizontal and vertical) radio buttons Input fields (single line textbox) Examples and documentation Demo (see screenshot) Main menu + options menu

So close.....Just the sliders. I hope to do some work on it this weekend. Fulltime job + custom jobs for people is taking most of my time. Sorry I have removed the old verison.

realtime navmesh updating was removed as of the terrain update. Which has been more than 1.5 years ago. You can update chunks of the navmesh instead of generating an entire new navmesh. This functionality is not exposed to Lua.

What I do for my own game is using the navmesh as a base for where movement is possible. Then I create my own layers of walkable areas on top of that (both waypoint and grid). When you look in to the recast repository it is actually not that common to make severall navmeshes. I also would have though this was something common but apparently this isn't the case.

All 'The zone' already have a corresponding phy model. I connected those to the prefabs. The prefabs no longer work but the phy files are still there.

I wouldn't count on it. This has been requested as of day 1 since leadwerks 3 was released in januari 2013. Many have already asked for it.

Sorry haven't had the time to use Leadwerks for a while. -restoreconfig didn't work but removing the config does the trick.

What is happening on that doodle page? I got like 50 emails in a week.

Personally I find the combination of bitbucket, tortoiseHG workbench and mercurcial a good solution.

Can't you switch between the two when needed?

When you want to place code and don't want to lose the indenting, click on the top left button 'Toggle editing mode'. (click on more reply options if you don't see that button).

running -restoreconfig didn't resolve the issue unfortunately.

It happens in other and new projects as well . I did use the slider to widen the properties bar. If I drag it really far out, the selection field returns but the script selection button remains out of sight.

Leadwerks and GIT

I had the same thing since I have access to all their models and textures. Most buildings require severall textures but since these textures are on different locations, leadwerks doesn't where to find them. Opening the model editor after recreating some faulty materials did the trick for me.

Without seeing code we can only guess. How do you spawn enemies?

I have to check if it happens with other projects as well. I am a little scared with updating other projects, so I am just going to make a new one. Not at home right now so it will have to wait. Seriously nodbody else experiencing this? It is not just the script button. Sometimes button for selecting textures or colors completely disappear.

FlowGUI 0.9 (beta) is almost ready, just finishing up the documentation and making various examples (including an example main menu with options menu). Since it is the beta I am leaving out the resolution scaling and the dropdowns to see if people are running in to trouble with the other functionality. Beta will include: buttons checkboxes labels sliders radio buttons I am currently waiting on a bug fix that prevents me from properly testing things, so here is a screenshot in the mean time. As you can see you can create gui styles for each individual gui element. If you want to have you buttons the same style, all you have to is make 1 style and apply it to the buttons.

I have updated my project this morning (not beta) and now the script tabs no longer function. I can't assign or change scripts to an entity.

1. Leadwerks is a game engine. Anything gameplay related has to be programmed. There are some gun examples in the deafult SDK but dual wielding is not part of that. This is something you would have to make yourself. 2. This is really complex stuff you are talking about here. I would not recommend doing this and rather use existing animations. 3. 2 answers here: Yes you can inlock the mouse: ShowMouse() to view it and making sure the Mouse coordinates are not centered every frame. Maximizing a window can also done by code. http://www.leadwerks.com/werkspace/page/documentation/_/command-reference/window/windowcreate-r462

Flowgui for Lua is almost ready.

You dont have to rebuild the entire navmesh. You van update per chunk as well.

From the first day I worked with Leadwerks (2.2) this is what grabbed me: Clean API Dynamic lighting No royalties

Since standalone isn't available (anymore), I have removed that specific section from the FAQ.