Renders Turning Black Once Updated

[Renders Turning Black Once Updated]

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!

[Texture Size]

6 minutes ago, Nuno Antunes said:

This node only affect the Mapping of the Object, not the entire texture of the file, correct.

Yes, only the mapping.

[Texture Size]

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.

[Vortex box]

Use a function perhaps, like x*x*50 or something similar?

[Texture Mapping with Marionette]

@Nuno Antunessee my reply to this thread, it has an object attached with some texture manipulation that should answer all your questions:

 

[Texture Size]

@Nuno Antunescheck out my Box objects. I am resizing the texture to fit to the lid for example. Does this help?

 

Box.vwx

[VW 2020 Suggestions]

I can only comment on the auto-cutout for countertop wish: That is entirely possible with the full version of interiorcad. You can group a routing contour with a sink symbol and have it behave like a window in a wall:

[Cabinet Drawers]

Is this the "Custom Cabinet" you are referring to? You can click inside a segment and adjust its size as shown in the screen shot.There are more advanced options in the full-blown version of interiorcad. Some videos here.

[Vortex box]

Try this. It's not far off, just needs some refinement.

 

Vortex Box.vwx

[Vortex box]

@Palle You need to supply a list of values to the rect and, subsequently, extrude node. That will take care of everything. The ordered list is not necessary for this kind of thing.

[Updated Books (2.1)]

The Books have been converted to run with VWX 2019 and I fixed an error where the 'Hardcover' library needed a shelf depth and height of 2m to produce any books.

[Vectorworks User Interface Overhaul]

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").

[Vectorworks User Interface Overhaul]

Interesting poll about colour in the Archicad UI after it was made all white. Yeah, one needs to be careful, users are fickle... 🙂

 

[Vectorworks User Interface Overhaul]

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.

[Vectorworks User Interface Overhaul]

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).

[Renderworks and OpenGL produce black backgrounds on one machine, render fine on my computer]

4 hours ago, David S said:

update driver

set the VW preferences to good performance

check the driver is pointing at VW not an internal graphics card

Oh, yes, sorry, forgot to mention that. Those are the first things we check. Thanks!

[Renderworks and OpenGL produce black backgrounds on one machine, render fine on my computer]

28 minutes ago, Bas Vellekoop said:

IMO i do not think this is the same thing, it this is a very persistent problem.

A restart does not fix it and it is visible in the resourse browser as well.

 Confirmed. The Resource Manager previews also show the black backgrounds. Once edited on a different machine, they return to normal.

[Renderworks and OpenGL produce black backgrounds on one machine, render fine on my computer]

Today everything is back to what it was before. So, again, the user folder must be reset to fix the black renders. I wonder what brings this about. Is there anything the customer might be doing, that provokes this behaviour?

[Renderworks and OpenGL produce black backgrounds on one machine, render fine on my computer]

Thank you @David Sand @Bas Vellekoop. Bas' suggestion solved the problem so thanks for saving my day! Yes, deleting the user folder is kind of brute force and should be done with care. I have restored the customer's workspace and everything seems fine now.

[Renderworks and OpenGL produce black backgrounds on one machine, render fine on my computer]

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!

[Dark Theme Please]

Check out this mockup and while you're there: please upvote the topic 🙂  Thanks!

[Vectorworks User Interface Overhaul]

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....

[Vectorworks User Interface Overhaul]

I made another little video. There were some comments and suggestions about the OIP earlier in this thread which I thought about. (There's more to come. I have been thinking about why the Attributes Palette is not part of the OIP and I think I must be overlooking something...) and I received some personal messages about how some of the things I proposed did not come across in an understandable way. Goes to show that everyone, including myself, struggles with that elusive chasm between sender and receiver. 

As always, here my little disclaimer: I haven't the slightest clue if any of what I am proposing makes any sense to anyone else or if it is even possible to implement in Vectorworks. Still, please upvote this if you haven't already (the little green triangle, right at the top...) 🙂 
PS - there's a little bonus extra at the end. Wait for it...

 

[Preview Render]

On 10/17/2018 at 4:29 PM, Andy Broomell said:

On Sheet Layers, one thing I currently do is duplicate the viewport in place, then use the Clip tool in Inclusion mode to draw a marquee around the small part of the rendering I want to see, then hit update.

That's how I do it. 

[Vectorworks User Interface Overhaul]

1 minute ago, zoomer said:

(or forget my last 5 Icons at the end of the list of Palettes I seldom use)

That's what the gradients are for. But you may be right after all. I suspect it would be too much of a paradigm-change 🙂