Josh

The gray skin has some problems with the gallery and blogs. It's removed.

My erosion filters were never very good. If you make a heightmap in L3DT (a free program) and then just use our editor to adjust it, you will get much better results.

Nice work, thanks. I think some color variation would make the piece more interesting. Maybe some metal details or lettering on the crate.

Well, we are having a custom skin designed soon. I am not completely satisfied with either.

Packet ordering and reliability are optional.

Use BindTexture() and then glTexImage2D() to upload the texture data a lot faster.

I'm looking again for web design help. I have been experimenting with ip.content, and I really like it. I want to pull the website, docs, and forum all together in one system with a uniform look.

The data transfers we are going to be sending are very small...the whole player update data is probably less than 100 bytes per update. Ethernet packets are capped at 1500 bytes: http://compnetworkin...mtu-maximum.htm

Well, what kind of data do we need to send? -Client contacts server to join game. -Server allows client to join game. -Client sends key and mouse input. -Server sends positions of players, physical objects, projectiles, health info, etc. -Client or server disconnects. -Game score, map changes, etc. For example, the server might send ten "messages" in one packet, to update all the player positions. I am pretty sure it would be better to send all ten players' data in one packet than to send it in ten separate packets. My feeling is the number of packets will be much more of a bottleneck than the actual size of the data.

I think as a general thing, one big packet is better than 10 little ones.

There's a new skin called "IPS Beyond" in the dropdown box at the bottom of the page. I like this a lot better than the default skin.

This should be working now. Looks like Y2K struck ten years late.

We need to design a basic framework for handling multiple clients with one server. Each client needs a lua table to be associated with it, in the same way a model has an object associated with it. How can each peer be identified? We could put the peers into a table by the object handle. We could also make it possible to retrieve the peer by name, in which case a rule would be needed that no two clients can have the same name on a server.

Here's what I propose for a packet format: Byte - number of messages For each message: Byte - message id (chat, player position, keyboard input, etc) This is followed by whatever data the message uses. So you can pack multiple pieces of information into each packet.

It's up.

Add a check to make sure the target isn't nil.

I am testing the networking commands with the interpreter and need to recompile the editor for it to work. I didn't expect anyone would need networking in the editor right away, but I can add this for you this morning.

To limit rain to one area, I'd use an orthogonal camera rendered to a depth buffer to create a sort of shadow map. Then use this texture in the particle shader to determine where rain should appear. It's automatic, and dynamic. This is how STALKER does rain.

I was getting out of my car, which is pretty low to the ground, and I decided to take the groceries with me, instead of walking around to the passenger side and picking them up. I have to sort of duck down to get out, and when I stood up, bad things happened. This is a good lesson in torque.

I hurt my back pretty badly last night and have been laid out. Will be back to normal tomorrow, I think.

They're using the surface normal to determine which way a texture scrolls. I really doubt their claim that puddles will form, that they make without showing any example. There's nothing in the first video that is specific to DirectX 10 or even DirectX. It looks nice, but I am not sure what the point is since it is just an animated texture and some particles.

If I were making a game that had different skins on the same model, the shader technique described here is exactly what I would use, even if a unique copy command was already implemented. It's so much faster when you render in batches.

Entity user data.

Why do people not like you? I like you.

No, the model bounding box has nothing to do with the collision type. Add some dummy vertices to make the mesh larger so it will make a bounding box big enough to contain all the mesh when animated.