Jump to content
AutoDesSys Forums

jeffgrune

Members
  • Content count

    49
  • Joined

  • Last visited

  • Days Won

    3

jeffgrune last won the day on September 4

jeffgrune had the most liked content!

About jeffgrune

  • Rank
    Advanced Member

Recent Profile Visitors

16 profile views
  1. jeffgrune

    2d people

    Thanks, folks. Very helpful.
  2. jeffgrune

    Forum Functionality is broken

    I couldn't log in with Safari or Chrome until I did a Control-click on the sign-in button.
  3. jeffgrune

    Locking snap guides

    Is there a way to lock the snap guide lines and points? Is there a way to turn them on and off?
  4. jeffgrune

    2d people

    Where can I find 2D billboard people that I can use with formZ?
  5. jeffgrune

    Component problems

    I had another embarrassing experience with Components when I updated a label and cap on a wine bottle component, expecting the edit to carry through on all placed instances in a cut case, as it did in the Symbol days. There was even a dialog that popped up telling me how many places that instance was also changed in the library. I sent the rendering to the client ad was told that the old label was still on the bottles. The bottle was edited and the proper label and cap art mapped on the file in the Component library folder before a scene was set up with those instances, but the Component objects became embedded and did not have the changes. The faster shaded render preview and ability to render scenes exceeding 2GB are why I tried to switch to 8.5, but the Component mess makes it unreliable for instance-heavy product scenes. I'm reluctantly returning to 6.6.5 for this client. I can't afford to have these embarrassments and time-consuming errors. Sorry, ADS, you ruined a good thing when you revamped completely reliable Symbols into unreliable Embedded Components. Not only are they unreliable, but they vastly increase the file sizes, sometimes 10X.
  6. jeffgrune

    Component problems

    I am running into big problems with Components. A couple of years ago, I made a run at switching over to 8.X, but ran into Component problems, so I went back to using 6.5. I've been using formZ for 20 years and the Symbol system was always reliable. Its editability improved over the years. 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. My principal client has hundreds of products that are updated regularly. I have been able to reliably swap out multiple Symbol instances with instances of other products. Anticipating the end of support for 32-bit applications, I am again trying to transition from the tried-and-true FormZ 6.5 to the 64-bit FormZ 8.5. The faster shaded working render and ability to RenderZone larger scenes are welcome improvements. 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. The Components also 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. When the client changes the packaging and I update it in the original Component and it doesn't show up in the rendering because the Embedded Component is the old version, I can't rely on this software. It was unreliable when I changed some Components and the instances in the renderings didn't reflect the changes that I copied and pasted the objects from the Component file. Might as well forget about using Components at all and have separate objects. I don't have time to wonder whether a Component I edited didn't end up in the scene. If I miss it, the client doesn't and I have to deal with that problem. Every time I click on a window, it reminds me of Components that have changed. I check the box that says, "Don't warn me again", but it returns and warns me again. 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 just need Components from the original Component library. I do have a need for more compact file sizes and bulletproof synchrony with the original Component library. Large file sizes are more of an annoyance when Auto-Save is on and it takes 5-10 seconds to save the file than the way they are gobbling up storage. Is there a way to turn off the Embedded feature so I can have more reliable instances and smaller file sizes again?
  7. jeffgrune

    Please sort out the component system

    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.
  8. I had a situation where a mapped texture set to less than 512 pixels in Shaded Work and Shaded Full mode displayed the wrong texture map and was different when rendered in Renderzone. In some other cases, some mapped textures did not show in Shaded modes at all unless the Texture Map preview resolution was set to 1024 or higher.
  9. In previous versions, Symbols could be sorted alphabetically. Is that possible with Components? I didn't see it in the interface
  10. I am working on a large file with many objects. I am now waiting on the pinwheel for 30 seconds after every change to the color picker. It is no longer interactive. The slider doesn't drag responsively. Clicking on the spot on the slider gradient does not make the selector jump to the spot. Even choosing swatches does not put the swatch color in the material. Sometimes the indicator jumps to one end or the other of the brightness bar. I saw discussions of this from several years ago in this forum, but the problem does not seem to be fixed.
  11. I have a file that was started in 6.6.5 that must have been set to Auto Save images to TIF. Opening and editing in 8.0.2 now autosaves every RenderZone rendering as a TIF, even though Auto Save images is turned off in the preferences. A new file by Save As doesn't change this. Short of copying everything and pasting into a new file, what can be done?
  12. jeffgrune

    Restoring formZ 6.5 from backup

    Thanks. The WIBU download fixed it.
  13. jeffgrune

    Restoring formZ 6.5 from backup

    Will that work with my 6.6 license? I recall 6.7.3 being a separate version.
  14. I still use form Z 6.5 for one of my clients. I had to replace a hard drive and copying the formZ folder from the backup to the new Applications folder. When I tried to launch, it produced a Key is Missing alert that quit the program. The key is plugged in. The installer on the disk only works on Rosetta or Power PC computers, so I can't use it to reinstall now that I'm using el Capitan. What file is missing to make this work? I've replaced formZ other times when migrating systems or replacing hard drives.
  15. jeffgrune

    Component embedding in 8.5

    I guess I never completely understood how to handle embedded components before this.
×