Joe, are your Marked Point and your LinkToMarkedPoint in the same assembly? As far as I know you can't use LinkToMarkedPoint to connect one assembly to another assembly, or to connect between assemblies on different baselines within the same corridor.
I struggled to figure it out too, and finally discovered that it would only work if both the MarkedPoint and the LinkToMarkedPoint were in the same assembly.
I have some screenshots of the assembly and my finished corridor if that would help you visualize what's going on. Nathan's screenshots of the properties windows are great - I wish I'd had those when I started.
That would be super Jeff, and yes that was my next question. The screen shot in help can lead one to believe you can link two different assemblies. And Nathans note are moving me along, too. I had been expecting to see the linking in layout mode - thats confusing to look at.
If you want two different assemblies, add an offset assembly.
But even with a Markedpoint in one assembly and the LinktoMarkedPoint in an offset assembly (or visa-versa), you still need to make the point before the link.
Nathan Selles-Alvarez, EIT
Here are my screenshots, Joe. First one is the layout view of my assembly, showing the marked point at the right end of the shoulder, next is a screenshot of how the assembly connects to the marked point to build the corridor model (I faked it for the illustration by just drawing the link as a red line). Tip: Make a new marker style for the MarkedPoint, so that you can actually see it in the layout view. I used a square instead of the magenta circle.
Last is the corridor, seen in object viewer, with the LinkToMarkedPoint connecting up to the marked point on the shoulder. It was in object viewer that I was able to confirm that the link was actually connecting to the marked point.
Great stuff cant wait to put it to use. I really appreciate all the effort you and Nathan put in to help me out.
I have observed that for "LinkToMarkPoint" subassembly we can assign custon codes to only Point Codes, not to Link Codes even there is option available for this.
I have changed my Link Codes to custom name and Edited my CODE SET STYLE for IMPORT CODES.
There were no Customised link codes but Point codes were available.
Can you just check this once...
Any suggestion would be appreciated.
I believe that you may looking in the wrong place, I may be mistaken. The link codes parameter in LinktoMarkedPoint is by default Top and Datum, however, you can change this to whatever you want. There is no way edit the point codes in LinktoMarkedPoint because there are no point codes. It seems to me that maybe you are confusing MarkedPoint with LinktoMarkedPoint?
Maybe you also be making the mistake of trying to us a LinktoMarkedPoint in one assembly to link to a MarkedPoint in another assembly? You should be using an assembly offset (such as for a service road) so that the MarkedPoint and the LinktoMarkedPoint are all in the same assembly.
Does this help?
Sorry I was talking about MarkPoint codes, its not about Points codes in LinkToMarkpoint subassembly.
Here I am still struggling with changing Link codes for "LinkToMarkpoint". I havnt spend much time on Codes but quite handy with subassembly properties.
I have attached one snap here for your review. Even I am following this procedure just take look at this,
I also in impression that I am doing some basic thing wrongly.
1. Open new dwg
2. Create new assembly or insert from "basic" palette.
3. Attach one mark point with name X
4. Attach one LinkToMarkpoint subassembly with link Codes "Test"
5. Assembly Properties >>> Codes >>> Edit Current Selection >>> Import codes ( selection by cross window and also with by picking subassembly>>>
6. Checking for link code "Test" in link codes.
and here there is no Custom Link Code "Test"
Just need your some valuable expertise here.
Hey...I got solution for this issue
Actually I m not buliding corridor, and looking for Link codes, once corridor get build it Link will create and it will display in Code Set style.
Thanks for your valuable time for me.