We are seeing problems defining aliases for motors using the Motors/Sensors wizard. We start RobotC from a fresh reboot of the laptop, make a new file, use the motors/sensors wizard as shown in the attached document, and then write a simple program to test if it has given aliases to the motors. The screenshots in the attached document tell the story best.

I am able to reproduce your issue so I would assume this to be a bug. Please send an email to support@robotc.net to report it through the official channel.

As a work-around, is there a reason you are not daisy-chaining your controllers? This seems to avoid the issue when I played around with your same basic setup, just connected differently.

thanks for the reply. we were simply trying to avoid daisy chaining to trouble shoot a problem... we wanted to eliminate the daisy chain itself as a potential problem.