Urbano 7 Release

Transcription

1 Urbano 7 Release The main novelty of this release is the support for Autodesk platforms 2013: AutoCAD 2013 and AutoCAD Civil 3D From now on, five versions of Urbano will be available. Depending of the version of the AutoCAD platform the following Urbano versions will be available: AutoCAD platform Windows 764-bit Windows XP 64-bit AutoCAD/Civil3D/Map 2013 Series bit AutoCAD/Civil3D/Map Series bit 2012 AutoCAD/Civil3D/Map Operating system Windows 732-bit Windows XP 32-bit Series bit Series bit Series bit These five installations do not interfere with each other. For example, if versions Series bit and Series bit are both installed on the computer, they will be placed in C:\Program Files\Studio ARS, but inside of this folder, each installation will have its own subfolder 2007, 2010 and New features added in version Pipe length calculation This new funcion calculates the number of pipes needed for a certain pipeline.

2 Lateral inlets and connection nodes can now be shown as blocks Lateral inlets and connection nodes can be drawn in long section (section profile of inlet pipe). These sections can be very small, and when printed, they appear as dots. Because of this, we made special blocks for this purpouse that can be assigned to every pipe. You can choose in your longitudinal section configuration whether you want that lateral inlets to be shown in its actual dimmension or with blocks, scaled or not. The same applies to systems intersection points these intersections can be adjusted the same way. For each pipe group only a few blocks were made. For example, if you would like to show pipe with diameter 200 mm, you will use pipe block that contains 300 in its name (i.e. ND_S_pipe_symbol300.dwg), and if you would like to show pipe with diameter 450 mm, you will choose pipe block that contains 600 in its name (i.e. ND_S_pipe_symbol600.dwg). You can add the section in your catalog that contains the block definition and add block for each pipe. You can do it by pressing CTRL+ Add new item button (marked with red rectangle):

3 When you do it the new section will appear:

4 By clicking on the picker in the section right corner you can choose predefined blocks from the drop down list: If you would like to make your own blocks, you have to name them ND_new name.dwg, and save them in the installation folder PipeCatalogueBlock and also, save it as unitless. Geodesy Geo Symbol blocks We made new geo symbols blocks, according to new rules for Geodetic symbols in Croatia. According these new rules, some symbos are not the same depending of the scale of the drawing. Therefore we made new feature user can make his own configurations, in which he can choose which group of symbols he wants to draw, according to the scale of the drawing. Example: If user needs to draw surveying drawing in scale 1:1000, he will use geodetic block symbols for scales 1:500 to 1:2000. He can adjust it in his configurations.

5 Bug fixes in this release are: Drawing of cross lines takes more time than it should When you open new system :Sewage, draw pipe system, assign pipes, manholes, trenches and upper layers to it, draw cross sections of trenches,and than open new system - Geodesy, draw alignment, and draw cross lines, drawing of cross lines takes a lot of time Value of rain intensity The value, which defines the rain intensity, will be not saved as value inside of the related system data Import Lae file - > croatian messages After import of attached LAE file some croatian messages are shown inside of LOG window Additional filter in renaming nodes works even it is not represented in editing method. When renaming nodes according to branches/arrays I noticed that command didn't rename all nodes. Few of nodes keept their old names. After few trials I understand that nodes, which stay with old names was only main nodes. After restarting Civil all nodes was renamed, not only few. Problem was that I run renaming with few methods (it was training). First i rename automatic. In this method I have additional filter for selection and i put it to plain nodes only. Then I run renaming again with different method - renaming according to array/branch (this method didn't have that kind of filter), without changing filter on previous command I notice that filter was still active (no matter it is from different method). When I restart Civil this filter was reset to initial state (all nodes) and thats why comand work on all nodes Cross section dialog is not updated after changing type of the cross section to be drawn When we double click to cross section that we defined to draw, the dialog opens. We select some part of the sistem and the program draws the cross section. If we don't close the dialog, and than change the type of the defined cross section that we want to draw, the program draws the cross section same as previous. In another words, if we choose to draw Cross section 100/100 and then draw it, and if we change the type to Cross section 500/500 after that, the program does not update the change, and draws the Cross section 100/100 type again Style overrideing in all text definition in Urbano - the text width is always set to 1 If we change the text width in some new text style and set that text style in the text definition in Urbano, the program will always draw the text with the width factor 1 and all width settings will be overrided. The program should take values from the style definition Problem with dialog in Canalis Waste water flow, TUR standard when this dialog is started, data was set and dialog was re-opened, it was blank and not usable, or error occures.

6 Problem of arc-shaped sections in layout If there was arc-shaped section, longitudinal section that contains that section could become invalid when clicking on REDRAW (the frame becomes purple) Problem with previews of excavation data In previews of nodes, following components can not be seen, although are available to add: Manhole excavation volume for referent terrain [m3] Filling volume above manhole for refferent terrain [m3] Same components can be added in table of longitudinal section, but can not be seen Issue with level line elevation in logitudinal section when new array added Array A was drawn, terrain height data and level line data were assigned. Long section of array A was drawn too. After that new branch B was drawn, connected to array A, but with different level line elevation (i.e. 3 m under the terrain). After this, it could be seen in longitudinal section of the array A, that level line elevation of the section after connection node was changed on that elevation too (3m under the terrain).