Testing

I have tested the nearly-finished project on two groups, one in the 20-40 age bracket and one in the 60-70 age bracket. 

A female tester aged over 60 really liked the project; she thought the landscape and models were impressive. She also found the controls very simple to use, an issue I had been worried about. She suggested that there were not enough objects to click on and look at; this is a valid criticism, but for purposes of this project it was necessary only to have one working object as making more would be repeating work already done. I would definitely expand the amount of objects if continuing work with the project, however. She also suggested the landscape was too sparse and that I should add trees and vegetation, a suggestion borne out by members of the 20-40 group.

A male tester aged over 60 thought the project was useful from a historical point of view. However, he had no interest in learning to use the controls and asked that I navigate around it for him. This could be a problem, as many people of this age group will not have  used similar applications such as video games and may not be interested in trying. It may be necessary to make more intuitive controls of a click-and-drag nature. This was my original plan but time constraints did not allow for it. He also wanted to get inside the crannog, which was part of my original plan but I did not follow through on it due to my decision to make the museum open air. In later incarnations I would be willing to make explorable architecture, which will involve significant work with lighting and baking textures. Again, time constraints do not allow me to do this at the moment, but it is something to think about. Both members of this group wanted the Unity player to be smaller, so that the whole player is viewable as you click into the homepage, so I will attempt to do this.

There were four testers in the 20-40 group, 3 male and 1 female. All enjoyed the project, but many were curious about what would happen if they went off the edge of the terrain, so it will be necessary to add more barriers to prevent this. One expressed a desire to explore the lake, but this goes beyond the scope of the project, as there is no facility at Lough Gur to explore beneath water level. One male, aged between 25 and 30, thought the texture on the crannog needed work. I agree, but this is again something I would do in conjunction with making it explorable.

During the testing process, some of the browsers were more suitable than others. Safari is currently my preferred browser for this project. It works well on Firefox as well, but many people use very restrictive pop-up blockers when using this browser, making it impractical. I will advise my users on the best choice of browser on the homepage, perhaps in the splash screen on the web application.

Splash Screen and web embedding

I created a basic splash screen and loaded the game to playing on clicking the button. It looks dreadful but at least I have the functionality there; I will edit it later.

The problem with the stretched application continues; I have uploaded to the web page but it stretches across the entire browser and does not look good. The code I used is available here:

http://docs.unity3d.com/Documentation/Manual/WorkingwithUnityObject.html#initPlugin 

I have posted on the Unity forums to find out if anyone can help, as I can't figure it out. Hopefully that will show something up. 

Another issue is that, in the finished application, when you click on an object to open a web page, it doesn't open in a new tab, rather it opens in the tab you have open so you have to browse back to the application and restart it. This is a pretty big problem so I am looking into ways to fix this now.

This is how much the application stretches :(

 

Level complete!

I've just finished the level - you can navigate round the environment, and click on objects to retrieve information on them. You can also rotate the macehead to get different angles on it. Now all I have left to do in Unity is create a start screen and possibly add some audio, anything else I need to do within Unity is optional. I also still need to work on the website and the embedding process but the main task is done. I'm going to go and reward myself with some GUI tutorials. Hooray!

First Person Controller and terrain constraints

My terrain is essentially finished, I might add some trees and grass later on but at the moment it is the shape I want it to be, apart from one small problem: I can't currently prevent my first person controller from going into the lake and not being able to get out. I have used step offset and slope limit to prevent him from going up the hills, but unfortunately I'm not sure how this works in the opposite direction. I've tried smoothing out the terrain by raising the parts of the lake that I've lowered, and it may just end up being a tedious process of doing that, but I'm sure there is also a scripting method I can use so I have to find that out.

This is what you can see from the lake. But you can't really do anything!

Unity file embedded to web

I've had a certain amount of success in that I have managed to create the basics of my Unity application and embedded it to the homepage of my online museum. It has not been seamless; the textures still aren't there, and I have a basic rotation on the macehead but it is not working the way I want it to. This I will sort out soon. At the moment the main problem is the way the web player appears in the page; I was hoping for a small window like in the actual Unity file in game mode, but the window is elongated. I also haven't compiled it at my desired start point and will have to look at creating a GUI as well. That said, I'm very happy with the way things are going so far. This is still my trial file so hopefully I will have these problems ironed out before I get the real thing sorted out.

As you can see, this screen shot shows just how problematic the game window is, but I should be able to sort this out.

Embedding Unity to a web page

I tried to embed Unity into a web page in order to know how to do it when I have the actual Unity project finished. It wasn't seamless; the Unity file itself needs to be a .unity3d file rather than a .unity file. Any files I've created in Unity so far have been .unity files so I need to figure out how to save my file with that extension. It may be a simple problem but I haven't done enough research yet on it to know. Here is the screenshot:

I got the code from the Unity community and added it to my own. Here is a screen shot of the code:

 

Site design and museum navigation

Here are the initial sketches for the site design as I envision it.

And here is the navigation design for the online museum.

Unfortunately the scans aren't perfect. However this is my initial idea of how the user navigates through the online museum, clicking and dragging to view the objects and areas. This may be subject to change as I am no longer certain that this type of navigation will be practical, but I am waiting to hear more advice from the project supervisors.