mjm

Kevin, I am truly sorry for your troubles. I have used VW all these years because it has relatively reliably assisted me in creating the vision my clients keep coming back for. When I create something in VW for client review, I can comfortably say:"What you see is what you get." To get to that place lately has been terminally frustrating. I have hope VW sees this situation for what it is: an opportunity to make good a pretty big mistake, and to do so.

This morning I found an email from a highly placed Vexctorworks executive, asking for input about my specific issues as described in my posts above. He asked for documentation on the workflow causing my issues. Instead of doing work-for-pay, as scheduled this morning I spent an hour or so recreating the scenario. While the 2019 Hidden Line render performed more predictably today, I encountered the dreaded 0:03 second black render, which was followed by the funny render shown below when I set the bounces to sixteen from four. The same file, down converted to 2018 with same render settings is shown in second render. I closed my reply to said exec thusly: "I hope you find this information of some use in solving the issues in this release. Please do know that, really and truly, I value reliability far more than new tricks. Trix are for kids. I eat oatmeal."

Thanks for your question Kevin. System is the same as in sig except I am now on High Sierra 10.13.6 2019 Sp01 seems to run reasonably for 30 - 60 mins, then bogs down. I don't have time for that. I can make a cup of coffee from scratch before many types of operations complete. Not productive. 2018 SP-latest runs reasonably smoothly from start till end of work day.

On SP-1 I am patiently waiting for an incredibly simple viewport to shift from unshaded polygon back to wireframe, and it's been minutes already. When that has completed, I will shut down 2019, as it's wasted another few hours of my life and my client's money. When I see steady user reports here that it's stable, I'll move forward with it. SP-1: Not better. 2018 SP-latest: • the viewport from wireframe to unshaded poly: 1:22 mins • the viewport from unshaded poly to wireframe: under ten seconds, as expected

Dang Peter. That was fast.

following on from @PatStanford, isn't making sheet layer viewports exactly the solution for this?

why is this so hard? I very very often make 3D symbols to resolve this very issue, being sure to place them at 0,0 Z.

This why I gave up long ago on that tool and 'just build it myself'.

It appears the tool is restricted to the Architect product. I'd sure be interested in having it as part of the Spotlight package as well.

And those pix are awesome. The camel shadow one esp, tho you probably aren't going to point-cloud them.

I generally draw in color. When I really need excellent greyscale output, first I publish/export to PDF, then I go to Adobe Acrobat's Print Production module, choosing 'Convert Colors' then in that dialogue window choose either of the two Grey Gamma choices in the 'Conversion Profile' field, et voila, perfect greyscale version. Tedious if doing many sheets tho.

Fabulous. What a great solution.

Cool. And which did you deploy in this instance?

this is really really cool. And but: "had the photos stitched into a photo textured 3D model in OBJ format" How exactly was that accomplished?

What a great tutorial. Thanks folks.

Once again @willofmaine, my thanks!

Loft. two rails. Two nurbs surfaces. Make sure direction is same for both shapes. The green = nurbs in same direction, the pink: nurbs in differing directions… Shape.vwx

Doesn't this problem just claw at your guts? What a way to kill an hour or two of productivity. I make these kinds of renders for clients all the time. I have these same problems often with no real pattern I can detect.

√

TYVM @willofmaine. The Irritation-O-Meter has gone down several notches this morning. Now if I could rid myself of that pesky notice that VW 2019 is available…

I lasted about 4 hours with 2019. Once I loaded some plugins and VW 2019 began crashing, I lost interest immediately, as work needs to get done. Somebody let me know when it's safe to use please, otherwise it'll be more like March before I look seriously at this again. I am considering uninstalling it, so don't have to keep closing it after inadvertently opening it with my 2018 files.

Thanks Jim, the reset is complete, the problem has disappeared. No time to investigate the whys tho.

thanks for your input Jim and I will get that Prefs wipe done…I'll keep you posted.

@Jim WilsonDirect messaged it to you