Jump to content
AutoDesSys Forums

Justin Montoya

Members
  • Content count

    720
  • Joined

  • Last visited

  • Days Won

    55

Everything posted by Justin Montoya

  1. 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/
  2. 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.
  3. 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?
  4. 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
  5. 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?
  6. Justin Montoya

    V-Ray for FZ update?

    Also hoping to hear news of VRay 5 for formZ.
  7. 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!
  8. 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.
  9. Justin Montoya

    vray image autosave

    I think Autosave is a terrible feature and should NOT be turned ON by DEFAULT.
  10. 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.
  11. Justin Montoya

    Independent window

    Niceeee Setz!
  12. Justin Montoya

    Palette Dock scroll bar

    Side bar scroll speed too slow is a bug. It's been reported. It's not currently usable here.
  13. Justin Montoya

    How to export OBJ to Blender and Maya?

    This should not be so difficult to use correctly!!! The default settings should just work out of the box for the most popular apps or give some feedback what is happening.
  14. I have reported many issues with the Inspector palette in v9 but none have been fixed yet. There is also a noticable lag when extruding objects with the Inspector palette open. It doesn't nest or stay resized correctly. It causes weird slowness while trying to work quickly. At this point I hate the new inspector palette and just want the old one back. I really don't see the point in this new palette.
  15. Justin Montoya

    Stretching Walls

    There's great flexibility to do things like this with formZ, many different ways to get the same result. The real question would be whether you were still working with the original 'Wall' shape or was it a Union of more than 1 wall? If just 1 original wall, then: Just select the wall and toggle f6 to Show Controls. Then I select the 2 corner points and press M for Move and then Click and drag to the new location (with snaps and grid snap ON ) then f6 Show Controls OFF. This unfortunately doesn't work once a multiple walls have been Unioned together like I suspect from seeing your geometry. For that I would use key shortcuts for most all common tools for efficiency so using a similar method to yours above would look like: CTRL+6 (Top View) CTRL+W (Wireframe) Spacebar (Pick shortcut) Click on the Faces option in the Tool Options - Pick Options window Click and drag to select faces. Click on the Solid option in the Tool Options - Pick Options window Shift Click and select your component door or other object. M (Move) them where you want. ... CTRL+1 (3D View) CTRL+J (Shaded View)
  16. Justin Montoya

    Suface solid (two sides)

    Agreed and good information here! Now to put it to a practical use... We still MUST use outside geometry from these Surface modelers and their Sudo Solids/Surface Solids junk. It's just the way it is. Tech, You are the experts at how this is different from our typical formZ geometry. Please help us, help you. Can you create an Import tool that gives us users some sort of feedback and/or visual Guide upon Importing so we can visually see the errors we may encounter when importing outside geometry? I'm seeing a pop up window with a preview of the file as the options are changed on the Import settings, the imported preview changes. It could also have some nice tools built-in like Andrew's suggestion where the geo is Seperated by Color, Object Doctor, Model Cleaner (Dunno what that is, but it sounds good!), etc. Even if it's not a new tool, we just need SOMETHING to give us some feedback of why all these outside models cause issues in formZ. When our clients are expecting us to be able to efficiently use models from the top modeling programs (3DSMAX, AutoCAD, MAYA, RHINO, SketchUp), we need to make that happen. formZ's future, for many of us, relies on it's ability to correctly translate outside files both Importing and Exporting. Help us, help you. I get just as much lousy geometry from 3DS and FBX files as you do from SketchUp files. Mine is mostly furniture and appliance type models which seem to import fine most times from 3D Warehouse/SketchUp. 3DS files constantly give me fits and require a Force Quit after it freezes fromZ for a few minutes while trying to Import. FBX files seem to always be exploded around and rotated strangely. I can open it in 3D Studio and it looks fine. I can even open it in the new 3D Viewer built into Windows 10 and it looks better than it does in formZ. Something is wrong with that for sure. Some users seem to have expert knowledge of the workarounds required to Import or Export anything to or from formZ, but what about everyone else? We need these solutions documented so formZ can grow. I have a friend with a 3D printing business and I was telling him about formZ, so he downloaded the free version to try and use for some a basic 3D printing project, where he downloads an outside model (Thingverse STL) and tweaks slightly and then prints it. Well thing's didn't go well for formZ and it was impossible to try and help him resolve his issues. New users like that just want things to work correctly the first time, and if they don't, provide some feedback so they can get it working without resorting to a support email everytime. 3D Printing is a huge market now and formZ seems to be missing out because of this outside model file translation issue. How do we fix it?
  17. Justin Montoya

    Texture mapping

    Thanks Andrew, I've run into this Shaded Material Updating bug from time to time as well and I'm not sure what causes it or how to fix it. I haven't been able to recreate it on a simple project yet, so it's difficult to explain what is actually happening. I'm curious which way you found the bump map to cause this error? Was it in the V-Ray for formZ > Material Parameters > 'Generic' texturing Method? Or, was it in the V-Ray (.vrmat) material editor? I mostly just use the Generic unless it's a much more complicated texture, so I tested it that way and it seems to be working on a very basic file using the Generic mode with a basic texture map file in the Diffuse channel and a different Bump Map channel file. This is with v9, so not sure if that's changing anything. Or perhaps your texture map files are causing the issue? Can you share your maps that caused this problem in a simple file like this? Maybe if more than 1 of us can recreate the problem, it will be easier for Tech to fix.
  18. Justin Montoya

    Suface solid (two sides)

    I have to disagree here. I use formZ Solids such as walls and other, often asymmetrical solid shapes with different materials applied to various sides, ALL THE TIME. It works perfectly in Shaded Full and V-Ray rendering engines. The idea of using 'Surfaces' is inefficient for much of the work we do, and is the reason why formZ is so fast, powerful, and efficient for many types of modeling such as Architecture, Furniture, and Exhibit design. There's no shortage of Surface based 3D modelers out there, but it's the SOLIDS that make formZ so special to us.
  19. Justin Montoya

    Display Resolutions

    Hmmm, I just always use Maximum Resolution. Why can't we just expect modern fast computers to use the best available without any compromise here?
  20. Justin Montoya

    Type input bug

    Good UI design dictates that whenever a Tool or Function is called upon that requires additional Input from the user, the new Input field should automatically be engaged. Tabbing through multiple fields from the first most important input field is also expected. This is the kind of thing we need fixed for formZ to feel complete and POLISHED. I think this may be a bug with the new Inspector Palette and is not working well for us at the moment. It also causes various slow downs while it is open (extrude for example becomes sluggish to respond when the Inspector Palette is open).
  21. Justin Montoya

    Example Images

    Looking good everyone! Thanks for sharing! I'm trying to decide if this virus, effectively killing the exhibit industry means I can share more work? Hmmm...
  22. Justin Montoya

    Transparency in front of reflective surface issue

    I've seen that as well! Shaded representation didn't translate the same as the VRay translation. Curious what happens if you use Flat as opposed to Cubic mapping?
  23. Justin Montoya

    Transparency in front of reflective surface issue

    That's sounding familiar, Dome light or GI settings.. Wait where did the rest of your message go? Try this, go into the V-ray raytrace settings and boost the min number of recursive rays to 6 or 8 or more. The default is 5 I believe and that isn't high enough for many reflections in scenes. Does that help?
  24. Justin Montoya

    Transparency in front of reflective surface issue

    That should work. I'm curious of your V-Ray settings then. I suspect you may have come across a transparency map bug. Are you using the Use GPU option? If so, Try turning that off and see if it has a different result. I have had them stop working for me when the Use GPU option is turned on.
  25. Justin Montoya

    Transparency in front of reflective surface issue

    Have you tried to turn off shadow casting for the plane object that has the transparency map?
×