Hey guys,
just letting you know im doing my part on Ann Myers Medical Center.
cheers,
Chaddy
Thursday, July 31, 2008
Wednesday, July 30, 2008
Object Bank
Hey guys,
I think our object bank is useless... I tried to upload the coding but it crashes everytime becuase its a huge amount of text, like a few hundred lines or so...Kiff, we have a conundrum...
Cheers,
Chaddy
I think our object bank is useless... I tried to upload the coding but it crashes everytime becuase its a huge amount of text, like a few hundred lines or so...Kiff, we have a conundrum...
Cheers,
Chaddy
Tuesday, July 29, 2008
Module Plan
I have typed up the module plan that we made today in the meeting in a Google doc
here's the link ~ http://docs.google.com/Doc?id=dcxtxfwn_47gt4gf5hr
I've made everyone collaborators so that you can make changes if you can think of any additions when running through the Case Study again.
Remember that Luke wants everyone to go through the Case Study again and make sure that we haven't missed anything major from weeks 4 to 9 then let us know about it in the comments add it to the Google Doc; Once you read through both then sign off in the comments here!
Cheers
here's the link ~ http://docs.google.com/Doc?id=dcxtxfwn_47gt4gf5hr
I've made everyone collaborators so that you can make changes if you can think of any additions when running through the Case Study again.
Remember that Luke wants everyone to go through the Case Study again and make sure that we haven't missed anything major from weeks 4 to 9 then let us know about it in the comments add it to the Google Doc; Once you read through both then sign off in the comments here!
Cheers
Minutes 29/07/08
TEAM CRITICAL LIFE – Minutes 29/07/08
TEAM MEETING
AGENDA
- Work through the Case Study to sort out the scenarios
ABSENTEES - NIL
NOTES
- Luke annoyed at Dylan losing case study
- New Deadlines
- Next Monday - Research Doc's to Dylan
- Next Wednesday - Updates to SADD to Dylan
- Monday Week 5 - Cut-scene plan (storyboard and script)
- End of Week 6 - have module done ready for testing (object and scripting done)
- End of Week 7 - Prototype for User Documentation
- End of Week 8 - Test Plan
- Dylan needs to update the schedule with these above deadlines, as well as the major deliverables set out in the Project 2 handout
- Milestone for Project 2 reached
- Joel had first good idea - use of the first person (camera mode) in SL to do the cut-scenes
- Need to chase up Client (Blake) for the handovers relating to the Case Study being adapted
- We need to add a sign to let the user which scenario they are currently in
- We could light up the scenario selector board
- At the end of each cut-scene we need to let the user know what the goals of the scenario are
ACTION
- All objects need to uploaded by Friday
- If we run out of prims put boxes in place of objects not yet uploaded - so we can start scripting
- Talk about what we are doing for the poster presentation next Monday meeting
- Dylan to update the schedule (as stated above in the notes!)
- Chase up Blake for the handovers
NEXT MEETING: - MONDAY 1:30PM 4/08/08 - TEAM MEETING
Objects and Prims
Hey guys,
I've uploaded the drug trolley and we have a massive.....20 prims left :P i think were going to need a few more since I have about 4 more objects to still go in.
Cheers,
Chaddy
I've uploaded the drug trolley and we have a massive.....20 prims left :P i think were going to need a few more since I have about 4 more objects to still go in.
Cheers,
Chaddy
Monday, July 28, 2008
Minutes 28/07/08
TEAM CRITICAL LIFE – Minutes 28/07/08
SUPERVISOR MEETING
AGENDA
- Discuss the Test Plan
- Discuss the first Semester
ABSENTEES - NIL
NOTES
- Justify the methodology in the SADD
- School of Nursing; need for hands on in education of Nursing
- Connect examples in SL to usefulness of the platform for Nursing
- Key points for extra research
- Nursing is mostly - hands on real life based
- SL simulates that (with multiple users)
- Define more constraints in the SADD to do with SL
- Poster presentation
- Print out as A2
- Use screen dumps - make things pretty
- Do the Test Plan
- Matty's in charge
- User Docs
- Text based
- Interactive DVD
- Youtube
- What is needed
- Introduction to SL
- Set up before you Sim (SLURL; browser)
- tips and tricks (shortcuts)
- how to operate sim
ACTION
- Joel to rig jig some of the prims (in the bed and so on) to save on more prims
- Fix the back wall up (windows)
- Continue with current set up for the research doc; Luke to slightly adapt his
- SDD
- Ben - Platform Rationale - constraints and advantages
- Make Teleportation buttons (board)
NEXT MEETING: - TUESDAY (After lecture) 29/07/08 - TEAM MEETING
Thursday, July 24, 2008
Team/Supervisor Meeting
Time: 1:30pm - 2:30pmDate: 28th JulyLocation: T124Agenda: Discussion Regarding Semester 1 & 2 Project.For project development team this means there will be an additionalmeeting on Tuesday after the Lecture.
Tuesday, July 22, 2008
Breathing Animation
After playing with animation scripts for weeks and pullling my hair out I've come up with the most simple and idiot proof way to animate the breating - no video this time becuase it is so simple - just go into second life and check it out. They are the two objects (supposed to be shaped like a stomach) in the right corner.
Amendment to Minutes 22/7/08
Matty, can you please amend the SPMP with the following roles (with a very brief description/responsibility as before) and upload them:
Dylan: Documentation Leader
Matt: Test manager
Joel & David: Video engineers
Luke & Ben: Sound engineers
Also:
Weekly meetings times: Monday 1:30-2:30 & Tuesday: after lecture
Also for next weeks meeting – we are to discuss the Poster for week 5 (perhaps in supervisor meeting)
Dylan: Documentation Leader
Matt: Test manager
Joel & David: Video engineers
Luke & Ben: Sound engineers
Also:
Weekly meetings times: Monday 1:30-2:30 & Tuesday: after lecture
Also for next weeks meeting – we are to discuss the Poster for week 5 (perhaps in supervisor meeting)
Minutes 22/7/08
TEAM CRITICAL LIFE – Minutes 22/7/08
TEAM MEETING
AGENDA
- Talk about meeting times for the semester
- Brainstorm about how to make a decent looking Patient
- Talk about what updates need to be made to Documents
ABSENTEES - NIL
NOTES
- Monday 1:30 is the new weekly team meeting **need to update SPMP with that info
- Tuesday after lecture a quick meeting as well
- Make sure that we have meeting room booked (don't have meetings in the airport lounge as that didn't work very well)
- Supervisor meeting next talk about stuff to do with project
- Design:
- Focus on making the final product on the bottom level - delete the second level
- Use the scenario selector to bring the relevant object
- Patient
- Dylan's gonna chase up his guy (superheroes), forward to Joel and Chaddy
- Thursday night @ 8:30 to chase up on the patient
- Importing patient textures (eyes and so on)
- The cutscenes on Youtube can go in the CD for the User Docs
- Matty is in charge of testing
- Dylan is in charge of User Docs
- Matty and Dylan will be assisting each other in those roles
ACTION
- Joel to draw up the current floorplan for the Project (which will be an update to the SADD)
- Delete the Top floor of the prototype, stick to the one floor for the final Product, with the different rooms as specified by the floorplan
- Everyone's Research Docs go to Dylan by Friday next week - Dylan to combine into one doc
- Luke to send email to Kathleen of who's doing what and how much (from lecture)
- (At least one person) Bring the Case Study next week (Monday) so that we can do the Build Plan (update to the SADD), we need to work out exactly how we are adapting the Case Study into the different scenario's
- Also talk about the Test Plan and User Docs next weeks meetings
- Dylan to update Semester 2 schedule (refer to Unit Description)
NEXT MEETING: - Monday 1:30 28/7/08 - TEAM MEETING (SUPERVISOR)
Thursday, July 17, 2008
Research doc
Hey Guys,
Just working on the research document i i thought i would just suggest to maybe add onto the template and references heading so you can record any additional references other than the obvious second life ones that you may use to produce your document.
Cheers.
Just working on the research document i i thought i would just suggest to maybe add onto the template and references heading so you can record any additional references other than the obvious second life ones that you may use to produce your document.
Cheers.
Monday, July 14, 2008
Minutes 14/7/08
TEAM CRITICAL LIFE – Minutes 14/7/08
TEAM MEETING
AGENDA
- Catch up on what has been done over the break
- Discuss what still needs to be done
ABSENTEES - Dylan
NOTES
- Dylan needs to get onto the study of the uni's computers ability
- Dylan,
- Research Doc (get it done and email to Luke by end of lecture break) ~ (week 3)
- Intro
- Overview of organisation
- Second Life Module
- What it is
- What it does
- Purpose
- Application
- SDD (due week 3)
- Basically re adapt what has been done in the SADD
- Try to get that done week1
- Matty start working on the Test Plan
- Line up with the Traceability Matrix
- Dylan to post on Blog what has been done on the documentation plan
- Dylan to advise if he needs someone to help with all the docs, CD video, as well as text based
- Scrap the whole idea of different stories on the building for the levels, instead have a reset that organises the objects to the correct states for that scenario
ACTION
- Luke to re email
- Everyone (especially Dylan) read the previous blog post saying what to do in the lecture break
- Joel and Chaddy are meeting in Second Life (layout the design...)
- Let us know how we are going prim's wise (prim count), and removing whatever unwanted objects
- Luke and Ben, functionality of the prototype is all there and working
- Joel and Chaddy, continue to add to the object bank
- Matty to add code to the code bank
- Dylan to do the schedule for semester 2 with all the deadlines
- Organise meeting after the first lecture
- Ben to do the template for the research doc
- Remember to sign the blog posts - so that Luke knows we've read it!
NEXT MEETING: - Day Time ##/##/## - MEETING TYPE
Friday, July 4, 2008
Detection Teleportaion i.e. Max number of people in a room
I've finished the teleportaion script. Check out the vid i'm sending and go online and have a looky
These links will help alot when it comes to implimenting them -
http://wiki.secondlife.com/wiki/LlSensor
http://wiki.secondlife.com/wiki/LlSensor
(i'll put them in the link bank if anyone wants them)
I'm off for a week - we have a meeting on the 14th of July 4:00pm - 5:00pm in T127 - i'm expecting alot of quesitons/ideas and quite a bit of work done in the next 2 weeks from everyone. Especially from that Rhay Finkler. If you have to contact me do so on my phone as I wont have the internet.
Peace.
These links will help alot when it comes to implimenting them -
http://wiki.secondlife.com/wiki/LlSensor
http://wiki.secondlife.com/wiki/LlSensor
(i'll put them in the link bank if anyone wants them)
I'm off for a week - we have a meeting on the 14th of July 4:00pm - 5:00pm in T127 - i'm expecting alot of quesitons/ideas and quite a bit of work done in the next 2 weeks from everyone. Especially from that Rhay Finkler. If you have to contact me do so on my phone as I wont have the internet.
Peace.
Thursday, July 3, 2008
Oxy baby
I’ve got the oxygen tank script to work based on the number of people in a room.
When clicked the oxygen tank counts the number of people in the room – it then detects who clicked it and adds them to an arraylist – ensuring they don’t already exists in this array so one person can’t click the on button 4 times to turn it on. Each person in the room clicks the ‘on’ tank and is added to the array. Once the array size is equal to the amount of people in the room the tank is turned on. At the moment there is text with it but I’ll remove that.
Also I’ve almost completed the transportation/room max size script. I’ll finish that tomorrow (please don’t edit) and upload it some time next week. I need to talk to Joel/Chaddy about the layout of the simulation. Prob in out meeting on the 14th July – I’ll post the details of that meeting tomorrow.
Luke.
When clicked the oxygen tank counts the number of people in the room – it then detects who clicked it and adds them to an arraylist – ensuring they don’t already exists in this array so one person can’t click the on button 4 times to turn it on. Each person in the room clicks the ‘on’ tank and is added to the array. Once the array size is equal to the amount of people in the room the tank is turned on. At the moment there is text with it but I’ll remove that.
Also I’ve almost completed the transportation/room max size script. I’ll finish that tomorrow (please don’t edit) and upload it some time next week. I need to talk to Joel/Chaddy about the layout of the simulation. Prob in out meeting on the 14th July – I’ll post the details of that meeting tomorrow.
Luke.
Wednesday, July 2, 2008
On Off Switches
I’ve been working on a script which will detect each avatar in the room and will then only turn something on once each avatar has clicked the on button. The issue is I have no problem detecting who is is the room but I can’t detect an individual avatar when they have clicked the on object.
If anyone (ben or matty especially) can find a scipt which will detects who the avatar is who clicks an object then we can create a script which detects each avatar in the room and adds them to a list(array) then as each one clicks the object their name is added to another array (after checking if they exist are not). Once the size of this array is equal to the number of avatars in the room the object will then turn on. It’s quite an affective way of doing it but wont work unless I can find something that will detect the avatar who clicks on an object.
Other wise I’ll have to do a similar thing but will only work once the object has been clicked 4 times – essentially meaning that any one person could click the on button 4 times to turn it on.
Let me know if anyone has any thoughts.
If anyone (ben or matty especially) can find a scipt which will detects who the avatar is who clicks an object then we can create a script which detects each avatar in the room and adds them to a list(array) then as each one clicks the object their name is added to another array (after checking if they exist are not). Once the size of this array is equal to the number of avatars in the room the object will then turn on. It’s quite an affective way of doing it but wont work unless I can find something that will detect the avatar who clicks on an object.
Other wise I’ll have to do a similar thing but will only work once the object has been clicked 4 times – essentially meaning that any one person could click the on button 4 times to turn it on.
Let me know if anyone has any thoughts.
Creating Objects in Max
This is really only relevant to Chaddy n I, but ill post it here coz its much easier.
When creating objects in Max, especially small equipment, don't assign a size value greater than 3, try to work in decimals. The unit is in metres, so objects will appear huge if it has a large size value.
I learned this the hard way, after spending hours creating the IV pump and aligning everything, I began to import it into SL before swot vac, once it was built the damn thing took up the entire room, and shot through the second-story roof. Hopefully no prims got stuck beneath the ground.
Also ive noticed that any objects flipped with the Mirror tool dont keep that orientation when transferred into SL.
And, I have also noticed an issue with objects when you move the Pivot Point.
Basically, if you want to "mirror" and object you'll just have to use the Rotate tool.
When creating objects in Max, especially small equipment, don't assign a size value greater than 3, try to work in decimals. The unit is in metres, so objects will appear huge if it has a large size value.
I learned this the hard way, after spending hours creating the IV pump and aligning everything, I began to import it into SL before swot vac, once it was built the damn thing took up the entire room, and shot through the second-story roof. Hopefully no prims got stuck beneath the ground.
Also ive noticed that any objects flipped with the Mirror tool dont keep that orientation when transferred into SL.
And, I have also noticed an issue with objects when you move the Pivot Point.
Basically, if you want to "mirror" and object you'll just have to use the Rotate tool.
Subscribe to:
Comments (Atom)