Freezing SDK 3.1 and 3.2

Hello, this is me again

Problem with the SDK 3.1 and 3.2 , when try to open the View Model, Edit in SceneComposer, Edit Terrain, Edit Vehicle, the interface stops responding to the mouse. At the same time, there status no
froze in manager.

SDK 3.0 version works

The output in the console, SDK 3.1 and 3.2 is the same:

Running on jMonkeyEngine 3.2-v3.2-prealpha-sdk1-29
 * Branch: v3.2-prealpha-sdk1
 * Git Hash: a64175c
 * Build Date: 2017-03-22
LWJGL 2.9.3 context running on thread jME3 Main
 * Graphics Adapter: aticfx64
 * Driver Version: 8.17.10.1116
 * Scaling Factor: 1
OpenGL Renderer Information
 * Vendor: ATI Technologies Inc.
 * Renderer: AMD Radeon HD 6400M Series
 * OpenGL Version: 4.2.11481 Compatibility Profile Context
 * GLSL Version: 4.20
 * Profile: Core
Audio Renderer Information
 * Device: OpenAL Soft
 * Vendor: OpenAL Community
 * Renderer: OpenAL Soft
 * Version: 1.1 ALSOFT 1.15.1
 * Supported channels: 64
 * ALC extensions: ALC_ENUMERATE_ALL_EXT ALC_ENUMERATION_EXT ALC_EXT_CAPTURE ALC_EXT_DEDICATED ALC_EXT_disconnect ALC_EXT_EFX ALC_EXT_thread_local_context ALC_SOFT_loopback
 * AL extensions: AL_EXT_ALAW AL_EXT_DOUBLE AL_EXT_EXPONENT_DISTANCE AL_EXT_FLOAT32 AL_EXT_IMA4 AL_EXT_LINEAR_DISTANCE AL_EXT_MCFORMATS AL_EXT_MULAW AL_EXT_MULAW_MCFORMATS AL_EXT_OFFSET AL_EXT_source_distance_model AL_LOKI_quadriphonic AL_SOFT_buffer_samples AL_SOFT_buffer_sub_data AL_SOFTX_deferred_updates AL_SOFT_direct_channels AL_SOFT_loop_points AL_SOFT_source_latency
Pausing audio device not supported.
Audio effect extension version: 1.0
Audio max auxiliary sends: 4
java.lang.IllegalStateException: Incomplete draw buffer.
	at com.jme3.renderer.opengl.GLRenderer.checkFrameBufferError(GLRenderer.java:1469)
	at com.jme3.renderer.opengl.GLRenderer.updateFrameBuffer(GLRenderer.java:1634)
	at com.jme3.renderer.opengl.GLRenderer.setFrameBuffer(GLRenderer.java:1775)
	at com.jme3.renderer.RenderManager.renderViewPort(RenderManager.java:1082)
	at com.jme3.renderer.RenderManager.render(RenderManager.java:1150)
	at com.jme3.gde.core.scene.SceneApplication.update(SceneApplication.java:324)
	at com.jme3.system.awt.AwtPanelsContext.updateInThread(AwtPanelsContext.java:200)
	at com.jme3.system.awt.AwtPanelsContext.access$100(AwtPanelsContext.java:45)
	at com.jme3.system.awt.AwtPanelsContext$AwtPanelsListener.update(AwtPanelsContext.java:69)
	at com.jme3.system.lwjgl.LwjglOffscreenBuffer.runLoop(LwjglOffscreenBuffer.java:125)
	at com.jme3.system.lwjgl.LwjglOffscreenBuffer.run(LwjglOffscreenBuffer.java:156)
	at java.lang.Thread.run(Thread.java:745)
Returning hash code of content
Reading welcome page content from web failed!
wiki.jmonkeyengine.org
Checking page id 0 vs stored id 0

But you can execute a normal JME application (through code)?

Yes

I can crash the sdk if I hit edit vehicle on any model or terrain myself. None are vehicles though. No output.

Clicking edit terrain on a regular model just opens the model in the terrain editor.

SDK probably needs a sanity check somewhere.

Edit: 3.1.0-stable SDK

I do not understand why you need integration in NetBeans … after all you can View Model, Edit in SceneComposer, Edit Terrain, Edit Vehicle. Implement as separate applications that will open their file types.

And have how many seperate applications that are created by whom and maintained by whom? Don’t forget his is an open-source project - and other people have created editors such as @Ali_RS

However - I do agree that netbeans is not for everybody. Personally I use intellij. Others use eclipse. Its great that there are so many options - but at the same time - not great. You can’t really win.

I mean that integration into another application is usually a source of not stability.

And not that NetBeans is bad. Drawing in the NetBeans window is not necessary: ​​View Model, Edit in SceneComposer, Edit Terrain, Edit Vehicle.

Ok. So why aren’t you writing this program, or fixing the issues? I’m guessing you don’t have time or (possibly) ability - and this is the same for pretty much everybody else. I’m not complaining that you aren’t fixing the problem - just explaining that if problems are there - it is up to the community to come up with a solution - for free - in their own personal time.

If you can at least provide a test case of some sort - it will help the person that is willing to fix it.

I reported this problem to report the fact. And not with a request to fix it.

For myself, I decided that the SDK is not a stable application, perhaps I will forget about its existence.

I do not think that I have a problem. 3.0 is working.