What steps will reproduce the problem?
1. Add any vehicle or drone that comes with a sensor array (rating 3 sensor
array in this example)
2. Right click the sensor array and choose "add as plug-in"
3. Browse to sensor functions and add camera
4. Right click camera and choose "add as plug-in"
5. Browse to vision enhancements and add any three 1 capacity enhancements
(such as image link, thermographic vision and smartlink)
6. Go to character info and click mark character as created
7. Try to save character
8. Get an error that says
"The following 1 items are over their capacity:
- Camera"
What is the expected output? What do you see instead?
The camera should not be "over capacity" it should have a capacity of 3.
Under "Sensor Functions" on pg 446, it says that if the function has the same
name as a imaging or audio device "it's the same as its description in those
sections with a capacity equal to its Rating" This should mean that a camera in
a rating 3 sensor array should have a capacity of 3.
Instead it seems to be stuck at capacity 1 no matter what the sensor array
rating is.
What version of the product are you using? On what operating system?
0.0.5.139
Seen on windows XP as well as windows 7
Please provide any additional information below.
I wonder if it because the program is assuming that a camera in a sensor array
is automatically a "Micro-Camera" with a capacity of 1. If so, that seems wrong
since the sensor functions table specifically says "Camera" instead of
"Micro-Camera"
A work around is:
- Instead of browsing to sensor functions to add the camera, browse to vision
enhancements and add a rating 3 camera
- the program will allow you to add vision enhancements to the camera as normal.
- The issue with this workaround is that the program does not count the camera
toward the 8 functions limit in the sensor array.
References:
See: "Sensor Functions" on pg 446 for rating and capacity info.
See: "Optical and Imaging Devices" on pg 443 for camera entry.
See: "Vision Enhancements": table of pg 444 for capacities of upgrades.
Original issue reported on code.google.com by jblu...@gmail.com on 15 Jan 2015 at 4:42
Original issue reported on code.google.com by
jblu...@gmail.com
on 15 Jan 2015 at 4:42