Jump to content

Alt+F4

Member
  • Posts

    24
  • Joined

  • Last visited

Posts posted by Alt+F4

  1. If you make the light sources visible you can see that the sweep (shade) does block the light correctly, only when the light source is moved too far up it shows through the sweep. As if the "point light" were the scematic light bulb used to show the light source.

    Maybe in OpenGL the light source is computed not with the single point light in mind, but rather using the scematic bulb...

    Its weird and doesn't make sense.

    Low light.jpg

    mid light.jpg

    hi light.jpg

  2. 2 minutes ago, Zeno said:

    Off course Alt+F4, i think is it the only way to find a solution for this problem. Better with 2 monitors, but a 2 click connection it could be much better than that actual situation. I think that VW need to have more attention to the front views and about all dimension editing parts.

    Yes, I agree. Sometimes it feels like VW has upgraded to 3D only recently but still mainly relies on 2D drafting views to do the modelling.

  3. Well it seems like his sweep (only the bottom part of the shade I believe) casts shadows correctly. It is the top part of the object that doesn't work, right? And if that is also a sweep, then you might have to check if it is a solid. (eg. the 2D Poly a closed shape)

  4. On 8/12/2018 at 6:04 PM, Zeno said:

    Component in section mode who can be connected exactly like in plan mode. Grafically, whit 2 clicks. Not after doing 100 tests in separate wall and slab styles and whit 100 viewport updates. In slabs, walls, roofs, around the windows, like in reality. Everywhere. Actually the system don’t works well. The plan mode only works well. VW need exactly the same in vertical mode. How can we draw in detail? Think about 5Dimension BIM

    I've found Multiple Drawing Views in VW18 to help with this a lot because I can work in 2D Plan and ortho (not section so much) at the same time. A section implementation would be awesome though.

  5. A request for a new function/tool:

    "Make a 3D Loci an 'overriding' snapping point"

    Similar to a symbol insertion point, but customizable and connected to the group/symbol/solid etc., so that one can snap to a manually defined point.

    This would be useful because sometimes desired snap points aren't corners or edges - the workaround at the moment is to snap to a normal endpoint and then move the object by hand to the desired position. Can become quite time-consuming and tedious.

     

     

  6. Is your point light far away enough from the geometry?

    Possible workaround: Add another solid over your light source to prevent any shadows over the fixture.

    That second posts' third pic is confusing though: Is the highlighted solid blocking any shadows if you try it on its own?

    Maybe you have to reposition the light source further down...Want to include the file?

  7. Jep, happened to me once. I tried all kinds off stuff rapidly just to finish the project and after a few minutes of reopening, deleting the VP"camera" and reinstalling one, restarting VW etc. etc. it was all fine again. I did suspect that this had to do with the "camera" in the VP -- and as that is what I focused my chaotic troubleshooting on and it worked after, I now think that must have been the problem.

    Generally, the VP-cam is causing a few problems and needs too many workarounds to be useful.

    (But I just can't resist depth of focus)

  8. 3 minutes ago, line-weight said:

    It's such a clunky way of doing things - the camera settings should simply be controlled from the viewport settings whilst remaining in the sheet layer, just like the render style settings are.

     

    Absolutely.

     

    3 minutes ago, line-weight said:

    In the end I found that deselecting the objects, returning to the viewport, then re-entering cam edit mode made it work again.

     

    If you know where the camera sits, just go into 2D Plan mode (within cam-edit). You'll be able to see and select it then and edit it.

    If you need to see what the camera sees, click on the edit button and use the sliders.

  9. On 8/6/2018 at 8:55 PM, line-weight said:

    All of this needs a complete overhaul. It's an absolutely terrible user interface experience. 

     

    I've been working with linked VPcameras a lot in the past few days and I must agree in all points.

    Another annoying issue I'm not sure with (maybe a bug):

    When editing a linked cam, sometimes when returning to the VP and rerendering, the render will come out completely black after a few seconds. So I go back to edit the camera and the settings are all over the place. Then I edit again and it seems to come out normally. It only does this sometimes and not in any particular pattern. I've tried different documents and it seems to be the case more often with larger ones. (?)

    Anyone else experiencing this? It's quite timeconsuming because entering the cam-edit through the VP takes a few secs to load.

  10. 17 hours ago, Luis M Ruiz said:

    buckets? would you be able to post a screenshot?

    I believe buckets are the "chunks" or tiles that are rendered one after another in Renderworks.

    I re-rendered it eventually and forgot to duplicate the viewport - this time no white squares - so I didn't have the faulty image.

    17 hours ago, JimW said:

    I have not come across this before, no. Are you able to replicate the issue with a faster rendering mode for testing?

    I'm trying to do this right now.

  11. So I've started an exterior rendering and I accidentally double-clicked the viewport and so entered the actual model. When leaving the model again (like when leaving a group) by clicking the orange button and returning to my layout, the viewport had 1-2 buckets missing (white) and didn't fix this during the rest of the rendering process. Now the rendering is complete and the white buckets remain. I suspect this is because of me entering the model. This has not happened to me before and it bugs me because the render took quite long.

    Has this happened to anyone else before and who knows what the cause could be?

     

    Anthony

     

×
×
  • Create New...