Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2016-09-08 ~ Oakland Gran Fondo 2016 R7 #7

Open
theo-armour opened this issue Sep 8, 2016 · 0 comments
Open

2016-09-08 ~ Oakland Gran Fondo 2016 R7 #7

theo-armour opened this issue Sep 8, 2016 · 0 comments

Comments

@theo-armour
Copy link
Member

image

@jaanga/terrain

full screen: Oakland Gran Fondo 2016 ~ 3D Route Viewer R6

Full screen - 'dev' release: Oakland Gran Fondo 100 2016 ~ 3D Route Viewer R7

2016-09-07 ~ R7

  • Complete rebuild
  • JavaScript split into nine small files
  • Each file has its own unique namespace JavaScript parent object
    • The object name also appears in the file name and in the folder name
    • You can identify the source and location of declaration for every function and variable just by looking at its name
      • Reduces the hunting through files to find the source
  • Progress in building a template system
    • Each file has its own parent HTML file for viewing and testing in isolation
    • Each file can load any menu it needs at load time
    • Each file can manipulate the Three.js scene, after the scene has been created
    • All scheduling and callback handling carried out by simple, easy to understand functions
  • Support four separate camera protocols
    • World camera: camera fixed at position in the air, follows nothing
    • Track camera: camera fixed at position on ground, follows actor
    • Chase camera: camera fixed inside actor, follows a point just ahead of the actor
    • Inside camera: camera fixed a distance from actor, follows actor position and rotation
  • Slight temporary reduction in some feature
    • Old and new features to be introduced in the next few days
  • Paths are displayed in three ways
    • Magenta line is the original TCX route of ~3,000 way points - full of twists and turns
    • Green line is a reduction of the path down to 300 points - takes out all the minor twists
      • This 'simple' line is used to create the highly visible path that you see
    • Yellow line is a spline that passes through the 300 points of the green line
      • You select how many points in the spline - from 200 to 4000
      • This line is the path for the camera
      • The camera stops at each point this determining the speed of the camera
        • The more the points/stops, the slower the camera proceeds
      • The default of 9,000 points gives a fairly smooth ride along the path
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant