layer combos keep resetting layer priorities please help!

[Anonymous]

it seems ive posted this in the wrong section mods please move to the other problems:


so i was working on doing some minor maintenance on my template today. mainly layer and layer combos. however i cant seem to figure out whats going on. everytime i try to use the element attributes to update my other drawings, or even a copy of the template. well the layer priorities reset. and not only that but when i open the layer dialog every priority is set to 1. if i click a combo the layers themselves flash the correct priority number. but then go back to 1. if i try to use the quick settings after using the element attributes it keeps me on a custom layer combo. if i select a different one, it jumps back to the custom. if i double click on a story in my view map it flashes the correct combo but then just goes back to the same custom as before. i rely quite a bit on these priorities and it has cost me most my day trying to figure out why they arent working. any help would be so much appreciated.

EDIT:if i open a drawing before my updates, and i create an aat file for just layers and layer combos, then save the drawing and close it. reopen and import the exact layers and combo's i just exported. the same issue arises rendering the drawing un editable with out recreating the combos or going back to the original before the updating of layers. i hope graphisoft gets this fixed soon. or i guess i hope im not the only one having this issue. going to go back to the previous build (3002 from 3013) to see if the issue exsists there as well and was just un noticed.

edit #2: even going back to b3002, and even with the stock archicad setup the issue is constant.

If anyone could test this issue for me it would be much appreciated. just to i can confirm if its somehow my machine or not. the issue also happens on another machine here at work but i would like to be 100% sure its not user error

thanks

EDIT #3 i thought i should add that if i down save to 16 then the same behavior in the file still happens. also that drawings that have not been touched by the element attribute manager do not have the issue of defaulting to a custom layer combo.

[Anonymous]

Barry wrote:

thepsyntyst wrote:
try opening the default ac 17 template file. then open the layers and change one or two of them to have different priorities. then open the attribute manager and save the layers and layer combos in an .att file....

When you are changing the layer priority number are you also updating the layer combos as well?
If not then the AAT file you are saving will have layer combos with the old priorities so you will just be re-importing the old settings.
Barry.

yes on the updating, ive even used my default pln created a brand new aat. then save close (probably not necessary) and reopen. load the recently saved saved aat with no changes to any layers or combos that are all how i need them, then i overwrite the layers, then the combos. apply and close the att manager. and then i am stuck on custom layer combo. when i open the layers i can select the combos and i see the layer priorities flash with the correct number. then its back to a custom combo with all priorities set at one. i can update each layer combo and then they work. but the aat file just isnt working. but like i said the pln when used everything is peachy

[Anonymous]

David,

RE: hotfix 3013, I can only assume that since I have a WIBU key and not a codemeter key, the GS website for upgrades is still to this day (July 9, 2013) informing me that 3002 is up-to-date.

Thanks for the link to the 3013 news about the codemeter fix.

However this could make trouble for TW2, since people in my situation will have to hunt down hot-fixes that don't relate to the older WIBU keys.

Mark

[David Maudlin]

MarkMoscrip wrote:
RE: hotfix 3013, I can only assume that since I have a WIBU key and not a codemeter key, the GS website for upgrades is still to this day (July 9, 2013) informing me that 3002 is up-to-date.

Mark:

In the release notes in the link on the thread, you will see that there are a few more fixes than just the CodeMeter issue (though that was probably the main issue being addressed). I am also on WIBU key, but have installed the hotfix; I don't remember if AC informed me that the hotfix is available, or if I did some searching, but it makes sense to keep up to date.

David

[Anonymous]

I received this today from GS North America regarding 3013:

"There is a problem with this hotfix so they pulled it down. You are better off to stay on build 3002 until sometime next week.