kinetecharts / openperform Goto Github PK

This is in three parts.

1. SNORRY AND FIRST PERSON ARE A BIT SCARY STILL

Try this:

Camera Controls -> Snorry -> Performer 1
Camera Controls -> First Person -> Performer 1

Screen is dark and weird.

Camera might be too close (or, in case of First Person, poly backfaces might be unnecessarily rendered).

2. "FLY TO TOP" HAS JITTER

Fly to top gets mad when it reaches 45 deg. or so. Also, it doesn't track performer, instead going slightly behind performer.

While checking out this, I might add, a "fly to side" could be cool.

3. ALL CAMERA CONTROLS HAVE A "NONE" OPTION IN THE DROP-DOWN PICKLIST

This option is NOT necessary! Only the unselected option should be selectable.

Bloom looks like Sarah Connor's hallucinatory dream of nuclear apocalypse in T2.

Space is black.

1. Go to 'Environment'
2. Click on 'Change Environment'
3. Select 'Space'
4. Feel like you're in a black hole - stars are all missing!

Expected: Space.

Got: Blackness everywhere.

Here's a screenshot of the environment.

Here's a screenshot of the console.

OS information extraneous.

Description: Uploading one's own BVH file from disc works. However, it doesn't seem like anything happened, until you actually hit "Load File" to proceed to 3D world.

To Repro:

