Jump to content

mjm

Member
  • Posts

    1,095
  • Joined

  • Last visited

Everything posted by mjm

  1. @Tom W. wow yes totally forgot about that render style limitation
  2. Decals seem pretty counter-intuitive as-built to me. User wise, Want to select a resource and click on a face to place it, then drag/scale/etc till done. Applying a decal and then hunting for it hasn't made sense to me yet, but it's just as likely I'm missing whatever crucial step in the decal workflow…
  3. @JuanP @Dave Donley; gents, thanks as ever for your attention to this matter. I have executed the steps as outlined in JimW's video and appear to achieved success. 2x in a row VWX has not crashed when editing the Page Setup pane. Thank you both for your input.
  4. Not getting much done here this morning. Super simple file; 11.xx mB file size, almost completely 2D. Page Set up consistently immediately crashes to the desktop. On this file. It was imported from a 2021 file to 2023. Screen Recording 2022-11-15 at 8.22.05 AM.mov
  5. mjm

    Shaded Render fail

    Super good news Dave, thank you
  6. yeah saving that time and energy is worth the re-start every time. I've come to learn that the 🔨 way
  7. Pretty much daily in my use, I love the Modify…Convert…Replace with Symbol… option. Means I can replace anything with whichever symbol I want.
  8. @Mark Aceto—Ah. Super, thank you! I did not change the UV and so it defaulted to 2x2 and I got the poor result I got!
  9. Hi @Daniel Dickman; maybe see this thread, esp Dave Donley's mention of Project Screen Objects. It solved a similar issue I was experiencing
  10. That Safelock table legs make that an iffy bet at best I think. Drape Surface is not that smart…
  11. mjm

    Zooming

    It is often a painful experience to come to grips with how fragile VWX tends to be in its earliest iterations -.0, .1, etc. I often feel used. Having said that, in another thread I enthusiastically offered whatever support I could to help move along a particular facet of the app which is crucial to my workflow. Aaand, having said ^that, I'd prefer to participate in a true beta, rather than sending in complaints after the official versions come out.
  12. @Dave Donley—how can I help in this process? It's of vital interest to me
  13. mjm

    Shaded Render fail

    Thanks man. Shaded has come a long way in '23. That specifically was why I've been willing to go thru all the pain of the dot zero release this year. For the first time I can move with so much more speed in generating reasonable visual ideas.
  14. mjm

    Shaded Render fail

    @Mark Aceto—woo-eee, thanks man!
  15. mjm

    Shaded Render fail

    Alright; I seem to be back on track, I want to thank all y'all (esp looking @Dave Donley) for your assistance and support. Back to having fun again, doing what I do!
  16. mjm

    Shaded Render fail

    yep — the point being that rendering in DL does not seem to offer that PSO option, so this issue never raised it's ugly head while actually creating the looks in Shaded on DL, so no warning beforehand, if you will.
  17. mjm

    Shaded Render fail

    @Dave Donley: Huzzah Dave—that solved that problem for me, thank you very much. However: what black rectangle? The only black rectangle I know of in that file is on the Auditorium Layer, there for unwanted light leaks during render, as my actual building data is very slim. That rectangle is I think it's 6'9" below 0,0. It is definitely on the 3D plane. Also: it appears Shaded Render on DL does not have any 'Project Screen Objects' options, so the issue does not seem to be visible there. And, of course changing that rect to an extrude seems to obviate the issue entirely.
  18. mjm

    Shaded Render fail

    Lol @Andy Broomell, yup, did ALL you suggested above, no joy and your sense of the issue is the same as mine. I did get all three to print by copy/pasting the three viewports into a blank file & exported without updating. THAT worked. Of course you can imagine what happened when those three viewports were then updated.
  19. mjm

    Shaded Render fail

    @Andy Broomell: Thanks man, had not thought of that. & so, just tested your thesis. Opened file All three render views already "rendered" Clicked 'Export to…PDF' UNclick Update visible out of date viewports prior to exporting Click render Result: Same as before.
  20. mjm

    Shaded Render fail

    @Mark Aceto, dang thanks for that. I am sure you can imagine how thrilling it is to have such potentially rapid turnaround on these kinds of things with the revision to Shaded Render, so to have it fail mid-stroke…
  21. mjm

    Where'd my Slab go?

    @jeff prince: thanks for that man, but here's the thing: The extrude which you found was unconnected was connected the day before. There's no reason (I am aware of) for that poly underlaying that extrude to have become unconnected. The extrude showing as connected is the same extrude from a backup file.
  22. mjm

    Shaded Render fail

    Thanks for the hug man, honestly needed that. And yes I have already capitulated to the screenshot idea, in order to GTD. Triggered, LOL. yup.
  23. mjm

    Where'd my Slab go?

    Yes. I did make it in '23. If you'd like to know why I am putting my energy and hopes into '23 its' because of the unlimited light sources available in Shaded Render: I can easily have 50+ lighting fixtures shooting thru haze / fog and quickly derive a perfectly communicable document…uh. That is till it randomly fails for no apparent reason. Here's a screenshot from another post this morning, describing the work stoppage incident last night, continuing today: All three views are built with exactly the same render mode and background. Oh. but wait! here's how it appears onscreen: I have a previz session this afternoon. Gonna be tough to pay for the hourly session but have nothing for the 'Vizzer to do. So I'm down to screen shots (I hope). And no. Restart VWX did not help/fix or ameliorate this issue.
  24. Here's something literally stopping me from delivering the goods TODAY. Happened last night out of the blue. Building a sheet for communicating Lighting Presets (moving lights recorded in a focus position, + color + gobo + etc) as one does, for one's previz operator. So far, so good. Loving the unlimited Shaded Render beams, wows my workflow speeded up because of that, ya…woops. So: here's the onscreen render: Yay, right? OK. so excited, I exported, published, printed to pdf, and all returned this: woops. This is stopping me from making my deadlines and pretty much super bad for my mental health. This task should has reached the braindead-rinse-and-repeat cycle of developing the previz shots, exporting to PDF. This ruined dinner & a movie last night and apparently it's gonna continue to be all an kinds if fun VWX-day here. Here are the render setting for each of those views: Same background used for all three as well. Ironically, the speed and overall readability of the 2023 Shaded Render offers so much potential to change my life for the better because it's so much faster than the other options.
×
×
  • Create New...