For v0.9.3

[DavidGoedicke]

Open Issues:

• Speed limits in GPS: CP 50 kmh/30mph, NS/NIS 80kmh/50mph @HaukeCornell
• QUestionnaire trigger stopes working after a while.

Issues until 2022/31/5:

• Rerun no light in cabin (was fixed once by placing additional light source in vehicle)
• Questionnaire sometimes (CP1-CP3) is tiny and too small to select anything.
• Intersection GPS trigger are too close behind the TL @HaukeCornell
• SA Q trigger are too far at the end of the intersection road @HaukeCornell
• TL instructions for NI are missing @HaukeCornell

Needed improvements

• Location photos in the questionnaire @HaukeCornell

Bugs that mysteriously vanished:

• Rerun shows wrong or duplicate visual scenes (CP2, CP6, NI1, NI2, NSI1, NSI2)

New Fices (5/12/2022):

• Hebrew inconsistent reversing and line breaks (Please I need help fixing this!)
• In the client the display of the "current question/ total questions" shows a total of zero in all scenarios.
• On the server-side, the same display shows the current question count which I don't understand where this number came from. Like 72/14 for NSI2-5 (Related to the previous question and should be solved)
• The scenario timer on the server-side should stop the moment the participants switched to the waiting room
• Is it possible to have some sort of indication (like a change of color) for scenarios already visited?

New Fixes(4/26/2022):

• Add Timer to the Server screen
• Change Steering Wheel calibration to the "10 and 2 position"
• Add Question Number to the Server QN info
• PairName TextBox not correctly working. ( cannot enter any name)
• Question out of the total question on the server-side display
• Add a screenshot ( well ok its implemented, but not tested at all; well I guess I want feedback)
• Partially conditional questionnaire (follow up question suppression)
• Move the questionnaire in front of the steering wheel
• Move the mirror up a little
• Fix timestamps

Fixes(4/12/2022):

• Engine sound hearable without any distance attenuation ( i need help with testing. trouble replicating it )
• Reverse Option R for Driving (We will not implement this)
• (ReRun) Recording Vehicle sound (Only wind sounds are recorded no engine sounds)
• New Server Interface
• Update QN trigger to instruct the participant to stop.
• FixTrafficLights (Red=>green)
• Break lights are not shared across the network.
• (ReRun) Horn Recording
• PleaseWait Screen at the end of a participant
• ResearchersInfo on the Questionnaire state
• GoBack Button for the questionnaire ( We are only retaining the "FINAL" answer from the participant)
• increase center mirror height
• Show scenario ID.
• TotalQuestionCount For the Participant.
• Faulty initial camera orientations for Camera FOUR @HaukeCornell You mentioned this is fixed for now?
• Add stopping line for all scenarios
• Check if the Horn works
• Brake the car when entering the SA trigger box
• Make the participants stop at the end of the scenario @HaukeCornell
• Skin color yellow or blue

Fixes:

• Hebrew Support (untested)
• Increased the height off the Questionnaire up:(1.5m => 2m up) forward:(4.5m=>4.25m)
• Increase FoV for ReRun
• NS1 fix trigger box @HaukeCornell
• Invisible border around the world
• NI1 (change GPS potentially)
• Add scenario name to the server screen

Ground Truth:

• Used signaling(bool)
• Used horn (bool)
• Signaling light (array of directions)
• Speed range
• Speed variance
• Used breaks (bool)
• Lane location (array of locations for each car, in case there is a change)
• Lane change (bool)
• Total scenario time
• Used Headlight Lights (bool) We dont have headlights
• Horn type (momentary / continues – array in case of more than one) Is in the quantitative data

Needed Features:

• Log files with all the quantity data
• Extra data (ground truth in the SA-Q log file)
• Traffic light implementation
• (ReRun) Addative loading of the Visual Scene [Implemented and initial tests.(needs more testing)]
• Counter balanced versions for all "NI" and "NSI" scenarios @HaukeCornell
• NSI needs a split road(different visuals @HaukeCornell
• NI1 there is no need for any other GPS instruction except for go straight
• NI1 We can place the SA-Q trigger sooner (fixed)
• NSI1 missing trigger box for the SA-Q and this is way one of the participant went over the edge.
• NSI2 There was no sync between the drivers. Car B pass before A had a chance to merge
• NSI2 There is a GPS instruction to go to the signal light, but I’m not sure there is one
• SA-Q CP – add to all question the answer “There was no other driver”

Hard to fix problems(will Not Fix for now):

• (ReRun) Recording and Playaback TrafficLight Integration

Nice To Have:

• On the server show the current IP for easy connection.
• Auto-Connect Quest headset (10sec. timer) @HaukeCornell could you take a look at this.
• IP-input field not working on first startup (VR-UI). @HaukeCornell
• Auto-Recenter on launch (Implications for user manual)

Adjustments (no coding required):

• Street height matches terrain height (new intersection)
• Rear view mirror position (too low)
• reduce scene complexity >70fps is a must @HaukeCornell

Testing and Improvments:

• Full Performance assessment (2+participants) (Quest)
• Full Performance assessment (2+participants) (Server)
• disable VR for windows builds

Issues that appeared in user testing:

Fixed Issues:

• necessary to see the users, and their perspective (using the rerun camera rig during server view)
• (ReRun) No Hand Gesture recording
• (ReRun) No signaling light recording
• Spawning and hidding the QN on sceneload (makes the scenario-end less jaring)
• QuestApp Shutdown on disconnect (when the Server exits or crashes)
• Speedometer Integration
• TrafficLight Integration
• Basic Performance assessment (1 participant)(Quest)

Fixes:

• World Designs and two-player scenarios
• (ReRun) Recording and Playaback Speedometer Integration
• Questionnaire Data recording and Serverside Storage
• Questionnaire Button input (Implement onButtonUp)
• Properly name and build the Quest app
• Physical steering wheel rotation matches virtually

ReRun

• Implement Automatic scene recording
• Automatic naming
• PlayBack Automatic Scene Loading
• PlayBack control
• Verify: Body Pose and Care pose recording
• Verify playback (Especially in server builds

Next Steps:

• Synchronized Actions (Software interface?) (e.g. traffic lights)
• CSV exporter?
• 4 Player setup?

---

Fixed

• StartUp GUI connect to the actual program.
• Automatically instantiate RenderTextures for each vehicle Camera Manager (MonoBehavior) on the client and server-side.
• Calibrate participant position
• Implement the Questionnaire.

Finished features

• Associate Steering wheel to participants (Setup) (Untested)
• Associate Steering wheel to participants (Runtime)
• Hand Gesture sharing?
• ReRun Recording controls (automatic recording start)
• Speedometer
• Add a speedometer to the car

[DavidGoedicke]

Other issues metioned befor:

Hauke:
Xcultural VR platform tests, issues

A:

• Wears glasses
• Struggles to fit glasses under HMD, puts down glasses for tests
• Unity accidentally closed after putting on headset (needs to put up again)
• Struggles to find the pedals, drives of the road and needs to restart the scene again
• Calibration did not work properly (hand tracking issues while holding the steering wheel, instructor did not know if calibration was good without a way to check)
• Stopped due to dizziness

B:

• Wears glasses
• Calibration crashes a few times, once head rotation reset on quest it works
• Test goes well
• Feels dizzy after driving
• Drove past the red traffic lights
• Says that the lack of grass made it feel unrealistic:
• "It's nice I can do whatever I want here"
• "Encounter with the other car felt a bit more real though"
• ''Head position from other driver A is offset from the perspective B (outside the car)'
• Avatar shifts during driving (drove many rounds and at the end the other participants avatar appears outside of the vehicle (while first person view still was from within the vehicle)

C:

• Drives past the traffic light
• After some driving her avatar disappeared
• Reports to feel dizzy

D:

• Wears glasses without issues
• Steering wheel somehow did not work on one USB port
• Calibration crashed
• Unity froze when starting server (2x)

Navit:
Test issues:

A:

• Light motion sickness. Since the scenario is very short he didn't have a chance to get acquainted with the environment.
• Something about the driving doesn't feels natural, like a regular automatic vehicle.
• "When you take of the leg from the paddle you expect the car to slow down"
• The noise of the car is to load and doesn't relate to the car speed. It should be different based on the car speed.
• The steering wheel feel very stiff not like a regular steering wheel.
• There was a problem with the hand calibration. Tried it for several time and eventually did a restart to the server and it worked.
• It's hard to know what the participant sees and help him in case of a problem. We should have some sort of a view in the server application.

---

• Car behavior
• • Car doesn't feel as fast as it drives
• • Turning is a bit delay
• Rendering performance
  -- Player B is visual stutter like seeing things twice
• GPS triggers off car B influence also in Car A
• Logitech steering wheel on left side of the table can only drive full left turns
• When two steering wheels connected on start server, one turns to random position
• SA-QA JSON doesn't loads
• In practice world & NI1 the B car falls from the ground
• Difficulties set up
• • We need to connect both participant view to cast both headset at the same time
• Alternatively auto connect IP
• • way to remotely reset rotation
• The rerun doesn't show the visual world
• In VR IP UI the hand tracking is unstable on one quest
• Server window:
• • Car interior too dark
• • Top down view on intersection