1. Go to 'Upload Your Own BVH' on the first screen, and click the button saying "Click to select file" or drag + drop a file from your filesystem GUI.
2. Click on 'Open' within your filesystem GUI if you did the "Click to Select File" option.
3. Note that the file has actually been loaded, but there is no apparent onscreen change (such as displaying the loaded file's filename.
4. Click 'Load File' within the OpenPerform modal.
5. Note that this operation completed successfully.

Expected Behavior: I wanted a happy face or a check mark or a filename to indicate I succeeded.

Additional Philosophizing: The button on the modal (shown below) saying "Load File" is perfect for the "Choose Example File..." flow of doing stuff but not perfect for the "Use Your Own BVH" flow of doing stuff.

Relevant Screenshot: For instance: This IS a LOADED file (in the sense of taken from local storage to my browser, just not in the sense of taken from "somewhere in my browser" to "visible in my browser's WebVR environment"):

OS:
ChromeOS
Platform:
11151.113.1 (Official Build) stable-channel eve
Firmware:
Google_Eve.9584.174.0
Channel:
Currently on stable
ARC Version:
5217886
Blink:
537.36 (@ab04191dbdc8146b84b76a6e91a762b88574eaa4)
V8:
7.1.302.33

It's not a bug. It's just annoying.

Ctrl + R

Expected: Rational filenames.

Got: Rational filenames with the word "edit" attached.

will hurt people's eyes

If I make my environment cool in Grid World, by making lines white instead of black, and grid red instead of grey, and background ("sky") blue instead of black, then change Environment to Water by accident, then change to Grid again, I lose my customizations.

asdf

Maybe?

I want to destroy the man sometimes, when I've made a mess out of him or the world.

All I can do is Ctrl + R.

Possible to add an in-window button to clear + reset scene without re-loading BVH file? A "clear world" button? Otherwise I'll note the importance of Refreshing in wiki.

Alternately: Deleting performers could be done in the bar.

Camera controls? Mouse controls? Links to GitHub issue page? Links to Kinetech Arts Meetup Page? You tell me what this needs!

If you have many performers onscreen it's hard to remember who is who.

Sometimes I want to know how far along the file I am. Would this be interesting and easy?

like this:

|--------------_______| 0.9s
|-----------------______| 1.0s
&c.

Use content from: https://github.com/kinetecharts/openPerform/blob/master/README-PerceptionNeuron.md

Description: User confused after accidentally moved world, instead of rotating world.

Steps to Repro:

1. Assume you're a total n00b.
2. Scroll around with two fingers to zoom in and out.
3. Click with one finger to rotate.
4. Click with two fingers accidentally, translating your position relative to the world, and assume you get stuck off to the side because of the accidental two-finger-ness factor of that two-finger-drag + click.
5. Go to the help menu to figure out how to use the camera.
6. Find literally every option except how to move the camera.
7. Maybe use the Camera Controls menu.
8. Find it doesn't correct your translation accident.
9. Realize you're a fool because it works just like all game engines, following a universal standard for interacting with 3D spaces via trackpad.
10. Wish it were in the Help Menu.

Here's what I want to see in the OpenPerform For Dummies Manual:
Two Finger Drag | Rotate world space
One Finger Click + Drag | Rotate world space
Two Finger Click + Drag | Translate world space

Here are some screenshots:

OS info extraneous.

Sometimes I want to move the camera.

I have to click. This works.

I want to use arrow keys though because I am a '90s kid I guess?

Willing to set this up and document how to change controls per https://github.com/kinetecharts/openPerform/tree/master/src/inputs

However, I probably need help going through this workflow once before documenting.

Why I need help: As it stands, the Readme.md for /src/inputs has the wrong pathname. Also presets are out of the GUI now. How to hack 'em back in?

Other relevant links on this topic for my convenience:
https://github.com/kinetecharts/openPerform/blob/master/src/inputs/presets/ExamplePreset.txt
https://github.com/kinetecharts/openPerform/tree/master/src/inputs/types
https://github.com/kinetecharts/openPerform/tree/master/src/outputs

Ideally also show how to hack menus and hopefully this is useful for that:
https://reactjs.org/blog/2015/09/02/new-react-developer-tools.html#installation
And also: https://github.com/kinetecharts/openPerform/tree/master/src/react/menus

Pretty simple bug

Discs and Robot avatars have big left shoulders nowadays. No other geometry effects have this shoulder bulge. Occurs independent of BVH file AFAICT.

Changing styles affects performance lots.

(FWIW I am on a Pixelbook w/ i5-7Y57 CPU @ 1.20GHz chipset.)

Open https://kinetecharts.github.io/openPerform/
In "Render Style" on lower-right click to open.
Select "Change Style" and select e.g. Sketch or AfterImage.

Expected behavior: It should be just as fast.

Actual behavior: It's laggy (frames being dropped?).

Here's a screencast:
https://drive.google.com/file/d/1-t_vaZw8yGBrR_qsuvygXyvlMnbeQqvo/view
You can see the performance improve (especially visible in feet) when switched to normal.

I guess using an i5 chip was a dumb idea. There's no issue on my Intel NUC w/ i7 and Iris 660.

PM for a trace of this issue by Chrome renderer.

The forest is too low.

Steps to reproduce the behavior:

1. Go to 'Environment'
2. Click on 'Change Environment'
3. Select 'Forest' in picklist
4. Adjust camera such that camera is level with ground.
5. See that man is floating.

Expected behavior: Man not floating.

Floating (default):

Translated to correct this:

OS:
ChromeOS
Platform:
11151.113.1 (Official Build) stable-channel eve
Firmware:
Google_Eve.9584.174.0
Channel:
Currently on stable
ARC Version:
5217886
Blink:
537.36 (@ab04191dbdc8146b84b76a6e91a762b88574eaa4)
V8:
7.1.302.33

Use content from: https://github.com/kinetecharts/openPerform/blob/master/README.md

We need more content than keyboard shortcuts, right? Filing a serrate issue for content recommendations.

... should say "Dependencies," although OpenPerform is definitely dependent on being dancy!

The man is floating about 1/2 mushroom-height above the ground. Translating Y axis by -0.38 puts him on the ground.

npm run build should come before npm run dev in docs

Happily, amazingly, multiple files can be loaded simultaneously, which is really cool.

There is a slight lag during initialization however (the first file-load). Later BVH-loads are not susceptible to this.

I never bothered too much to make any of these look good. They need to be looked at and adjusted.

Issue Description:

The button is small in the first place, but the actually selectable area is even smaller than the displayed button. Slightly confusing.

To Reproduce: Try clicking in the lower area of the (?) thing.

OS:
ChromeOS
Platform:
11151.113.1 (Official Build) stable-channel eve
Firmware:
Google_Eve.9584.174.0
Channel:
Currently on stable
ARC Version:
5217886
Blink:
537.36 (@ab04191dbdc8146b84b76a6e91a762b88574eaa4)
V8:
7.1.302.33

First Pass at Issues

####################
INSTALLING
####################

1. Include links to:
   nvm
   node
   npm
   sourcetree
   git Bash
   Windows Subsystem for Linux, including how to set up. This is a good thing. Git Bash is lame.

2. Using Sourcetree for the first time.
   Click the clone button (screenshot).
   Provide the exact URL needed for Git Bash.
   https://github.com/kinetecharts/openperform
   Or say obviously - click the thing (screenshot of the "Copy" button).
   Click the "File Explorer" button (screenshot).

3. Setting up node.

npm --version
nvm use 8.4
(click yes twice)
node --version
npm install node yarn webpack
(npm creates a package-lock.json file. is that ok? yarn says NO.)
(There is a typo here: "Install Dependancies." Though they are indeed dancy dependecies in this case!)
yarn
(does [email protected] need to be included? it throws an error with Git Bash on Windows, anyway)
(the thing where you have to make config_example.js be called config.js is silly. remove?)
(there is a typo here: "Once built, start produciton servers.")

4. Final Step.

npm run build
This worked fine.
npm run dev
This threw a strange error.

`> npm run dev

[email protected] dev C:\Users\Public\workspace\op2
npm run webpack | npm run data

[email protected] data C:\Users\Public\workspace\op2
node server/dataServer.js

Connecting to the Perception Neuron at ws://192.168.1.250:9000/service
Perception Neuron Server broadasting on 9100
Gamepad Server broadasting on 9101
Midi Controller broadasting on 9301
PoseNet listening on 9500
PoseNet broadcasting on 9501
IPhoneX listening on 9600
IPhoneX broadcasting on 9601
Perception Neuron Server Error!
Gamepad Server Error! { Error: listen EADDRINUSE :::9101
at Object._errnoException (util.js:1041:11)
at _exceptionWithHostPort (util.js:1064:20)
at Server.setupListenHandle [as _listen2] (net.js:1322:14)
at listenInCluster (net.js:1370:12)
at Server.listen (net.js:1466:7)
at WebSocketServer (C:\Users\Public\workspace\op2\node_modules\ws\lib\WebSocketServer.js:76:20)
at new Gamepads (C:\Users\Public\workspace\op2\server\sockets\Gamepads.js:16:16)
at Object. (C:\Users\Public\workspace\op2\server\dataServer.js:25:20)
at Module._compile (module.js:573:30)
at Object.Module._extensions..js (module.js:584:10)
code: 'EADDRINUSE',
errno: 'EADDRINUSE',
syscall: 'listen',
address: '::',
port: 9101 }
Midi Controller Error! { Error: listen EADDRINUSE :::9301
at Object._errnoException (util.js:1041:11)
at _exceptionWithHostPort (util.js:1064:20)
at Server.setupListenHandle [as _listen2] (net.js:1322:14)
at listenInCluster (net.js:1370:12)
at Server.listen (net.js:1466:7)
at WebSocketServer (C:\Users\Public\workspace\op2\node_modules\ws\lib\WebSocketServer.js:76:20)
at new MidiController (C:\Users\Public\workspace\op2\server\sockets\MidiController.js:16:16)
at Object. (C:\Users\Public\workspace\op2\server\dataServer.js:31:26)
at Module._compile (module.js:573:30)
at Object.Module._extensions..js (module.js:584:10)
code: 'EADDRINUSE',
errno: 'EADDRINUSE',
syscall: 'listen',
address: '::',
port: 9301 }
PoseNet Incoming Error! { Error: listen EADDRINUSE :::9500
at Object._errnoException (util.js:1041:11)
at _exceptionWithHostPort (util.js:1064:20)
at Server.setupListenHandle [as _listen2] (net.js:1322:14)
at listenInCluster (net.js:1370:12)
at Server.listen (net.js:1466:7)
at WebSocketServer (C:\Users\Public\workspace\op2\node_modules\ws\lib\WebSocketServer.js:76:20)
at new PoseNet (C:\Users\Public\workspace\op2\server\sockets\PoseNet.js:16:24)
at Object. (C:\Users\Public\workspace\op2\server\dataServer.js:43:25)
at Module._compile (module.js:573:30)
at Object.Module._extensions..js (module.js:584:10)
code: 'EADDRINUSE',
errno: 'EADDRINUSE',
syscall: 'listen',
address: '::',
port: 9500 }
PoseNet Outgoing Error! { Error: listen EADDRINUSE :::9501
at Object._errnoException (util.js:1041:11)
at _exceptionWithHostPort (util.js:1064:20)
at Server.setupListenHandle [as _listen2] (net.js:1322:14)
at listenInCluster (net.js:1370:12)
at Server.listen (net.js:1466:7)
at WebSocketServer (C:\Users\Public\workspace\op2\node_modules\ws\lib\WebSocketServer.js:76:20)
at new PoseNet (C:\Users\Public\workspace\op2\server\sockets\PoseNet.js:22:24)
at Object. (C:\Users\Public\workspace\op2\server\dataServer.js:43:25)
at Module._compile (module.js:573:30)
at Object.Module._extensions..js (module.js:584:10)
code: 'EADDRINUSE',
errno: 'EADDRINUSE',
syscall: 'listen',
address: '::',
port: 9501 }
IPhoneX Outgoing Error! { Error: listen EADDRINUSE :::9601
at Object._errnoException (util.js:1041:11)
at _exceptionWithHostPort (util.js:1064:20)
at Server.setupListenHandle [as _listen2] (net.js:1322:14)
at listenInCluster (net.js:1370:12)
at Server.listen (net.js:1466:7)
at WebSocketServer (C:\Users\Public\workspace\op2\node_modules\ws\lib\WebSocketServer.js:76:20)
at new IPhoneX (C:\Users\Public\workspace\op2\server\sockets\iPhoneX.js:20:24)
at Object. (C:\Users\Public\workspace\op2\server\dataServer.js:49:25)
at Module._compile (module.js:573:30)
at Object.Module._extensions..js (module.js:584:10)
code: 'EADDRINUSE',
errno: 'EADDRINUSE',
syscall: 'listen',
address: '::',
port: 9601 }
events.js:182
throw er; // Unhandled 'error' event
^

Error: listen EADDRINUSE 0.0.0.0:9600
at Object._errnoException (util.js:1041:11)
at _exceptionWithHostPort (util.js:1064:20)
at Server.setupListenHandle [as _listen2] (net.js:1322:14)
at listenInCluster (net.js:1370:12)
at doListen (net.js:1492:7)
at _combinedTickCallback (internal/process/next_tick.js:141:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
at Function.Module.runMain (module.js:611:11)
at startup (bootstrap_node.js:158:16)
at bootstrap_node.js:598:3
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] data: node server/dataServer.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] data script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\charl\AppData\Roaming\npm-cache_logs\2018-08-28T05_34_36_036Z-debug.log`

... because I ran it in Command Prompt.

Debug log output for above:

0 info it worked if it ends with ok 1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe', 1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js', 1 verbose cli 'run', 1 verbose cli 'data' ] 2 info using [email protected] 3 info using [email protected] 4 verbose run-script [ 'predata', 'data', 'postdata' ] 5 info lifecycle [email protected]~predata: [email protected] 6 info lifecycle [email protected]~data: [email protected] 7 verbose lifecycle [email protected]~data: unsafe-perm in lifecycle true 8 verbose lifecycle [email protected]~data: PATH: C:\Users\charl\AppData\Roaming\nvm\v8.4.0\node_modules\npm\bin\node-gyp-bin;C:\Users\Public\workspace\op2\node_modules\.bin;C:\Users\charl\AppData\Roaming\nvm\v8.4.0\node_modules\npm\bin\node-gyp-bin;C:\Users\Public\workspace\op2\node_modules\.bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\iCLS\;C:\Program Files\Intel\Intel(R) Management Engine Components\iCLS\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\Git\cmd;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\PuTTY\;C:\Users\charl\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Users\charl\AppData\Local\Microsoft\WindowsApps;C:\Program Files\Heroku\bin;C:\Users\charl\AppData\Local\atom\bin;C:\Program Files\Microsoft VS Code\bin;C:\Users\charl\AppData\Roaming\npm;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Users\charl\AppData\Local\Microsoft\WindowsApps;C:\Users\charl\AppData\Roaming\nvm;C:\Program Files\nodejs 9 verbose lifecycle [email protected]~data: CWD: C:\Users\Public\workspace\op2 10 silly lifecycle [email protected]~data: Args: [ '/d /s /c', 'node server/dataServer.js' ] 11 silly lifecycle [email protected]~data: Returned: code: 1 signal: null 12 info lifecycle [email protected]~data: Failed to exec data script 13 verbose stack Error: [email protected] data: node server/dataServer.js13 verbose stack Exit status 1 13 verbose stack at EventEmitter.<anonymous> (C:\Users\charl\AppData\Roaming\nvm\v8.4.0\node_modules\npm\lib\utils\lifecycle.js:289:16) 13 verbose stack at emitTwo (events.js:125:13) 13 verbose stack at EventEmitter.emit (events.js:213:7) 13 verbose stack at ChildProcess.<anonymous> (C:\Users\charl\AppData\Roaming\nvm\v8.4.0\node_modules\npm\lib\utils\spawn.js:40:14) 13 verbose stack at emitTwo (events.js:125:13) 13 verbose stack at ChildProcess.emit (events.js:213:7) 13 verbose stack at maybeClose (internal/child_process.js:927:16) 13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5) 14 verbose pkgid [email protected] 15 verbose cwd C:\Users\Public\workspace\op2 16 verbose Windows_NT 10.0.17134 17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "data" 18 verbose node v8.4.0 19 verbose npm v5.3.0 20 error code ELIFECYCLE 21 error errno 1 22 error [email protected] data:node server/dataServer.js 22 error Exit status 1 23 error Failed at the [email protected] data script. 23 error This is probably not a problem with npm. There is likely additional logging output above. 24 verbose exit [ 1, true ]

