blueapples

I cannot find any vegetation items that don't have a shadow shader assigned. What else can cause this kind of strange artifact? It looks like a grass texture but doesn't match any grass textures I'm actually using that I can tell.

Allow for custom shapes defined by a heightmap other than circle for all deformation actions in the terrain editor. Provide some default heightmap brushes based on common patterns generated by programs such as L3DT.

My mind is exploding with ideas.

This is going to be great for my UI needs, really glad it's coming!

After Josh's suggestion, I am currently using a stack structure in Lua to keep track of "outer" worlds, which I then pop off and reactivate to exit an area. I think what I might do to keep video memory use constant and reduce interior load times is to place a bunch of the interior assets in an off-map area of the main map, so their resources are loaded on startup and then stay in memory. I'm okay with loading a few assets when moving into interiors if they are unique to that "tree" of maps, if that makes sense, since they will only be loaded/unloaded the first time you enter each area. The biggest issue I'm running into now is that with exterior and interior assets I'm already pushing 950MB of video memory. Definitely going to need an extreme optimization pass. Or more like passes.

What would be the best way to make the grass billboards a bit less dark? You can see an identifiable line in the distance where the billboards start.

That would have to apply to all vegetation right? I'm not super familiar with how the shaders work yet.

Is it possible to adjust the height or scale of vegetation with either code (Lua or C++) or within the editor? For instance, see the following screenshot with the marshgrass asset in front of a building with a door at player height. It's very tall, preventing the default FPSPlayer prefab from seeing over the top of it easily. Is the only way to do this to adjust the model? If so, how can we get varying heights / scale sizes for grass or trees?

Yeah, C++ is fully functional. I haven't done a lot with it but you just open the sln file and hit build and it runs. You have complete control over the main application loop (with a basic provided source that I believe corresponds to the default EXE), and you can use the "app" oriented object pattern as well. You can still easily use lua with a customized C++ build as well, basically all the default does is load up the lua layer and trigger it at the right spots.

Have a simple portal door system working with an interior map I've just started working on today. One issue I'm running into with this setup is that the exterior map is completely unloaded when moving into an interior map. This causes a huge load time when you exit the building. I'd really like to be able to optimize some of that but so far I'm pretty much drawing a blank. Maybe it's a bit too late, will think on it more tomorrow.

Two great tutorial videos for people who want to do custom FPS weapons: The guy frames these as being about getting assets ready for Unity, but this should also work in Leadwerks. The arms are made using the open source MakeHuman project, which also looks like an awesome way to make actual fully rigged characters.

Wow you weren't kidding they are very finicky... finally got something that sort of works though! Obviously needs some work still, but thank you for the tips! Another thing that helped a lot was to make a new map and just wire up the FPSPlayer to the weapon like you suggested. This loads a lot faster than my real map and made tweaking a lot easier. One other thing that helped was to play with the scale value slowly until the model was at least visible, and rotate around the second rotation point by 30 or so degrees at a time to try to find the prefab. Then the rest was just trial and error. I had also started working on a mod for FPSPlayer that would let you make adjustments in the game itself to try to "find" the prefab basically, maybe I'll finish that at some point.

Hmm that did seem to work. I can drop it into the scene and it appears correctly. Having trouble with it not being visible when attached as a weapon model after pickup, but the export isn't blocking me now! http://www.leadwerks.com/werkspace/topic/14764-custom-fps-model-not-visible-after-pickup-how-to-debug/

Actually this one does sort of seem to work if I export as FBX: http://www.blendswap.com/blends/view/42830 I'm having trouble positioning it however. Created a new thread related to that.

I've created a custom fbx model and imported it, then set it up similar to an existing melee prefab. This is wired up to a pickup object running PickupWeapon.lua, with it's VWep value set to the exported prefab of my custom model. Here are the two prefabs on the scene for visual comparison: These are the settings for the custom prefab root: The original machete prefab had the second rotation value set to 180, but because my model appears to be 180 degree turned, I have it set to 0. The issue I'm running into is that when the pickup triggers, it seems to work -- the weapon is available, pressing fire plays the sound attached to the prefab, etc. But the weapon isn't actually visible: I have tried values between 1-100 for rotation and offset without luck. How should I go about debugging this? I can't inspect the item while it's running so it's hard to know what is setup incorrectly.

Does this stop happening in run mode instead of debug? The frame rate in debug mode is consistently 1/4 of what I get in run mode. Lower frame rate may prevent the culling caluluation from reacting fast enough.

Shadmar's effects pack has an animated shader, at least I think that's where I got it.

I did find some that look pretty good but they won't export from blender due to an error... might have to keep looking.

Nice, that totally fixed it. Hopefully this will help out anyone else who downloads these from the Workshop, they are otherwise really good, well textured.

