Hi Nick
Have you read our last posts???
Can you please let us know ASAP if you have any ideas as we are submitting tomorrow....
Thanks
Mark, Richard, Whiskers
Tuesday 21 April 2009
Friday 17 April 2009
rotate view script
hi nick
also, by any chance would you know a script which could be used to change the screen view. what we want to do is rotate the view for 4 different states in isometric mode....
if you have any ideas let us know
thanks
mark, richard, felix
changing the colour of an object
hi nick
would you know of a script to change the colour of an object, using if statements. At the minute we are using, for example:
if((sensorInput.sensor3>=348)&&(sensorInput.sensor2>=348))
{
pCube13.setAttr "blinn2.color" -type double3 1 0 0;
}
all we want to do is change the colour to say RED when the sensor readings are over these values, and from this we can adjust to the rest of our script.
Please let us know asap
Thanks
Mark, Richard, Catman
Friday 10 April 2009
If expression for multiple objects
Nick,
Hope the Easter holidays are going well.
We are having problems with connecting the If statements to multiple object output. An example (in the long run) we are trying to achieve is that if sensor A <X then translateX, if sensor A >X but < Y then translate Z, and if sensorA >Y then translate Y. Though we are having trouble connecting just even one statement. Here is the script we have complied together:
int $num = 30;
float $multi = 10;
float $zFactor = 2;
for($j=1; $j<=$num; $j++) {float $xMove = sin($j); float $yMove = ($j*.5); string $name = ("plane_"+$j); string $expressM = ($name+".translateZ=sensorInput.sensor1*" + ($j*10)); string $expressR = ($name+".rotateZ=sensorInput.sensor2*" + (sin($j)*5)); string $expressIf = (if (sensorInput.sensor3 >0.6)\r\n{$name+".translateX =sensorInput.sensor3*" + ($j*2)});
polyCube -n $name -ch on -o on -w $j -h $j -d 0.3;
move -a ($xMove*$multi) ($yMove*$multi) ($j*$zFactor) $name;
expression -s $expressM -o plane_1 -ae 1 -uc all;
expression -s $expressR -o plane_1 -ae 1 -uc all;
expression -e -s $expressIf -o plane_1 -ae 1 -uc all;
}
We have tried other ways of putting "if" statements into the seperate expressions that are created but again it doesnt work. I think this might be the closest way following the script editor and placing certain texts in the expression edittor. But I am thinking the problem is in this part of the code -string $expressIf = (if (sensorInput.sensor3 >0.6)\r\n{$name+".translateX =sensorInput.sensor3*" + ($j*2)}); - but I just don't know where.
Any help from anyone would be great fun! :)
Enjoy the rest of the "holidays"
OONAGH
spoons2101@hotmail.com
Hope the Easter holidays are going well.
We are having problems with connecting the If statements to multiple object output. An example (in the long run) we are trying to achieve is that if sensor A <
int $num = 30;
float $multi = 10;
float $zFactor = 2;
for($j=1; $j<=$num; $j++) {float $xMove = sin($j); float $yMove = ($j*.5); string $name = ("plane_"+$j); string $expressM = ($name+".translateZ=sensorInput.sensor1*" + ($j*10)); string $expressR = ($name+".rotateZ=sensorInput.sensor2*" + (sin($j)*5)); string $expressIf = (if (sensorInput.sensor3 >0.6)\r\n{$name+".translateX =sensorInput.sensor3*" + ($j*2)});
polyCube -n $name -ch on -o on -w $j -h $j -d 0.3;
move -a ($xMove*$multi) ($yMove*$multi) ($j*$zFactor) $name;
expression -s $expressM -o plane_1 -ae 1 -uc all;
expression -s $expressR -o plane_1 -ae 1 -uc all;
expression -e -s $expressIf -o plane_1 -ae 1 -uc all;
}
We have tried other ways of putting "if" statements into the seperate expressions that are created but again it doesnt work. I think this might be the closest way following the script editor and placing certain texts in the expression edittor. But I am thinking the problem is in this part of the code -string $expressIf = (if (sensorInput.sensor3 >0.6)\r\n{$name+".translateX =sensorInput.sensor3*" + ($j*2)}); - but I just don't know where.
Any help from anyone would be great fun! :)
Enjoy the rest of the "holidays"
OONAGH
spoons2101@hotmail.com
Monday 6 April 2009
The Submission
Hi everyone,
Hope the break is going well. As a reminder, below is an outline for the course submission. Each team member needs to hand in their own submission.
A4 document
-photos detailing the development of of the interface controllers
-drawings/diagrams explaining the relationship between the interface and the digital model
-renders from the animation
CD/DVD
-original maya files
-all developmental animations produced
-final animation
-pdf of A4 document
-all image files documenting the device
Hope the break is going well. As a reminder, below is an outline for the course submission. Each team member needs to hand in their own submission.
A4 document
-photos detailing the development of of the interface controllers
-drawings/diagrams explaining the relationship between the interface and the digital model
-renders from the animation
CD/DVD
-original maya files
-all developmental animations produced
-final animation
-pdf of A4 document
-all image files documenting the device
Friday 3 April 2009
files to be sent....
Hi Nick
Before we broke up for easter you said that you would send us a few scripts for our project; to remind you:
The "if" statement script which allows us to create a value that will not reduce in number even when the sensor input is lower than that value. This is so that we can move the sensors across a lofted surface creating multiple permanent depressions which stay in place when the sensor is moved. I think we discussed this as putting a STOP to the sensor value, or to hold it so that it cant reduce in value.
If there is any confusion in how I have described this, please let me know, or email me at marksteedman64@hotmail.com
thanks
Mark
Subscribe to:
Posts (Atom)