Thanks to the many testers for providing feedback on the desktop app we now have a more stable version. DroneBlocks Desktop 0.1.8 has the following fixes:
Thank you for the updated. The abort button does reset to the beginning of the program and will take off but will not run the next code after take off. It will start then just land. I am not sure if anyone else is experiencing this behavior
Great question. As of right now Windows 10 and Mac 10.13+ but not certain about specific hardware requirements. We are working to optimize the video feed which does take a fair amount of processing. Are there any specific systems you’re trying to target?
Nothing specific, but we work with schools using this program and we want them to know the exact requirements as to not be surprised by older computers not working. Windows 10 should be fine.
Hi DroneBlocks dev team. Thank you for re-uploading a working build of v0.1.8 so quickly. The exe now works. However, all previously saved missions created with v0.1.6 are no longer present in v0.1.8. They are still retrievable in v.0.1.6. The My Missions portion in v0.1.8 is completely blank. Has anyone else experienced this?
Hello development team! I have a problem with entering the menu in the Windows version. The menu simply does not open. This was the case in version 0.1.6 and unfortunately remained in version 0.1.8. The menu works in the Mac version. Maybe I’m doing something wrong?
Thanks @adam for the suggestion. That definitely sounds like @Sergij problem. We need to make this more clear as it would be nice if the menu expanded when it’s collapsed into “hamburger” mode.
My district uses Duo Security which needs authentication to occur for Droneblocks Windows version 0.1.8 to run. This Windows version hangs at authentication.
See pictures for the Beta version and the hanging screen.
Thank you so much Adam and Dennis. I made sure the menu works in full screen mode. But it would be nice if the menu worked when folded into a “hamburger”
Just a tiny bug I noticed with the Mac version. If you close the app using the red close button and then try to reopen it from your dock you get the following error messages:
Uncaught Exception:
Error: bind EADDRINUSE 0.0.0.0:8889
at node:dgram:351:20
at process.processTicksAndRejections (node:internal/process/task_queues:84:21)
Uncaught Exception:
Error: bind EADDRINUSE 0.0.0.0:8890
at node:dgram:351:20
at process.processTicksAndRejections (node:internal/process/task_queues:84:21)
Uncaught Exception:
Error: listen EADDRINUSE: address already in use 127.0.0.1:3000
at Server.setupListenHandle [as _listen2] (node:net:1372:16)
at listenInCluster (node:net:1420:12)
at GetAddrInfoReqWrap.doListen [as callback] (node:net:1559:7)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:73:8)
I would assume that this has something to do with the port connection not being closed when you close the window but I’m not sure. It works fine on first start up and is easily fixed by completely closing the program and restarting but I know how kids can be and wanted to flag it for y’all.
Great work overall and congrats on the Windows app release!
Thanks for pointing this out. We need to figure out how to terminate the connection when the red X is closed. I’m not 100% sure if we can do this but will look into it. We are working to get a version submitted to the Mac App Store soon and we’ll share when we do.
