Jump to content


Photo
- - - - -

UI - status / progress of current operation


  • Please log in to reply
4 replies to this topic

#1 3dworks

3dworks

    Advanced Member

  • Members
  • PipPipPip
  • 336 posts
  • LocationBerlin, Germany

Posted 20 November 2016 - 04:41 AM

i didn't find it in this long list of suggestion, but i remember it was in the archived forum: everyone here knows that some of FZ's operations are SLOW. what makes frustration rise to a higher level is that most of the times we don't know what FZ is actually doing. even checking CPU activity can lead to wrong interpretations. is it in an endless loop or is the operation finished in 10 seconds? if you decide to force - quit after 10 minutes of waiting and seeing a colored ball  is no good.

 

please implement progress bars, text status or whatever shows that status of operation ongoing in the next version. apart from opening a or importing geometry almost no operation has currently status display.

 

right now i am pasting a complex setup of components (a completely furbished office room with around 50 components) from one project into another and waiting for 20 minutes with a ...colored wheel. should i force quit or wait?

 

markus


Edited by 3dworks, 20 November 2016 - 04:44 AM.

  • bestdoci, Harrybow, Williamsek and 4 others like this

3dworks visual computing + photography


#2 Tech

Tech

    Moderator

  • Moderators
  • 4,110 posts

Posted 21 November 2016 - 11:12 AM

Hi Markus,

 

Thanks for your suggestions, we will see if these can be added for the future.

 

If you have an operation that is taking longer than you would like, feel free to email the file and the details and we will see what we can do to improve that performance as well.  ;)



#3 3dworks

3dworks

    Advanced Member

  • Members
  • PipPipPip
  • 336 posts
  • LocationBerlin, Germany

Posted 21 November 2016 - 01:18 PM

dear FZ tech support - almost all operations with massive geometry are taking too long. maybe it's a mac problem? if for example i mirror a selection of complex furniture components (about 12 times a set of 6 high detailed furniture sets) i am waiting about 10 minutes for FZ to become responsive again. if i did an error and make undo, it's about 20 min to go back. and this using a dedicated SSD scratch disk and 48 G of RAM. in my opinion it's more a general design problem of the software. honestly, i've checked the famous software named after a massive animal starting with R lately and must say that this kind of geometry is no problem there - also on mac, with the same hardware. all operations are almost instant and responsive, even when using a shaded view mode. what can i say...

 

btw my model makes FZ use about 4,5G of RAM, so it isn't an unreasonable amount of geometry i'm handling...

 

cheers - hoping for some speed up in the near future.

 

markus


Edited by 3dworks, 21 November 2016 - 01:19 PM.

3dworks visual computing + photography


#4 rich f

rich f

    Advanced Member

  • Members
  • PipPipPip
  • 55 posts

Posted 21 November 2016 - 02:27 PM

FormZ performance has always been kid of laggy on how it handles large numbers of objects.... one old trick is to disable undo before you undertake such an operation. That can help tremendously in certain situations. Be sure to save first in case you don't like the result or need to force quit. In addition I've long had a habit of making sequential saves fairly often.

 

If you are merging a large file the "add to project" option can be faster than copy/paste. (delete what you don't need from the first project, save a temp file and add that to the second project.)


  • 3dworks likes this

#5 Tech

Tech

    Moderator

  • Moderators
  • 4,110 posts

Posted 21 November 2016 - 02:35 PM

Hi Gentlemen,

 

Thanks for this info, we will see what we can do to improve this.

 

Different data sets (different types or groupings, components, geometry, smooth or facetted, etc) can benefit from different optimizations and there are some trade offs.  If at all possible, if you could send in a file or two that are typical of the types of projects that you are working with when you notice this issue, we can use them to better tune our optimizations. 

 

Thanks in advance!  ;)






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users