3D应用程序代写 IntroductionWeek 1 to 8 Laboratory sessions were designed to ensure you have engaged with the process of building a simple 3D App
Assignment Requirements 3D应用程序代写
In this Assignment, you will build a more refined 3D App using the skills, technologies and components acquired from week 1 to week 8.
In detail, you are required to:
Redesign your existing 3D App layout to provide a new Coca Cola Brand, you are specifically advised not to submit the brand designed during the lab work
- You could take inspiration from existing Coca Cola brands (see https://www.coca-cola.co.uk/brands), while being mindful of copyright issues, and choose three new brands to represent your Coca Cola Product models, e.g. Coke, Fanta, Sprint, Dr Pepper …,
- A simple way to do this would be to produce a Coke can, Fanta Can, Sprite can as your 3 Coca Cola Product 3D Models, this would give you access to the modelling marks defined in the rubric.
- Producing at least one of these Coca Cola Product 3D Models with more complexity, e.g. create a Sprite Bottle or a Coke Bottle would gain access to the higher end of the modelling marks and automatically qualify for one of the 45 mark blocks reserved for ‘deeper understanding’.
- You will need to acquire the appropriate textures for branding your 3D models.
You are required to integrate your 3D Models into a Coca Cola Branded UserInterface — your 3D App. You are only required to present three 3D Models for your 3D App, but you can add extra models based on your originals to populate your interface.
You shouldadd appropriate levels of interactivity between your 3D models and your 3D App:
- You should investigate the many examples on x3dom.orgfor ideas.
These tips are not exhaustive; it is up to you to make your own choices in relation to the proposed marking scheme. 3D应用程序代写
- Your3D App page:
- You must providea button to switch between wireframe mode to view your models — example code for this is provided in the Lab 9 Coca Cola VM on the Live Feedback Site.
- Utilising a texture panel in the HTML5 to select new textures on the model.
- Utilising a 3D model gallery to load new models in X3DOM.
- Provide buttons to select different camera views.
- Provide buttons to control lighting.
- You are expected to exploit AJAX and JSON, with JQuery (or an alternative) to dynamically load web page contents from a JSON packet supplied by the backend — see Lab 6 and 7.
These features are not exhaustive; it is up to you to make your own choices in relation to the proposed marking scheme.
Your 3D Applayout should have, as a minimum, the following responsive block elements:
- A header — you shoulddesign a CSS logo, e.g. ‘My Coca Cola Brand’ with a strapline.
- You should not use images for the logo, instead you should make effective use of CSS3.
- A method for displaying the selected 3D object
- You are advised, strongly, to use X3DOM (i.e. X3D inline in the HTML5)
- X3DOMprovides a degree of control built-in, but generally you will need to develop your own controls. Remember the Camera panel you created in Lab 4 to select Camera views in X3DOM — look at Lab 6 to see how to connect cameras to your models.
- See interactionideas mentioned above
- A method for displaying a description of the 3D objects displayed, which is synced with the object selection (e.g. JQuery.getJSON()) — Object Description.
- You should integrate other media objects where appropriate, e.g. further information, video, audio,images, etc. You can organise this by ‘swapping’ out media, e.g. swap the X3DOM view for an Image view, etc.
You must exploitthe Model, View, Controller (MVC) design pattern to implement your Virtual Museum — you may adapt the codes from Lab 7 and 8 tutorials, see the Live Feedback Site, while noting Lab 9 is not a complete version and should not be copied verbatim. Do not simply copy the example codes from the Live Feedback Site, this will only give you threshold marks, you must adapt and go beyond! In general, you are advised to:
- Use AJAX methodology to asynchronously update content on your 3D App exploiting JSON to exchange data between the view and a ‘server side’ model (the data store being SQLite)
- Use PHP scripting to access data from the data store (SQLite).
- As a minimum, place your Object Descriptions in the data store; you might be able to think of other elements such as appropriate metadata, interaction properties, etc. that can be stored.
- Note, while you are allowed to exploit a different frontend framework, you are limited to the backend PHP framework because of the University ITS Web Server. More specifically, your backend technology should run on the ITS Server.
You must provide a link to a GitHub archiveof your complete codebase and 3D models, and code documentation.
- You will need to set up a GitHub account. This allows us to very easily and in a consistent way check your codebase. This method of archiving and managing your codebase will attract 5 of the extra going beyond marks.
- Make sure that your codebase also includes your complete 3ds Max archivefor your 3 models. Check out in 3ds Max how to save an archive
You must provide a separate link on your 3D App, e.g. in the footer, to access your VRML or X3D model on your GitHub archive, including associated materials, i.e. textures, so that they can be viewed in an external 3D player, e.g. the instantrealitiyintstantplayer.
- This will be used for emergencies, e.g. if we can’t gauge the quality of your 3D Models with the X3D embedded into your 3D App.
- It is easy just to provide your VRML exports if using 3ds Max, but don’t forget the textures, etc.
Your 3D App may also contain home page contents, and other page contents (content swapping) for items such as ‘About’, Statement of Originality’, Site Map, References, and GitHub links
You are allowed to adapt open source code(e.g. check out the X3DOM examples, etc.), but make sure you cite the source in the object description and appropriate references. However, clearly illustrating your own work in a system building approach will gain most marks.