Page 3 of 3 FirstFirst 123
Results 31 to 32 of 32

Thread: Set Content Directory

  1. #31
    Registered User jaf's Avatar
    Join Date
    Oct 2006
    San Diego, CA
    Wanted to bring this up again. I'm on 2019.1 right now. I started Model -- first time today. I went to Load|Set content directory, that was a new existing directory. I started modeling and about 5 minutes later started saving "Save object as" and the dialog suggested a content directory I used a couple weeks ago! Just to be sure, I fed it the new directory I had made and it was there waiting for some use. Can't believe this hasn't been fixed!
    02oct19: Lightwave 2019.1 Build 3127, win10 x64, AMD Ryzen 1800+, 64 GB mem, EVGA GeForce GTX 1080 ti v436.48 (02oct19)

  2. #32
    Electron wrangler jwiede's Avatar
    Join Date
    Aug 2007
    San Jose, CA
    What's really disappointing is the apparent lack of priority towards addressing these kinds of "minor" issues. These are problems which make use daily-painful and aggravating, and together with the overall stability problems, really upset customers. Sure, all software has bugs, but that doesn't really excuse anything, and the truth is that there IS greater stability available elsewhere in 3D pkgs, and customers seem quite willing to pay more to obtain it.

    "Fixing lots of bugs" isn't meaningful if the net is that more are created than fixed. Reliable software quality comes from adopting engineering processes and metrics focused on ensuring fewer bugs are released, not on addressing more after release. The latter basically proves there isn't enough of the former.

    I had hopes Vizrt would force a greater focus on quality, we'll see.
    Last edited by jwiede; 08-17-2019 at 07:31 PM.
    John W.
    LW2015.3UB/2019.1.4 on MacPro(12C/24T/10.13.6),32GB RAM, NV 980ti

Page 3 of 3 FirstFirst 123


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts