Why is this happening?

I have a PDF showing proposed works that I want to import and overlay on top of the overall site plan. The PDF has two details showing proposed works in two separate locations on the site. In order to be able to overlay both details in their correct locations I have cropped the PDF to create two drawings, which i have saved as Detail1 and Detail 2.

However, when I import Detail 1 it doesn't just bring in the part I want. Somehow the software is loading the uncropped file. I've no idea how this is happening. I've even tried shutting Kubla Cubed down and restarting - didn't work. I've restarted explorer - that didn't work. Somehow Kubla Cubed seems to be able to put the cropped PDF back together again.

Please explain

Thanks

Kevin

Hi Ted,

I try to import a designed finished surface in dxf file format (which was produced by Microstation software by our client) into Kubla Cubed, but not successful. The Kubla prompt that the dxf is not a valid file. Could you please help to resolve this problem. (This is the 1st time I encountered this type of problem) Your early respond will be appreciated. FYI, the dxf file can be opened by Autocad program.

The screen shot is attached herein for your reference.


Thanks and regards,
Bernard

I have a cistern excavation to calculate. The excavation has to go down to a level of -3ft below grade and I then have to place 12" of fill in the bottom of the pit. How do I establish a zero batter for the cut and fill. If I simply change the batters for the cut and fill to zero a red border pops up around the respective boxes, which I assume means there is an error.

Why is there no batter? - because firstly the Contractor will not get paid for over dig and we've agreed a rate on that basis. Secondly the ground is very stable, meaning that there's very little risk of collapse, hence the reason why the contractor will not get paid for over digging the size of the pit needed.


Thanks

Kevin

I can't find a quick way to do this; I've used the 'Feature Surface' option and inputted spot levels to establish the cut/fill needed to establish the formation level for the construction of a car park. I now want to calculate the fill required to bring the level up to underside of the asphalt. My idea was to use the 'Spread' option to do this because this fill is specified at a constant 6" thick. My issue is that this fill will cover the same area as the cut/fill calculation, but I can find no way of copying the boundary I created when using the 'Feature Surface' option. Obviously i can copy the 'Feature Surface' to a new Construction Phase; but I can't then edit it to use with the 'Spread' option.

Of course, the simple solution is simply to use a calculator to multiply the 2D area of the cut/fill by 6" to generate the volume of fill needed. But I was hoping to be able to show the client a 3D Kubla Cubed model which would show this fill

All answers on a post card please :-)

Thanks in advance

Kevin

When I try to export the existing ground conditions to produce and image, I get 'Image export failed.  Error details:  Object reference not set to an instance of an object'.  I don't think this has happened before but Windows recently carried out an upgrade which may have a bearing on this.

This is the biggest update to the program since Kubla Cubed 2017 was launched with a lot of new features that many users have requested.  The biggest changes are :


A) Support for direct import of triangulations (from CAD or LandXML).

B) Big Improvements to CAD Export and new LandXML export (for potential use in machine control systems).

B) Enhanced visualisations with a 'skirt' around the model and vertical exaggeration slider.

C) Improved export of project data with new spreadsheet export and export of 'user input' data including boundary areas, perimeters etc... (this information is often required by quantity surveyors).


Tip : To calculate an area create a spread element with 0 depth and export user input data to find it's boundary area.  The same trick can be done with paths with 

Full list of updates below : 
___________________________________________
14:00 22/05/2018 - Kubla Cubed Version 4.6
___________________________________________

New Features

+ Added a presentation mode that can be used when presenting Kubla Cubed projects to a group on a big screen or projector.
+ Created a spreadsheet export of user input data and estimation summary. 
+ Added a new element 'Triangle Surface' which can be used to add triangulated meshes into the program.  Supports Kubla project files as well as .DXF and LandXML files.
+ Added new 'Export to LandXML' option which can be used to export project data into machine control systems and CAD programs when .DXF is not supported. LandXML is widely supported by machine control systems as an import.  
+ Added ability to export labelled gridded data in the CAD export.  This can be used to analyse the cut\fill details especially by site teams accustomed to working with gridded data plans than CAD files.  It also can provide a good way to import surfaces into programs that do not support TIN import.
+ Enhanced the visualisation with a new 'vertical exaggeration' control which allows users to exaggerate the visualisation of their project in the Z-axis.  Vertical exaggeration is useful for viewing sites that have fairly minor elevation changes over a large area and is widely used in topography modelling programs.

