While testing, we saw that the blue car is not an event object but has activation triggers. While testing, I was crashing into the car because i did not overtake during the event itself. It's not a huge problem, since we still have a working event when we take the car out - but maybe we'll refine it, to have a more pressing event.

See title. When running the eyeValidation, the cross and the fixation dot is sometimes off. This is because of the origin Position set in SteamVR(When you basically calibrate VR). If you are not in the exact Position of Steam VR, the fixation dot and the cross are off, which looks very weird and feels confusing.

Workaround: if you encounter that problem, just do recalibration of SteamVR.

Potential Solution: The Cross might take the direction and position of the Participant into account.

There is a cololess car in the scenes. Somehow the material is missing. It's not that important, but would be cool to have that fixed at some point

There is a plane in the Eye tracking Scene. Make it got away 😸

In the main menu there an assertion exception from post processing

There is a trigger needed to slow down the car without affecting HUD.

Car 14 and 16 in the photo are almost always crashed as the participant's car passes by. Since they are physical how they exactly behave is not concrete so we get also the situation in the photo.

Solution: assigning them to a suitable activation trigger or removing the pylon that keeps car 14 and therefor 16 and then test.

Hey hey,

We found in the built version, that the terrain is showing immensly through the road. Actually, there weren't any pieces of roads visable. This needs to be fixed. Nora said, that it would be helpful, if you could finalize the roads on that.

@farbod69 we are not sure if we should keep a editable brnach as copy. But we need to finalize 2 Weeks before the event end.
Therefore we are proposing a hard finalization of the road network right now

Data saving in the training scene is missing. No Data is saved from the training scene. That should be fixed.

After re-spawning the blue car which is driving a bit further than the participant's car, disappears.

In Autobahn, there are activation triggers in the events. Relocate them, because they won't work if test subjects fails before going through these triggers. So move them forwards.

This still needs testing later on.

The first event in autobahn has no colliders on the railguards. So touching the railguards should be a fail, since it would wreck the car.

make the braking pedal more sensitive. Right now, a cow has to step on the pedal. Just multiply the input codewise.

Inconsistend marking of the car. We just saw that sometimes we have Box colliders, sometimes we have Mesh coliders.
We weren't really sure what to use, but for the sake of computational power, we would say the box colider is it.

In the Bike event, there is a blue Clio driving in front of the participant. And "POOF" all over sudden this car disappears, like it was never there. We would suggest to let the car turn.
ANNNNND since the car is part of the events, it should be marked and get demarked, when it's not part of the event anymore.
You can replicate that, when you don't fail the event and you don't take over the blue Clio.

Right now, we encountered a lot of dancing trees in all scenes. This means, that the billborads are dancing on the z axis.
We know, that the stolen code for the shader might be a bit problematic, but there has to be a way to lock these on the x and z axis.

The second and third events in country road at some points don't have colliders on the guardrails. So touching the guardrails should be a fail, since it would wreck the car.

Apart from that, all the events should also cover the sides after the event for 1 second, since it is still manual driving. This is not the case in country road in the first event (see below)

which can lead to the situation below and car gets stuck there:

and in the third event:

Please move the re-spawn point of the first city event to after the event area since it might cause problems there.

The van is not marked and there is a collider on the side of the road which stopped the car.

"GoingAlongCars" game object is inactive in the hierarchy, thus throws error.

Solution: simply activate it

After passing the Ghost Driver event, this car disappears.

The self-drive time in the training scene is not long enough. I just tried to do that and I had only 3 seconds or so to drive by myself before the automated drive switched. Maybe you could try to have the automated drive first? I don't know yet, but for now this sees to be a bug.

The light doesn't make sense here :D

We got conflicting data from eye calibration and eye validation scenes. The position was off.

1. There was a null reference exception and LOD group missing from the Avatar 24 which is used in the first event as event object.

2. There is probably some component missing or the assignment for event objects are wrong in the third event. When the car hit the biker there's an outline exception

After changing the scene loading to the new system, the old system for input recording should have been adjusted.

This the new car which is interfering.

Solution: either moving it further or removing it or parking it somewhere.

We saw, that the railguards in the Motorbike event are not in the area of respawing.
I'd say, this is a crash and therefore we need colliders there.

Just shows the triangle but actually should be identical to the ActivateHUD() function without playing the audio

All events should be a variant of the events. If something goes wrong, this is way easier to fix

This happens when one fails in the training.

The guardrails on the right side of the road are not placed correctly.

Currently the terrain is showing in the Autobahn. Either these are floating currently, or the terrain is peaking through it.

The cyclist stays like this at end of its path. He could be adjusted so, that it doesn't go to the ground.

AIDrive icon and text are still there

In Westbrück, there is a sitting guy in the corner silently crying. Currently this guy is burried knee deep into the terrain. GIVE THIS MAN A BENCH TO CRY ON AND A PARTNER TO LISTEN. ;)

The Terrain, especially the mountains look weird in VR, they pop up and if we increase the clipping, we are using alot of computational power.

We thought, that we maybe just reduce the height, so that the participant look at some trees and then the skybox rather than on the high hills in the background

This is another test!

While testing we figured out, that there are patched of gras peeking through the road while driving on it. Also, this is not a big issue, but somehow makes the scene a bit invalid.

This is a test!