Levels Uploaded and Mondays Meeting

[Scott Meaney]

The uploads section now holds the following:

3D Level - All in Unity, mesh colliders setup and ready for the
programmers
2D Level - All in Unity, no mesh colliders and ready for the
programmers
Muse Rig - Rig with no animation, if you want to muck about with the
rig
Link to other files - Speaks for itself

Please keep these 4 as the only ones not in a folder so there is no
confusion.

Over the weekend, myself and Pete have made the level in Unity with
everything that was avaliable to us. Yes some walls are grey and some
textures are extremely basic, but this is what we had to work with.
Apart from the Taurus Cardinal texture which I know Jason has, but I
jus cant get off him right now due to him being away for the weekend,
nothing will get changed in this build now.

Let us all help the programmers as much as possible when they need
things tested. If any changed need to be made, the following will be
the correct actions:

1, Programmers report problem on Discussion Board

2, Depending on the issue, a designer will take responsiblity for
resolving this issue and set a time frame to do this within. Be
sensible with the time frames as we only have 12 days. If you cannot
start to resolve an issue straight away, dont take responsiblity.

3, When issue has been resolved by said designer and tested in Unity,
that designer will pass the file to Scott or Pete for a further test
in Unity.

4, Scott or Pete will then upload the new build for the programmers to
continue working with. (Scott and Pete will communicate on Discussion
Board about this).

That all seems very clear so if anyone has any issues with that,
please discuss here.

Most problems should be fast fixes that are able to be resolved in
under a few hours. If anything cannot be resolved in a small time
frame, then we need to discuss further a solution.

Please can everyone check the discussion board 3-4 times a day for now
on looking for issues to be resolved. This is a simple request to ask.

I will bring this up in tomorrows meeting. The meeting will be at
1.30pm, please all meet in the bar. If anyone has trouble getting in
for 1.30pm please mention that now on here so we expect you to be
late.

Thanks


--
Subscription settings: http://groups.google.com/group/wings-of-fate/subscribe?hl=en

[Peter Harries]

sounds good!

Could everyone please try as hard as possible to be around tomoro at
1:30! There's less than 2 weeks until hand it so it's pretty important
that everyones there so we can make sure we're all happy with whats
going on.

Also If people want to bring their dev diaries in so we can help each
other thats cool!

so yeh, in short, please be in the SU tomorow at 1:30 :D

[sammie clarke]

Very sorry guys, just got this message.

Obviously im not there today, but any problems you can get me through
here and scott/jason you have my skype addy so we can chat.

Ive uploaded the checkpoint sound today to the files and its under the
finished assets for unity section.

Any problems like i said let me know

[Charlotte]

Okay team, here's the revised [tidy/pro] version of the Error
reporting and resolving Procedure... I think. Scott, check it anf
ammend if required.



1. Finder of Error posts a new thread on Discussion Board.

- The subject title should follow this format:

"Error Report: [Whatever the error is] for [who needs to accept
responsibility for the error e.g. the ones who were involved in an
asset's production]"

- The actual post should follow this format:

Build Version: ___
Area of Problem: ___ [e.g. Muse, Cardinals, Sistine Objects, Sound,
etc]
Error Description: _____________

2. Error recognised by team. Everyone needs to stay aware of issues
that come up even if the asset was not one of yours, just in case you
have a solution to the problem.

- The designer responsible for asset posts a reply to say they've been
made aware of the problem, then starts working on it ASAP.

2b. If the designer gets stuck, post a new reply on the same thread
ASAP to request help, stating their problem.
2c. Team members input possible solutions.

3. When the designer believes the error is resolved in Unity, they
then pass it on to Scott/Pete for a further test in the build.

4. Error resolved.

- When the error is definitely resolved, Scott/Pete will upload the
fixed build for the programmers to continue working with and post a
reply on the thread:

Error resolved.
New build version: ___

[Scott Meaney]

I agree with everything Charlotte has said bar one thing. Step 1 I
feel does not need to mention a name in the title to whom should take
responsibilty for it just because they created the asset. Yes, I do
believe if that person created something, it would be best for them to
look into the issue, however I think it is upto them to said if they
will or not. I think that just stating the problem in the topc title
with further description in the post itself would be fine. I hope that
makes sense.