MindRover Known Bugs List

Open Issues:
Fixed in V1.07
Fixed in V1.06
Fixed in V1.05
Fixed in V1.02

 

  GeForce Crash
 

Description: MindRover crashes on start up with a GeForce 3D accelerator card.
Work-around: The GeForce 3d accelerator supports SO MANY OpenGL extensions that MindRover gets confused just writing them to the log. Goto the downloads page and download a registry entry called "nologs.reg". Double-click on it to start, and say "Yes" when it asks if you're sure.

This prevents MR from writing to its log file at all. Not so good if you're trying to help us track down other problems, but at least it won't crash.
Status: Logged in bugtracking (KFQ397)
Fixed in v1.02

Second Tutorial Crash
 

Description: I consistently get a game (not system) crash when I load the second (track sensors) tutorial for the SECOND TIME. 
Work-around: For now, don't run the second tutorial more than once. So far this has been reported on Voodoo III and Banshee boards. This indicates a problem which may occur at other times during game play as well.
Status: 3dfx has fixed it... please check their website for latest driver releases. Also be sure to update your DirectX driver from Microsoft as well.

 Autorun searches for the CD
 

Description: After starting MindRover with the autorun feature, if you finish playing the game and remove the CD, later on (like during a shutdown), autorun will want the CD and may cause the blue screen of death. Autorun doesn't shut down after starting, it just minimizes itself.
Work-around: Close down the Autorun program
Status: Logged in bugtracking (KFQ402). This can only be fixed for the next CD build.

TextBox Editing
 

Description: The text editor window used to enter vehicle descriptions needs some work on its wordwrapping. Go to the middle of a description and edit it by typing some additional text. Then check the repeated text that appears at the end of the description.
Work-around: Go back and delete unwanted text
Status: Some fixes will be in v1.05

Slow Motion text
 

Description: The words 'Slow Motion' appear in the upper left of the screen from time to time, and it doesn't seem to correspond to frame rate. 
Work-around: Ignore this. What we were trying to do was to tell you when your computer's frame rate wasn't able to keep up with the physics. But it isn't working properly.
Status: I think we will eliminate this message. (KJK21)
Fixed in v1.02

Windows Mouse
 

Description: I sometimes get a windows mouse icon overlaid on the screen.
Work-around: Ignore it. This sometimes happens if something else is happening on your computer while you are playing MindRover (such as a screensaver, or aim message).
Status: We hope this is fixed in V1.05.

Missing Components
 
 

Description: I made a vehicle with a sonar, a loop timer, a few lasers and a machine gun. All was well but I was through with the vehicle and deleted it. When I went back to make a new vehicle, the components I had on the vehicle I deleted were no longer there.
Work-around: Quit MR and restart, the components will return.
Status: Fixed in next release. (KJK6)
Fixed in v1.02

Quarry Battle Scoring 
 

Description: In Quarry Battle, when the computer scores the third point, the score jumps to 4 instead of 3 and the game just continues. 
Work-around: There is no work-around (but at least you always win!).
Status: Fixed in upcoming patch 1.01. (KJK13)
Fixed in v1.02 as well.

Shooting through Walls 
 

Description: The machine gun and the laser are able to hit a vehicle on the other side of a wall or obstacle. 
Work-around:  
Status: Put in bugtracker. (KJK15)
Fixed in v1.02

  Logical Component Input
 

Description: I tried to pass a 1 value from a Variable into a LogicalNOT the game crashed with a message saying in effect "don't pass float values to Logical operators." 
Work-around: The logical components need true/false, boolean values.
Status: Fixed in upcoming patch 1.01 (KJK16)
Fixed in v1.02 as well.

  Wrong F1 Help
 

Description: When I first choose a new scenario and then click on F1 help, I get help for some component, not the for the scenario.
Work-around: Click on the scenario again, and then F1. After loading a new scenario, valid vehicles and components are also loaded. To get the focus back to the scenario, just click on it again. 
Status: Logged in bugtracking. (KJK17)
Fixed in v1.02

 

  Math Component Range
 

Description: Math component ranges are limited to +/- 99 instead of +/- 180.
Work-around: Use extra components to add up to the amount you need.
Status: Logged in bugtracking (KJK23)
Fixed in v1.02

 

 Sound/Music Sliders
 

Description: Music volume slider has no effect.
Work-around: You can set the music volume from windows before starting MindRover. This may be true for the demo, but work fine for the game since the demo uses Midi music and the game uses Red Book Audio.
Status: Logged in bugtracking (KJK9/10)
Fixed in v1.02 (still may not work for demo)

 Capture the Flag
 

Description: If one team member has a LootCarrier and the other doesn't, it can result in a situation where the vehicle carrying the flag thinks he has handed it off to his teammate, but he is still holding the flag and can't drop it or score with it.
Work-around: None. Replay the match.
Status: Fixed in V1.05.

 Renamed vehicles lost
 

