
Re: Repeated Decisions 4: Obstacle Detecting Until Red Line
I heard back from RobotC Support and got the link for the pre-release build of RobotC (thanks John!), so here's an update on my 2 issues:
random freezes/crashes of IDE and failure of the colorSensor...
First I uninstalled all Robomatter products and deleted any remaining files/folders in the following directories:
C:\Program Files\Robomatter Inc
C:\Program Files\Robot Virtual Worlds
Then I installed the new version of RobotC: v4.11
And then installed the latest ChallengePack: v108
The short answer is IT WORKED! My programs that use the colorSensor are now successful - Yay!
And so far I haven't seen any RobotC IDE freezes, hangs or crashes. I'll report 'em if I do.The longer answer is that the process was a bit rough (for me anyway). So if others will be doing the same, here's the gory details.
If not -- no need to read below this!
Gotchas / Bugs seen on semi-fresh install of RobotC 4.11:BTW - I say "semi-fresh" because tho I uninstalled all RoboMatter products, I didn't purge the Windows Registry or delete all my previous programs (authored in v4.10). So consequently my license keys were already present, and maybe some other cruft (in the Registry).
Issue 1: After installing RobotC v4.11, I installed ChallengePack-v108 and accepted all defaults (esp: Program Maintenance setting of "Modify"):

Though it successfully completes, this results in an bogus install that actually reports as v105 when you download a program to your virtual 'bot. To fix this you have to run the ChallengePack-v108 installer and be sure to select the
"Repair" option on the Program Maintenance screen. That should give you the full set of v108 files.
Issue 2: For me, every time I run RobotC Graphical I have to go to the menus and change the settings from NXT to VX IQ, Virtual Worlds, and use Challenge Pack for VEX IQ:
These menu settings should be "sticky" across sessions:
Robot-> Platform Type-> VEX IQ
Robot-> Compiler Target-> Virtual Worlds
Window->Select Virtual World to Use->Challenge Pack for VEX IQ
Issue 3: Opening programs written by a previous version of RobotC will result in some strange function formatting that will need to be corrected before your program will compile without errors.
For example:

This can be fixed by manually choosing the correct function options from the drop-down control on each affected function in your program - tedious, but it works. But note that if your pull-downs don't have the full set of parameters you need to check and reset your Robot-> Motors and Sensors Setup screen. I had to select the Standard Models VEX IQ Clawbot to get the Devices tab to populate correctly.

There are probably other issues, but this post is long enough already

Can't wait to get after the line following activities!
Cheers, Scott