MSTS Signal Export Bug (Resolved)

I have this resolved. I’m preparing a new release of 3DC now. It should be available today.

Was the MSTS signal sub-object export bug that I’ve reported time….and time….and time….and time again ever fixed in version 7 or working correctly in version 8? Version 6.xxx was the last issue the export worked correctly.

Having been a loyal customer of this product since the release of MSTS in 2001, I would have expected better technical support in this matter than I’ve received.

Please have the courtesy to respond.

Thank you
Hank Sundermeyer
Newark, DE

Hey hank. you may have more luck if you sent a email to
<!– e –><a href="mailto:support2@amabilis.com">support2@amabilis.com</a><!– e –> and you could get a reply faster.
I suspect that our elusive one, is busy and not able to get to the forums as much as I know he would like.

[BLOCKQUOTE class=’ip-ubbcode-quote’][div class=’ip-ubbcode-quote-title’]quote:[/div][div class=’ip-ubbcode-quote-content’]Originally posted by BigPeter:
Hey hank. you may have more luck if you sent a email to
<!– e –><a href="mailto:support2@amabilis.com">support2@amabilis.com</a><!– e –> … [/div][/BLOCKQUOTE]

… and you would get a message ‘Just a note to say that I will be unavailable until July 12th.’.

Thank you for the responses.

Right now, the fact the signals actually work in near prototypical fashion in ‘legacy’ MSTS, is what separates it from Rail Simulator/Works where signals don’t work worth a tinkers’ da#n. <!– s:( –><img src="{SMILIES_PATH}/icon_e_sad.gif" alt="" title="Sad" /><!– s:( –>

Hank

I have been looking into this with Hank and have found the cause of the failure of MSTS signal objects exported from V7 (+?)

In the ‘sub_object_header (‘ section, after
subobject_light_cfgs ( x x ) 0
is a digit (0 in this case)

This digit should be unique for each sub object (within the distance level) and was correct for V6 but for V7 they are all 0

Any chance of a fix for this Richard – for 7.1.2 and 8+ ?

Yes, a fix will come.

The strange thing is that I compared version 6 and 7 and never found this problem. Not sure how I missed it.

I’ll move this to the ‘bugs’ section shortly.

I’m working on this now. When I get this fixed, I’ll send out a new version.