Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Quality of Bricscad desktop integration

What is you overall experience with BricsCAD under Gnome (Ubuntu 18.04 in my case)? I have just filled a very angry support request about V20, because that "glitch", reported there was just enough. So I want to ask here, if I'am the only person having problems with BricsCAD integration into Gnome desktop? If I compare it with Blender, which is a free software, for example, it is very unflattering ...

Comments

  • First,
    Gnome and KDE are the 2 only Desktop Environments officially supported.
    So Bricscad should run well with Gnome.
    If you find a bug it is totally ok to file a SR and they will fix it.

    It is no secret that you will get the most flawless Bricscad experience on
    Windows only.
    Bricscad's macOS and Linux versions are noticeable behind so far.
    But Bricsys wants to support macOS and Linux although it is a smaller
    user base. So as more people test or use it and file bug reports,
    the better it will get over time.

    The other thing is to see if such problems have really anything to do
    with the Desktop Environment at all.
    My experience is that about 80% of issues in Linux happen on macOS
    as well.

    Beside,
    I think the most Bricscad Linux testing happens on standard Ubuntu/Gnome
    which most Linux users may use. So you are already on the less problematic
    side with your choice.

  • @Vaclav Cermak said:
    What is you overall experience with BricsCAD under Gnome (Ubuntu 18.04 in my case)? I have just filled a very angry support request about V20, because that "glitch", reported there was just enough. So I want to ask here, if I'am the only person having problems with BricsCAD integration into Gnome desktop? If I compare it with Blender, which is a free software, for example, it is very unflattering ...

    I meet some segment fault when I use Bricscad V20 in ubuntu 18.04.3 Gnome environment, the v19 version is much stable. I guess the problems come from the new wxgtk3 and the new dark theme, it may need some time to overcome these bugs.

  • I agree with @Michael Mayer :
    It seems to me that the cross platform GUI libraries used for BricsCAD (wxwidgets?) have migrated from depending on GTK2 to GTK3 (a natural development) starting with V20 and it has introduced some new bugs and glitches in the GUI. Let's help out and file reproducible support requests for the issues found asap (I filed a bunch of them today) and hopefully we can get most of them fixed in a point-release without much delay.

    During initial testing of v20 at our office; we noticed that the GUI flickers considerably with v20 (compared to earlier versions of BricsCAD) when panels and toolbars are rebuilding during startup, or when shifting workspace. This flickering can leave traces and produce some tearing of static GUI elements on the screen unless VSync is taken care of by the configuration of your compositor.
    We don't use Gnome or KDE/Plasma (yet.. but most likely Plasma in a couple of years) on our workstations. We are using compton as our compositor and the following compton settings work well for our AMD GPUs using the open source driver:
    $ compton -CcG -o 0.1 --backend xr_glx_hybrid --vsync opengl-swc --vsync-use-glfinish &

    (Yes I know VSync, and if Linux and xorg use true vsync or not, can become an endless discussion: But unless you are playing games on your computer and the only thing you care about is frame rates, then making sure frame updates on your screen is vertically synchronized will most likely produce the best results, even if frame rates can be somewhat lower.)

  • Let's help out and file reproducible support requests for the issues found asap (I filed a bunch of them today) and hopefully we can get most of them fixed in a point-release without much delay.

    Thanks for supporting.

    AFAIK I had that flickering and tripple times GUI rebuilding for any
    Bricscad Versions (V18-V20?) on Linux and macOS.
    Especially after customizing UI and closing the dialog.
    In V20 just a few more issues related to dark mode or HiDPI screen.

  • I did not notice real progress on the GUI related problems, from the first V20 beta until the recently released V20.3.
    But I am quite far on the unsupported side (running debian 10 with LXDE desktop on an aging macbook 6.1 with the nouveau driver), and cannot really bother support with this - so I am wondering and asking here:
    Would I be better off on ubuntu / gnome / proprietary drivers, or are the following glitches plaguing all Linux users:

    • wrong floating toolbar sizes
    • wrong command completion pop-up size
    • truncated helpstrings in the commandline
    • menus not scrollable
    • panels not horizontally scrollable
    • 100% CPU load while displaying the GUI-menu (right-clicking on the menubar / the panelbar)
    • floating toolbars / panels not dockable via dragging
    • doctabs showing even if SHOWDOCTABS = 0
    • RGB-color-chooser not accepting numeric input
    • gtk-theme settings overridden, sometimes resulting in unreadable text

    See attached screenshots.

    helpstrings.png
    1280 x 800 - 146K
    toolbars_panels_autocomplete.png
    1280 x 780 - 70K
    notification.png
    462 x 150 - 16K
  • Here things like :

    • Start Screen (showing Panels ON)
      Showing 2D Drafting Layout which I never used instead of current BIM Layout.
      Linux and Mac.

    • Numbers shifted horizontally inside DYNDIMS so they are hard to recognize.
      Linux (at least with HiDPI scaling on 4K Monitor)

    • Custom added Panels and/or Access(3D) Panels disappearing from Workspace
      every once in a while.
      Mac.

    • Unexpected Crashing or Freezing in any kind of situations.
      (V20.2.03-1 is really a crash Monster for me)
      At least on macOS Mojave.
      (While Windows version works like a charm)

    • Structure Tree in crowded Files :

    • Select + SHIFT Select impossible, does another click on last selected which
      destroys you selection.
    • Collapse Tree when unselect ON : does not resize Scrollbars and Window Space,
      You have to Scoll Up back manually to find your collspased Tree on top.
    • Also it does not switch back horizontally after it opened many branches in depth
      even those were already closed. Needs manual back movement to the left.
      (At least on Mac)
    • Structure Tree, Expand on Selection Settings Deactivated - Ignored
      (All OS)

    I think the likeliness to have less flaws when using a standard Ubuntu/Gnome
    is larger opposed to more exotic Distros/DEs, but Bricscad on Windows is still
    a completely different and better experience, even with roughest Betas.

    Officially supported are Ubuntu and Open Suse (including Tumbleweed)
    and Gnome and KDE Desktops.
    So it is pretty useless to bother Support with my (beloved) Manjaro (Arch/KDE)
    problems. But everything Ubuntu/Suse/Gnome/KDE stuf will be worked on.

    If thee Problems would only be reproducible by myself or Support.
    There are only few situations where I could provide an SR with more than
    just a Crash Log from macOS.

  • edited March 22

    My experience with Linux Distributions.
    Beside some little Problems, that were all solvable for me,
    me as a Linux Newbie, managed to still keep running my Rolling Releases :
    mainly Manjaro and Open SUSE Tumbleweed,
    since 1 ½ years.

    While I lost all non-rolling Releases, like ElementaryOS, MX LInux and
    Ubuntu, while trying to do a version Upgrade sooner or later for some reasons.
    Beside that I am excited about newest Software and Kernels new features
    in general, when I started with current PC hardware at that time there
    wasn't even an option to run it stable with old LTS stuff.

    The second try with my ElementaryOS
    (OK, has its exotic Pantheon Desktop, Gnome derivate)
    is still ok for now and I enjoy the Ubuntu-ness behind it, for better
    proprietary Software's support like Bricscad.
    I think Bricscad's Ubuntu DEBs are still easier and more reliable for
    installation than RPMs on Suse overall.
    But if I am forced to Ubuntu and could live ancient LTS Kernels, I think
    I would go with Kubuntu or Plasma.

    BTW,
    All 3D Apps I know, like Modo, only officially support CentOS/RHEL,
    which seems to be a common standard in 3D Studios.
    (While Modo somehow runs equally well on any Distribution and
    Desktop Environment for whatever reason)

  • Hello Michael,
    do I understand correctly that you did not experience the glitches that I described with the distros that you use?

    As to the problems that you mentioned:

    • I also see the GUI opening with some standard toolbars, and then rebuilding without them (I don't use any toolbars). The cui command sometimes triggers even wilder iterative repainting of the GUI, I do not really understand what is happening here.

    • Dynamic dimension display seems to be affected by the gtk settings used, perhaps it makes sense to try several themes (you can put several startup scripts with different settings in $home/.local/share/applications, e.g. with lines like Exec=env GTK_THEME=Numix:dark bricscadv20 %F . I also made an attempt to tweak settings by looking at the interface elements with gtk-inspector, but I could not find any class names or id that would have allowed me to use css formatting.

    • The GUI configuration is as fragile as it was on V19, I try to avoid touching it whenever I can.

    • Stability of V20 is not so bad on my box.

    • I cannot comment on the structure browser, I have hardly used it so far.

  • Honestly you mentioned a lot of things I normally don't use,
    (floating toolbars, commandline, ...) or just did not try yet.
    Well, trying the color chooser would be interesting for me too.
    (EDIT : numeric input works for me on Mac.
    Although an ENTER directly closing the Dialog is a bit unexpected for me in Bricscad)

    a)
    AFAIK Windows will show your current(*) GUI in Start Screen
    (or most parts of it, at least it looks familiar)

    (* Or the one you choose before in welcome screen)

    b)
    DYNDIM,
    yes, bei GTK overlay and or HiDPI scaling or whatever.

    c)
    Me too.
    It is so scary. I think last time I tried its started blinking again also
    I canceled customize UI dialog again.

    d)/e) ...

    I have my 2 activations on my old nMac Pro and on the Windows Machine.
    So when trials end I use/test Bricscad on Linux only in free Shape Mode.
    As I am still not that confident that I could not likely lose one of my Linux
    installations, as a Linux newbie.
    I want to avoid the license issues. I already lost one activation when I lost
    my Windows in the past.

    But my Experience is that Bricscad Windows works great and reliable as
    you would expect from a proprietary App.
    For Mac and Linux I think they have basically the same or similar amount
    of GUI flaws and unexpected crashes, while Linux for me feels a bit more stable.
    So I mostly play with Bricscad non-Windows on Mac only,
    but I always see both Linux and Mac Version as the same or pretty similar.

  • Yes, user experience on windows is so much better.
    I fully understand that the amount of developer hours that can be put into the Mac and Linux versions is limited, but it still gets frustrating sometimes...

  • I think it is both,
    the amount of meaningful investement according user base and
    the smaller user base amount and quality of feedback and reports.

    But I see the latest work they do and really appreciate things like
    - nearly feature parity between operation systems
    - synchronized release of OS versions at the same time

    Often frustrating and pity, yes,
    but somehow I am confident that it gets better over time and not worse.

  • Regardless of which operating system is being used, is anyone receiving any feedback when they report an incident and the initial analysis confirms a need for development to correct a problem?

  • Everytime I report an incident I get a response from the technical team. The correction of the problem is usually implemented in the following update. I once even got some help in the development of a VBA program to generate beam reinforcement from an Excel spreadsheet.
    Great customer service and tech support.

  • I get an initial response and if what I reported is an actual bug the last thing I get is a message that it's been sent to development. Nothing after that.

    I don't see a lot of incentive to spend my time testing, reporting, developing videos of a session that clearly demonstrates a failure, more testing as requested by support, more reporting and to simply have the whole thing drop with no progress report or a statement that the bug is fixed in such and such release.

    From my perspective support looks like a black hole where things go in and nothing comes out. The fact that something gets fixed is fine, but the lack of communications is an issue.

  • What you describe is exactly what I had in mind when I talked about my occasional frustration.
    I guess it remains to be seen if Bricsys can uphold its commitment to Linux after the acquisition by Hexagon.

  • I'am experiencing similar problems with Ubuntu 18.04. I have filled SRs about various glitches, got a quick replay from support team for every single one. Although I filled them one regular and one beta release ago, none of them is fixed yet :-/. I decided to wait for Ubuntu 20.04, because some of problems may be fixed by Gnome update (I hope).

  • @Mikael Nordvall said:

    It seems to me that the cross platform GUI libraries used for BricsCAD (wxwidgets?) have migrated from depending on GTK2 to GTK3 (a natural development) starting with V20 and it has introduced some new bugs and glitches in the GUI.

    Agree.
    When I start Bricscad from Terminal on Tumbleweed,
    the Terminal Window fills with lots of GTK Warnings.

    FreeCAD is interesting and promising, but like many other essential
    open source Software like GIMP, far from the Software state and
    Development situation of a shiny Blender beacon.
    Bricscad on the other hand, so far, is still the only professional CAD solution
    on Linux. If there is any small CAD market on Linux, Bricscad has that whole
    market.

  • V20.02.xy actually works for me now under plain vanilla Ubuntu (v20.01.xy were not). I am quite happy with it as CAD was one of the main reasons locking our consultancy office into Windows-world, migrating to linux got one step closer again.

    Personally my main annoyance with BricsCAD is how it (mis)handles focus: if one tries to edit text (especially in a table) the focus is on the foating window on the text style tab by default, so one has to press tab twice to be able to enter text. It is incredibly annoying filling in a massive table with lots of data (copy-pasting is not working... incredibly annoying again).
    Does any of you has this same problem? Even better maybe a solution for it?

    Cheers.

  • edited March 30

    Yes, focus is another big problem in Bricscad. Often I can't even write a command, because focus changes while typing and I see some characters written last sitting at the beginning in command bar. I must type it very slowly :(.

    Personally, I'am waiting for Ubuntu 20.04, with a new Gnome, it may improve a lot (I hope). Then I'll fill support requests for such things, if they persist.

Sign In or Register to comment.
Origami
Origami is the Japanese word for paper folding. ORI means to fold and KAMI means paper and involves the creation of paper forms usually entirely by folding.

Powered by VanillaForums, Designed by Steam