Josh
-
Posts
24,629 -
Joined
-
Last visited
Content Type
Blogs
Forums
Store
Gallery
Videos
Downloads
Everything posted by Josh
-
And here is a mockup that rearranges the bar a little bit -
Here's one that's even darker:
-
Adjusted the icons to more closely resemble what selected objects actually look like in Ultra. It made no sense to use red for this. Also found that using a darker background for the left-side object bar makes the icons "pop" a lot more.
-
I want to focus on the editor first because any changes I make to the GUI system could affect this issue, rather than the reverse.
-
Yeah, I was planning on that.
-
Menu hotkeys and new three-viewport layout shown.
-
Viewport navigation is done, viewport grids are done, more icons replaced in edit bar. Again testing with content from Cyclone game.
-
Source 2 does not look good.
-
I can try it and see what happens!
-
I don't know if my downsampling idea is even a good one. It doesn't look like the shader itself is the bottleneck.
-
I think it will be necessary to get a 1.0 release out, see all the ramifications of how the flowgraph works with the new component system, and then take that knowledge and design something more advanced for a future release. I think I will just focus on delivering the same functionality Leadwerks had, plus zooming. Otherwise I am likely to design something, and then remove and redesign it in another update.
-
Viewport grids and popup menus now working...
-
Using a new style for the top four icons in the left-side edit bar that don't distract so much from the main content. Brushes are using a wireframe mesh that only shows brush edges, not full triangulated surfaces. Testing with a map from Cyclone.
-
In Inkscape Path > Stroke to Path does it
-
Our SVG loader does not support lines a.k.a. "stroke", it only supports polygons. Is there some way to convert a stroked shape into a polygon? edit-face.zip
-
I have not gone through and tested every Lua command, but most of it is working now. Debugging Lua in VSCode is very good. I plan to use the ChatGPT API to auto-generate Lua documentation from the C++ docs, and then go through and make fixes by hand. My initial tests at this gave very good results.
-
I don't like tabs for two reasons: You can't see the two areas of content at once. With the flowgraph, being able to see the selected objects in the 3D viewport and see how that correlates to the nodes in the graph is very helpful. It sacrifices a lot of screen space for something that is rarely used.
-
I'm going to experiment with placing the logic view in a viewport, so to get to it you just switch the viewport's view to "logic". Then it will appear in the editor main window alongside the 3D view, and you can switch it to a single viewport and back when you need more space.
-
How did you make the settings UI?
-
Meshes are shared across different instances of the same model, so if a material is applied to a mesh, it appears on all instances. You can load a model with the unmanaged flag to load a new copy of it, or use Entity::Copy() to make a unique copy.
-
-
I'm designing the new flowgraph editor now. This is what I've got: It's using the windowed GUI, not a 3D viewport, and I think this will give it a better appearance. I plan for the entity to display each component it has, with the input and output functions for each component. I want a slider to scale / zoom the interface, and some way to add, edit, and select multiple "pages" (which are separate flowgraphs within the same scene, but not connected to each other). I don't know what the UI for this should look like. Ideas?
