Black Screen on when attempting to render UI text in editor on 1.2.87 (SOLVED)

Questions
#1

I was changing the layout of my game to test it out on an android device when I ran into a render bug on the GUI screens. The screen is black except for any gui nodes that rendered before the text attempted to render. Deleted the text allows the gui to render correctly (Though adding new text areas to replace the old ones causes the issue again). When I launch the game, text renders correctly.

Stack Strace:

java.lang.LinkageError: com/dynamo/bob/font/Fontc$InputFontFormat
at com.dynamo.cr.guied.ui.TextNodeRenderer.render(TextNodeRenderer.java:294)
at com.dynamo.cr.guied.ui.TextNodeRenderer.render(TextNodeRenderer.java:1)
at com.dynamo.cr.sceneed.ui.RenderView.doRender(RenderView.java:749)
at com.dynamo.cr.sceneed.ui.RenderView.renderNodes(RenderView.java:799)
at com.dynamo.cr.sceneed.ui.RenderView.render(RenderView.java:739)
at com.dynamo.cr.sceneed.ui.RenderView.paint(RenderView.java:718)
at com.dynamo.cr.sceneed.ui.RenderView.access$3(RenderView.java:699)
at com.dynamo.cr.sceneed.ui.RenderView$1.run(RenderView.java:693)
at org.eclipse.swt.widgets.Display.runTimer(Display.java:4270)
at org.eclipse.swt.widgets.Display.messageProc(Display.java:3357)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2546)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3756)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at com.dynamo.cr.editor.Application.start(Application.java:42)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)

Session Data:
eclipse.buildId=unknown
java.version=1.8.0_05
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86

Running Windows 10.

#2

Does this happen for different fonts or a specific one? I have never seen this error before, and googling it makes it seem like something that would happen for everyone. I just verified I could create text nodes with the builtin system font.

#3

It seems to be any font. I just did a test where I added a new gui script and added a text area to it and then the system_font. This was the result

renderbug.png1920×1040 142 KB

That text only seems to appear because of the box I accidentally added too. No box, no text.

#4

So did a bit of searching on the forum and found this : Blank GUI screen which was never answered but did lead me to some info that might be useful. The newest version of openGL my computer can support is 4.4

#5

Updating my graphics driver seems to have fixed the issue. No release notes mention a change that would make 4.4 not work. Was there an update that did so?

#6

Not that I know of. @sven?

#7

As far as I know the editor does not require any higher OpenGL version than 2.1, maybe 3.0 at the highest.

Might just have been a bug in your graphics driver?

#8

It is a possibility. Anyway, I’m glad that it seems to be resolved. Hopefully it doesn’t occur again.

1 Like
#9

I had exactly the same problem. To solve it I created a folder on my c:/ - drive and copied / extracted a fresh copy of defold to it. et voilà - problem permanently solved. (I’m on windows 10 with the newest opengl and graphic drivers)