Well, after upgrade from b7 to b8 everything seems fine til open the network map… It opens the map and after few seconds the CPU reach 100% on p4 machine 1G ram and then, crashes… I couldnt check in time if the “fit” feature is related to this problem. Im really really really really not in the mood to start over a new map again. The only thing that I really care about is the network map and the hundred devices on it, nothing else. But seems, til someone else come with a way to save/restore “only” network maps from dudes to dudes, from times to times, you need to start over a new network map. 
too bad… But still a great tool. A lack of parses when upgrading from older versions maybe, but still great. For now, I shouldnt open the map or I will get 100% cpu… Anyone else is geting the same? Is there a good XML editor that could split the main .xml backup file into different section .xml files? i.e: tools.xml, networks.xml, mynetmap.xml, myaddrlists.xml, etc? Thanks, I am one who would love have a .xml file for every section dudes have…
send us the export file that does not work for you, or at least provide us
with the crash information dude is giving if you have any. (send to
support@mikrotik.com)
I am also experiencing CPU performance problems when opening the map. Otherwise no problems after upgrading from beta7 to beta8.
Since 2.0b8 I have a small problem with link info boxes (the ones that appear on a link when you’ve defined it as a SNMP link). Sometimes the values disappear and the box only shows:
Rx:
Tx:
Speed:
Hovering over the box also does not produce the popup info box and history chart.
Simply opening the link settings and closing the settings again without touching any option, fixes the info box. Good thing, the data gathering was still ongoing while the info box was ‘broken’; there are no gaps in the history chart.
Anyone else experiencing this?
(Dude server and client are running normally on a single WinXP machine, not as a service.)
dude export file sended to mikrotik support… I have done some experiments also. In my case, deleting all the links (256 approx.) solve the CPU problem. Perhaps my network map is too big/complex. Im anxious for a answer. Anyway, before dude 2.0b8 I could open my current map with no problem, nothing…
for some reason I couldnt send dude export file… Im trying to send the undelivery message I got. oh well…
Okay, I have sended a zipped file… another thing I have noticed when adding a dependency, there is a return error saying “no such device”. Btw only some devices do this, others not.
Please, Is there a feed-back available about this thread and the file sended?