

Virtual Reality (VR) is one of the most exciting technologies to hit the AEC market in years.

When working with OS coordinates it is good practice to remove three digits from northings and eastings. Before the service packs point clouds just came in on top of each other, even if you used 'origin to last placed'. It also solve the issue when bringing in multiple point clouds that are registered on the same grid. It's worth installing SP 1 and 2 because it solves an issue where Revit did not respect the point clouds coordinates when they were outside the limits. After service pack 1 and 2 it is about 20 miles. In the first shipment of Revit 2012 I believe the working area was limited to 2 miles before things started to break up. Your comments and help would be greatly appreciated as our deadline rapidly approaches. Is the distance from the origin the issue? has anyone experienced similar behaviour within Revit? Is there a work around? When the pcg is deleted, items inserted in the same position behave as normal.

Revit is now acting in a extremely peculiar fashion where walls that are inserted are taking on a triangular shape and will not appear to stay in the position they were inserted into. I noticed the point cloud pcg files were very "jumpy" when being rotated or zoomed and recalled a similar issue with pcg files in AutoCad when far from the origin. So we re-issued all the point clouds in this system and moved the Revit model which was fraught with unforeseen changes and challenges. The client then requested we match all the data to a topographical survey which was performed on our WGS84 cadastral system. We started on a site grid from a previous model with the coordinates close to the 0,0,0 origin. We are busy with a Revit model of a large factory and surrounding buildings.
