Jump to content

Josh

Staff
  • Content Count

    16,173
  • Joined

  • Last visited

Everything posted by Josh

  1. I don't think it's good to have multiple conventions. Yeah, I agree with that.
  2. Probably not, since I am using the Lua command dofile() so that compiled Lua files can be run.
  3. I agree it is a pain to remember shader names, but it would be even more painful if we started an intermediate convention like you suggest. At least right now there is no ambiguity to what you are specifying. I would not rely on scaling at all, since Newton can't handle scaled matrices.
  4. Josh

    European Nature Pack

    We worked out a special deal for LE users. See the readme.txt file included in the package.
  5. I think everyone here already expects great-looking scenery, and wants to see more gameplay. Throw some characters in one of your scenes and a HUD, and suddenly everyone will be very interested.
  6. New Steam hardware survey results are available: http://store.steampowered.com/hwsurvey As of October 2009, 80.79% machines surveyed can run Leadwerks Engine.
  7. I don't know if that was even implemented in 2.25. I think your physics objects will have problems if you are moving the submarine without using physics forces. There are commands to calculate the forces to move or rotate a body a certain way.
  8. Either: light:Move(Vec3(1,2,3)) light:Movef(1,2,3) I will try to add the "f" version for every command.
  9. They would all be parented to the scene pivot, which you could move around, but if you are trying to use physics it would get messy. I think you could just roll the camera if you want to simulate motion when inside the sub.
  10. Leadwerks Engine 2.3 has been released. This major update includes a new editor, Lua script integration, forest rendering, roads, and more. Lua Script Integration: Write object scripts and write your game in any programming language, or you can write your entire game in Lua. New Editor: Leadwerks Editor is our new tool for creating enormous terrains, placing objects, and creating worlds. You can even edit scripts and see the results instantly. Forest Rendering: An advanced new rendering algorithm makes it possible to render hundreds of thousands of trees and plants, at playable framerates. Make dense forests that stretch for miles. Roads: Build spline-based roads and paths in the editor. Roads can branch, stretch, and fade out. You can even go for a drive on your highways and byways in the editor. Terrain Holes: Remove patches of terrain and go underground with caves and bunkers. This feature brings a new subterranean dimension to your games. High Dynamic Range (HDR): Brights are brighter, and darkness is darker. High dynamic range allows a greater range of color to be displayed, with automatic iris adjustment to correct for the ambient lighting environment. Animation Improvements: Characters can have up to 256 bones, with fast hardware skinning performed on the graphics card. Rendering Framework: It's easy to toggle advanced effects on and off, in any combination, with commands like SetBloom() and SetHDR(). On Lua Like many programmers, I used to consider scripting languages to be a "toy": They are nice and easy to use, but ultimately I thought it was just programming for people who don't want to install Visual Studio. I started playing with Lua back in June of 2009, and the potential for this wonderful language quickly became apparent. Our integration of Lua allows script to be written on both a global and per-object basis; You can write your entire program in Lua, like you would with C++ or another language, or you can write a script specifically for one object class, with different predefined functions to be called during the program. There are functions that can be called when an object hits something, when it is created, or once every frame to update the object. Object scripts can be used together with C++ or another programming language. This means that anyone who uses Leadwerks Engine, with any language, can download a scripted object, drop it into their program, and have the same behavior working in their own game. The implications of this are immense. Suddenly we found that instead of being a collection of a few hundred individual programmers, the community suddenly became a collaborative, collective group. If one developer writes a script for a scary monster and posts it online, another user can download it, drop it into the editor, and see the results, with no code changes. You can even edit the script in Leadwerks Editor, save it, and instantly see the results. For the first time, developers could easily work together and share their creations, and still use whatever programming language they preferred. Lua has changed the whole feel of the community to a more social and cooperative group. Keeping it Real-time Our design philosophy for Leadwerks Engine is that everything should run in real-time, and thus be editable in real-time. Lighting and physics are already editable in real-time with instant feedback, but it took some time before I realized we can extend this approach to something else: programming. The new editor has an integrated script editor. To edit an object's script, you simply double-click on its node in the scene tree. You can view all the code that makes the object to whatever it is doing. You can also make changes to the script, save it, and the object's behavior is instantly updated! The lack of a compiling phase allows you to fine-tune behavior to get it just the way you want. Plus, it's a just lot of fun to use. For an in-depth description of our Lua implementation, see here: http://www.leadwerks.com/files/Tutorials/Lua/Getting_Started_With_Lua.pdf The Road to Perfection Roads look nice, but the reason I really like them is they allow new dimensions of gameplay. When I started off writing the road editor, I had a few requirements. I wanted the roads to be written entirely with Lua object scripts. This was a challenge, and forced me to add several features to the script integration to make it work. I also wanted roads that aligned perfectly to the terrain, like they do in Crysis. First I wrote the mesh generation routine that makes a spline-based road. This is fairly simple, but it is only part of the problem. The biggest challenge was slicing the road up by the terrain grid, so that every vertex on the road lined up along the terrain, and the whole road lay perfectly snug. UV mapping the tessellated road was another major challenge, but a clever solution was found after many attempts. The resulting roads look great and conform perfectly to the terrain. And they're fun to go driving on! Seeing the Forest for the Trees The forest rendering algorithm is my favorite new rendering feature. The bulk of this was written in the spring of last year, but there were a few details I didn't complete until recently. I spent hours playing with the Crysis editor and trying to figure out how they heck they were able to render so much foliage. I read article after article, but no one seemed to have a good approach. Most of the forum discussions on graphics development sites seemed to amount to just saying "use billboards". The problem is that rendering 100,000 billboards is still a major challenge. The solution was found by analyzing what format data the GPU will render most efficiently, and then working backwards to find a way to get the vegetation in that format. The solution is elegant, and seamless to the end user. There's no baking or pre-processing. You paint as many trees and plants on the terrain as you want, and it just works. I still have some more ideas to implement, like destructable trees and even better efficiency, but I am quite happy with how it turned out.
  11. Why does the interior of the submarine need to move around? Do submarines have windows?
  12. I include a file with any of my assets. I think everything should there should be free for use with a Leadwerks Engine game, but I am looking for a place to put a global copyright notice. Go to "Full Edit" to change the title of a topic.
  13. Happy birthday!

  14. That's a pretty good summary.
  15. Josh

    Guardhouse

    File Name: Guardhouse File Submitter: Josh File Submitted: 28 Nov 2009 File Updated: 24 May 2011 File Category: Models Triangles: 712 LOD Versions: Yes Small building inspired by the Agroprom level in S.T.A.L.K.E.R. Click here to download this file
  16. Josh

    Terrain Textures

    File Name: Terrain Textures File Submitter: Josh File Submitted: 28 Nov 2009 File Updated: 28 Nov 2009 File Category: Materials Resolution: 1024x1024 Terrain Textures by Rich DiGiovanni. Our goal with this texture package was to provide a cohesive set of terrain textures for a variety of environments. During production we experimented with different techniques to improve appearance and reduce common visual artifacts. We found that by using the same base for all textures in a set we could produce results that blended together better. A special algorithm was written which fades mipmaps out to their average color as the mipmap level increases. This reduces tiling artifacts on far away terrain. Textures use two layers of details so that tiling is reduced but near details are retained. We also created transition textures that create a natural transition from rock faces to flat ground, by breaking the rocks into smaller pieces. There are five themes included in this package: forest, jungle, desert, mountain, and savannah. Click here to download this file
  17. File Name: European Nature Pack File Submitter: Josh File Submitted: 28 Nov 2009 File Updated: 28 Nov 2009 File Category: Models Triangles: variable Large pack of different trees and plants by Michael Betke. http://www.michaelbetke.net Converted to GMF format by Alex. http://www.arbuznikov.com Click here to download this file
  18. Ah ha. Then we need to do something like this: if fw~=nil then listener = fw.listener else listener=GetGlobalObject("listener") end And your main program would set the global object "listener" to a listener entity.
  19. Impact sounds have nothing to do with the framewerk, and should work on their own.
  20. I recommend parsing this entity manually, and adjusting settings based on its values. It's just a placeholder to store scene settings in anyways, and it doesn't need to be changed once you load the scene.
  21. You would need the whole framewerk to be written in Lua.
  22. Well, you have stumbled upon one problem of having framewerk in C++ code. Lua doesn't have the framewerk commands, since they are C++ commands written in your app. Therefore, Lua can't call the commands to change the settings. The traditional ProcessScene() approach would work for this entity, since it is a special case. Does that make sense?
  23. Josh

    Access

    Everyone should be in now.
×
×
  • Create New...