Einlander
-
Posts
778 -
Joined
-
Last visited
Content Type
Blogs
Forums
Store
Gallery
Videos
Posts posted by Einlander
-
-
Does this tool allow you to create basic vertex blended shaders for models, etc? That's one key thing I'm trying to get my hands on, just something that lets me blend materials on an object using R, G and B vertex colors. Other engines have the capability, but I haven't seen any shader for LW that supports this, yet.
I've looked into learning how to program GLSL to do it myself but... yeah lol... way beyond me (I'm not a programmer at all).
If there was a way to create these shaders visually, and then export them to LW in a way that's supported, that would be beautiful. But, if I'm understanding correctly, it looks like it might still require some programming know-how.
Shader tool is not a visual shader creator. You have to manually create the shader. It allows you to edit shaders without having to have to load a game engine.
-
I kind of need it to update when you change the values. My game uses it. All the materials that use csg's are scaled at 2.5 and I cant create a material and have to save and open the project to view it properly.
-
1
-
-
sync
in Programming
I use vsync so i can gauge what other users may experience. and it makes slowdowns blatantly obvious. It also introduces input lag, and the leadwerks occluder cant keep up with it.
-
It's not a waste, it's just the initial setup that is a pain. once you have the model loaded and textured (the have a pass-through shader to assist in this) it makes it easier to do things. IN leadwerk you have the engine doing the loading and the rendering for you, in shader tool you have to do that in provided nodes and connect them.
Once it's all set up that's where the difference is, in leadwerks you will need to code all uniforms you want to pass in and manually code them in lua. In shader tool you add the uniform and connect a slider to it and edit the input values in real-time. So leadwerks: Easier setup, and tedious to edit. Shader-tool tedious to setup, easy to edit.
-
4
-
-
I just dont have the patience to make a shader currently. Also leadwerks does some of the heavy lifting. It loads the models, textures and cameras. all you need to do is use the built in shader editor.
-
I have shader tool and I suck at shaders. The hardest part is setting up the renderer in shader tool. And casting errors (it sucks as at it).
-
Yep, setting it to true will fix that.
-
Yeah but iirc you can't actually go fullscreen after you start with any windowed/windowed borderless mode.
-
When I use Leadwerks I normally have my game run at desktop resolution windowed. Sometimes I want to see the performance difference in full screen (it's always better). To do this I would normally need to edit main.lua. After a bit of thinking and experimenting I made a short 'hack' that will allow you to hold f5 of f6 to run in full screen instead of windowed.
tempwindow=Window:Create("key capture",0,0,1,1,1)
context=Context:Create(tempwindow,0)
if (tempwindow:KeyDown(Key.F5) or tempwindow:KeyDown(Key.F6))== true then
windowstyle=windowstyle+window.FullScreen
end
Place this after
if System:GetProperty("fullscreen")=="1" then windowstyle=windowstyle+window.FullScreen endand before
window=Window:Create(title,0,0,System:GetProperty("screenwidth","1024"),System:GetProperty("screenheight","768"),windowstyle) -
-
Thanks, it seems to work. The goal is to build a house with sub models: Roof, building, steps. I will create a prefab that a script will be attached to. This script will choose a color from a pre-specified list. It will then look for all the children, check their surfaces and get materials. If the materials match a pre-made list of black and white textures it will change the color of that material and reapply it to the mesh. This will happen in onstart. The result will be houses that have different colors every time you load the level. Also each house that is put in the level will have a different color. This will break up the monotony of having the same house in close vicinity.
-
2
-
-
How would one go about getting the name of a model as displayed in the editor. Is there a command or would I need to put scripts on every limb?
-
I get the same kind of performance. Around 10 to 20 fps on populated levels. I usually attribute it to extra debug processes running.
-
Are you in Linux?
-
In leaders, nope. You have to scale on export in your modeling program, or model to scale.
-
Leadwerks does not support embedded materials, and you have to do the scaling yourself.
-
The engine does support checking if an entity is culled: http://www.leadwerks.com/werkspace/page/api-reference/_/entity/entitygetculled-r768
So if you keep track of what you loaded, you could always check (if culled) => disable physics
-
Can someone test this for me since I'm at work?
Set the collision type to none
http://www.leadwerks.com/werkspace/page/documentation/_/command-reference/collision-r778
And then set the mass to 0
And check performance. It may help, may not.
-
When I hide "remove" a crawler in my game crawler defense , the turret seems to still focus on it. The turret has a target and alligns to the enemy set in a scene. When I hide the crawler and it is nowhere shown again in the script, it is just invinsible (for me).
I need to think of an other way for when a crawler gets trought the whole path in the tower defense game.
Well of course, the entity still exists. So your script will still track it. You would to add a hidden entity check to tell the turret to not aim at it.
-
True, but you only have to push/pop when explicitly told to. If an object is hidden by code, and never shown again, it is never iterated. and you have a shorted list of things to iterate.
-
It could have to lists, 1 render list and 1 ignore list. This way you would never have to iterate over the hidden list if you take it out the render list. This is how I would do it, but it's up to Josh to tell us how. View range determination / culling would require all entities that are not explicitly set to hidden to be iterated, else how would it know to render it?
-
Do you know what version fbx you at trying to load?
-
Take a look at this. http://www.leadwerks.com/werkspace/blog/120/entry-1414-playing-around-with-near-real-time-map-edititng/
It's probably what you are talking about. There is code there to get started. Let me know if you need help. Since leadwerks no longer has an app loop it will need to be edited a bit.
-
Window initial caps
window. Initial caps period
WINDOW all caps
window. All caps period
"Window" initial caps quote
"window." Initial caps period quote
"WINDOW" all caps quote
"window." All caps quote period
and to be sure:
Entity.GetPosition()
entity.getposition()
Terrain normals don't scale with diffuse, and texture is backwards
in Leadwerks Engine Bug Reports
Posted
Now this is getting frustrating. 4 months later this is still around. I started trying to make my winter games entry and discovered that it's still messed up.
Anyway, I did some more experiments, other than the texture being backwards, The large normals are from the mipmap when you are far away. Both the diffuse and normal are still showing. If you use a high contrast texture like I use, you can see that some of the lines have 2 colors on them.