Build when game window is opened takes more time

Not sure what is the reason, but when the game window is opened and instead of hot reload you use build or rebuild it takes more time to show game content in the window, meanwhile at this time window is black. Without opened game window it started much faster.

Not sure if it is related, but I have persistent warning WARNING:INPUT: No gamepad map found for gamepad 0 (keyd virtual pointer). The raw gamepad map will be used.in the console window. I’m using https://github.com/rvaiya/keyd remapping daemon and it seems like defold detects it as some kind of connected gamepad? This black screen is always happening right before this warning. But when I build without opened game window even though this warning is still present window started without this black screen.

Is it possible to not increase debug build time with black screen? (Can you confirm that it doesn’t happen for you?)
How I can fix mentioned warning?

Also seldom there is error when trying to debug build, when using camera in the collection

ERROR:SCRIPT: builtins/render/default.render_script:71: bad argument #1 to '__mul' (matrix4 expected, got nil)
stack traceback:
  [C]:-1: in function __mul
  builtins/render/default.render_script:71: in function update_camera
  builtins/render/default.render_script:90: in function update_state
  builtins/render/default.render_script:218: in function <builtins/render/default.render_script:212>

Could you please explain a bit more what you are doing when it happens? You mentioned trying to debug a build. Is it when you hit a breakpoint? Or when you resume again?

This is the issue: Loading resources is slow if engine is restarted via editor · Issue #4116 · defold/defold · GitHub

@jhonny.goransson was recently investigating this issue and there is a draft PR to fix some issues: https://github.com/defold/defold/pull/9475

Sorry, I’m mixing some terms here. Just when building with Ctrl-B. It happens more often when you fast close a game window, and then build again. It doesn’t happen too often to be a problem, but can get it few times in a session.

Ok, thanks. It seems like there’s an issue when rebooting the engine and perhaps rendering a frame inbetween shutdown and restart when the camera has no view or something… :thinking: If it starts happening more often or if it becomes a problem in some other way please report it on GitHub!