It's not going backwards at all. It's just that this is the way of doing things in Civil 3D. Unfortunately it just takes a while to actually appreciate and embrace the new techniques. It's almost always far better than the LDT method. Yours is a very common position on this. We all went through that stage when we switched from LDT.
You don't have to pay for anything as much as Sinc would love for you to . In a previous post of mine I suggested how you can get those blocks into the drawing. Use description keys like you've always done and explode those points twice. Import the points again (without desc keys on) and there you have both blocks AND points.
Having blocks embedded into the points is simply better in most cases, you just have to learn how to deal with them...and other features when you get to them...and try to forget that "I could do it this way in LDT".
Cansel - Autodesk Division
If you are adjusting the scales manually, you could create a point style for your electricity box, then copy the style and change the scale on the new style to match your needs. Do this for the number of sizes you need.
If you create 10 different point styles, and all electricity box come in with one of those styles, to change a particular point to another style, select the point, and in the properties palette you can change the point style to the one you need. You can also change the styles on multiple points at the say time. Probably quicker changing one point style than changing 2 block scale factors.
And if you set the point styles up in the template, you'll only need to create them once and they will be ready each new drawing.
We have a similar situation where I work, although not that extreme. We only have two different size telecom pits (not ten) and we have two different codes for the surveyors to use. "TM" and "TS" for Telecom Medium and Telecom Small. Our surveyors use the corresponding code and the correct pit size is insert on import.
Might be a stretch, but what about a different code for each pit? say "ELECA", "ELECB" "ELECC", etc. I know it's a pain to work with a lot of codes in the field. If your surveyors can manage it, it would save you the time of changing all the points styles manually.
Maitland, NSW, Australia
Windows 7 Enterprise 64bit
Intel core i7 2600 @ 3.40 GHz with 16GB Ram
Civil 3d 2013 64bit
Thank you Andrew. I couldn't put it into words as well.
Joseph D. Bouza, P.E. (one of 'THOSE' People) Civil 3D 2012 & 2013
HP Z210 Workstation
Intel Xeon CPU E31240 @ 3.30 Hz
12 GB Ram
Note: Its all Resistentialism, so keep calm and carry on
64 Bit Win7 OS
Don't want to sound snarky, but...
Some of the others have pointed this out - C3d is not LDD/LDC. The sooner one (any of us) can stop thinking "that's how I did it in LDC, Carlson, Trimble, etc" and embrace the fact that C3d is a totally different approach to survey / design, the easier the transition wil be.
Another thing that will help imensley is training. I'm not a big fan of spending money trying to learn a program, BUT, in this case it's the most cost effective way to use the software. Once you get into C3d, you'll see power there that leaves LDC in the dust. Just approach it with "it's new software, and I have to learn how it works" and you'll find out it works well (for most things - no software is "perfect"). Just pretend you're back in school, and learning how to do this stuff for the first time.
Using description keys as Matt said would require only one block if the descriptor contained the size. Our crew would code this.
The scaling abilities in the keys can size the block automatically. The file wil plot a box 1.67' and 2'. Scaling would of course need to include unit factors.
I will also tell you that we did want blocks in our files when we were learning the app. Truth be told we have not used a block to represent a point since 2/08 with our last LDD project.
C3D 2012, RD 2012
Win 7 64, Core i7,
6 GB RAM, Quadro FX 1700
Not originally. They are converted to fieldbook (FBK) from raw file, yet I can convert them into ANSII text file, if it helps.
What I did is use the map import to bring in the points ENZD format, with the desc as the block name. Then export that to a SDF format creating data from the desc. Then in the project dwg map import the SDF file and use blocks as the point marker getting the block name from the attributes/data. As long as the blocks are defined in the dwg it will replace the point with the block.
Someday in the future Civil/Map3d will be able to use a pipe network for electrical lines and structures with pads, enclosures, secondary box and vaults. Along with alignments that will let you run then 40 above a surface and draw the line swag in the profiles,
Supportting the troops daily.