gamecreator
-
Content Count
4,812 -
Joined
-
Last visited
-
There are some good GDC talks about how they designed the art for the Diablo games and the choices they had to make to make things more readable. For example, a beam of lightning and a beam of ice might look very similar, especially if you're playing the game on a couch, at a distance from your monitor/TV. It's also more stylish to not have the same shades of gray in every level. But I agree with you and them that they may have turned the colors up a bit too much in the last installments. It's an interesting compromise between making things stylish and readable versus true to the nature of the game, which often limits your palette.
-
Camera don't render on texture in STANDALONE version
gamecreator replied to Russell's topic in Bug Reports
Are you loading a texture that's maybe not in the exported datafile? Have you checked to make sure all your textures/etc. load successfully? -
I had to try this myself. I added textures but the results were what you would expect: Brushes: Models: I then combined all boxes into 1 mesh and all collision boxes into 1 collisionmesh in 3DS Max and exported it. The speed was again good: I think the lesson is that limbs slow Leadwerks down a lot and yet individual brushes don't.
-
When you zoom in (mousewheel) in the editor, it centers on the mouse position. Why doesn't it do the same when you zoom out?
- Show previous comments 1 more
-
But it doesn't zoom straight out if you're off center. The center of the viewport doesn't stay in the center. Have 0, 0, 0 in the center, as it is when you start a new map. Then move your mouse to the bottom right section of the viewport (or anywhere else other than the center). Then zoom out. What is it zooming out based on? It seems very unintuitive.
-
-
-
Does this mean that if reepblue combined all of those boxes into a single mesh that it would be the same speed? Because that's probably how you would want to export the house in the original post anyway.
-
Terrain Building API in Leadwerks 5 Beta
gamecreator commented on Josh's blog entry in Josh's Dev Blog
Does this mean you're not planning on implementing a dynamic navmesh, like for doors that open to let characters through? Or is that something different? -
The automatic physics options don't work very well for most shapes and certainly not for complex ones. Even something relatively simple like the scene below (a single FBX), the various options either overdo it or give horrible results. The final one is convex decomposition with the maximum (6) iterations.
-
I wish there was a standard for this but it really depends on your game. I wonder how many triangles and bones these models are in Shadows of Mordor: Or these in Arkham Knight:
-
That's pretty neat so far. I wonder how that same test will compare with dynamic shadows.
-
I guess I don't understand the difference. What can you do with your method that you can't do by exporting the models together (one as the visible mesh, one as the collision model)?
-
I saw that and had several comments on that page. It seemed to me like a longer way to do what you can do directly in the modeling program (create and label a collisionmesh or collisionhull).
-
Leadwerks doesn't seem to be very good at creating even simpler collision meshes (as per my thread) so I think you'll need to use Marcousik's suggestion and make them in your modeling program yourself. Edit: just realized that the thread is in the LE5 beta forums though it discusses LE4 so I don't know who will have access.
-
I suspected so but wanted to mention it. Thanks.
-
I'm not sure if it's an animator decision or something with the engine but the neck seems to stretch and head stays in place during the right-arm attack starting at 5 seconds. In contrast, the left-arm attack at 13 seconds seems much more fluid and the head moves down with the body.
-
In that case then yes. If that's possible that would be very nice.
