Dust3D is a cross-platform open-source 3D modeling software

I'm trying dust3d on a GNU/Linux 64bit system, and it just crashes when I click on the "+" tool and click on the screen to place it. Here's a stack trace when that happens:

#0  0x00007ffff66ac090 in QOpenGLContext::shareGroup() const () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#1  0x00007ffff69bec3a in QOpenGLFunctions::initializeOpenGLFunctions() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#2  0x00007ffff69c2b2d in QOpenGLFramebufferObject::QOpenGLFramebufferObject(QSize const&, QOpenGLFramebufferObjectFormat const&) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#3  0x000055555558acb0 in ModelOfflineRender::toImage (this=0x555555ade960, size=...) at src/modelofflinerender.cpp:52
#4  0x000055555560b090 in MeshGenerator::process (this=0x555555ca4330) at src/meshgenerator.cpp:377
#5  0x00005555555b4d35 in QtPrivate::FunctorCall<QtPrivate::IndexesList<>, QtPrivate::List<>, void, void (MeshGenerator::*)()>::call(void (MeshGenerator::*)(), MeshGenerator*, void**) (
    f=(void (MeshGenerator::*)(MeshGenerator * const)) 0x555555608e9e <MeshGenerator::process()>, o=0x555555ca4330, 
    arg=0x7fffdc913970) at ../../../include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:136
#6  0x00005555555b283f in QtPrivate::FunctionPointer<void (MeshGenerator::*)()>::call<QtPrivate::List<>, void>(void (MeshGenerator::*)(), MeshGenerator*, void**) (
    f=(void (MeshGenerator::*)(MeshGenerator * const)) 0x555555608e9e <MeshGenerator::process()>, o=0x555555ca4330, 
    arg=0x7fffdc913970) at ../../../include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:169
#7  0x00005555555ad871 in QtPrivate::QSlotObject<void (MeshGenerator::*)(), QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x555555b60060, r=0x555555ca4330, a=0x7fffdc913970, ret=0x0)
    at ../../../include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:398
#8  0x00007ffff61352af in QMetaObject::activate(QObject*, int, int, void**) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007ffff5f184d7 in QThread::started(QThread::QPrivateSignal) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007ffff5f1eb36 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007ffff5bc9f2a in start_thread (arg=0x7fffdc914700) at pthread_create.c:463
#12 0x00007ffff57c9edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

I attached a gzipped core dump core.gz

Problem

The text is difficult to read in the UI on high DPI displays.

Repro

1. Set the DPI scaling of your operating system to 100%
2. Observe the text size of Dust3D
3. Set the DPI scaling of your operating system to 150% or 200%
4. Observe the text size of Dust3D

Expectation

I expected the text size of Dust3D to scale with the operating system's DPI.

Actual

The text size of Dust3D remains relative to the resolution of the display.

Related

• #1

References

• http://doc.qt.io/qt-5/highdpi.html#migration-of-existing-applications

Problem Nothing happens when I try to load an image to be used as reference sheet. The program works but the canvas stays blank. No errors, alerts or dialogs of any kind.

Steps followed

1. Open the program.
2. File -> Change Reference Sheet...
3. Select any JPEG image file of any size or type. I also tried the ones from the modeling examples like the ant and the horse.
4. Canvas stays blank.

System description Dust3D 1.0.0-beta.6, Windows 10, NVidia GTX1060, 16 GB Ram

having difficulty with appimage atm. using chromeos with crouton. I tried blender's flatpak but it runs slow (cheap processor) this would probably be my best bet for lightweight app to study 3d modelling.
being able to find this over at flathub.org would be awesome. thanks

I found out that the icon name for Dust3D was called icon on the icon line of the desktop file. https://github.com/huxingyi/dust3d/blob/master/ci/dust3d.desktop https://github.com/huxingyi/dust3d/blob/master/ci/icon.png

Could the icon be renamed to dust3d for icon themes?

When compiling dust3d I was greeted with this glorious error:

src/meshgenerator.cpp:396:20: error: converting to ‘bool’ from ‘std::nullptr_t’ requires direct-initialization [-fpermissive]
             return nullptr;

Here is the compile log

I did a quick search and this was a set feature from gcc <5. I was using gcc 8.2.3 to compile.

Either fix the error or add to the requirements that you need gcc-4.9.

The *.desktop file is lacking a Categories= entry.

According to the menu spec,

By including one of the Main Categories in an application's desktop entry file, the application will be ensured that it will show up in a section of the application menu dedicated to this category. If multiple Main Categories are included in a single desktop entry file, the entry may appear more than once in the menu.

Hence, please add at least one of the following in the Categories= key.

