Hi.
welcome @forums.autodesk.com !
>> This seems to happen frequently when zooming in and out
Zoom is very depending on the graphics card and it's driver, so I would start first to disable hardware acceleration in AutoCAD (command _3DCONFIG ==> manual tune) and watch if the exceptions occurs again or not.
Second step would be to search for a new driver (or also for an older driver) and update your gc-driver (you might also look into the list of certified drivers from Autodesk >>>here<<<).
It might be also interesting to know:
- what Map3D-version do you have
- what servicepack for Map3D is installed (verify that you have the latest one >>>here<<<)
- what graphic card do you have
- what operating system do you have
- does that exception occure in some specific drawing types (like drawings with areal photos, FDO-objects, ...)
- alfred -
Hi,
>> AMD RADEON HD 6670 driver version 8.800.0.0
Look to the site of Autodesk with certified graphiccards, I found >>>that page<<< that should be valid for your graphic card too, it's version 9.2 (instead of your 8.8). I'm using the same driver-version on my laptop and I'm running AutoCAD 2010 to 2014 quite stable (at least no problems with zoom)
>> Dwg's do reference aerial photos and are accessed over a network
If the new driver does not make anything better then I would:
a) verify if the exceptions only occur with drawings containing areal photos (other drawings do not crash Map3D?)
b) for a test period look if it's better to have the raster files local instead of the network path
c) change the type of raster images, so e.g. if you are using ECW then convert that to TIFF and
try a project with the other file format
d) if you referenced the images with _MAPIINSERT then try it with _MAPCONNECT (FDO) instead (or vice versa)
I know these are not the best tests/workarounds, but it may bring you closer to the source of the problem (I hope).
- alfred -