my VW 2018 SP0 issues

[zoomer]

After working a while I experienced following issues.

 

1.

Best Performance GPU setting reached a state again where it forgets to show any geometry changes

(Like in VW 2017 SP 0-3)

 

2.

When using Visibility Tool and hover over my DLVP referenced 2D Geometry in Top Plan View,

it will highlight possible Classes's Objects in an Isometric Orientation (!?)

(I use single Pane View only !)

 

3.

I reached a state where "Undo" did no more Geometry Change's Undos but View Change* Undos only

(*I think Class/Layer changes where included)

I have always set VW Pref "Undo" > View Changes to "never".

It needed a VW restart.

 

4.

Many simple Tasks, like in Layer/Class Organisation or such things, lag or are extremely slow.

 

5. (Solved !)

For my referenced 2D Geometries DLVPs I have to activate "Zoom Line Thickness"

to make the lines stay thin, so that I can see my geometry.

(I think I noticed that already in VW 2017 ?)

while when being in a Sheet Layer I have to switch it off, as expected, to keep thin lines.

For me that looks like something is mixed up there.

Edited October 8, 2017 by zoomer

[zoomer]

6.

I have that same "VGM" crash every half an hour.

(Although I save after each Tool/Command)

 

Time Awake Since Boot: 31000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x00000000000000c0
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [0]

VM Regions Near 0xc0:
--> 
    __TEXT                 0000000109e66000-000000010d53f000 [ 54.8M] r-x/rwx SM=COW  /Applications/Vectorworks 2018/Vectorworks 2018.app/Contents/MacOS/Vectorworks

Application Specific Signatures:
{"sn":"EDXEGZ-XXXXXX-XXXXXX-G0DJTN", "ts":"6f68656c1", "platform":"MAC", "os_ver":"10.13.0", "vw_ver":"2018 [23.0.0(389445)] (64-Bit app)", "error_reporting_mode":2}

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   ???                               0x00000000000000c0 0 + 192
1   net.nemetschek.vectorworks.VWGraphicsModule    0x00000001355ad799 VGM::GetTextImage(VGM::ISystems*, VGM::Material*, void*, unsigned short, VGM::IClientServices*) + 395
2   net.nemetschek.vectorworks.VWGraphicsModule    0x00000001355d4e4c VGM::GraphicsEngine::UpdateTextTextures() + 188
3   net.nemetschek.vectorworks.VWGraphicsModule    0x00000001355d59f1 VGM::GraphicsEngine::RenderScene(glm::detail::tvec4<int> const&, unsigned int, unsigned int, unsigned int, VGM::FrameQuality const&, VGM::DisplayMode, void*) + 813
4   net.nemetschek.vectorworks        0x000000010c3b23c4 0x109e66000 + 39109572
5   net.nemetschek.vectorworks        0x000000010b9606b0 0x109e66000 + 28288688
6   net.nemetschek.vectorworks        0x000000010b968180 0x109e66000 + 28320128
7   net.nemetschek.vectorworks        0x000000010b969480 0x109e66000 + 28324992
8   net.nemetschek.vectorworks        0x000000010b243488 0x109e66000 + 20829320
9   net.nemetschek.vectorworks        0x000000010b95dd79 0x109e66000 + 28278137
10  net.nemetschek.vectorworks        0x000000010b96e073 0x109e66000 + 28344435
11  net.nemetschek.vectorworks        0x000000010abcd82a 0x109e66000 + 14055466
12  net.nemetschek.vectorworks        0x000000010a034e53 0x109e66000 + 1896019
13  com.apple.AppKit                  0x00007fff25f1a50c _NSViewWillDraw + 45
14  com.apple.AppKit                  0x00007fff257a503f -[NSView viewWillDraw] + 1092
15  com.apple.AppKit                  0x00007fff25f1a50c _NSViewWillDraw + 45
16  com.apple.AppKit                  0x00007fff257a503f -[NSView viewWillDraw] + 1092
17  com.apple.AppKit                  0x00007fff25f1a50c _NSViewWillDraw + 45

[zoomer]

17 hours ago, zoomer said:

5.

For my referenced 2D Geometries DLVPs I have to activate "Zoom Line Thickness"

to make the lines stay thin, so that I can see my geometry.

(I think I noticed that already in VW 2017 ?)

while when being in a Sheet Layer I have to switch it off, as expected, to keep thin lines.

For me that looks like something is mixed up there.

 

Looks like there is nothing mixed up and it's working as expected.

There were very thick lines (applied in a per object mode) imported in the DWGs.

[zoomer]

On the other hand, when not dealing with DLVPs,

VW 2018 runs totally flawless since 2 days.

(none of 1.-6. !!!)

 

That is great.

 

 

But I still fight with : 

 

7. Push Pull Tool Blindness 

PPT does not find even simple DL-planed Rectangles with Fill in Isometric.

Looks like only one single point of the whole Rectangle is selectable, so no chance

if that point is hidden by other Rectangles already extruded, although large parts of

its face are visible directly.

 

Disabling other Layers/Classes Edit/Visibility did not help.

Normal Selection - to extrude manually by CMD+E - works flawlessly.

 

BTW,

I may have set their Class to have some Fill Transparency.

 

 

 

Edited October 10, 2017 by zoomer

[Art V]

10 hours ago, zoomer said:

On the other hand, when not dealing with DLVPs,

VW 2018 runs totally flawless since 2 days.

(none of 1.-6. !!!)

 

That is great.

 

Now that is really good to hear as I have been hesitant to use VW2018 for now because of all the reported issues. The downside is that when I use DLVPs it is usually for large (or large number of objects) drawings so I hope that SP1 fixes the issues.

[zoomer]

I was told that many of those issues may already be listed as bugs, some should be already solved.

Will see when SP1 comes out, or if it needs another one or more SPs.

 

Normally I don't have many crashes with later VW Versions.

It was just a lot with VW 2017 and editing Site Models and VW 2018 with DLVP editing and creation.

 

But last similar serious DLVP editing before was already years ago so I would not wonder if the

same crashes would have appeared in VW 2017 too or that it is not a new VW 2018 thing.

As I was told the DLVP System is quite complicated and it maybe wasn't estimated that people use

it that extensive.

As long as those DLVP from referenced Geometry are just laying around and their visibility gets altered,

there seems to be no big problem with these for me so far.

[bjoerka]

sp1 is a not really helpful when working with multiple view panes.

i often get a spinball and vw does not react anymore when more than 2 panes are set up...

 

Edited October 11, 2017 by bjoerka

[Art V]

Fortunately my DLVPs are just laying around and when changes need to be made it will normally be in the source file, so that is a non-issue for me then.

[zoomer]

17 hours ago, bjoerka said:

sp1 is a not really helpful when working with multiple view panes.

i often get a spinball and vw does not react anymore when more than 2 panes are set up...

 

 

What Tools are you actually using ?

 

I work single Pane only but have heavy lags updating PIO Styles.

Not sure if this will always open the beachball, at least I have to wait.

 

And switching parts of Geometry Visibilities of large Files as always may need some time to

reload to the GPU for OpenGL display. Should take even longer.

(Also not sure if this really opens the beachball ?)

 

But you have a MBP with discrete GPU, so on the save side.

 

Could it be something like this too

or are you sure it is Multi Pane View ?