Thanks, upload beta version to playmarket. Now it worked, no more warnings.
1 Like
Thanks, I’ll have a look!
(I’m on vacation though, so I’m not sure when I can get to it…)
3 Likes
Update with the fix will be available in ~1h.
3 Likes
The bottom window (Console/Curve Editor/Build Errors/Search Results) goes to like 99.9% height when the editor window width changes to such a value that the “game view” area width becomes 0 and then returns to “normal” on Linux with Wayland (Hyprland).
When I briefly open another window next to the editor window and then I close that window I need to resize the console area every time.
Is this a regression from 1.10.3?
Oh. Seems to happen with earlier versions too, so no.
One strange thing I’ve noticed with this version: when I have the game objects expanded in a collecion in the editor, right clicking on the game object sometimes instead of showing the contextual menu, opens up the script associated with the game object directly.
If I repeat the operation then the menu is shown and it works as expected for a while before repeating.
It’s very random, so quite difficult to find a pattern.
This is on OSX 15.5 with the 1.10.4 beta
2 Likes
Question about configuring the grid in the XZ plane: I am having difficulty setting it up, i.e. the grid almost disappears when I rotate the camera to the default view in 3D editors (Blender, etc.):
It is only visible when viewed from above:
(the small grid under the model’s feet is mine, which I used earlier)
2 Likes
Thanks for the report. It looks like a regression introduced by the rename enhancement.
Will be handled here Right clicking after selecting an outline node might trigger file open · Issue #11018 · defold/defold · GitHub
3 Likes
That is a known issue that is now more prominent, because you can use the grid on 3D scenes. We plan to tackle this soon. For now, increasing the opacity could mitigate this (up to a point).
4 Likes
I cannot reproduce this. Since that’s not a regression, could you please open a GitHub issue with some additional info about your system?
3 Likes
A fix is now included in the latest beta build.
6 Likes
Kind reminder: 1.10.4 will be released next week.
Please test the beta in your projects 
4 Likes
Was this message addressed to me or to @d954mas ?
I missed this your message, sorry. I’ll take a look
@sergey.lerg it seems like you use pretty old texture packer extension. Please, update extension to the latest version.
(The error you see is related to Bob API which was removed half a year ago, here is PR that fixes it in TexturePacker )
1 Like
Thanks, I tried it again and now it works
I did update the extension when I was having this issue and clicked to fetch the libraries, maybe I just needed to restart the editor, sorry for the false alarm.
5 Likes
sys.reboot doesn’t work for me
INFO:DLIB: Log server started on port 50063
INFO:ENGINE: Target listening with name: DESKTOP-PPO5QNJ - ::1 - Windows
INFO:ENGINE: Engine service started on port 50064
INFO:GRAPHICS: Installed graphics device 'ADAPTER_FAMILY_OPENGL'
INFO:ENGINE: Defold Engine 1.10.4 (b11d2b6)
INFO:PROFILER: Initialized Remotery (ws://127.0.0.1:17815/rmt)
INFO:ENGINE: Loading data from: build/default
INFO:SOUND: Mix format:
INFO:SOUND: wFormatTag: fffe IEEE_FLOAT/PCM/EXTENSIBLE: 3 / 1 / fffe
INFO:SOUND: nChannels: 2
INFO:SOUND: nSamplesPerSec: 48000
INFO:SOUND: nAvgBytesPerSec: 384000
INFO:SOUND: nBlockAlign: 8
INFO:SOUND: wBitsPerSample: 32
INFO:SOUND: -> Format: 3 IEEE_FLOAT/PCM/EXTENSIBLE: 3 / 1 / fffe
INFO:SOUND: DSP backend: SSE
INFO:SOUND: Sound
INFO:SOUND: nSamplesPerSec: 48000
INFO:ENGINE: Initialised sound device 'default'
INFO:DLIB: SSDP: Started on address 192.168.0.24
INFO:ENGINE: Defold Engine 1.10.4 (b11d2b6)
Assertion failed: g_Remotery == NULL, file ..\src\remotery\lib\Remotery.c, line 7025
INFO:CRASH: Successfully wrote Crashdump to file: C:/Users/27C6~1/AppData/Roaming/Defold/_crash
_crash.zip (1.7 KB)
test.zip (9.5 MB)
4 Likes
Thank you for this report. The fix is on its way and will be available in ~1h.
3 Likes
I wanted to try out the new HTML5 Performance profiler, but unfortunately, it doesn’t show symbol names in my case. Most of the call stack consists of wasm-function[123]. What am I doing wrong?
1 Like