ebiten: on Windows 10 remote desktop not work.

I use Ebiten v1.9.3 and Golang 1.12 on Windows 10 Pro 1809. The following error occurred when trying to display the Ebiten window on the remote desktop PC.

panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x4f1262]

goroutine 1 [running, locked to thread]:
github.com/hajimehoshi/ebiten/internal/glfw.(*Window).GetMonitor(0x0, 0x0)
	D:/sample/vendor/github.com/hajimehoshi/ebiten/internal/glfw/glfw_windows.go:135 +0x42
github.com/hajimehoshi/ebiten/internal/ui.(*userInterface).currentMonitor(0xa5f180, 0x15decd4)
	D:/sample/vendor/github.com/hajimehoshi/ebiten/internal/ui/ui_glfw.go:955 +0x36
github.com/hajimehoshi/ebiten/internal/ui.glfwScale(0xc00005c2a8)
	D:/sample/vendor/github.com/hajimehoshi/ebiten/internal/ui/ui_windows.go:105 +0x34
github.com/hajimehoshi/ebiten/internal/ui.initialize(0xf, 0xc00009d140)
	D:/sample/vendor/github.com/hajimehoshi/ebiten/internal/ui/ui_glfw.go:116 +0x122
github.com/hajimehoshi/ebiten/internal/ui.init.0()
	D:/sample/vendor/github.com/hajimehoshi/ebiten/internal/ui/ui_glfw.go:89 +0x2e

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 24 (13 by maintainers)

Commits related to this issue

Most upvoted comments

No. I understand you suggested Vulkan instead of DirectX, but as Ebiten’s graphics usage is very limited, I feel like using DirectX directly should be enough. Actually I’ve succeeded to port the graphics driver to Metal in Ebiten.

Again, as I said, I don’t plan to use Vulkan on Windows 😃

https://github.com/Think-Silicon/GLOVE

Or MoltenVK? I know there are such translating layers, but as Ebiten’s graphics usage is very limited, writing code that uses DirectX should not be so painful.