Overlay Data Missing?

[suches]

I've got HLT Grand Prix. I recently upgraded from Petrolhead, because my laps didn't contain any data, just worked as a lap timer, and I hoped the upgrade would help. Now I've got data that shows on the charts, etc., but when I tried to overlay a video, I got "Master video ok, overlay data missing, reference PiP video not valid-excluded"

I would really appreciate some help on this from those more knowledgable.

[Harry]

[Moved to Using LapTimer]

Does the data show up for the same lap you try to overlay? To make sure, select the lap you want to generate an overlay for and scroll down to the Data Recording section. Check the number of fixes in row "Fixes" here. The number should be roughly the lap's number of seconds. Next, check your reference lap (it is shown in the above lap's details). Check if the reference's video and data look fine. Finally, check if the above lap's video looks fine.

- Harry

[suches]

I looked back at all my laps from yesterday. Some have data in the Data Recording section, and show the appropriate number of Fixes. Those without data either don't show the Data Recording section at all, or show:

GPS Sensor Internal@0.0 Hz
Fixes 1 (GPS, ACCEL)

I guess this means that the GPS wasn't working? This seems odd since the timer worked, and the GPS connected on other laps?

[Harry]

Yes, that means the GPS data is missing. Which GPS did you use? The internal or an external device? How have the recordings been triggered? Automatically or by pressing the start recording in Video View or elsewhere?

- Harry

[suches]

It's the internal Iphone 4S GPS. The laps and video were automatically triggered. The track is Atlanta Motorsports Park. It's worked fine in the past.

Thanks.

[Harry]

Please send a mail from LapTimer's using the Contact button (press the gray button on LapTimer's About screen) so I can check the configuration. You may send the lap showing 1 fix in addition, maybe I can see something. Finally, in Lap List, scroll to the end and select "Check Data".

Actually there are no known bugs in 17.1.2 that could create this situation. Sounds like an issue with the GPS.

- Harry