desktopW is the screen widh at the moment of application start
screenW is the screen width at the current moment

I'll improve the comments on the methods

ah, k ,ty

Some more:

1. How many people can work with one indie (200$) license? Any amount?
2. Can't I let the world editor automatically generate a phys mesh for any static object/mesh?
   Do I really have to generate/create a phys file for every mesh I place, even though it'll just be a shape created from the mesh data (static geometry, e.g. building)?
   Can you add automatic generation (maybe add a button next to the phys line saying "Create from mesh" or so)?
3. (in WE) Why do material overrides have to be "compatible with default mesh material"?
   Can't I assign a material to a mesh which actually has none (by default/in mesh editor)? Why not? Can you change this?
4. How do I make an object not align to the ground when moving it?
5. Why (in play mode in WE) is the view range so limited (the view range in WE itself is set to very high, but in play mode it's always very small).
   Is there a way to change this?
6. Why does "update visible and play" still take quite long to build the terrain even when I didn't change anything?
7. Is there a way to limit an object's view/visibility range (in WE)? To make it disappear completely after x meters?
8. Can physics joints be created in the WE? In ME?
9. Could you please lower the minimum texture scale for terrain textures in WE (0.063 is not small/big enough, please lower to like 0.01)?
10. Can the world editor environment settings be loaded in my own engine application easily? If so how? If not, could you add that?

4. go to object -> turn off heighmap aligning. And use ctrl or alt for moving up and down and to rotate.

1. The whole team, assuming that it's working on 1 game.
2. Maybe in future
3. Because they must use the same shaders
5. Use [] keys to change it
6. It always rebuilds visible
7. You can assign any object to "ACCESS_GRASS"
8. no
9. ok
10. ill add this to my list

I read through most of the pages and learned a lot. Nice topic

Some implementation questions:

1. I guess most of your classes do have private methods used for their implementation. How do you remove their declarations from the headers you distribute (because none of the classes exposed there have any private, non-template methods)? Do you have some tool that does this? Does C++ really allow doing this (use private method Class::foo() for implementation but not expose it) or do you hide the implementation in some other way?
   

struct X
{
#ifdef ENGINE
void hiddenMethod();
#endif
};

I've written a c++ program which processes headers, and removes everything inside ENGINE region, you can use it for ordinary methods only (you can't use it for members or for virtual methods)

Ah, I see, that's why the attribute data is still there. And the virtual functions have to be there because the implementation must be able to go down the hierarchy when calling a virtual method.

I guessed the exclusion of the private member functions is done somehow automatically.

Thanks for telling me.

1. The autoupdater does not save the SDK location, I have to set it again every time. The only things in Autoupdate.txt are:
   
   Code:
   

   Remove   = 1
VSPath   = ""
DataPath = ""
   
   Also, I think it should use ".." (relative to the updater .exe's location) as the directory if none is entered and not just say "invalid directory".
   

Could you please quickly fix this? It's pretty annoying having to copy-paste the sdk path with every update.
Thanks in advance.

I think I did this in the last update, please check.

Ah, right, it's there now, thanks

Quote:SDKPath = "

What exactly replaces InstancedRenderer?
Calling
Multiple times?

yeah, generally when drawing many similar meshes, they get automatically instanced by the engine.