We cleared out some space by getting rid of the old Blender (v.2.79) copy, resulting in smaller downloadable. This also means that the SDK is not supporting FBX nor Ogre model imports anymore. We feel that GLTF format replaces these completely and they are just not worth of having really old Blender around. Maybe in the future we can look to AssImp (or MonkeyWrench) to provide support for other asset formats.
Netbeans 20 and updated Gradle game template provides support for Java 21. Note that this requires manually taking it into use as the SDK is still shipped with only Java 17. But all possible for those wanting to try it, the SDK wont slow you down!
Speaking of the updated Gradle game template… it now works out of the box on MacOS with LWJGL 3!
For the sake of humanity I hope there is no one I asked myself the same question on every release. Doing it doesn’t really require that much from us so I guess that is why it has stayed. I think it would be safe to drop in the future. Good point.
Hello everyone,
I have downloaded the new portable version of the SDK. Great job guys! Thanks for your efforts to improve the editor. I am doing some usability tests. Many bugs have been fixed, but there are still some glitches.
When opening j3md files, the following error message appears:
smoothing groups are not supported, statement ignored: s
Here are some suggestions for the Materials editor:
I would like to use this configuration with the windows side by side, to see the effects of changes immediately, but the parameters in the Materials editor are always clipped.
See the red notes.
The configuration options of the j3md file are never fully visible, either by detaching the panel from the editor (see Figure B1) or by viewing the file individually (see Figure B2). For this reason, I still think it would be better to put the ‘AdditionalRenderState’ tab back where it originally was (along with the Textures & Colors tab) to optimize space. The editor should also be easy to use on medium sized monitors, not just 27".
I believe the cropping issue with the layout of the latest SDK 3.6.1 material editor panel still exists. According to an article I read (SDK 3.6.1-sdk2 released - #18 by VR), it mentions that the SDK material editor panel layout has cropping issues in non-fullscreen windows and lacks a horizontal scrollbar.
As shown in the image below, in non-fullscreen mode, the vertical scrollbar cannot scroll to the bottom, and the horizontal direction cuts off part of the panel’s content.
Is the height of the material editor panel fixed? I noticed that the vertical and horizontal scrollbars only appear when scrolling to the bottom. The material editor in the older SDK versions 3.1 to 3.3.2 automatically adapts to the view size.
I can only see the complete horizontal and vertical scrollbars when I maximize the height of the entire panel. I request a fix for this issue, as the editor panel’s height should not be restricted. It would be great if it could automatically adapt to the height like in SDK versions 3.1 to 3.3.2.
I completely agree with your opinion. In the old SDK, the Textures & Colors and Additional RenderState panels were grouped together, which made better use of space and significantly improved window size adaptability. Additionally, more tabs could be added to the same area in the future. I also have a medium-sized monitor, and even when I maximize the window, I can barely see all the panels in the latest SDK’s material editor. It takes up a lot of space, and I prefer to have smaller windows side by side for different editors rather than displaying one editor in full screen.
I think that if I were familiar with this part of the plugin code, I would adjust and optimize the adaptive spacing for side-by-side display.
But I haven’t looked at that part of the code yet, so I hope the maintainers can take our suggestions into consideration. Thank you.
There are other issues as well. Please take a look at this image. When I drag the window to the left in non-fullscreen mode, the material editor gets severely cut off. Although I saw in the GitHub commits that this issue was addressed, the problem still persists. Just in case, please check the positions indicated by the two red boxes.
---------------------------------------------------------------------------------------------->
There are also some other issues, mainly related to the ToolBar. However, after I accidentally detached the toolbar into a separate window, I can’t see the related toolbar when I close the small window, and I have to reopen the material editor.
I hope the SDK developers can address this issue. Thank you for your hard work in maintaining it.
I asked myself the same question on every release. Doing it doesn’t really require that much from us so I guess that is why it has stayed. I think it would be safe to drop in the future. Good point.
