insomniac_lemon

Ideally, modularity would be configured during asset creation. Like how Godot already allows Blender naming to do some stuff like this (even empties into joints/wheels) on import.

For basic use, I assume some of it could be done with an import script to split one scene into multiple variants based on the node tree (and names) with some simple logic/keywords. Likely makes even more sense with component-based code and using the same handling for editing code parameters.

For more advanced capability (particularly up to a character/vehicle editor) I assume it'd involve an add-on as well. At least it'd need a really solid editor script to handle offsets, symmetry/flipping (optionally, more inputs), scaling or other parameters. Something where you could easily create a new variation via a node or function call.

The ultimate form of this would be something that uses a flexible connector system, to the point you could probably assemble characters from 3D-printed parts if not a small scene.

I have explored multiple options. I know gridmap* could likely handle some of this (smaller grid for static objects, maybe other tricks for semi-static entities), I've been working on a custom shader with parameters to help with dynamic stuff (csg/textmesh color, color replacement for effects like emission or animation).

I assume things like Cyclops (level editor) or SDF modeling (and animations) could be used for an in-engine workflow. Though I am already having freezing/crashing (including some data loss) when editing things with shaders/lighting (4.4.1) so I have not tried those yet.

Also on a more basic level, I assume some rigging can be done just with node visibility and animations (+state?) though I haven't tried Blender animation yet.

* though from what I've seen, it seems like it's missing ways to properly configure bigger cell sizes easily. Sort of necessitating multiple grids (even in addition to walls vs decoration) or having cells that can overlap if you don't place them properly. I assume having multiple grids also does not calculate free grid spaces either (unless you mix grid and non-grid to use the new raycast placement).

This is for models that use vertex colors. I want all faces with the max brightness of the object. So in daytime lighting it should look unshaded, but in a dark environment it should darken (like the thumbnail).

What I've tried:

• using vertex_lighting* and then setting the normal directly (eg NORMAL = vec3(0.0, 1.0, 0.0);)
  • this works, but only if the lighting is perfectly overhead... a slightly wrong angle or even too far into the middle of an omnilight will create a shadow
• attempting to save the original color value, change the normal, and then bring it the old brightness back via max() if the new value is dimmer
  • lots of moving parts/assumptions on my part here
• other math stuff with NORMAL/VERTEX, abs() and normalize() etc
  • on top of the direction failure, there's also failure to keep consistent brightness (with a spinning animation), and darkening across a TextMesh

I also know I could do this with unshaded and just multiply/mix it in the shader, but I don't really like the idea of making a custom lighting/detection system (rather than using actual lights, that is).

I am not totally against diffuse shading, something like a vertex toon shader (2-3 brightness bands) could be interesting aesthetically. If that's even possible, it seems like the vertex light calculation is hardcoded (though it's also possible I just don't understand it).

* this is a relatively re-added feature (4.4)

XFCE note: autohide panel (the clock is not), accessibility WM tweaks turned on (hide title...) as I usually have a window maximized. Raise-on-focus (Window Manager settings, similar setting in tweaks for window cycling) turned off, allowing rolled-up windows to not disappear when unfocused.

System note: ~~I have not maintained it well, broken dependencies right now and have finally got bit by nVidia as my system won't properly wake from suspend. Getting an alternative GPU is somewhat of a mess, especially prices and getting full performance.~~ EDIT: Updated, working fine now

I made this ultra-minimalist window theme a while ago (this is the second version, with the widget-capable layout and style-based color accent) and have been using it.

The title is 12px tall (the buttons are default 8px, though can get taller with alternate hover/click states).

At this size, XFWM has a design issue with font sizes/baselines so most fonts are cut off (the selected font is Nimbus Mono PS Bold 10, larger has text descenders cut because text can't overlap window contents)

I would try to take this idea further (and fix some of XFWM's other relevant issues) with my own WM but I use a somewhat niche language and couldn't figure out how to render a rectangle the last time I looked into it (the WM I was looking at doesn't have titles/window controls).

Not set on a name as lots of themes have size-based names but are not as minimal.

Personal note: Aside from a software demo (+very small change to other demo) and a basic 3D character controller (which I need to work on again), I really haven't worked with this much.

I have been more focused on vertex color models and their use in Godot. Haven't done much here either... but have started a collection of materials, got billboarded models* working and a simple gridmap.

*=face negative Y in blender, apply rotation. Otherwise it will not export properly.