All Activity

Maybe there is a shader compile error earlier in the log?

Since the recent AMD driver update I have been getting this error with any Leadwerks install (fresh or existing). Steps to reproduce start Leadwerks game engine -> wait for it to load -> error is immediately evident on an empty map. See the screenshot below for more.

bool SaveTable(table& t, const WString& path) { std::string s = t.to_json(); auto stream = WriteFile(path); if (stream == NULL) return false; stream->WriteString(s, false); return true; }

Np, i hope it will be fixed sooner now. Can't make a maps for my game without normally working prefabs.

Oh sorry for the duplicate. We probably should continue on that topic.

Sounds as an issue that i met before

How would I save a table without it saving like below? "{\n\t\"Console\": 112,\n\t\"Fullscreen\": 122,\n\t\"InGameControls\":\n\t{\n\t\t\"Crouch\": 17,\n\t\t\"Jump\": 32,\n\t\t\"MoveBackward\": 83,\n\t\t\"MoveForward\": 87,\n\t\t\"MoveLeft\": 65,\n\t\t\"MoveRight\": 68,\n\t\t\"QuickSpin\": 81,\n\t\t\"Use\": 69,\n\t\t\"ZoomIn\": 257,\n\t\t\"ZoomOut\": 258,\n\t\t\"axes\":\n\t\t{\n\t\t\t\"Camera\": 0\n\t\t},\n\t\t\"mousecursor\": 0\n\t},\n\t\"Pause\": 27,\n\t\"Quick Load\": 117,\n\t\"Quick Save\": 116,\n\t\"Screenshot\": 113,\n\t\"Terminate\": 35,\n\t\"mousecursor\": 1\n}"

Load this in the XFORM project. Open the prefab and pay attention to the texture coordinates. Then make a new map and place the prefab exactly at the origin and notice the texture offset. testarea.zip

Do you still have your source code? Also, some applications such as Samsung's Disk Magician can prevent Leadwerks from launching in fullscreen from my experience.

Is there a way to disable any dependency for UI from DPI scale and stuff? Even if i create app initionally on 2nd screen with 100% scale it's still have wrong offset if 1st had 125%. ui->SetScale(1.0f); does not help

0.9.6 Added an example of a custom shader family and shader. I tried to make it as simple as possible, with one input and one output structure in which all parameters are stored. The files in "Shaders/Custom" are an example of what any node-based shader editor should output.

any ideas

0.9.6 Shader update fixes mesh layer normals. Shader update fixes missing ambient light in imposter fragment shader.

The grate.mat material in the XFORM project seems to be hit or miss trying to select a brush that has this material applied to it. You also can't move it in the 2D viewports nor retexture the brush. Must be something with the picking. XFORM/Materials/Developer at main · UltraEngine/XFORM (github.com)

New error on the rise, oh joy! XD Upon usage of TriggerChangeMap.lua in the base scripts, I find the error "Assert Failed" no comment. I used my map name as a string, and used the object which parents the script as a fail-safe for falling out the map, in order to trigger a reset of the map in use. start.map -- "start" (as used in the string)

That makes a lot more sense now.

Yes

With multiple monitors?

It goes to other screen