Confirmed this does not occur in Git Bash.

####################
RUNNING
####################

0. If you leave it open for a while, then terminate processes to stop, Git Bash stops responding.

1. Warnings are emitted on npm run dev using my first repo (before config was removed - unclear if related).
   This is an otherwise functioning system.
   Shell: Git Bash
   OS: Winsuck 10
   NPM version (under nvm control)
   { npm: '5.3.0',
   ares: '1.10.1-DEV',
   cldr: '31.0.1',
   http_parser: '2.7.0',
   icu: '59.1',
   modules: '57',
   nghttp2: '1.22.0',
   node: '8.4.0',
   openssl: '1.0.2l',
   tz: '2017b',
   unicode: '9.0',
   uv: '1.13.1',
   v8: '6.0.286.52',
   zlib: '1.2.11' }
   Browser: Firefox Quantum or whatever.

Warnings:

`WARNING in ../OP/node_modules/ansi-html/index.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\Public\workspace\OP\node_modules\ansi-html\index.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\OP\node_modules\webpack-dev-server\client\overlay.js
• C:\Users\Public\workspace\op\node_modules\ansi-html\index.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\op\node_modules\webpack-dev-server\client\overlay.js
  @ ../OP/node_modules/ansi-html/index.js
  @ ../OP/node_modules/webpack-dev-server/client/overlay.js
  @ ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080
  @ multi ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only-dev-server ./src/index.jsx

WARNING in ../OP/node_modules/base64-js/index.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\Public\workspace\OP\node_modules\base64-js\index.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\OP\node_modules\buffer\index.js
• C:\Users\Public\workspace\op\node_modules\base64-js\index.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\op\node_modules\buffer\index.js
  @ ../OP/node_modules/base64-js/index.js
  @ ../OP/node_modules/buffer/index.js
  @ ./node_modules/buffer-equal/index.js
  @ ./node_modules/load-bmfont/lib/is-binary.js
  @ ./node_modules/load-bmfont/browser.js
  @ ./src/effects/performer/DataTags.js
  @ ./src/effects/performer/index.js
  @ ./src/performers/Performer.js
  @ ./src/performers/Performers.js
  @ ./src/react/pages/Main.jsx
  @ ./src/index.jsx
  @ multi ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only-dev-server ./src/index.jsx

WARNING in ../OP/node_modules/buffer/index.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\Public\workspace\OP\node_modules\buffer\index.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\op\node_modules\buffer-equal\index.js
• C:\Users\Public\workspace\op\node_modules\buffer\index.js
  Used by 2 module(s), i. e.
  C:\Users\Public\workspace\op\node_modules\load-bmfont\browser.js
  @ ../OP/node_modules/buffer/index.js
  @ ./node_modules/buffer-equal/index.js
  @ ./node_modules/load-bmfont/lib/is-binary.js
  @ ./node_modules/load-bmfont/browser.js
  @ ./src/effects/performer/DataTags.js
  @ ./src/effects/performer/index.js
  @ ./src/performers/Performer.js
  @ ./src/performers/Performers.js
  @ ./src/react/pages/Main.jsx
  @ ./src/index.jsx
  @ multi ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only-dev-server ./src/index.jsx

WARNING in ../OP/node_modules/html-entities/index.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\Public\workspace\OP\node_modules\html-entities\index.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\OP\node_modules\webpack-dev-server\client\overlay.js
• C:\Users\Public\workspace\op\node_modules\html-entities\index.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\op\node_modules\webpack-dev-server\client\overlay.js
  @ ../OP/node_modules/html-entities/index.js
  @ ../OP/node_modules/webpack-dev-server/client/overlay.js
  @ ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080
  @ multi ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only-dev-server ./src/index.jsx

WARNING in ../OP/node_modules/html-entities/lib/html4-entities.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\Public\workspace\OP\node_modules\html-entities\lib\html4-entities.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\OP\node_modules\html-entities\index.js
• C:\Users\Public\workspace\op\node_modules\html-entities\lib\html4-entities.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\op\node_modules\html-entities\index.js
  @ ../OP/node_modules/html-entities/lib/html4-entities.js
  @ ../OP/node_modules/html-entities/index.js
  @ ../OP/node_modules/webpack-dev-server/client/overlay.js
  @ ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080
  @ multi ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only-dev-server ./src/index.jsx

WARNING in ../OP/node_modules/html-entities/lib/html5-entities.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\Public\workspace\OP\node_modules\html-entities\lib\html5-entities.js
  Used by 2 module(s), i. e.
  C:\Users\Public\workspace\OP\node_modules\html-entities\index.js
• C:\Users\Public\workspace\op\node_modules\html-entities\lib\html5-entities.js
  Used by 2 module(s), i. e.
  C:\Users\Public\workspace\op\node_modules\html-entities\index.js
  @ ../OP/node_modules/html-entities/lib/html5-entities.js
  @ ../OP/node_modules/html-entities/index.js
  @ ../OP/node_modules/webpack-dev-server/client/overlay.js
  @ ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080
  @ multi ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only-dev-server ./src/index.jsx

WARNING in ../OP/node_modules/html-entities/lib/xml-entities.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\Public\workspace\OP\node_modules\html-entities\lib\xml-entities.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\OP\node_modules\html-entities\index.js
• C:\Users\Public\workspace\op\node_modules\html-entities\lib\xml-entities.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\op\node_modules\html-entities\index.js
  @ ../OP/node_modules/html-entities/lib/xml-entities.js
  @ ../OP/node_modules/html-entities/index.js
  @ ../OP/node_modules/webpack-dev-server/client/overlay.js
  @ ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080
  @ multi ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only-dev-server ./src/index.jsx

WARNING in ../OP/node_modules/ieee754/index.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\Public\workspace\OP\node_modules\ieee754\index.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\OP\node_modules\buffer\index.js
• C:\Users\Public\workspace\op\node_modules\ieee754\index.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\op\node_modules\buffer\index.js
  @ ../OP/node_modules/ieee754/index.js
  @ ../OP/node_modules/buffer/index.js
  @ ./node_modules/buffer-equal/index.js
  @ ./node_modules/load-bmfont/lib/is-binary.js
  @ ./node_modules/load-bmfont/browser.js
  @ ./src/effects/performer/DataTags.js
  @ ./src/effects/performer/index.js
  @ ./src/performers/Performer.js
  @ ./src/performers/Performers.js
  @ ./src/react/pages/Main.jsx
  @ ./src/index.jsx
  @ multi ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only-dev-server ./src/index.jsx

WARNING in ../OP/node_modules/isarray/index.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\Public\workspace\OP\node_modules\isarray\index.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\OP\node_modules\buffer\index.js
• C:\Users\Public\workspace\op\node_modules\isarray\index.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\op\node_modules\buffer\index.js
  @ ../OP/node_modules/isarray/index.js
  @ ../OP/node_modules/buffer/index.js
  @ ./node_modules/buffer-equal/index.js
  @ ./node_modules/load-bmfont/lib/is-binary.js
  @ ./node_modules/load-bmfont/browser.js
  @ ./src/effects/performer/DataTags.js
  @ ./src/effects/performer/index.js
  @ ./src/performers/Performer.js
  @ ./src/performers/Performers.js
  @ ./src/react/pages/Main.jsx
  @ ./src/index.jsx
  @ multi ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only-dev-server ./src/index.jsx

WARNING in ../OP/node_modules/loglevel/lib/loglevel.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\Public\workspace\OP\node_modules\loglevel\lib\loglevel.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\OP\node_modules\webpack-dev-server\client\index.js?http://0.0.0.0:8080
• C:\Users\Public\workspace\op\node_modules\loglevel\lib\loglevel.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\op\node_modules\webpack-dev-server\client\index.js?http://0.0.0.0:8080
  @ ../OP/node_modules/loglevel/lib/loglevel.js
  @ ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080
  @ multi ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only-dev-server ./src/index.jsx

WARNING in ../OP/node_modules/process/browser.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\Public\workspace\OP\node_modules\process\browser.js
  Used by 2 module(s), i. e.
  C:\Users\Public\workspace\OP\node_modules\util\util.js
• C:\Users\Public\workspace\op\node_modules\process\browser.js
  Used by 32 module(s), i. e.
  C:\Users\Public\workspace\op\node_modules\react-hot-loader\lib\patch.js
  @ ../OP/node_modules/process/browser.js
  @ ../OP/node_modules/util/util.js
  @ ./node_modules/node-neurosky/node-neurosky.js
  @ ./src/inputs/types/NeuroSky.js
  @ ./src/inputs/types ^./.*$
  @ ./src/inputs/index.js
  @ ./src/react/pages/Main.jsx
  @ ./src/index.jsx
  @ multi ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only-dev-server ./src/index.jsx

WARNING in ../OP/node_modules/sockjs-client/dist/sockjs.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\Public\workspace\OP\node_modules\sockjs-client\dist\sockjs.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\OP\node_modules\webpack-dev-server\client\socket.js
• C:\Users\Public\workspace\op\node_modules\sockjs-client\dist\sockjs.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\op\node_modules\webpack-dev-server\client\socket.js
  @ ../OP/node_modules/sockjs-client/dist/sockjs.js
  @ ../OP/node_modules/webpack-dev-server/client/socket.js
  @ ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080
  @ multi ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only-dev-server ./src/index.jsx

WARNING in ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\Public\workspace\OP\node_modules\webpack-dev-server\client\index.js?http://0.0.0.0:8080
  Used by 1 module(s), i. e.
  multi C:\Users\Public\workspace\OP\node_modules\webpack-dev-server\client\index.js?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only- dev-server ./src/index.jsx
• C:\Users\Public\workspace\op\node_modules\webpack-dev-server\client\index.js?http://0.0.0.0:8080
  Used by 1 module(s), i. e.
  multi C:\Users\Public\workspace\OP\node_modules\webpack-dev-server\client\index.js?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only- dev-server ./src/index.jsx
  @ ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080
  @ multi ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only-dev-server ./src/index.jsx

WARNING in ../OP/node_modules/webpack-dev-server/client/overlay.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\Public\workspace\OP\node_modules\webpack-dev-server\client\overlay.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\OP\node_modules\webpack-dev-server\client\index.js?http://0.0.0.0:8080
• C:\Users\Public\workspace\op\node_modules\webpack-dev-server\client\overlay.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\op\node_modules\webpack-dev-server\client\index.js?http://0.0.0.0:8080
  @ ../OP/node_modules/webpack-dev-server/client/overlay.js
  @ ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080
  @ multi ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only-dev-server ./src/index.jsx

WARNING in ../OP/node_modules/webpack-dev-server/client/socket.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\Public\workspace\OP\node_modules\webpack-dev-server\client\socket.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\OP\node_modules\webpack-dev-server\client\index.js?http://0.0.0.0:8080
• C:\Users\Public\workspace\op\node_modules\webpack-dev-server\client\socket.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\op\node_modules\webpack-dev-server\client\index.js?http://0.0.0.0:8080
  @ ../OP/node_modules/webpack-dev-server/client/socket.js
  @ ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080
  @ multi ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only-dev-server ./src/index.jsx

WARNING in ../OP/node_modules/webpack-dev-server/node_modules/ansi-regex/index.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\Public\workspace\OP\node_modules\webpack-dev-server\node_modules\ansi-regex\index.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\OP\node_modules\webpack-dev-server\node_modules\strip-ansi\index.js
• C:\Users\Public\workspace\op\node_modules\webpack-dev-server\node_modules\ansi-regex\index.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\op\node_modules\webpack-dev-server\node_modules\strip-ansi\index.js
  @ ../OP/node_modules/webpack-dev-server/node_modules/ansi-regex/index.js
  @ ../OP/node_modules/webpack-dev-server/node_modules/strip-ansi/index.js
  @ ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080
  @ multi ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only-dev-server ./src/index.jsx

WARNING in ../OP/node_modules/webpack-dev-server/node_modules/strip-ansi/index.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\Public\workspace\OP\node_modules\webpack-dev-server\node_modules\strip-ansi\index.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\OP\node_modules\webpack-dev-server\client\index.js?http://0.0.0.0:8080
• C:\Users\Public\workspace\op\node_modules\webpack-dev-server\node_modules\strip-ansi\index.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\op\node_modules\webpack-dev-server\client\index.js?http://0.0.0.0:8080
  @ ../OP/node_modules/webpack-dev-server/node_modules/strip-ansi/index.js
  @ ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080
  @ multi ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only-dev-server ./src/index.jsx

WARNING in ../OP/node_modules/webpack/buildin/global.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\Public\workspace\OP\node_modules\webpack\buildin\global.js
  Used by 4 module(s), i. e.
  C:\Users\Public\workspace\OP\node_modules\punycode\punycode.js
• C:\Users\Public\workspace\op\node_modules\webpack\buildin\global.js
  Used by 9 module(s), i. e.
  C:\Users\Public\workspace\op\node_modules\sockjs-client\dist\sockjs.js
  @ ../OP/node_modules/webpack/buildin/global.js
  @ ../OP/node_modules/punycode/punycode.js
  @ ../OP/node_modules/url/url.js
  @ ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080
  @ multi ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only-dev-server ./src/index.jsx

WARNING in ../OP/node_modules/webpack/buildin/module.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\Public\workspace\OP\node_modules\webpack\buildin\module.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\OP\node_modules\punycode\punycode.js
• C:\Users\Public\workspace\op\node_modules\webpack\buildin\module.js
  Used by 7 module(s), i. e.
  C:\Users\Public\workspace\op\node_modules\lodash\lodash.js
  @ ../OP/node_modules/webpack/buildin/module.js
  @ ../OP/node_modules/punycode/punycode.js
  @ ../OP/node_modules/url/url.js
  @ ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080
  @ multi ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only-dev-server ./src/index.jsx

WARNING in ../OP/node_modules/webpack/hot nonrecursive ^./log$
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\Public\workspace\OP\node_modules\webpack\hot nonrecursive /^./log$/
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\OP\node_modules\webpack-dev-server\client\index.js?http://0.0.0.0:8080
• C:\Users\Public\workspace\op\node_modules\webpack\hot nonrecursive /^./log$/
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\op\node_modules\webpack-dev-server\client\index.js?http://0.0.0.0:8080
  @ ../OP/node_modules/webpack/hot nonrecursive ^./log$
  @ ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080
  @ multi ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only-dev-server ./src/index.jsx

WARNING in ../OP/node_modules/webpack/hot/emitter.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\Public\workspace\OP\node_modules\webpack\hot\emitter.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\OP\node_modules\webpack-dev-server\client\index.js?http://0.0.0.0:8080
• C:\Users\Public\workspace\op\node_modules\webpack\hot\emitter.js
  Used by 3 module(s), i. e.
  C:\Users\Public\workspace\op\node_modules\webpack\hot\dev-server.js
  @ ../OP/node_modules/webpack/hot/emitter.js
  @ ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080
  @ multi ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only-dev-server ./src/index.jsx

WARNING in ../OP/node_modules/webpack/hot/log.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\Public\workspace\OP\node_modules\webpack\hot\log.js
  Used by 1 module(s), i. e.
  C:\Users\Public\workspace\OP\node_modules\webpack\hot nonrecursive /^./log$/
• C:\Users\Public\workspace\op\node_modules\webpack\hot\log.js
  Used by 4 module(s), i. e.
  C:\Users\Public\workspace\op\node_modules\webpack\hot\dev-server.js
  @ ../OP/node_modules/webpack/hot/log.js
  @ ../OP/node_modules/webpack/hot nonrecursive ^./log$
  @ ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080
  @ multi ../OP/node_modules/webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/dev-server react-hot-loader/patch webpack-dev-server/client?http://0.0.0.0:8080 webpack/hot/only-dev-server ./src/index.jsx`