Main Category | Description | Notes -- | -- | -- AudioVideo | Application for presenting, creating, or processing multimedia (audio/video) |
Audio | An audio application | Desktop entry must include AudioVideo as well Video | A video application | Desktop entry must include AudioVideo as well Development | An application for development |
Education | Educational software |
Game | A game |
Graphics | Application for viewing, creating, or processing graphics |
Network | Network application such as a web browser |
Office | An office type application |
Science | Scientific software |
Settings | Settings applications | Entries may appear in a separate menu or as part of a "Control Center" System | System application, "System Tools" such as say a log viewer or network monitor |
Utility | Small utility application, "Accessories"

In addition, you could specify one or more from the longer list of Additional Categories.

Please test the result with desktop-file-validate and make sure it passes.

electron-builder offers native support for this since v19.22.1.. Please see the category key at https://www.electron.build/configuration/linux-other.

References:

• https://github.com/AppImage/appimage.github.io/issues/2
• https://github.com/AppImage/appimage.github.io/pull/645

Hi,

Neat little program you have here! However, a minor issue is preventing me to use it in a laptop. You see, the previewed mesh is manipulated with the middle mouse button, which laptops don't have. So, could you please provide some other means to manipulate it? Like, using the mouse with ALT, or something like that (like Blender does).

Thanks, and great job so far!

Paul

3d model manipulation is slow and choppy. It freezes constantly when trying to move, rotate or zoom the generated 3d model. My PC specs are: System: Windows 10 CPU: i7 8700k GPU: RTX 2080 RAM: 64GB

seems related to: https://github.com/maxrd2/subtitlecomposer/issues/117 which says: Solution: Please do not bundle

'libxcb-dri3.so.0'
'libxcb-dri2.so.0'

Hello! I tried the unstable release version on Windows 7 64 bits and it shows a blank screen and the toolbar is black.

I'm using: Intel Core i5 2500k Intel HD Graphics 3000

Screenshot:

I try to launch Dust3D with QT_QPA_PLATFORM=wayland ./dust3d-1.0.0-rc.6.AppImage. This is the return I am getting in the terminal:

$ QT_QPA_PLATFORM=wayland ./dust3d-1.0.0-rc.6.AppImage
This application failed to start because it could not find or load the Qt platform plugin "wayland" in "".

Available platform plugins are: xcb.

Reinstalling the application may fix this problem.
Aborted (core dumped)

Without native Wayland support, the app UI is very blurry.

About info:

Dust3D 1.0.0-rc.6 (version: 1.0.0.36 build: Apr 12 2020 11:22:47)
opengl: 4.6 (Core Profile) Mesa 22.1.7 shader: 4.60 core: true

I am running the app on openSUSE Tumbleweed.

Hi! Tell me why the wireframe is not displayed? I've tried different releases.Thanks for the answer Os debian 11 help/about : Dust3D 1.0.0-rc.6 (version: 1.0.0.36 build: Apr 12 2020 11:22:47) opengl: 2.1 Mesa 20.3.5 shader: 1.20 core: true

In file included from /wrkdirs/usr/ports/graphics/dust3d/work/dust3d-1.0.0-rc.6/thirdparty/instant-meshes/instant-meshes-dust3d/ext/tbb/src/tbb/itt_notify.cpp:47:
In file included from /wrkdirs/usr/ports/graphics/dust3d/work/dust3d-1.0.0-rc.6/thirdparty/instant-meshes/instant-meshes-dust3d/ext/tbb/src/tbb/tools_api/ittnotify_static.c:21:
/wrkdirs/usr/ports/graphics/dust3d/work/dust3d-1.0.0-rc.6/thirdparty/instant-meshes/instant-meshes-dust3d/ext/tbb/src/tbb/tools_api/ittnotify_config.h:329:12: error: use of undeclared identifier '__TBB_machine_fetchadd4'
    return __TBB_machine_fetchadd4(ptr, 1) + 1L;
           ^
1 error generated.

Log: http://ampere2.nyi.freebsd.org/data/main-arm64-default/pcfc0b7a81f2e_s7e45839aca/logs/dust3d-1.0.0.r.6.log (IPv6 URL)

Version: 1.0.0.r.6 FreeBSD 14-CURRENT

Hi Jeremy, as I first met Dust3D (about half an hour ago) I couldn't believe my eyes: in a 3Dworld where hardware and software are glibly overloaded with zillions of useless vertices and surfaces, a piece of software dedicated to creating good low-poly models is really a rare pearl.

Unfortunately though I'm tied to my good old (ancient?) Win XP - mostly but not only because I like to stay master and commander on my own ship - and as such I found out all too soon that even the 32-bit version of Dust3D won't run on it - despite Dust3D's "multiplatformity".

Do you see any way I could escape this impasse without having to downgrade to a new but not necessarily better Windows version?

Thanks!

Gilbert

After some uses the app won't open and even though I have deleted and copied again the files. The app window opens but there is only a white screen and despite waiting nearly 30 mins it won't change and says app not responding. Any idea of why could it be? do you need a log or something?