Josh

They stream textures and shaders in. That's why textures start blurry and get sharper as they are loaded. I don't like requests like this because people are requesting things they can't even define.

Dynamic loading like you describe is unlikely to happen. It would only benefit a few people with a design so ambitious it is unlikely to ever be completed. Even STALKER and Crysis don't use this approach. This would also limit the flexibility of the engine. For example, right now you can loop through all the entities in a scene. What happens when you have other sections of a scene loading and being freed? An entity you have a handle to might no longer exist. A raycast you perform might go outside of the loaded area of the scene. And if people aren't even filling up the existing area they have now with a scene they make, why would they need more space?

It will come.

The animation state between instances are not related, so I don't see any problems here.

It's already supported. Uncomment line 343 of shaders\lighting\pointlight.frag: //ambient = gl_LightSource[0].diffuse * (1.0-falloff) * 0.25 * diffuse;

https://www.paypal.com/xclick/business=orders%40leadwerks.com&item_name=Leadwerks%20Engine%202.3%20single-user%20Upgrade&amount=50.00&no_shipping=0&no_note=1&currency_code=USD I am not sure why you need to register an account. You should be able to do just a plain credit card transaction with PayPal.

The state approach makes sense to me. I don't know how else you would do it.

It will be by Friday next week. I have some real-life stuff going on right now that is taking a lot of time this week, but it ends next week. I think mostly beta testers didn't want to start messing with beta script implementations, and my presentation of it was not very good during testing.

mesh1:AddForceAtPoint(TFormVector(Vec3(0,Force,0),null,mesh1),TFormPoint(Vec3(0,0,2),null,mesh1)) 1. You can't add forces to a mesh, only a body or a model. 2. Is Force a float value or a Vec3 itself? 3. In Lua you use nil, not null. 4. AddForceAtPoint is global, so I am not sure why you are transforming the point and force to local space to begin with.

The Newton module has to be edited to support Linux/MacOS, and the OpenAL binding needs some small changes, but other than that everything should compile and run the same on all platforms.

It is possible there could be a problem with NVidia SM3 cards. It seems unlikely, but that's the only possibility I can think of. Will test.

Just make a quad and angle it to face the camera.

LoadScene?

SendMessage will remain in place to make sure existing code is supported. However, I think in three months no one will ever use it. It's easier just to do what you want to do to the lua table.

Fascinating how good it looks. Maybe some muzzle flash would perfect it? I notice in STALKER the pistol has a faint heat haze effect, but I don't think that is too important.

That is why I am doing this now and not later. I didn't get much feedback on Lua in the beta phase. There was very little interest in it, actually. I had the choice to make between a simpler less powerful system that was a nice toy, or a more powerful system that was less forgiving. I chose the first. Then when it was released it became apparent that lots of people were very serious about using it, so I quickly decided a single state system was more appropriate. It's not the way I would have chosen to make decisions, but as soon as it became apparent it was better to do it before anyone had committed any code. I probably do more trial and error than some other engines I have seen, but I also think we come up with better designs in the end. The Lua stuff is very new, so I would not look to it for stability right now. The main engine API has been quite stable for the last 6 months or so, and I don't see any changes happening there. Onwards!

This is the first of many LULZ!

Enter your reg key in both fields.

Rewrote the scripts that needed to be done with the OO single-state system. Just a few things to wrap up now and I will have it available.

I had a dream, but it had nothing to do with coding.

Newton doesn't like scaled matrices. That's it.

Yes.

Even the $7000 Mac can't run Crysis because it has a budget card. I have tried a GEForce 9800M laptop and was really fast, faster than a full-size 8800. I wouldn't complain so much if Macs had good hardware at ridiculous prices, but the laptop GPUs are about as powerful as a GEForce 6800 and they are selling them for thousands of dollars. And Mac fanboys always brag about how Apple doesn't cut corners with their hardware. Yes they do!

A lua table can't be sent back to the main program. If you think about how Lua has memory management, this makes sense.

Local position: model.position.x Global position: model.mat.tx