Jump to content

Kaare Baekgaard

Member
  • Posts

    731
  • Joined

  • Last visited

Everything posted by Kaare Baekgaard

  1. When I try out the redshift renderstyle – even on very simple geometry – I get the teapot symbol for an inordinate long time with no feedback whatsoever and no end in sight. The one time i let it run out, the result was less than dazzling. If it requires some special hardware, am I likely to get it anytime soon? My Imac has a few years to go, before I get a new one. So it does smell like vaporware. Do anyone have positive experiences with the new rendermode?
  2. When I try to tune a perspective in VW 2022 using the translate view tool in wireframe, my geometry disappears until I let the mouse button go. This renders the translate view (and the flyover) tool rather useless. So I try to use the tool in shaded mode, but then my backdrop disappears. Some new gimmick, that has not been coded properly, I guess. So I try to make a Renderworks background from the backdrop, but backgrounds are screwed up in VW2022 and do not display properly. So now what? Back to VW 2021? There used to be a responsiveness setting somewhere, that allowed a setting, whereby I could press and hold the mouse button and wait for a while, until I got a live preview of the scene as I rotated and translated it. Has this setting been removed with no legacy concerns? Please advice.
  3. HDRI Backgrounds do not crop properly in shaded views, and image backgrounds loose their proportions and become stretched. This is serious stuff, so please fix it.
  4. When two or more viewports are present on a sheet, And when background render is set to opengl/shaded And when foreground render is set to hidden line And when two or more viewports are updated simultaneously Only one of the viewports renders correctly with the hidden lines. The rest show the background render, but not the hidden lines. I can get the hidden lines back by rendering the viewports one by one. When I use the publish function, I usually get all the hidden lines correct on all viewports, but I have seen it go wrong on one occasion here as well. This is a bug.
  5. 99 % of all image props in my workflows have the same settings when it comes to masks. If there is an alpha channel present in the image, that is what I use. But it takes a frustratingly high number of clicks to get there: Click use mask, click create mask, click reuse an image from another source, click alpha channel, click ok, click ok again. If there is an alpha channel present in the imported file, I wish VW would just select that by default, so that I can just click OK once, unless i need something out of the ordinary.
  6. I can do a lot of formatting on callouts, but I cannot pre-assign a different class than the active one. Dimensions do this automatically - they use the dimension class. I want the same with callouts - I want their class to be 'Dimensions', or I want them to be in a class of their own. i wish VW would add this little feature to the Callout Preferences.
  7. Thanks for the answers, Zoomer. Sorry for the rant, there are two preferences menu item, and I was looking in the wrong one.
  8. The menu item is greyed out and I need to turn it on. How do i do that? Where is the 'legacy tab' - and why is it legacy, when it is absolutely essential? Not much help in the help section...
  9. By default all new objects, that I make, have their texture assigned by class. I think most users work this way. So when I change the class of an object, I change its textures. Preferably all of them (always!). I may assign an override on purpose after that, but never before.
  10. Cool? Sure in a novelty kind of way. Useful? Not really.
  11. When I use an existing textured object to create a new object - by shelling or using boolean operations – and then give the new object textures by changing its class – I get unwanted texture overrides. Leftovers from its earlier incarnations so to say, that I then have to delete. This is a bug.
  12. You can use the split tool, if you do it along a planar surface. It has to 'touch' one of the objects...
  13. You could just start with 'Add Tangent Faces'. This - and Add Single Faces to selection would probably suffice for 95% of all users 🙂
  14. I get that Shengxi - but I am allowed to wish 🙂 While we are at it, I played around with the render tab of the OIP – And i noticed, that I now have much better control over the old, estranged Add Decal feature, which I think has been largely unused since it was conceived. (The nice trick is to add the decal to a texture override face) This could become useful. Except that the decal does not show up in the Shaded/Opengl render mode, but only in the Renderworks mode. I hope, that this is an easy fix, and if so I wish you would fix it.
  15. Panoramic backgrounds do not crop in perspectives in design layers - and they are shown differently in shaded representation as compared to renderworks representations. Does anyone know how to fix/change this?
  16. I meant tabs, Ian. I am not a native english speaker, so some words become muddled. Thanks 🙂
  17. I do not disagree, but the objects that I work with often have hundreds of faces and the textures are subtle and do not give a lot of instant feedback. The wish is quite reasonable, if you consider it again.
  18. We must have gotten this in VW 2022? I cannot find it, where is it?
  19. The new Texture tool is a welcome addition, and it is almost great. I wish we could shift-click to add faces to a selection - like we do when we add faces to a Shell Solid selection. I really, really wish I could add all tangent faces to a selection. This would be extremely useful for displaying different textures for the inside and outside surfaces of a shell - or a lamp.
  20. I do not wish that 'top level dimensioning' should replace the annotation layer, but supplement it. Besides dimensions, I use the annotation layer for all sorts of stuff like 2D section details. But I often have several viewports in one sheet - and I reuse them all the time by duplicating a sheet - and then change the layer setting of the viewports to reflect a different component. For that purpose - among several, it would be nice to just delete all dimensions on the sheet and start on a clean slate. There should probably always be more than one way to achieve functions, that are performed so regularly as dimensioning. To be able to do this in the top level of the sheet is very plug-and-play-ish.
  21. To add dimensions in sheet layers, we have to enter into an annotation 'layer' of the individual viewport. Making changes involves a lot of clicking with the mouse. I wish, we could just add the dimensions right there in the sheet without ever leaving the 'top layer'. The dimensions would somehow automatically adjust to the scale of the viewport underneath - and would automatically change when the scale of the viewport is changed and move, when the viewport is moved. And why not?
  22. I want to plant trees along an editable path. Using image props as posts with the railing/Fence tool could do the trick. Except it cannot. The textures are lost in the process. 😐 I wish it could. Or a similar parametric method to do the same with the architect license...
  23. Multible Extrude has not changed since MiniCad, and it is the only extrusion tool, that does not support nurbs. Which is the only reason, that I almost never use it. I can see how some geometry may be too complicated be used for a nurbs-based multible extrude. But when the command is invoked, it should try. Or maybe there should be a setting, that allows simple geometry to produce nurbs-based multible extrudes, if it can be done.
×
×
  • Create New...