[BSP Mesh Export]

I'm going to upload this tomorrow morning. I don't like putting out an update before I got to sleep.

[shadow prob]

I need the files so I can produce the problem myself.

[BSP Mesh Export]

No, you get it in about 30 minutes.

[properties panel]

You should be able to move it to whereever you want.

[Undo Does Not Refresh Gizmos]

Thanks, fixed for the next update.

[BSP Mesh Export]

Okay, I made a fix so hidden lights would not be renderered, but I accidentally forgot the "!" in front of the if condition.

 

This only affects the PC/Mac version.

[properties panel]

The panel can be resized out of the way. Maximize the window and then hover your mouse at the bottom of the scene area, and there should be a resizable handle down there you can grab.

[BSP Mesh Export]

You're right. Something is wrong, probably the light data not being fed to the shader...I'm using the same code for Leadwerks 3.0 and the 3.1 beta, and using macros to switch between the two and it appears something got overlooked in the new update. Let me investigate...

[BSP Mesh Export]

Please post your map file so we can look at it.

[BSP Mesh Export]

This is actually controlled in the material files. Materials can use static or dynamic lighting.

[force and friction for camera movement]

This will do it, if you can get to the Newton body object:

http://newtondynamics.com/wiki/index.php5?title=NewtonBodySetLinearDamping

[Waiting to LW 3.1 ?]

In order to get it out faster, it will be released before the Kickstart stretch goals are implemented, and then those will be added.

[Camera->Pick() Terrain]

Fixed. Note that the radius will presently be ignored for terrain, and just a ray will be cast.

[[Solved] Having All Kinds of Troubles]

There was an update yesterday and I guess everyone already had the zlib headers...they're in now, so if you just run the updater it will download and extract them.

 

The rest of what you described is normal behavior. In the next version the Leadwerks path is a single property in the project, so you can change it in one place and all the paths will use that value.

[Waiting to LW 3.1 ?]

There will not be a new trial version of 3.0 before 3.1 is released.

[Waiting to LW 3.1 ?]

There's basically three things that need to be done:

• Finish Linux build of the editor.
  
• Finish the tutorials.
  
• Small miscellaneous bug fixes.
  

 

So the original estimated release date of December is not unreasonable.

[Access violation]

FYI, you don't need to increment the shape ref count. It will automatically do that when you add it to the shape. Your normal usage shuld be like this:

shape = Shape::Sphere();
pivot = Pivot::Create();
pivot->SetShape(shape);
shape->Release();

[fbx drag and drop not working]

I cannot produce this problem. If anyone else experiences it please speak up.

[compile project]

Not at this time. I may use Code::Blocks for Linux projects.

[compile project]

You should really open the .sln file. It's in "YourGame/Project/Windows/YourGame.sln"

[Battlefield Director: Linux Only Needs One 'Killer' Game To Explode]

I have two older system's 1. AMD/ATI and 2. Intel Core 2 Duo with Intel GPU of some kind. Anyways the point is that there is software that uses OpenGL that will run on Linux but not Windows. I couldn't run unity on ether of the two systems above, even thou I could kinda get unity working in wine on both of those systems. I think Microsoft sabotages OpenGL on windows, to push DirectX.

• Until recently, Intel was doing a good job of sabotaging PC gaming with bad drivers.
  
• OpenGL prior to 4.0 was a bloated complex mess with lots of legacy features from the fixed-function pipeline days. OpenGL4 is streamlined and dumps all the old/bad ways of doing things. So driver support for OpenGL 4 is very good, even from Intel. So you get good driver support combined with the more efficient nature of OpenGL.
  

[Battlefield Director: Linux Only Needs One 'Killer' Game To Explode]

After this work, Left 4 Dead 2 is running at 315 FPS on Linux. That the Linux version runs faster than the Windows version (270.6) seems a little counter-intuitive, given the greater amount of time we have spent on the Windows version. However, it does speak to the underlying efficiency of the kernel and OpenGL

http://blogs.valvesoftware.com/linux/faster-zombies/

[Release Runtime Error]

You probably realize this, pointers are the only thing you really need to worry about, and only for the purpose of preventing yourself from calling a function on a non-existent object. It's only a way to help prevent user error, they don't actually have to be initialized if you don't make any mistakes.

 

Another trick is to look at the object's ref count and check the collected value. If the object's refcount is either zero or some huge crazy number, it's probably an invalid object. If the collected member is true, it was probably deleted.

[launch problem]

Fixed.

[launch problem]

I forgot to upload the new DLL...fixing it now.