Jump to content
AutoDesSys Forums

Justin Montoya

Members
  • Content count

    725
  • Joined

  • Last visited

  • Days Won

    58

Justin Montoya last won the day on August 22

Justin Montoya had the most liked content!

About Justin Montoya

  • Rank
    Advanced Member

Contact Methods

  • Website URL
    www.montoyadesignworks.com

Profile Information

  • Location
    Bend, OR

Recent Profile Visitors

726 profile views
  1. Justin Montoya

    Mac OS BigSUR With Issues, Render Zone Not Working

    RenderZone is a REALLY OLD rendering software at this point and it can no longer be easily updated. I wonder what it's future really is here in 2020. Combine that with the fact that Apple is constantly bullying developers and cutting off other important software (CUDA, OpenGL, etc), I think it should be phased out and replaced with a more modern, Open Source renderer like Cycles which is at least still being updated regularly. Cycles is arguably a better choice for the default engine for future formZ. The source code is available under the Apache License v2, and can be integrated in open source and commercial software. Cycles is natively integrated in Blender, Poser, and Rhino. The Cycles4D plugin for Cinema4D and a plugin for 3ds Max are available as well. It's cross compatible for Mac, Windows, and Linux too. I've seen some work out of Cycles that gives even V-Ray or Maxwell a run for their money. Check it out - https://www.cycles-renderer.org/
  2. Justin Montoya

    Scene FIles and Proxy objects.

    That's certainly a bummer. In the past I've found it to significantly decrease my save times as well as open times. I wonder if this changed in v9? I know you are as much of an expert as anyone on formZ, and I only hope that I can somehow find a way to help you with your issue here while we wait for AutoDesSys to respond. It sure sounds to me like your file is saving more than geometry, or trying to compress the file, or something else is going on with the hard drive itself. Saving should be pretty fast for a 630mb file, maybe 10-15 seconds max. I was curious so I just did a quick test. Here is one of my only examples of a file that size with a large amount of outside geometry (furniture, 3d plants, TVs, gaming room stuff like action figures and a fully detailed gaming computer, detailed hardware, chairs, cabinets, etc): It's 584,747 KB in v8 as where it originated, but reopening now in v9 and saving as another file it's down to 525,633 KB. So smaller than your example, but it only takes about 5 seconds to save for me in v9! Something strange is happening in the matrix... Maybe there's another setting you might have missed that could be affecting this. It's confusing, but there are 2 places in formZ where we need to Turn OFF Keep Textures. First is in the File > Project Settings > Project Files > File Optimization: Use Open Fast and Unselect Keep Textures options. Another place to look is under Preferences > Project > Project Files > Keep Textures: Unselect that if it's not already. If that doesn't do it for the Saving speed, then there must be some explanation why, as the math simply doesn't add up. Any way I could test that file for you here? That being said, VRSCENE files sound like the long term solution you need. I would have thought that Components would have worked as well to reduce the file size, but it looks like they add to it just like regular geometry?!? Haven't used those in a while since they used to not work very well in v8, but had heard in v9 they were working better. It would be great if these were just block place holders as setting them up visually in the Component manager is a much nicer way of dealing with a large catalog of models than just browsing for the files. Still, it's not the solution you need if they add to the file size. Hopefully ADS will chime in here... VRSCENE files are an important feature, and we need to make sure this works correctly in the future. I have to say I have not tested it much since the BETA days and it did work OK for me at one point, so I would assume it's just another update that broke it. Testing here shows a similar situation to your example where my VRSCENE file had a sofa, chairs, tables, and upon Importing the file it gets triangulated and looks like garbage. HOWEVER, when I render it with VRAY, it renders as it should: So that tells me that this VRSCENE file worked but it's Shaded and Wireframe representation is broken. Did you happen to try and render your example to see if it was just broken in Shaded/Wireframe preview? Hopefully this is all moot and we have a NEW VRAY 5 plugin coming very soon! Sorry for the long post, but hope this helps.
  3. Justin Montoya

    Palette dock FZ v9

    I think the problem is that the Material Parameters palette is not currently compatible with the side bar palette 'dock'. As suggested above, reset your workspace, and trash your preferences if necessary to get it back to defaults and then when you have it back to vanilla install, just make sure you keep the Material Parameters palette as a free floating window. I would also advise against leaving the Material Parameters window Open while working on projects. Doing so forces it to refresh constantly, with every change and selection made, causing noticeable slow downs while working. I actually miss the v6 Material Parameters window with the OK, CANCEL buttons because this forced you to close the material window when done with the material changes, and kept everything fast and tidy.
  4. Justin Montoya

    Scene FIles and Proxy objects.

    Hey Andrew, Quick thought, on your large project, do you have the Open Fast File Optimization enabled or Smaller Files? I prefer the Open Fast setting as it also means Save Fast because it doesn't have to compress the formZ file when it saves it. I think this should be the default setting for formZ files, but Smaller Files is unfortunately set as the default.
  5. Justin Montoya

    Paste in place

    Sounds like you want a version of Paste based on how Components work, where you have to click to set the location. I wonder if there isn't a way to easily create this since the toolset already exists?
  6. Justin Montoya

    CUDA on ARM

    You'd be better off asking over at the Chaos Group forums for that sort of question, but I have some opinions. My guess is that it's definitely on Chaos Groups radar, given that the custom CUDA based RTX chips have incredible power in the optimized VRAY RTX GPU engine. But I doubt it's anywhere near a priority. ARM has a lot of promise, but it's still not a convincing solution for extreme power users who need high GHZ processors with multiple cores to get work done fast, and we don't care how much energy it uses while doing it. ARM is more focused on efficiency, so think lightweight laptops and stupid, overly skinny devices like Apple thinks is a good idea. Then there's the CUDA problem. Apple has made it's bed on a sinking ship by continuing to cut off outside developers. CUDA is no longer available on Apple, so I don't see why that would change once they move to ARM chips. That means no VRay GPU or the newer RTX rendering on Apple. However, VRAY CPU is still a fast, powerful solution that runs great on both X86 platforms and has many more features than the GPU engine, albeit, slower. I would not expect the X86 based VRAY CPU rendering engine to continue on Apple after the ARM chip move but it's really up to Chaos to decide if it's worth supporting and how long that would take to implement. Unless Apple backtracks on their CUDA stance, it wouldn't make a lot of sense for Chaos to offer the CPU engine on ARM Macs without CUDA, as it's only part of their VRay product and they are really pushing toward the CUDA products in the future. CUDA is great, and just look at all the possibilities it has with ARM: https://www.nextplatform.com/2019/06/17/nvidia-makes-arm-a-peer-to-x86-and-power-for-gpu-acceleration/
  7. Justin Montoya

    Object selection

    Understandable. However, just know that most of v9's bugs have been resolved if they were reported clearly and v8 has its own set of quirks to workaround. v9 is a better place to start today, IMHO. I also realize the large change from v6 to v8 is already a big gap, as I also didn't like v7 (loved v6) so I skipped it and waited for v8. However, even with the choice between v8 and v9 now, I'll choose v9 everyday for new projects. It's brought back some missing v6 features we all knew and loved, as well as added a lot more stability 'behind the scenes' for large files. It will also be the only way to use the updated plugins like VRay and Maxwell. $345 is a pretty small price to pay for all of that. Not trying to sell you anything here, and I completely understand your trepidation given some of the early v9 forum posts, just sharing an honest opinion. There's many happy users who simply just don't share that experience on the forum. Users are much more likely to post a complaint or a problem than they are to share a positive experience. It just seems to be the human condition. We're all guilty of it. But if you look around on other 3D software forums (Rhino, SketchUp, etc), they are all the same. Problems with new versions from experienced users who expect things to work a certain way. Either the software will adapt or the user will, and the work will get done. Ideally these changes happen in the beta testing phase, but given the flexibility of formZ to do so many things in different ways on different systems, it's inevitable that some things slip through to the public release. But if you find one of these issues and clearly report it to support@formZ.com, it is usually resolved by the next release which has been happening monthly as best I can tell. Plus the forum is always full of other like minded formZ users willing to help figure it out.
  8. Justin Montoya

    Object selection

    Just curious why you aren't using v9? If you're moving on from v6, why would you not jump to the newest?
  9. Justin Montoya

    Object selection

    Looking back, I seem to remember a Preferences Option that called for a 2 Edge Pick, but I can't seem to find it... EDIT: snow got there first
  10. Justin Montoya

    Object selection

    You should definitely be able to select two edges to select that face in Wireframe mode. I suspect you have found a bug. Can you please share a simple fmz file with as little geometry as possible and the view you are working in so we can also test it for you?
  11. Justin Montoya

    V-Ray for FZ update?

    Also hoping to hear news of VRay 5 for formZ.
  12. Justin Montoya

    Setting Up V-Ray/FormZ Workspace

    Greetings Dennis, Been away for a while, but hope I can still help you here. It sounds like you may have found a bug in the VFB (VRay Frame Buffer) window, where it is not saving its last location. You should report that to support@formz with your OS and other info. However, you mentioned the Multi Window option and I think I can help you get that setup. If you turn off the "Use Frame Buffer", then VRay will render in the 3D view window panel. I'll also add that I do not usually use the VRay Interactive mode since it seems to cause instability in my projects and formZ. But I find the lower resolution VRay images to preview fast enough that I don't really miss it much. Hope this helps!
  13. Justin Montoya

    vray image autosave

    I agree it can save you time if setup correctly. However, by DEFAULT it should not be turned ON to save files in a place I never go or look at. So, I think it should be turned OFF by default, that way If a user wants to use this feature, they should need to turn it ON and then pick their desired location for saving. It's kind of like applications automatically installing hideous desktop icons. It's extremely inefficient to use and organize and quite frankly, just an ugly method of creating litter on the desktop, left over from failed computing ideas 20 years ago.
  14. Justin Montoya

    vray image autosave

    I think Autosave is a terrible feature and should NOT be turned ON by DEFAULT.
  15. Justin Montoya

    Will a solid state drive speed up saving large files?

    Hi Matt, Getting a NVME PCIe SSD in your Mac Pro will certainly improve these speeds, but you are still going to be dealing with much slower performance than just about any other new workstation when it comes to these simple single core optimized tasks. That's because new CPUs are much much faster than they were back in 2010. You are also playing chance on when the machine will fail, likely right in the middle of a stressful rendering operation. IT Professionals recommend 3D design and rendering workstations be replaced every 3-5 years for optimal performance and the least chance of down time for mission critical work. Apple did an amazing job back then at offering competitive hardware that was built to last. But after 10 years, it's really starting to push the limit as to when it will fail. Newer Apple hardware cannot compare to the Windows based AMD CPU workstations for 3D design and rendering. Check out the new Threadripper 3960x, 3970x, or 3990x to see how much more CPU power you can get than the sadly overpriced and underpowered Intel offerings that Apple offers. https://www.pugetsystems.com/labs/articles/V-Ray-CPU-Rendering-Performance-Intel-Core-10th-Gen-vs-AMD-Ryzen-3rd-Gen-1764/ All to say that I agree. Time is sanity, and money. It works the other way too. Spend the money to protect your time and sanity.
×