Josh

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

The 9400M gets 13 FPS with Crysis. The ATI 4670 seems to get decent performance, and that is what they are using in all but the worst IMacs. Too bad the only way to get the 4670 is to pay an extra $300! I could buy a much better GPU for less than half the price increase. The 21.5" iMac with the ATI 4670 is probably the best choice. At $1499, it's more than twice what I would pay for a much better PC.

Their prices are more than 250% the price of a comparable PC. Even their "most expensive" laptop is using a budget GPU! So for less than half the price, you can actually get a laptop with a much better GPU! $999: http://www.newegg.co...=laptop%209800m $2499: http://store.apple.c...mco=MTM3NDcyOTc Just for fun, I checked all the most expensive options. The grand total was $7305.35. Who spends $7000 on a laptop with a budget GPU??? I can't believe how dense their management is. It's as if they don't want to succeed.

Increased to 1024. I didn't even know this setting existed.

So you want global variables, but you don't? I suggest storing any per-class variable as member of the class: class.myglobal=3 That should keep your per-class variables out of trouble, and your other scripts can still access them.

GetBodyVelocity?

You could use model:GetKey() or you could set an internal value when the Lua script calls SetKey(). function SetKey(model,key,value) if key=="pickable" then entity.pickable=tonumber(value) else end end

Uncompressed is required for editing, because the terrain editing is performed on the GPU.

whatever = 3

Why would you want to only check for objects that can be picked up? If there is a wall between you and the object, the raycast won't see it. Use collision types for this.