Improvements 

+ Improved behavior of slope when switching between different options ensuring all options have more meaningful starting values.
+ Amended disturbance area calculations to remove areas that had been returned to their original elevations by subsequent elevation adjustments within the same phase.
+ Added 'User Input Data' to the report and the new spreadsheet export.  This is useful to validate user inputs and for creating bill of quantity (BOQ) reports.  Importantly element boundary areas and perimeters are calculated which can be useful for estimating material and curbing costs using the area and perimeter of strips that have been used to adjust for construction thickness.
+ Included an offset option for the existing element.  This can be useful for analysing volumes at different depths.
+ Achieved significant performance improvements in general and especially with projects many construction phases and projects with feature surfaces with automatic outline levels.  Average load time improvement across all test files is over 4x faster compared with 4.5 release.
+ Improvements to calculation of automatic outline levels to resolve unrealistic levels in certain unusual scenarios.
+ Added 'back a step' feature into take-off form and element boundary creation.  This allows users to correct mistakes by pressing back space if they make a mistake whilst creating (contours, outlines, platforms, strips etc...)
+ Updated triangulation code to only include elevation features within an outline.  This aids with clarity and allows for validation to only take place within the outline.
+ Added labels to the generated contours in the CAD export.
+ Added 'skirts' around 3D models to give them a more solid appearance and to give a greater awareness of depth with elevation colours now running down the sides of the model.

Fixes

+ Resolved activation issue caused by the license file being saved into the users roaming profile which could then overwrote the license file with incorrect information on their second device.
+ Fixed issue which was causing the varying levels outline elevations to display as vertical bars '|' in the take-off form.
+ Resolved issue whereby a feature surface boundary would only display the outline of the first island.  Also fixed rendering issue where the outline was rendered with many different line segments rather than as a smooth path.
+ Resolved issue with the image exporter that was showing the wrong range in the colour key when 'absolute shading' was selected as an option.
+ Resolved problem with image exporter which was causing the level shading to shade incorrectly as a single colour.
+ Resolved a bug which caused PDF's to fail to load when computers were set to language cultures that use a comma as a decimal point. Swedish users reported this problem.
+ Resolved minor bugs in phases tab control.  This included improvements to the selection of tabs.  Previously tabs were selected only when you clicked on the text, rather than the tab itself.  Also included ensuring that the selected tab was scrolled into view when a file is loaded with one of the later tabs selected.


Please post any feedback below.

Good afternoon,

V4.6 has landed and wow has it speeded up the calculation process 
The Export to Excel is fantastic and will save vast amounts of time.

Still playing, but this appears to be even better than expected.

Well done KC 

Cheers

Tim

This would help a lot.  I am often zooming in to make a point close to another one. I miss having a scale in the lower part of the screen showing if I am at 100 M, 1 m or a couple of mm close to something. It of course changes as you zoom in or out.

Seaking

I am currently using an i5 processor and 8 GB ram, I know it will be better with more RAM and a faster more capable processor. Does the software use the multithreading of a processor or do I need the fastest processor I can get. Also what screen resolution works best and size of monitor, I want to get 24 inch monitors at 1920 x 1200. That is what I used previously , what are your recommendations.


Thank you 
Seaking

I am measuring a camp site and need help with plotting proposed features with offsets (roads for example).

I have a drawing which contains existing contours and proposed contours. I have plotted the existing as normal but am having difficulty with the proposed levels. Usually, when measuring a road for example, I am provided with point elevations to the road perimeter. I use these to draw out the road using the Surface Feature element (the path element is often not suitable) and then add a negative offset. However, I only have proposed contours for this job so this will not work.

I have plotted the proposed contours, but now want to draw the roads, paths, pads, etc over this and apply offsets. Kubla would need to use the contours to calculate the proposed levels.

Can anyone help?

I found that if I used the Surface feature element for the proposed contours and then used the Strip element afterwards for the road this appeared to work.

Hope that makes sense, feel like I have made this more complicated than it needs to be.