Jump to content
  • 0
EAlexander

Assign to layer BUG

Question

I can crash VW2017 on my system every time by moving and object from one layer to another via the OIP.  This is happening with 3D objects in files picked up from 2016.  

To test, I made a new 2017 document, made two layers, drew a rectangle on one, and when I change it's layer via OIP, instant crash.  So what exactly is the best way to report this with system and OS specs to tech?

Thanks,

e.

  • Like 1

Share this post


Link to post

Recommended Posts

  • 0

This has happened to me a few times. I guess the bug submit area of the forum is the place to go.

Share this post


Link to post
  • 0

Send us the file along with this:

http://kbase.vectorworks.net/questions/627/DirectX+Diagnostics+and+System+Profiler

from your machine please. Moving this thread into Troubleshooting, you can just add the file here. any new cases you find should be new posts in Troubleshooting, from there once they are confirmed, I will move them to Known Issues for public tracking.

Share this post


Link to post
  • 0
8 minutes ago, markdd said:

Bottom of the forum list there is a grey area that says bug submit

^ Either via this page, or feel free to attach it to a post in Troubleshooting, either route gets them to the proper place. Eventually we will do it differently (add a little more automation) but for now both of these work fine.

Share this post


Link to post
  • 0

So have I! If this problem persists it will mean that spotlight is unusable for me.

Edited by markdd
apdated
  • Like 2

Share this post


Link to post
  • 1

Confirmed, this issue affects users with Fundamentals only or Spotlight only it looks like. Many reports of this happening, going to push for this one to be fixed ASAP for obvious reasons.

VB-136713

  • Like 2

Share this post


Link to post
  • 0
1 hour ago, JimW said:

Confirmed, this issue affects users with Fundamentals only or Spotlight only it looks like. Many reports of this happening, going to push for this one to be fixed ASAP for obvious reasons.

VB-136713

Yes, this is bad news as I am not going to be able to work with this version of VW until it is fixed. A special update perhaps?

Share this post


Link to post
  • 1
1 minute ago, markdd said:

Yes, this is bad news as I am not going to be able to work with this version of VW until it is fixed. A special update perhaps?

Pushing for one! This is bad bad bad.

  • Like 2

Share this post


Link to post
  • 0

It also happens when i assign it to a layer via object info.... 

staying on 16 for now

Share this post


Link to post
  • 1

I know it's not very helpful, but it seems that something like this should have been caught in beta testing.

Edited by rDesign
  • Like 1

Share this post


Link to post
  • 0
10 minutes ago, rDesign said:

I know it's not very helpful, but it seems that something like this should have been caught in beta testing.

I mean, yeah, but same problems and reasons as every bug in every software, unfortunately.

We're on it.

Share this post


Link to post
  • 0

Open Beta :) otherwise its impossible to test a wide range of workflows. I never move an object from one layer to another using the Layer dropdown in the OIP. I always use Cut/Paste in Place. I wouldn't even know this bug exists except for this forum post.....

Kevin

Share this post


Link to post
  • 1
1 minute ago, Kevin McAllister said:

Open Beta :) otherwise its impossible to test a wide range of workflows. I never move an object from one layer to another using the Layer dropdown in the OIP. I always use Cut/Paste in Place. I wouldn't even know this bug exists except for this forum post.....

Kevin

This is the "Problem" (Not really a problem in my view) of public lists of Known Issues like we are now doing this year. Everyone sees every problem even if they don't come across it themselves. 

It will take some getting used to, but openness is better.

  • Like 1

Share this post


Link to post
  • 0

Paste in place is a workaround but messing up with my Flow and with the flow of other team members which I trained . I told them to hold off on 17 for now because they will drive my nuts with other issues that they will find.

 

Share this post


Link to post
  • 0
1 hour ago, Kevin McAllister said:

Open Beta :) otherwise its impossible to test a wide range of workflows. I never move an object from one layer to another using the Layer dropdown in the OIP. I always use Cut/Paste in Place. I wouldn't even know this bug exists except for this forum post.....

Kevin

Whereas I do this all the time: Moving objects between layers via the OIP layer dropdown (I have a lot of Layers).

It just proves that there's more than one way to make your software crash. ;)

Share this post


Link to post
  • 0

Issue identified in code, fix is in the works and we are going to see how fast we can get something out to users without having to wait, ideally.

Share this post


Link to post
  • 0
11 hours ago, jonmg2005 said:

I'm stumped, any ideas?  

My crash log is attached.

Thanks

VW CRASH.txt

Working on a fix for this now.

Share this post


Link to post
  • 0

Glad I'm not the only one! Good idea on cut and paste in place. I feel like the time saved using the search function makes up for the extra time of moving things between layers at the moment. I hope there is a fix available within the week,

 

 

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

 

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.

×