Jump to content


Photo

Please sort out the component system


  • Please log in to reply
10 replies to this topic

#1 bbuxton

bbuxton

    Advanced Member

  • Members
  • PipPipPip
  • 35 posts

Posted 11 November 2017 - 04:19 AM

Seriously it is the worst block/symbol/component system of any 3D application I have ever come across.

 

What is the point of a component if moving or rotating either edits the original definition or explodes the instance or creates a new definition?

 

Component transforms should not be considered edits to the original definition, If I want to edit the original definition I should open it or use edit component.

 

 


  • andrew, Justin Montoya, dubir and 2 others like this

#2 jeffgrune

jeffgrune

    Advanced Member

  • Members
  • PipPipPip
  • 45 posts

Posted 15 November 2017 - 12:41 PM

I am running into this problem with Components. I've been using formZ for 20 years and the Symbol system was always reliable. Files with placed symbols were compact. The Symbol Library file could be opened, edited and the changes would be reflected in all instances of the symbol anywhere it was placed.

Now, with the Component system, every placed Component becomes embedded, increasing the file size. What was a 3 MB file in FormZ 6.5 has become a 202 MB file in FormZ 8.5. Changing a layer a Component is on brings a dialog about changing the original Component. It shouldn't matter to the original what layer a Component is on in a scene and the Components bring their layer info with them and add it to the list of layers in the scene.

Other serious problems are happening when I edit a Component in the original library and the edit is not duplicated in the embedded Component, so the change doesn't show up in the renderings.

The purpose of embedded Components is to make the file portable so the original library is not necessary for someone else to work on it in a different location.

I have no need for portability of my FormZ files. I don't want embedded Components in my scenes. I do have a need for more compact file sizes and bulletproof synchrony with the original. Component Library.


  • dubir likes this

#3 andrew

andrew

    Advanced Member

  • Members
  • PipPipPip
  • 78 posts
  • LocationMinneapolis

Posted 15 November 2017 - 01:11 PM

I'll suggest that the old method of having Library Files that then referenced proxies in the modeling file was a superior way of working with projects, especially over time, when a Library represented catagories of objects or a client's assets.  

 

I have a Library file now where I keep some assets, and when I bring them in I explode them and using a different layer. I just cant afford to have the new system screw up days of work.



#4 Spacer

Spacer

    Advanced Member

  • Members
  • PipPipPip
  • 170 posts

Posted 13 December 2017 - 02:31 PM

PLUS ONE



#5 Spacer

Spacer

    Advanced Member

  • Members
  • PipPipPip
  • 170 posts

Posted 14 December 2017 - 04:06 AM

For example i have gotten this window 6 times in the last 15 minutes - even though I click "ok":

 

Capture d'écran 2017-12-14 09.48.10.png

 

I thought that maybe I was doing something wrong in my manipulation of components,but after reading severalposts where others are having trouble with this, I want to weigh in.

 

Can Support give an idea on when this will be fixed?



#6 Justin Montoya

Justin Montoya

    Advanced Member

  • Members
  • PipPipPip
  • 377 posts

Posted 03 January 2018 - 03:48 PM

I think the general consensus is do not use Components until they are fixed back to what Symbols used to be.  Otherwise, you are going to have issues.


  • FZnoob and Bartjuan like this

#7 Andyb

Andyb

    Advanced Member

  • Members
  • PipPipPip
  • 142 posts

Posted 05 January 2018 - 08:19 AM

Generally speaking, I'm of the opinion that the components system needs a complete overhall top to bottom. To be blunt, a lot of the models are ugly and very basic. Too basic to be of any real use. The whole thing needs to be modernised.



#8 dubir

dubir

    Advanced Member

  • Members
  • PipPipPip
  • 47 posts

Posted 05 January 2018 - 09:04 AM

Plus one

 



#9 ASONE

ASONE

    Advanced Member

  • Members
  • PipPipPip
  • 332 posts
  • LocationBoulder, Colorado, USA

Posted 12 January 2018 - 11:48 AM

+1

 

I have given up trying to use components.


FormZ PRO v8.5.  2017 iMac 4.0 GHz quad core i7 24MB RAM and a 2015 Macbook Pro quad core i7 16MB RAM, Modern Architecture in Boulder and Denver Colorado www.ASONEarchitecture.com 


#10 Bartjuan

Bartjuan

    Advanced Member

  • Members
  • PipPipPip
  • 124 posts
  • LocationMonterey,CA

Posted 16 January 2018 - 12:59 PM

+1 

components = corrupted files



#11 rhodesy

rhodesy

    Member

  • Members
  • PipPip
  • 18 posts

Posted 16 January 2018 - 06:55 PM

Funny I used to be a FormZ user (v7 and 8) but the terrible component issues was one of the main reasons I had to look elsewhere and have been using sketchup for the last few years. FormZ is definitely more powerful but components/general 90's interface and slow snapping tools made me switch. I keep checking back in to see what has changed and if its worth switching back but I see the same issues are being reported. Maybe V9 might solve everything when it comes out.

 

Side winge but the quality of the FormZ interface really jars against the new vray plugin. One is modern the other was out of date even when it was brought out back with Bonzai v1!






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users