RMIT
/
Project_Junker
1
0
Fork 0
Code Issues 0 Pull Requests 0 Releases 0 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
47 Commits
1 Branch
277 MiB
Tree: df5d174a53
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'df5d174a53'
${ noResults }
Project_Junker/unity_Project/Assets/0bjects/Terrain/README_Terrain.txt

17 lines
555 B
Raw Normal View History

NOTE 1: "MainLevel" scene made un Unity 5, ver.5.1.3f1 NOTE 2: If you require me to revert my Unity version and save the scene for v5.1.2f1 compatibility, let me know ASAP. + Created a new Unity scene named "MainLevel.unity" in the Scenes folder. (All prefab objects are in this scene.) + Most of the essential structures in the level have been set up. More props for purely aesthetic will be added later. + MainLevel scene uses "InputManager.asset" downloaded via Facebook chat on 29.8.15 + Added objects from original Maya scaffold scene as seperate objects for prefab use. + Created a new folder named "Custom Meshes". Contains meshes for appropriate collision for certain objects + Added README text files to the following folders: Objects, Textures, ToonShading. (Certain README text files contain specific information including naming conventions. Please read for more info.) KNOWN ISSUES: - Interactable objects with the "moveable" tag and using a Mesh Collider have no effect on the magnet rods. When using a default RigidBody on such objects, the following console error occurs: "Non-convex MeshCollider with non-kinematic Rigidbody is no longer supported in Unity 5" "If you want to use a non-convex mesh, either make the Rigidbody kinematic or remove the rigidbody component" - The above error does not occur when "Is Kinematic" is ticked in the Rigidbody component; however the object cannot interact with the magnet rod.
9 years ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
 
  1. ======================================
  2. PROJECT JUNKER
  3. ======================================
  4. TEXT FILE LAST UPDATE: 31.8.2015
  5. 

  6. 

  7. 

  8. ==========================================================================
  9. > TERRAIN/AREA
  10. ==========================================================================
  11. > All terrain meshes must be exported as a .FBX file.
  12. 

  13. > All objects should use the following naming convention:
  14.   "area_XX.fbx" where "XX" is the name of the object.
  15.   
  16.   E.g. "area_shack.fbx"
  17.   E.g. "area_scaffold_enterance.fbx"
  18.   E.g. "area_scaffold_end.fbx"