Jump to content

Matt Overton

Member
  • Posts

    980
  • Joined

  • Last visited

Everything posted by Matt Overton

  1. Just to confirm when you say recreating the Project File you mean the one residing on the server? So periodically taking a working file, saving as a standard file, then pulling it back to being a working file again? We have been using 2016 Project sharing and noticed a few of these issues. Generally getting 2-3 weeks of development before hitting a problem.
  2. THAT Would be brilliant!! Maybe the focus on machine learning in Com Sci these days could make a system to watch what I do for small repetitive tasks then does them if I hit the AboutToDo button. Even offer up suggestions on the TouchBar.
  3. $5 says this weeks Tease is "What's new in Styles"?
  4. We should be able to set folder attributes as relative overrides. So If I have a class for Brick with attributes for new brick but drop a copy into existing the infill would override to black but lineweight could reduce by say 20%.
  5. So, in other words, a way of building Parametric objects (like plug-in) by geometry not code? That would be really great. Given the direction of Marionette and improvements in how data is displayed it would seem to be a logical next step somewhere along the way.
  6. User definable prefix would be a great option for all styles and resource types?
  7. I was able to do something simlar in the GUI using the less than A999 to get all starting with A. I wonder if greater than X000 would work? Will have to look at wildcard next time.
  8. So invoices have been rendered for next years fees and I have to say feeling more "meh" than titillated so far. Still, you have 2 more Tuesdays to pull a rabbit of productivity out of the hat.
  9. Yes Also been looking at ARkit with interest and playing a proof of concept. ok mostly just loading VW model to Apple supplied demo. Not at the full scale of a walk thru but more under laying a scale model view under the drawing sitting on a table. Shows a lot of promise on helping the clients see drawings how we see them.
  10. Given you make port by doing something very similar to this ....is it really a problem. Funny you say that because paper is still freer than design layers which are always constrained horizontal. Paper is also a working view not just an outcome. Not sure we can say paper and drafting are the problem till the system at least gets much closer to an approximation.
  11. Co-ordination is in my experience an art not a science yet again in recent weeks have meet with engineers who use VR rigs for BIM co-ordination and frankly it's amazing. The abiltiy to zoom in on and hammer doubts that would take hours of drawing reading to find is full of value. Our latest insert building inside existing shed project has me keen on drone* video generated point clouds are something we really need going forward. Data from AR and VR really does show a lot of promise... (It's just not to change the need for drawings anytime soon, given these comments might sound like a reversal of ones in another thread) *well ok Wide angle walking camera would work but you know drones more fun.
  12. Would this work with a 7 or L rotated? After all the text box doesn’t need to be regular text.
  13. Yes I know the attached is the VAA revise Issue Print Dialogue but it has handy buttons that could equally apply to Publish dialogue as well. Would it be possible to add a button here similar to Today's revisions that instead selects Checked Out Sheets when using project sharing? Would help make smaller drawing issues slightly faster.
  14. I feel like I've been miss quoted here. Still full agree with above suggestions and to me the crazy thing is these are mostly taken care by using system supplied stock tabs instead of the 3rd party tabs.
  15. Wasn't 2017 tabs enough of a UI regression without going for 8Bit inspired fonts and garish oversized buttons?
  16. If everything ends in one file you aren't really saving file space or speed. The other option is to split files into drawing packages so each logical end point is a file, - One file Plans with all general and co-ordinated model information. - Elevations and Sections which are heavy files due to rendering load as another one or two. Although you want these sections as full model generation so only annotations are beyond the model. - Distinct works packages that have low co-ordination demand, joinery, fitout, ... separated out. - Details - Again low coordination demand The tough part here is making sure each file has all the information it should be able to edit in file either model or annotations. Works reasonably well if each document produced has both a sheet and design layer that is the key holder of the editable information. Then again Project sharing is a good option and works well if you have a good file structure.
  17. Well yes unless you consider annotation space.... now in my excitement, I realized of missed something vital here*. This isn't in the documentation/paper space that allows us to edit all information that goes into a document in context. It's somewhere else again as far as the software is concerned, i.e model space? So it really doesn't avoid the contextual shift of "Edit Design Layers" it just gets us to a useful place faster after the shift. A very welcome improvement and hoping the first of many. Especially given other comments in the thread about where this is heading contextually. If my misunderstanding is correct then yes no relevance to flat viewports. If it was a full contextual active view then being able to move model annotations and paper annotations without having to think which is which would be very helpful in late stage documentation and when we have multiple people working. So what does this do with annotation space?
  18. There used to be an easier way of making VS objects using the export vectorscript function. Draw graphically but make each dimension odd and unique. Once exported as vectorscript. A simple Text editor could then find a replace instances of those numbers with a variable name. Using odd numbers product even number calculated dimensions mostly. Still a bit tedious but far easier then crafting scratch code and testing. Would be interesting to see if a text converter could be made to automagically turn geometry into a python include file? From there not sure how you make it "Marrionettable" if that's a term.
  19. Sooooo...... do we get a tease about similar function for plan viewports next week or are you going to string us out till the same time next year?
  20. It's not Tuesday at NNA till it's at least Wednesday here in AUS/NZ
  21. Sure language evolves and drafting is a language like all others but... I think this is a line CAD/BIM companies have been pushing to hide the fact they had missed the point for the last 20years and want to sell it as an upgrade when it isn't. They want a revolution to suit the technology, not us.
  22. If anything the shame is this approach hasn't been pushed further as the programme developed. After all sections and elevation are as much in need of drafting convention for information clarity as plans are yet we still suffer from having to overlay vast amounts of disconnected information over these views to turn them into credible documents. To me the failing is not to have taken Hybrid further as the 3D developed and let us have other planes of hybrid representation that could augment the model cut if not completely replace it depending on the situation.
  23. Only thing to add here is.... Set up Naming rules early and not often. We use 3 (0xx) digit prefix so that similar symbol group together even if not in folders. Mostly as our job numbers are 3 digits so project specific symbols have job code as a prefix. To keep library file smaller and fast we break up libraries by first 2 digits. However the important thing is to have a naming system, but it only needs to be as complex suits your workflow. If you don't then people don't feel like they can find what they need and will keep just going back to last time.
  24. Thrusday after the iPhone if history is any guide!
  25. Does the App need to be full screen to handle two monitor support or can view on the second screen be a separate window with say resource browser docked into it? And Is it possible to set say viewports to create a picture in picture instead of the Return to Viewport button?
×
×
  • Create New...