These look scary and make people sad.
Another time, it failed to load BVH files, but I can't repro this.

2. The output doesn't say, "Start ur browser!" at the end, but should.
3. You can't drag BVH files from the left to the right side in the Welcome to OP modal.
4. You apparently can't drag BVH files from another directory even though it says you can.
   4.1 Actually, you can, it just doesn't do any GUI stuff.
5. Antimalware Service Executable wastes valuable CPU. How to open these localhost ports?
6. Output doesn't actually say, "Your app is running on port 8080."
7. The links in README saying "open http://localhost:8080" should open a new window.
8. In my new version (downloaded after config.js was removed), npm run start works but npm run dev doesn't. Output looks normal, but Firefox reports only "Waiting for localhost..."
   8.1 Confirmed old version works.

####################
DOING STUFF
####################

1. A little random but, search for "BVH" and the first thing you'll see is the CMU BVH repo. What kinda bones are they using? Are they "good for" OpenPerform?
   1.1 What other BVH utilities exist?
   1.2 Maybe link to PN documentation of bones hierarchy?
2. The files "Duality Edit" and "Sean Edit" and "Wei Edit" and "Movie-1 1" do not exist (post-config.js-removal repo).
   2.1 The files shouldn't say "Edit."
3. There is a split-second weird white mesh person before a file loads.
4. Without messing with other settings, I can load 8 performers easily. There might be memory leaks related to UI bugs.
5. Controls: These could use some redaction.

