VW2017 - OpenGL render not working in SL viewports which view DLVPs

[digitalcarbon 243]

bug - OpenGL Section Cuts - Fail

i sent the file to luis.

(i can not even begin to think how i would type this up.  the bug team will need to watch the video and get the file from Luis) 

 

[digitalcarbon 243]

ok, if you turn on foreground rendering to hidden line it works but if you turn it off and re-render it goes back to missing fill

[digitalcarbon 243]

nope still not working even with foreground rendering set to hidden line

[digitalcarbon 243]

exported back to 2016 and re-rendered in OpenGL with foreground render set to none and it works fine

[line-weight 407]

This is a problem which has arisen in a file converted from a 2016 version and opened in 2017.

 

I have a design layer, on which I have some Design Layer Viewports. These DLVP are section viewports generated from the clip cube.

 

Then I have a sheet layer. On this layer, I have Sheet Layer Viewports which are perspective views of those DLVPs on the design layer. This is how I generate 3D sliced sections through the model.

 

Those SLVPs are set with Background Render = Open GL and Foreground Render = None.

 

In VW2016 this works fine.

 

But imported into VW2017, those SLVPs are empty. The geometry is there because if I change Background Render to wireframe, it shows up as expected. Setting it back to OpenGL, everything disappears again.

 

I've tried generating the sections and viewports afresh, but the same still happens.

 

Elsewhere I have SLVPs that are direct 3d views of the model (ie. no intermediate DLVP stage) but these are fine if I render them in OpenGL. So the problem seems to be something related to the SLVP viewing DLVP viewing model setup.

 

I'm not sure whether this might be related to the problem described in this thread:

 

 

[PVA - Jim 2,292]

Does this only happen in OpenGL or in Renderworks modes as well?

[line-weight 407]

Hi JimW.

 

I've just tried rendering the same viewport in a couple of Renderworks modes and it seems to be fine. So only a problem in OpenGL as far as I can see.

[PVA - Jim 2,292]

If you create a new section of a DLVP in 2017 on a new sheet layer, does it appear to have the same problem? Or is it only the sections that were created before the 2017 conversion that do this? 

 

Testing a few things here as well now.

[PVA - Jim 2,292]

Nope, nevermind, got it to happen here. Submitting it as a bug now, thank you. 

 

Threads merged. VB-137044

[line-weight 407]

To be clear - it's the DLVP that is the section viewport - then it's just a "normal" viewport of that which is on the Sheet Layer.

 

But I've made a new sheet layer, and make a new viewport (looking at the DLVP) on that, and the problems is still there - nothing in OpenGL.

[PVA - Jim 2,292]

Yep I had my tests set up improperly at first, I was mistakenly including both the original objects and the DLVP geometry, but once i limited the layers in the section viewport to only show the DLVP on its own layer it was very obvious.

[line-weight 407]

Great - thanks for responding so quickly.

[Patrick Fritsch 51]

Was this resolved? It's happening to me in VW 2018 SP3. OPEN GL section viewports are blank...

[Corey Verdusco 1]

I'm having the same issue in 2018 SP3

[line-weight 407]

This bug was submitted over 18 months ago.

[Patrick Fritsch 51]

This has not been resolved in VW 2019 SP1, if I create the section viewport from a Design layer it will render in Open GL but not is I create the section viewport from another viewport...Do you want my file ?

[PVA - Jim 2,292]

1 minute ago, Patrick Fritsch said:

This has not been resolved in VW 2019 SP1, if I create the section viewport from a Design layer it will render in Open GL but not is I create the section viewport from another viewport...Do you want my file ?

Please!

[MHBrown 11]

Why has this OpenGL problem not been solved? Because OpenGL does not work inside groups and other editing windows (like Symbols) you cannot do texture mapping in VW. The Attributes tool does not work because the OpenGL image disappears. You can work with Fast Renderworks, but that is, ironically, slow. I usually use Strata3D for my rendering and it used to be the buggy software. Now it's VW that is a problem. It is NOT a rendering program if you can't see what you are doing. Furthermore, you cannot select objects when they are rendered...assuming you get OpenGL to work in the handful of situations where it does work.

This must be fixed before I continue the subscription. This has been happening for a couple of years now. When will it be fixed?

MHBrown

[markdd 404]

9 minutes ago, MHBrown said:

Why has this OpenGL problem not been solved? Because OpenGL does not work inside groups and other editing windows (like Symbols) you cannot do texture mapping in VW

I use OpenGL in Groups and Symbols all the time and it works well. The only time that OpenGL will not work is when you are editing from a sheet layer. 

[MHBrown 11]

Mark, I'm glad it works for you in those windows, but it does not work for me. Regardless, OpenGL should work when editing from a sheet layer. It should always work everywhere. Anything less is unacceptable. Right not, some combination of VW, my video card, or something is causing OpenGL to fail. It is NOT my individual file. It happens everywhere. It may have to do with files created in VW2016 or VW2017, but it is very, very, very, very, very common to start a job in one version of VW and finish it in another. This minimal compatibility should be top of the list for future versions, but apparently it is not. I think that is the problem and it needs to be fixed if VW is going to continue its absurd release frequency of once a year---twice what it should be, in my opinion, to ensure a stable product.

[PVA - Jim 2,292]

2 minutes ago, MHBrown said:

Mark, I'm glad it works for you in those windows, but it does not work for me.

 

17 hours ago, markdd said:

I use OpenGL in Groups and Symbols all the time and it works well. The only time that OpenGL will not work is when you are editing from a sheet layer. 

It had been working but I have now seen this problem even in my own files, restart doesn't always correct it either, sometimes i need to edit a symbol on the design layer before i can edit in the resource manager again, or a group within a symbol. I will be reconfirming and resubmitting this one if there isn't already an active bug on it for sp2.

(This was different from the original post topic but just thought it merited mentioning)

[MHBrown 11]

The problem seems to be with working in 2018 with files created in a previous version. This is an unforgivable oversight. I would wager that--especially with the accelerated, yearly upgrades--that nearly 100 percent of VectorWorks users start in one version and complete in another. My work around is to have an Untitled 2018 file open next to my real file. I copy and past anything I need to work on into that file and then copy and paste back. OpenGL works great in the Untitled file. This, however, is not an acceptable workflow step. Is this fixed in version 2019?

[Patrick Fritsch 51]

I don't know if VW get's it, but they need to slow down on the annual release features that simply make the latest version UNUSABLE.

 

To top it off they actually advertised that this release as follows and I quote "Dr. Sarkar said this year when they approached the development of version 2019 they divided 90 tasks into three major categories. These three categories were simplifying workflows, enhancing modeling, and lastly, enhancing quality and performance."

 

Pretty hard to do when the software barely works, Rant over!

[Jordan 0]

Having a similar issue occur in VW 19'. Open GL style viewports not appearing in Sheet Layers. However, when I scroll to zoom, the layers appear then disappear when I stop zooming. Super weird.

[michaelk 235]

Do you have the latest service pack?

[MHBrown 11]

Yes. I have the latest service pack. Why do people always ask that? That has never helped an unknown problem. This is a big problem with VW not having the resources to do a major upgrade every year. Is there an SP for that problem?