Jump to content

Stephan Moenninghoff

  • Content Count

  • Joined

  • Last visited

Posts posted by Stephan Moenninghoff

  1. On 12/3/2018 at 4:16 PM, Jim Wilson said:

    I am still looking for reports of this happening in 2019 SP2 specifically. If it is still happening in 2018 SP5.1, there is a CHANCE it could be fixed for SP6 but only if we can identify what the issue actually was, and if it isn't tied to the Cinerender engine version which can't be upgraded in 2018.

    @Jim Wilson I think it's gone. I haven't seen it since SP2. Thanks!

  2. 1 minute ago, Nuno Antunes said:

    Please confirm if is this?

    Think so. It's been a while. I had a quick look inside the wrapper and it looks like this:

    Feed the values in according to the node description. You may have to string several of these together.

    Bildschirmfoto 2018-12-04 um 16.21.45.png

  3. 1 hour ago, Kevin McAllister said:


    I'm very surprised to read this. What I like about the demo videos you've shared is almost entirely about how the interface you're proposing  *feels* and *functions*. 

    Yes but what I am proposing are changes pertaining to the functioning of the UI. That's UX. What I was trying to say was, let's not confuse VWX functions ("How do I change the crop of a viewport") with UI functions ("How do I access the side pane widget while the RM is in a docked state").

    • Like 3

  4. 2 minutes ago, Jim Wilson said:

    For instance, we completely reworked the Resource Browser into the Resource Manager, and plenty of users have had time to acclimate. I think our eyes are on the OIP and Nav palettes next. If we had done all three at once though I suspect there would have been much more discomfort.


    Jim, with the Resource Manager, users were not given a choice though. They *had* to use it. And while it's better than before, the UI does still not allow for the RM to be used in a docked state. I do tech support once a week (because I want to) and whenever I Teamviewer into customers' screens, I see the RM floating and collapsed. Why? Because its options are not visible in a docked and hence narrow state. This is a pure UX thing and I think it needs to be addressed. I have detailed how it could be addressed in my prototype. I am not proposing that my graphics be used (I think they are just next year's old UI and some young, talented designers will do a better job, no doubt) but the way it *behaves* isn't right. It's a usability bug if nothing else.

    • Like 2

  5. 1 hour ago, Mark Aceto said:

    I love that we're all obsessing over GPU's, multiple cores...  and then spend 15min individually updating a single revision note repeated on every single sheet of a drawing set. And the cherry on top is when I double click a revision note, nothing happens. Sort of like double clicking a column to autofit it will either A) autofit the column or B) minimize the column to 1 pixel wide or C) maximize the column 30' to the right.

    Dark mode would be nice but these are the UI/UX issues that consistently keep me at work past 11pm.

    All good and well but please let's not create the standard excuse for not caring about the aesthetics of the UI here. This thread is and has been about how VWX *looks*. Perhaps also a little bit about how it *feels*. But not about how it *functions*. A modern appearance is completely separate from functionality and what this thread is about is mostly aesthetics. Improving on features has never been a weak part of VWX, in fact I think we must admit that huge progress has been made over the past years. This all has happened while maintaining a dated and clunky UI. That is what this thread is about so please let's not muddy the message by such comments (although I'm sure it is a valid comment in a different thread).

    • Like 1

  6. Here are two viewports rendered with OpenGL (top) and Renderworks (bottom) on a client machine (left) and the same viewports rendered on my computer (right). The client is quite desperate because he is getting these black backgrounds in both OpenGL and Renderworks intermittently. He is also seeing white (RGB 255,255,255) areas in rendered images turning black on his computers but nobody is able to reproduce the behaviour anywhere else.

    Any ideas? Thanks!

    Bildschirmfoto 2018-11-15 um 11.02.07.png

  7. 3 hours ago, Matt Overton said:

    I think the filter type tabs of your Resource browser would work well for object info as well.


    We have had separate tabs for  Data and render for a long time and much smaller screens.

    Meanwhile, the complexity of plug-ins has increased, renderworks has become stock and marionette has been added. All things pushing for more tabs to help find information but also less tabs because that information shouldn't be out of the way nor does it need to be now we have larger screens.


    Thinking tabs would be, say, Location, Shape, Massing, Object Settings,  Attributes(incl render), Data, Tool Settings....

    FIltering would then allow us to trim information to suit with nothing hidden more than a click away.

    Tabs would definitely have to be more dynamic. Developers should be able to decide which tabs, besides the stock ones, they want to add. Also, why is the Attribute Palette not part of the OIP? There are some really nice opportunities there. Just think class attributes and the like. I still keep thinking I'm overlooking something though and there are some logical clashes there....

    • Like 4


7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114


© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

  • Create New...