Jump to content

Anthony Neary

  • Posts

  • Joined

  • Last visited


21 Great

Personal Information

  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Alienware users - the information at this link: https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/297952/nahimic-and-nvidia-drivers-conflict/ has so far worked for me on an alienware M15 R5 Ryzen edition. I can now change workspaces and resize my windows and I am not getting the DLL crash. Remains to be seen if I run in to issues elsewhere, but so far so good. Essentially you need to add the VW executable to a blacklist of programs for the Nihimic audio tools.
  2. Well this is just ridiculous. No previous version of Vectorworks has had an issue with Dell and Alienware support services, and frankly I am not going to uninstall core features of a laptop I've purchased to be able to run a piece of software that should operate perfectly fine alongside them. Just installed 2022 finally, and frankly it's unusable. At this point I may as well uninstall 2022, reinstall 2021, cancel my VSS license, and just stick with 2021. I'd like to think a fix was coming, but considering that we are apparently already on SP3 it seems pretty bloody unlikely.
  3. Plain just turns it in to a basic sheet of glass, from what I was mucking with object fill colour had no effect, though that would have been a nice shortcut
  4. Once you apply transparency the texture ignores the object colour and just uses the colour set in the transparency shader. With the lens object using a glow texture, let's say you have a render where you're looking at the lens, the glow texture doesn't give that "staring at a light" effect. If you turn the glow texture brightness up it mucks with the colour saturation, eventually just turning white. You can muck around with a renderworks camera and go through the exposure etc, and try to balance all of the other lighting objects, but If I could put a really bright white glow texture "inside" the fixture, and have the lens object by a transparency, then my bright glow object would be coloured by the transparency and I solve my "not being able to turn up a glow texture brightness" issue.
  5. Right now, in a drawing, if I want green, red, and blue glass, I need to create separate green, red, and blue glass textures. But I can use a single glow texture, apply it to ten different objects, give them a different object fill colour, and the glow texture for each object changes colour. If I could have a single transparency texture and apply it to different objects, and have it use the object colour for the transparency, there are a number of things I can now do with that texture. One of them would be to play around with using a transparency texture on a 'gel' object in front of a spotlight instrument, and my rendering might look more realistic than the glow texture, which has limitations in brightness capability.
  6. Right now we can use a single texture for things like glow textures, across multiple items, and the glow texture uses the object colour. If we could do that with transparencies, you could have one glass texture and use it across multiple items and have the object colour affect the glass transparency colour. Seems like a useful option.
  7. I find it weird that we can't set a transparency shader to use the object attribute colour, would seem like a useful option.
  8. I would really like to see Glow Textures get "fixed" so that if you increase the brightness over 100 it doesn't 'over-expose' the colour to white (or give us an option either way). I'm trying to make my fixtures look like the fronts are glowing relatively realistically in renders, and re-balancing the entire drawing (camera exposure, other glow texture brightness, render light brightness, etc) around trying to make the lens glow texture flare as if you are looking at the fixture is a real pain in the ass. It would seem far easier to just be able to turn up the brightness on my lens glow texture without it washing the colour out to white when I do so. To me this seems like a simply fix.
  9. Did a quick search but didn't see a topic about this already. So 2020 is doing a weird thing. Every so often my menus go grey and stop functioning. For example File>Save is greyed out and will not perform it's action. The only way I can save is to close the program and say Yes to the save prompt. All of my menu options get greyed out and nothing works. Restarting VW corrects the issue.
  10. I'm not sure what I am doing incorrectly here. I am playing around with the Renderworks Camera Tool with the exposure, bloom, etc settings, and I am not seeing any differences when rendering. Now, I am just in my design layer and using a selection of custom render styles to mess around here. Is there a setting in the render styles that has to be active for the camera effects to be applied? Or do they only work on viewports in sheet layers? Otherwise as I said, I am not seeing any change in my results when adjusting camera settings like exposure and bloom. What I am playing around with is wanting to adjust exposure and bloom so that my spotlight lens glow texture looks like the fixture is actually emitting light as in real life. Then will adjust exposure and spotlight object light brightness to get my renders looking more realistic. This was a suggestion from Jim a while ago I just haven't had time to sit down and play around with it. I feel like I'm missing something. Running 2020 SP2.
  11. I might be splitting hairs on this, but I find it constantly annoying. Alright, let's say I create a cropped viewport on a sheet layer, then I go in to the viewport and move the crop, I would really like Vectorworks to be a bit smarter and keep the viewport crop centered on the sheet layer where it was originally and not make me run after the viewport and move the object back to where it was on the sheet layer. Surely this is feasible?
  12. Are there Release Notes anywhere for what has been changed/fixed in SP5? Can't seem to locate anything.
  13. @JuanPWhatever the issue is it seems tied to Desktop updates, when I turned off my background image slide show in the desktop Theme all issues stopped.
  14. Update, the culprit seems to be the desktop background image slide show. The hiccups were aligned to just after the desktop changed to a new image, disabled the slide show on the desktop and VW seems to be happier. So MS seems to have done something to the backend causing screen processing or refreshing issues or something.
  • Create New...