Does this happen for everybody? I find they stay huge until I reset the size, but the next time they are edited they become huge again:
Hi @djhg,
Which VisualARQ and Rhino versions are you using? Please, could you send me this file? I’ll try to reproduce the error.
My Rhino and Va are up to date.
In four years with Va, I don’t remember a project where this wasn’t a common occurence, but other bugs have always been more critical (and still are, like problems selecting objects in Hidden view mode, and Va view modes resetting to wireframe between sessions)
I cannot reproduce it in my computer. Which other plug-ins do you have installed in your Rhino? Please, try disabling them just to check if any of them is causing this behaviour.
I’ll try it without enscape, which is the only plugin. But it has been an issue since long before I installed that.
Yes, this happens all the time.
Thomas, do you have plugins installed?
Come to think of it I have one which expands navigation performance with certain mouse click/hold/drag combinations, but I am pretty sure this issue far predates the installation of that one also.
Did you try it without that plug-in? What’s the name of it?
Yes I have enscape, vray, visarq running.
But it seems to be a Visualarq thing. The section test style will default to a size 3 instead of just being ‘By Parent’ with everything driven by a dimension style. Once I change it, the size is fixed. But it regularly defaults back to 3 when I open a file.
Default:
Preferred:
I still couldn’t reproduce it. I am using VisualARQ 2.12.6 and Rhino 7.25, are these the versions you are using?
So I understand that this is happening with the sections styles in the templates. Is it happening with every VisualARQ template and with every section style in the template?
Please, could you send me one of these files just in case I can reproduce it with them?
Alfonso,
I just sent you some template files to illustrate the issue I have been seeing. My Rhino is 7.22 and Visualarq is 2.12.6.16419
It happens a little differently in the standard Visualarq 2 - Feet template vs my own. I try to update the templates about once a year, so my template would have probably been from around Jan '22.
Hello,
It seems to me that you, Asuni guys, have perfectly configured computers… 
This is an old problem, section styles don’t keep their properties, any action changes their text styles. As long as you don’t change it it’s OK. Or if you have text set to a reasonable height regarding model space scaling.
Cheers, Jaro
“text set to a reasonable height regarding model space scaling”
Can you elaborate in what you mean here, Jaro? Maybe it represents a work around, which would be helpful. (Not to rely on displaying VaSection generated references on final drawings - not there yet - but it would be good to have them visible without them dominating a drawing. As it is I have to keep them hidden/locked to have a workable model, which means unhiding/unlocking - or both - to work with them every time I need to refer to them.)
I’m sorry I’m late
I think the problem is with the “model space scale” at the annotation definition. If it is set to “1” everything should be OK. If you set it regarding scale of your print-outs (as I usually do) and if you enable model space scaling, Rhino recomputes some annotations and changes their scale/display. Also, this parameter makes a fuss when exporting drawings to a DWG format. With the very next project I am planning to check an option without re-scaling of texts.
Cheers, Jaro
So far after changing the model space scale to “1” for all my annotation styles (there are a lot of them) a few days ago I don’t have the giganticizing issue.