Remove a link from Signal

[xxuntitledxx]

Hi all,

So I was fiddling around with the RCAP signals and I inadvertently, and to my surprise made a gantry mount signal mast with no signals. Which is something I have always wanted to do but couldn’t figure out how to do it. So…now that I have it, it still thinks signals are attached to it (although not visible) so how can I make it just a scenery object for use with the signal gantry? Also…is anyone familiar with the matrix in the bottom of the xml files? Does this allow you to put multiple heads on different mounts? I would love to mix heads so I can get configurations that aren’t already in the initial RCAP files.

Ken

[DieselMatt75]

Hi all,

it still thinks signals are attached to it (although not visible) so how can I make it just a scenery object for use with the signal gantry?

You would want to reference the gantry post to a scenery blueprint instead of a signal blueprint. The scenery blueprint has no functions other than showing the model.

is anyone familiar with the matrix in the bottom of the xml files? Does this allow you to put multiple heads on different mounts? I would love to mix heads so I can get configurations that aren’t already in the initial RCAP files.

In a way, yes. RCAP has this mostly sorted out on their end except for the ones I posted in the other thread. As for other providers' signals, the spacing might be different on the post, but it still can be done.

-Matt

[xxuntitledxx]

In a way, yes. RCAP has this mostly sorted out on their end except for the ones I posted in the other thread. As for other providers' signals, the spacing might be different on the post, but it still can be done.

-Matt

[/quote]

I was going to use all signal heads from RCAP and just try to mix and match heads... is it all trial and error based on what goes on each line in the "0" or "1" spot?

In this section...
<Element>
<e d:type="sFloat32" d:alt_encoding="000000000000F03F" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="000000000000F03F" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="000000000000F03F" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="000000000000F03F" d:precision="string">0</e>
</Element>

[DieselMatt75]

In this section...
<Element>
<e d:type="sFloat32" d:alt_encoding="000000000000F03F" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="000000000000F03F" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="000000000000F03F" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</e>
<e d:type="sFloat32" d:alt_encoding="000000000000F03F" d:precision="string">0</e>
</Element>

This area changes the position, rotation, and height of a model. The heads that RCAP provide are (simply put) locked in the .geopcdx file. For example, the 3/3 head was modeled like that and cannot be changed without modifying the geo file and scripts. It's unfortunate that the source files of the RCAP signals are probably long gone. With source files, it would be possible to mix and match heads using a 3D modeling program.