ptoner
-
Posts
108 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Articles
Marionette
Store
Posts posted by ptoner
-
-
Getting this also with Revit files, I am sure that the originator would not be using Revit 2010, I will check and see if they are and confirm.
Sender confirmed that the file was in Revit 2016. Using Vectorworks 2018 SP3 and it says unsupported.
Seems to import in 2017 SP5, but taking forever. Will update with the outcome.
Possible bug in VW2018 SP3. -
54 minutes ago, Tolu said:
This is a symptom of improperly configured user permissions on the Mac Server. Have you tried enabling “Direct Safe Save”? This can help when your user permissions are improperly configured. This option is available under the Settings tab of the Project Sharing dialog. By the way, all users need full access to the shared folder.
Did you configure the PF to only accept a specific protocol? If so, which protocol did you choose?
We use Xserve RAID for storage of files.
I will look into the "Direct Safe Save".We selected AFP as SMB on a mac network creates directory issues.
-
18 hours ago, Tolu said:
On what type of server is your Project File located?
Check that your PF is indeed writeable. Vectorworks shows that message whenever it is unable to write to the PF
Server is running OSX Server, on a maxxed out Mac Mini Spec. We are all running OSX on iMacs OSX 10.13.3 and have 40 stations.
This is the first time I have used workgroup sharing as a test and clearly, it is not fit for purpose.
Some how the permissions on the on the PF changed to read only. As IT admin also, I changed the permissions for the file back to read/write. Still would not work.
At this stage due to the unchecked out layers and the above issue, none of the staff in my workplace will be using this feature.
Do not have time on quick turn around projects to waste time on bugs like the above.
We were working form a WF located on the local machines with the saves and commit being copied to the PF on the server. Network speeds are not an issue. The software is.
-
Only started using this today... having serious issues with users not releasing classes/layers and now I am being told the Project file is in use, by another user when no one else has it open!
-
Yeah, the text wraps if you have spaces between words. If you have labeled a drawing in order to comply with BIM Level 2, no spaces, with underscores instead.... the text keeps going in a line. It should wrap to the text box, but it doesn't. Very problematic.
-
3 minutes ago, Mihail Rizov said:
If you want to speedup your IFC Export - please, switch to OpenGL and zoom in close to the building, so that nothing from the building is visible.
I always have OpenGL on, still it takes forever.
Zooming into the building speeds it up, bizarre. Will try it anyways, cause at this stage anything is better than what it is.-
1
-
-
Jims solution worked for users that must have click the tick box, in our company.
Side effect is, all their other settings reset also, like toolbar shortcuts etc -
Thats pretty pathetic, seems we are continually going to have at least one machine , out of use when exporting/importing IFC etc.
That is not good!
How come ArchiCAD can do it in minutes, with the same file?
This needs urgently looked at IMO. -
Yeah. that's the only thing that we could pin it on. Hope the curtain walling is made more efficient down the line.
-
Not ready for UK either, still at this point. Massive lack of objects available, and revit import is poor still, fraught with issues.
Its actually a sits out like a sore thumb the lack of support for proper BIM objects. -
On 08/01/2018 at 2:19 PM, zoomer said:
This will only help if you have some curved geometry like cylindrical columns and such.
(Or things like furniture Symbols !)
It can't reduce geometry of rectangular geometry like straight Walls and such.
Yes IFC exports take a lot of time in VW and need a lot of RAM.
Geometry expensive Furniture Symbols can have a large impact.
Especially for exports where the may not export as Symbols/instances but separate objects.
I have not much experience if that works faster in other Apps or if there is still much potential
for improvements in VW.
No furniture in the model, walls, doors, floors, ceilings and curtain walling mainly.
-
I take it no one has actual experience of exporting .ifc' s then.
-
17 hours ago, Kevin McAllister said:
How are you "attaching" the record? I just experimented a bit and it seems to work differently with the new Title Block Border. VW sees any text created in the Title Block edit space as "Text in Title Block". The link is established by checking the Link Value checkbox in the OIP and then selecting the field to link it to in the "Parameter" dropdown. I'm not sure that you can still use the old method.
Kevin
Thanks, tired this and associated the text to the record, via link value. It shows up the path then in the template/style but when you come out of the editing process and have it viewed normally. It does not show. Any further assistance? @Kevin McAllister
-
Having issues trying to get the Titleblock Style to show the file path of the drawing.
Attached record, and enabled the option, yet still nothing.
Has anyone else the same issue or advise me on what to do properly?
-
Having issues exporting an ifc file. Everything converts and exports as it should, yet it takes 45mins plus for it to process and complete.
File size, after purging is 370mb approx.
Stories all set up correctly, for each of the 16 stories. Set in plan/top view when exporting, 3D conversion is "low" and most settings are as per the Vectorworks "Sharing your model with IFC" Document.
Really is poor, as it means that no drawing work can be done until after the export. ArchiCAD users in the office export larger buildings than this in under a min in work.
Any further tips? or is this standard for VW?
You can see from the attached image, there is not a lot of detail in the model.Also attached is my computer specs. Its a top of the range iMac
-
1
-
-
On 21/10/2017 at 7:41 AM, Kevin McAllister said:
After my bug submission I received an email reply with the steps to reset my VW user folder and preferences. This solved the title block scaling issue for me in the current public build of VW2018 SP1 (unfortunately it created another issue where I get an error dialog about the Vision Libraries which I'm working with Tech Support to solve).
Kevin
What was the procedure that they told you to do, in order to get the scaling of the titleblocks reset?
-
On 13/09/2017 at 9:13 AM, markdd said:
tioning issue, I found this. If you change the origin of your sheet layer to the centre then all is well. Use the Move Page tool (nested under the Pan tool) to move the page to the centre. This seems to be the case with my drawin
Your build differs from mine and I am using titleblocks that we created ourselves, that have been updated, to suit the new title block parameters/settings/dialog boxes.
So I am thinking its a conversion issue, with 2017 titleblocks.
I imagine it is a bug. I will report it.
-
15 minutes ago, Nikolay Zhelyazkov said:
I am testing it in SP1, build 390873, and it is working. If it is not working for you, please fill in a bug report.
Thanks,
Yes, you can insert the 0.5 scale factor, but it will not actually change anything.
You guys really need to test it properly before commenting. -
3 minutes ago, Nikolay Zhelyazkov said:
Hello ptoner,
This is possible through the Scale Factor control in Title Block Settings dialog -> Title Block pane from SP-1.
Best Regards,
Nikolay Zhelyazkov
yes you can scale from 1 up... but not make the titleblcok smaller by using 0.8 for example. Thats using SP1 -
Another Titleblock related issue, used to be able to scale down, lower than a factor of 1, the title blocks themselves. No longer possible. Which is annoying.
-
11 hours ago, Kevin C said:
Robert,
I am not sure what you bean by your response.
I get the fact that the formulas and coding have changed - that is a relatively simple fix. Does not get round the problem with the "none" data value being displayed when no revision is present in the drawing though. Unless 23.0.1 means service Pack 1?? If this is the case - When is it being released?
The throwing of the title block away from the page centre is a major problem as I will be unable to upgrade my office to 2018 with this bug. All of my projects have title blocks which are locked to the page. When I set up a title sheet - I do not choose the location of the title block; VW does it and always has done. If I have to start and redo every drawing sheet (there are thousands) because someone has decided that they don't care about existing users, I do not now how I can continue. This is quite serious for me, I need a solution.
I really think the issue is, that the Beta versions are not actually tested in a working environment, otherwise, these issues would have been identified straight away.
-
3
-
-
16 minutes ago, Andy Broomell said:
If you have it set to "Use as Titleblock Only" with "Lock to Page Center" turned off, you should be able to move the title block wherever you want.
If you're NOT using it as Titleblock Only, just add a locus point in the 2D geometry to set the spacing from the border.
That is not a solution when most people use borders that are hidden, in order to centre on the page itself automatically, if you change page size etc.
-
11 minutes ago, crosetti said:
So what's the solution if any? because 2018 is useless with this border/title block issue.
The solution is, that there isn't one sadly.
Not worth rolling out to the business.
-
Sadly our smart titleblock, created in 2017 all have this issue. We have to turn off, lock to centre of page, custom page size, turn off border, so it can be dragged to the location it should be.
The lock to page center is not working with titleblocks and borders from older 2017 drawings.
I have even reworked the template for the titleblcok and when i click center on page... it moves and does not center on the page.
See examples.
Editing from the Object Info does not stop the fact that center on page does not work.
Import Revit File - Version Not supported
in General Discussion
Posted
UPDATE: VSS tried it in 2018 & 2017 and could not import the file. I tried it in 2017 and it worked. But it gives me no options and imports as a mesh, which i do not want.
They emailed me saying that it must be an issue with Revit file being upgraded and then exported. The originator uses Revit 2017 and saved it as 2016. Looks like an issue with Revit back saving or Vectorworks import bug.