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.
67 Commits
1 Branch
277 MiB
Tree: 9f153ce981
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '9f153ce981'
${ noResults }
Project_Junker/unity_Project/Assets/0bjects/Custom Meshes/README_Custom_Meshes.txt

41 lines
1.4 KiB
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
​
​
2ND COMMIT (1.9.15) ========== ADDED: ========== + Tutorial puzzle (AKA GIF Puzzle) has been built. + New terrain added (work in progress). + "Resource Bay" objects (for Lift Puzzle) have been placed behind the Scaffold inner building. + Several interactable objects have been placed around the scaffold area. ========== CHANGED: ========== > Players 1 & 2 have been re-positioned to the front of the tutorial puzzle. > The object "Resource Bay" now uses 3 x box colliders instead of the custom mesh. (Custom mesh was in fact less that 256 vertices, but Unity still rejected it). > Reduced the Lighting feature "Ambient Intensity" from 1 to 0.62. > Temporarily disabled two Lighting features to stop unnecessary rendering: 1. Precomputed Realtime GI 2. Baked GI The above features can be enabled via Windows > Lighting > Scene Tab ================= WORK-IN-PROGRESS: ================= - Still need to place more prop objects for visual aesthetics. (Please give an update on FPS numbers to see if new scaffolds and terrain have a huge effect on frame rate) (Personally, my PC still ran at 60 FPS)
9 years ago
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
​
​
​
​
​
​
​
​
​
​
​
2ND COMMIT (1.9.15) ========== ADDED: ========== + Tutorial puzzle (AKA GIF Puzzle) has been built. + New terrain added (work in progress). + "Resource Bay" objects (for Lift Puzzle) have been placed behind the Scaffold inner building. + Several interactable objects have been placed around the scaffold area. ========== CHANGED: ========== > Players 1 & 2 have been re-positioned to the front of the tutorial puzzle. > The object "Resource Bay" now uses 3 x box colliders instead of the custom mesh. (Custom mesh was in fact less that 256 vertices, but Unity still rejected it). > Reduced the Lighting feature "Ambient Intensity" from 1 to 0.62. > Temporarily disabled two Lighting features to stop unnecessary rendering: 1. Precomputed Realtime GI 2. Baked GI The above features can be enabled via Windows > Lighting > Scene Tab ================= WORK-IN-PROGRESS: ================= - Still need to place more prop objects for visual aesthetics. (Please give an update on FPS numbers to see if new scaffolds and terrain have a huge effect on frame rate) (Personally, my PC still ran at 60 FPS)
9 years ago
​
​
​
​
​
​
​
​
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: 1.9.2015
  5. 

  6. 

  7. ==========================================================================
  8. > CUSTOM MESHES
  9. ==========================================================================
  10. 

  11. > Custom-shaped meshes should be used for objects with complex shapes
  12.   for proper object collision in-game.
  13. 

  14. > ***ONLY use a custom mesh WHERE NECESSARY. If an object will be used simplistically,
  15.      an appropriate mesh should be assigned in Unity (e.g. Box Collider) 
  16. 

  17. > Due to Unity 5's changes, any mesh with vertices greater than 256 will not work.
  18.   YOU MUST either reduce the number of vertices in a mesh OR cut the mesh into
  19.   several parts then parent those parts to empty childs in Unity.
  20. 

  21.   Refer to this YouTube link for more details:
  22.   https://www.youtube.com/watch?v=YJD05OFhyh8
  23. 

  24. 

  25. 

  26. > All customn meshes must be exported as a .FBX file.
  27. 

  28. > All custom meshes must be placed in the "Custom Meshes" folder.
  29. 

  30. > All custom meshes should use the following naming convention:
  31.   "mesh_XX.fbx" where "XX" is the name of the object.
  32.   
  33.   E.g. "mesh_cart.fbx"
  34. 

  35. > If there are two or more variations of a mesh, an alphabet prefix should be
  36.   at the end of the object name.
  37.   ******DO NOT USE NUMBERS as the ending prefix******
  38. 

  39.   E.g. "mesh_scaffold_A.fbx"
  40.        "mesh_scaffold_B.fbx"
  41.        "mesh_scaffold_C.fbx" etc....