Description: If you change the name of a rover, remove it from its team slot, then quit MR using F12, the rover is deleted.
Work-around: If you leave the renamed vehicle in the slot when you exit the game, it will not be deleted.
Status: Fixed in v1.05 (KJK025)

Sonar Angle
 

Description: I found that the sonar is sweeping through angles (it looks like) 90 to 180, after the first pass. It never comes forward again, and it doesn't seem to pass over the 180 mark.
Work-around:  
Status: Fixed in v1.05 -- no speed or angle rotation limits

Random Start 
 

Description: If I quit and restart MindRover and then immediately run a scenario for which I have already designed a vehicle, the actual running of the scenario is identical each time I completely quit and restart the game. 
Work-around:  
Status: Fixed in upcoming patch 1.01. (KJK4)
Fixed in v1.02

Vechicle cameras get confused
 

Description: After a while when running in a scenario, my camera gets confused (maybe when both vehicles die at the same time) and the camera controls reverse or all point to the same vehicle.
Work-around:
Status: Logged. (KFQ396), fixed in v1.06

back

Camera flies off into space
 

Description: Sometimes when you take control of the camera with shift-0, the camera will zoom off into space
Work-around: Hit 1 or 2 (or shift-1 or shift-2) to get back into the arena.
Status: Logged.

Long text tokens can crash the game.
 

Description: If you have a text token that's too long to wrap well at your screen resolution, the game may assert in TextBox.cpp, line 1275 with "remaining >= nonWhiteLength".
Work-around: Break up the long token into separate, shorter words that will wrap better.
Status: Fixed in V1.05

back

Machine gun rotation is not being restrained.
 

Description: The machine gun is not being restrained to +/- 45 degrees rotation.
Work-around: Exhibit self-restraint and don't set its angle outside this range. :-)
Status: Fixed in upcoming patch 1.01 (KJK0027)
Fixed in v1.02

Quotes are permitted in description.
 

Description: Using quotation marks in a Rover's description causes a compilation error and loss of future editing capability.
Work-around: Don't use quotes; they're supposed to be illegal characters.
Status: Fixed in v1.05

Going Through the Hockey Net
 

Description: In the hockey scenario, vehicles and the puck can travel through the sides of the net inappropriately.
Work-around: None.
Status: Logged in bugtracking

back

Sonar pings invisible objects
 

Description: Sometimes the sonar pings off invisible objects -- such as the area near waypoint A in GoldRush, or various points around the track in race scenarios.
Work-around: None. We need to fix sonar to ignore invisible objects (there really are objects there, the scenario is using them to make decisions, but sonar needs to ignore them)
Status: Fixed in v1.05

back

RangeTest Min/Max are integers
 

Description: You can't set a non-integer range for the RangeTest component (for instance .2 min to 2.5 max)
Work-around: Use variables and multiply your input to the RangeTest component by 10; set the min/max appropriately
Status: We are changing RangeTest to use non-integer values in v1.06.

TreadControl doesn't limit values
 

Description: TreadControl is allowing the LeftTread and RightTread properties to be set to values >100 at runtime.
Work-around: none
Status: Fixed in 1.05 (KJK0041)

Memory Leak
 

Description: The game gets slow or takes a long time to shut down after playing a long time.
Work-around: Exit MindRover and restart every once in a while.
Status: Fixed in 1.05

Collisions not always detected
 

Description: Sometimes collisions are not detected - for instance when a vehicle goes over loot and doesn't pick it up, or when a rocket goes through a vehicle without exploding.
Work-around: none
Status: Fixed in 1.05

Compile error
 

Description: Draw a wire from one component to another. If the default is to copy-on-change from Output to Input and you change it so that the wire activates the dest instead, then the vehicle may not compile when you hit "GO".
Work-around: If you highlight the suspect wire, click on 'Value' and then set the properties that you really want, it will fix this problem and the vehicle should compile.
Status: Fixed in 1.05

Can't win hallway race
 

Description: Sometimes a vehicle can make it around the hallway track and beat the opponent, but it doesn't register as a win. This happens because the invisible track sensors don't register that the vehicle has passed. The winning condition requires that the vehicle pass all these checkpoints in order. The games sensors are not basically not covering the entire width of the track.
Work-around: Save your vehicle and when the patch comes out, try it again. Or create a vehicle that stays pretty much in the middle of the track.
Status: Fixed in 1.05

Bump Sensor detects invisible things
 

Description: Sometimes the BumpSensor seems to bump into invisible things or start/finish lines.
Work-around: The start and finish line as well as a few points around a track in any race scenario includes some invisible objects that let us determine if each vehicle is going around the entire track in the right direction. Unfortunately, the BumpSensor can detect these things. We don't have a fix for this yet.
Status: Logged.