• very powerful in theory.
• on the bottom, in Performers, we have:
  Play/pause
  Stop
  Ghostbusters "no ghosts" No sign/Reload sign.
  Track (Camera icon)
  Name (Performer #) <-this should be the name of the file.
  Source <- why do these ALL say BVH?
  Translate <- maybe rethink this
  Style
  Effect
  Clone

In the hotkey menu, we have:

DEFAULT
esc | Hide / Show Keyboard Shortcuts

• | Toggle GUI
  = | Toggle Fullscreen
  l | Tracking Camera - Low Angle
  c | Vogue Clone
  q | Randomize All Mesh Scale
  w | Random Limb Scale
  n | Detach Left Arm
  m | Detach Right Arm
  , | Detach Left Leg
  . | Detach Right Leg
  / | Detach Head
  space | Toggle Floor
  r | Rotate Camera
  e | Fly Wide
  g | Snorry Cam
  f | First Person
  t | Track Performer
  y | Top View
  u | 3/4 View
  i | Fly Out
  left | Fly Out
  up | Fly Out
  right | Fly Out
  down | Fly Out

DUALITY
esc | Hide / Show Keyboard Shortcuts

• | Toggle GUI
  = | Toggle Fullscreen

MESH COMBUSTIBLE
esc | Hide / Show Keyboard Shortcuts

• | Toggle GUI
  = | Toggle Fullscreen
  l | low track
  ; | zoom out
  ' | zoom in
  q | randomize limb scale
  w | randomize limb scale
  space | Hide Floor
  n | Unparent
  m | Unparent
  , | Unparent
  . | Unparent
  / | Unparent

MESH FRESH FEST
esc | Hide / Show Keyboard Shortcuts

• | Toggle GUI
  = | Toggle Fullscreen
  l | Tracking - Low Angle
  ; | Tracking - Zoom Out
  ????? Tracking - Zoom In
  q | Randomize All Mesh Scale
  w | Random Limb Scale
  ????? space
  ????? Toggle Floor
  n | Detach Left Arm
  m | Detach Right Arm
  , | Detach Left Leg
  . | Detach Right Leg
  / | Detach Head

NEW DEFAULT
esc | Hide / Show Keyboard Shortcuts

• | Toggle GUI
  = | Toggle Fullscreen

TRANSFORM WORK
esc | Hide / Show Keyboard Shortcuts

• | Toggle GUI
  = | Toggle Fullscreen
  ` | Switch to Default scene.
  1 | Switch to 1st scene.
  2 | Switch to 2nd scene.
  3 | Switch to 3rd scene.
  4 | Switch to 4th scene.
  5 | Switch to 5th scene.
  6 | Switch to 6th scene.
  7 | Switch to 7th scene.
  8 | Switch to 8th scene.
  9 | Switch to 9th scene.
  0 | Switch to 10th scene.
  l | Tracking Camera - Low Angle
  c | Vogue Clone
  q | Randomize All Mesh Scale
  w | Random Limb Scale
  n | Detach Left Arm
  m | Detach Right Arm
  , | Detach Left Leg
  . | Detach Right Leg
  / | Detach Head
  ????? space
  Show Overlay
  r | Rotate Camera
  q | Fly Close
  w | Fly Medium
  e | Fly Wide
  g | Snorry Cam
  f | First Person
  t | Track Performer
  y | Top View
  u | 3/4 View
  i | Fly Out
  left | Previous Colors
  right | Next Colors

(continuing on:)

• however, only the following actually matter:
  (NOTES TO THIS SECTION)
  (????? means it was blank)
  (dupes were omitted)
  (not all combinations were tested)
  (the idea of "unparenting" is cool, btw)

DEFAULT
esc | Hide / Show Keyboard Shortcuts <- works

• | Toggle GUI <- works
  = | Toggle Fullscreen <- works
  l | Tracking Camera - Low Angle <- works
  c | Vogue Clone <-- doesn't work
  q | Randomize All Mesh Scale <- works, but can't be undone
  w | Random Limb Scale <- works, but can't be undone
  n | Detach Left Arm <- ditto
  m | Detach Right Arm <- ditto
  , | Detach Left Leg <- ditto
  . | Detach Right Leg <- ditto
  / | Detach Head <- ditto, and I want the above 7 to be do-able for clones as well!!!
  space | Toggle Floor <- works
  r | Rotate Camera <- works, but only goes a few degrees, then waits, then works
  e | Fly Wide <- works
  g | Snorry Cam <- works, but (e) and (t) can't "get out" of it. (y) can, for some reason.
  f | First Person <- works
  t | Track Performer <- works
  y | Top View <- works
  u | 3/4 View <- doesn't work
  i | Fly Out <- freezes everything
  left | Fly Out <- moves clones only
  up | Fly Out <- moves clones only, not correctly
  right | Fly Out <- moves clones only, not correctly
  down | Fly Out <- moves clones only, not correctly
  ; | zoom out <- doesn't work (WOULD BE NICE)
  ' | zoom in <- doesn't work (WOULD BE NICE)

MESH FRESH FEST
????? Tracking - Zoom In
????? space
????? Toggle Floor

TRANSFORM WORK
1 | Switch to 1st scene.
2 | Switch to 2nd scene.
3 | Switch to 3rd scene. <- only this one works
4 | Switch to 4th scene. <- first clone starts here
5 | Switch to 5th scene. ... if you keep messing with it, it gets weird
6 | Switch to 6th scene. ... i don't know enough to describe better.
7 | Switch to 7th scene.
8 | Switch to 8th scene.
9 | Switch to 9th scene.
0 | Switch to 10th scene.
...
????? space
????? Show Overlay
...
left | Previous Colors <- doesn't seem to do anything
right | Next Colors <- doesn't seem to do anything

• NOTE: sometimes using controls makes the "Quick Links" open in Firefox.

6. Tooltips. WHERE ARE MY DAMN TOOLTIPS :D :D :D
7. Arrow keys should fly me around.
8. Space bar for grid, right click to translate and left click to rotate should be documented.
9. Inputs in I/O in upper-left says: "I Phone X." Correct nomenclature is "iPhone X." (Note: might be improper bmfont rendering!)
10. Outputs in '': should say "nothing to output to" if there isn't anything to output to.
11. Please have a reload button where we can reload without clicking the refresh button and without choosing BVH file again.

ENVIRONMENT:

1. Going to Water and then changing again makes the world white.
2. Going to Forest doesn't work.
3. Clicking Grid when in Grid make the world and avatar black.
4. Background color:

• the black box when first clicking the paintbrush doesn't change.
• clicking anywhere on the modal but off the controls should NOT make it disappear.
• changing the upper slider then clicking the gradient box zone makes it disappear.
• the lower slider refuses to change and makes it disappear
• the upper slider works :)

5. Empty is itself empty.
6. The label for the picklist doesn't change when it is changed.

ENTER VR

1. All reality is virtual reality, but is this the totally Zen point of the Enter VR button doing nothing?
2. The mouse no longer operates on the world space after clicking this button.

CAMERA CONTROLS

1. For some reason, I find this button hard to find.
2. Cut: 3/4 doesn't work.
3. First person is unstable. Should it map to the chest, not the head, or to the chest plus some weighted/lagged movement from the head?
4. Doing Track -> Peformer 1 -> Cut -> Medium doesn't "reset" the picklist of Track (but does revert the camera to stationary).

PERFORMERS

1. Why isn't there a temporal time ticker going by, like in Ableton?
2. Past 8 clones, the Perfomers control area goes beyond the edge of the screen. Scroll bar?
3. Make a clone. Translate to 0,0,0. How to know they're on top of each other?
4. Related: Clicking a performer's name should make them flash.
5. Style: Geometry: Hands makes the app halt. Including the debug window. CPU doesn't spike, however.

• same goes for heads.

6. Style: Geometry: [anything] and then return to default refuses to return to default.
7. Effect has the same problem as Environment in lower-right, with color selection and modal.
8. Clones are unstyled. This is fine, but there should be a way to replicate style clones.
9. Effect: Ghosting: Maxing out clone rate seems to make ghosting stop.
10. Effect: Particles: Most of these variables stack, and should be scaled down/together somehow. (Going above 1.5 is basically crazy.)
11. Effect: Data tags: Can these be tracked, via Camera Controls? So that the label never moves.
12. Effect: Can inter-joint distances be selected? I.e., skeletal parameters? Like that one ballet video.
13. Effect: Movement Sculpture: This is absolutely amazing.
    13.1 Effect: Movement Sculpture: Can there be a way to clear them, though?
    13.2 Effect: Movement Sculpture: Maxing out the variables produced around 7 after a single test, not 25. There appear to be duplicated vertices.
14. Control: Weird ghostbusters sign: What does this do? What does the Restart looping arrow mean?
15. Control: Stop vs Pause: What is the difference (in terms of intended functionality)? I can see how they're different, but why? Just curious.
16. Control: Stop: The basic T-pose seems to have missing joints.

Otherwise, seems to work flawlessly!
:D