Hey Josh, I downloaded the official Blender to Leadwerks exporter from github. I am getting this error when trying to export this hands blend file to mld format: read blend: C:\Users\isaac\Downloads\_Leadwerks\Models\42830_The_First_Person_Shooter_Hands\HandSwap.blend Traceback (most recent call last): File "C:\Program Files (x86)\Steam\steamapps\common\Blender\2.77\scripts\addons\io_scene_leadwerks\leadwerks\ui.py", line 101, in execute return LeadwerksExporter(**kwargs).export() File "C:\Program Files (x86)\Steam\steamapps\common\Blender\2.77\scripts\addons\io_scene_leadwerks\leadwerks\exporter.py", line 54, in export self.save_exportable(e, name) File "C:\Program Files (x86)\Steam\steamapps\common\Blender\2.77\scripts\addons\io_scene_leadwerks\leadwerks\exporter.py", line 80, in save_exportable cc.compile() File "C:\Program Files (x86)\Steam\steamapps\common\Blender\2.77\scripts\addons\io_scene_leadwerks\xml_tool\compiler.py", line 24, in compile self.compile_node(self.source) File "C:\Program Files (x86)\Steam\steamapps\common\Blender\2.77\scripts\addons\io_scene_leadwerks\xml_tool\compiler.py", line 39, in compile_node self.compile_node(s) File "C:\Program Files (x86)\Steam\steamapps\common\Blender\2.77\scripts\addons\io_scene_leadwerks\xml_tool\compiler.py", line 39, in compile_node self.compile_node(s) File "C:\Program Files (x86)\Steam\steamapps\common\Blender\2.77\scripts\addons\io_scene_leadwerks\xml_tool\compiler.py", line 39, in compile_node self.compile_node(s) File "C:\Program Files (x86)\Steam\steamapps\common\Blender\2.77\scripts\addons\io_scene_leadwerks\xml_tool\compiler.py", line 39, in compile_node self.compile_node(s) File "C:\Program Files (x86)\Steam\steamapps\common\Blender\2.77\scripts\addons\io_scene_leadwerks\xml_tool\compiler.py", line 39, in compile_node self.compile_node(s) File "C:\Program Files (x86)\Steam\steamapps\common\Blender\2.77\scripts\addons\io_scene_leadwerks\xml_tool\compiler.py", line 39, in compile_node self.compile_node(s) File "C:\Program Files (x86)\Steam\steamapps\common\Blender\2.77\scripts\addons\io_scene_leadwerks\xml_tool\compiler.py", line 39, in compile_node self.compile_node(s) File "C:\Program Files (x86)\Steam\steamapps\common\Blender\2.77\scripts\addons\io_scene_leadwerks\xml_tool\compiler.py", line 32, in compile_node compile(node) File "C:\Program Files (x86)\Steam\steamapps\common\Blender\2.77\scripts\addons\io_scene_leadwerks\xml_tool\compiler.py", line 123, in props_compiler self.writer.write_nt_str(p) File "C:\Program Files (x86)\Steam\steamapps\common\Blender\2.77\scripts\addons\io_scene_leadwerks\xml_tool\streams.py", line 96, in write_nt_str self.stream.write(bytes(val, encoding='ascii')) UnicodeEncodeError: 'ascii' codec can't encode character '\xc4' in position 6: ordinal not in range(128) location: <unknown location>:-1 location: <unknown location>:-1

Well the issue is more about the hands. I want to have matching hands that will not look significantly different, or different at all really, from those in the FPS Weapons package that I got on the workshop. I guess it goes back to wishing the source files were part of the Workshop packages, as this sort of means I can't really use any of those assets if I want a consistent look between them and anything custom I come up with. Also, I'm just not very good at organic modeling... and it's been a long time since I animated anything. Animating the pole itself might not be too hard, but arm movement, ugh... it seems like a waste of time when it's been done so many times by people so much better at it. The fishing pole isn't fully custom either, just tweaked a bit from an asset I found on a blender website. @Jen Yeah I am using shadmar's effects package and daynight cycle, really neat stuff.

I have the Cottages package from the Workshop and try to add a Poly Mesh collider to Cottage 1 or Cottage 2. This appears to work fine: But when I run the game, the outside walls have no collision. Reopening the MDL I find that it is clear they are lacking that part of the collision mesh somehow: Is there any way I can fix this or is it just a bug?

Is the example file still available somewhere? I installed Vue Espirit and it does some neat stuff, but I'd really like to play with the source file used to generate the default skybox and tweak it a bit. The file "C:\Program Files (x86)\Steam\steamapps\common\Leadwerks\Source Art\Skyboxes" and open the file "Cloudy Blue Skies.vue" doesn't seem to be in the install anymore.

Personally I would go with CSG. So far it has been awesome, allowing me to make a variety of geometry. My understanding is that CSG is much faster than rendering a model because they are much simpler shapes, but I suppose that will really depend on what you're making with it. It also seems to be the recommended way to construct maps, based on the fact that it's recommended in the tutorials (which are fantastic, I hadn't realized how powerful CSG was until I read through all of that). As far as your project goes, a set of prefabs containing CSG brushes would be awesome for a modular building construction set -- so easy to customize, unlike models. I would buy it.

I am trying to customize a FPS weapon model and find that it's not quite as easy as I thought due to needing to edit the actual original "player weapon" model. In this example, I tried putting my custom "weapon" onto the vwep machete.pfb prefab. It almost works... But as you can see, looks a bit odd with the original weapon sticking out as well. Otherwise, the animation works surprisingly well actually. So I'm hoping someone out there has some similar fbx or blend files that I can use to create custom weapons. I'd also probably want to customize actual gun weapons but I'm working on the melee type for now.