Alt Tab crashes a voodoo III/5 card
 

Description: If you try to use ALT TAB to change windows with a Voodoo III or 5, the game crashes
Work-around: The only work around is not to use ALT TAB or to use windowed mode. 3dfx has told us they fixed this, but new drivers have not been released as of Oct 2000.
Status: Logged.

You can't rename wires
 

Description: You can rename components and vehciles, but you can't rename wires
Work-around: There is none. We will look at this as a feature request for the next version
Status: Logged.

 

Thruster exhaust doesn't appear in the right place
 

Description: The Thruster doesn't always point in the right direction if you have rotated it while placing it on your vehicle.
Work-around:  
Status: Fixed in v1.06

Script Timeout capability
 

Description: It would be very helpful to have a script timout capability for scripting multiple games... then if the scenario doesn't end on its own, it can timeout.
Work-around:  
Status: Added in v1.06

Very complex rovers start acting funny
 

Description: Sometimes with a very complex rover you will find that things aren't behaving as expected. The rover may respawn itself outside of the arena or just may not follow its own logic. If you look in the mindrov.log file you will see a message "Out of memory in VM heap".
Work-around: Remove some logic components and wiring.
Status: We made the maximum VM size more than twice as large in v1.06, and added better message to the player if this limit is reached.

TrackSensor doesn't work properly when you rotate it
 

Description: If you rotate a TrackSensor while placing it on the vehicle, then the TrackSensor always looks forward. The line is going in the right direction but the TrackSensor is really pointed forward.
Work-around: Don't rotate the TrackSensors when you place them. Instead use the property setting in the Wiring screen to set the rotation. This works correctly.
Status: KJK0002, Fixed in v1.06

MindRover crashes with too many vehicles to load
 

Description: If you have lots of vehicles in your login directory, you may run into a bug that was just introduced in v1.06 where MindRover will crash when trying to run or load the vehicles
Work-around: The only thing you can do for now is to move some of the vehicles out of your login directory.
Status: To be fixed in v1.07

You can't run v1.06 from the v1.02 CD
 

Description: If you installed the game originally from the v1.00 or v1.02 CD, then upgraded to v1.06, you can't run the game from the CD autorun.
Work-around: Run the game from the Start menu or Explorer
Status: Investigating better options

DemoV106 second tutorial is broken
 

Description: In the demo, when you click on the TrackSensors scenario (in the tutorials) there are no chassis or opponent and you can't run this tutorial.
Work-around: Run the other scenarios.
Status: This will be back in the next demo version. But by then you won't need this tutorial! Fixed in v1.07

Upgrade V1.06 doesn't work with Matrox G400
 

Description: After installing the upgrade V1.06, G400 graphics cards crash on startup of MindRover.
Work-around: Run the settings program and use the 'simulated openGL' option.
Status: Fixed in V1.07

Weird F1 help message
 

Description: After pressing F1 for help and then Escape to quit the help screen, the next time you press F1 you get a weird help message.
Work-around: Don't use Escape to close the help window. There is a "close" button on the lower right of the help window, or use F1 a second time to close the window.
Status: Fixed in v1.07

Vehicle description text gets messed up
 

Description: If you make any edits in the vehicle description, then the formatting (extra spaces between paragraphs, etc) does not get saved.
Work-around: none
Status: Fixed in v1.07

Keyboard entry gets extra keys on some NT machines
 

Description: With some NT systems, when you hit a key on the keyboard it appears to hang. Or if you are editing text in a text box you get lots of extra keys.
Work-around: There is a registry setting you can make to work around this problem: keyrepeat.reg (you can get it from the downloads page).
Status: Logged in bugtracking

Matrox G400 drivers are buggy
 

Description: The latest version of Matrox G400 drivers (6.04.029, Sept 2000) have polygon displaying problems. You may see missing or strangely placed polygons.
Work-around: Run the 'Settings.exe' program from the MindRover installed directory and choose the 'simulated openGL' setting. When Matrox comes out with new drivers you can go back to the 'standard' setting.
Status: Logged in bugtracking; Matrox is aware of the problem and working on it.

Proximity Radar detects in 180 instead of 360 degree arc
 

Description: The proximity radar is only able to detect up to 180 degrees
Work-around: none; patch available
Status: There is a patch available on the downloads page.

Vehicle mysteriously hits Waypoint
 

Description: When a scenario moves a vehicle, the vehicle mistakenly registers HitWaypoint.
Work-around: none; avoid having the rover be moved over a Waypoint.
Status: Logged in bugtracking

back

When upgrading to Win2K MindRover stops working
 

Description: After upgrading to Win2K, MindRover sometimes crashes.
Work-around: We're still working on why this happens, but an uninstall and reinstall of MindRover should get you going again. Please use the mruninstall.exe program and make sure you save your vehicles directory.
Status: Logged in bugtracking

back