Data Overlay Configuration - What's the trick? Or is this a bug?

[Candive]

Using RR 3.6.5. When you import a data log file into a project, RR3 opens up to a selection to data templates. When you select one, another window opens, allowing you to select the gauges you require from the template. Fantastic! The problem is, when I create my own data template and use it, it doesn't come up with the same type of data overlay configuration selection. Although gauges are missing, all of the are added to the project. Am I missing a step in the creation process, or is this a bug?

[Weston@HPTuners]

It sounds like this is just a display object naming issue with the custom template. It's looking for display objects matching certain names to know if it should show a checkbox for certain categories. Here are the names it currently looks for...

Speedometer

    "Speedometer",	// SpeedMax will be applied to this
	"Speed",		// SpeedMax will be applied to this
	"Speed Graph",		// SpeedMax will be applied to this
	"Speed Graphs",
	"Max Speed",
    "Top Speed",
	"Peak Speed",
	"Peak+Base Speed",
	"Peak Base Speed",
	"Speed Max",
	"Speed Peak",
	"Speed Peak+Base",
	"Speed Peak Base",
	"Speed Background",	// SpeedMax will be applied to this
    "Speed Display",
	"Speed Text",

Tachometer

    "Tachometer",	// TachMax & TachRed will be applied to this
	"Tach",			// TachMax & TachRed will be applied to this
    "Tach Background",	// TachMax & TachRed will be applied to this
    "Tach Display",
	"Tach Text",

Shift Light

	"Shift Light",	// TachMax & TachRed will be applied to this
	"Shift Lights",	// TachMax & TachRed will be applied to this

Gear Indicator

    "Gear",
    "Gear Knob",
    "Gear Background",
    "Gear Display",
	"Gear Text",

Throttle Position

	"Throttle",
	"Throttle Background",
	"Throttle Display",
	"Throttle Text",

Brake

	"Brake",
	"Brake Background",
	"Brake Display",
	"Brake Text",

Air/Fuel

	"Air/Fuel",
	"Air/Fuel Background",
	"Air/Fuel Display",
	"Air/Fuel Text",
	"AFR",
	"AFR Background",
	"AFR Display",
	"AFR Text",

Engine Power

	"Power",	// PowerMax will be applied to this
	"Power Plot",	// PowerMax will be applied to this
	"Power Gauge",	// PowerMax will be applied to this
	"Power Background",	// PowerMax will be applied to this
	"Power Display",
	"Power Text",
	"Horsepower",
	"Horsepower Background",
	"Horsepower Display",
	"Horsepower Text",

Engine Torque

	"Torque",	// TorqueMax will be applied to this
	"Torque Plot",	// TorqueMax will be applied to this
	"Torque Gauge",	// TorqueMax will be applied to this
	"Torque Background",	// TorqueMax will be applied to this
	"Torque Display",
	"Torque Text",

G-Force

	"G-Force",
	"G-Force Peak",
	"Peak G-Force",
	"Peak G",
	"G-Force Graph",
	"G-Force Background",
	"G-Force Display",
	"G-Force Text",

Track Map

	"Track Map",
	"Combined Track Map",
	"Map",
	"Map Background",
	"Map Display",

Altitude

	"Altitude",
	"Altitude Min",
	"Altitude Max",
	"Altitude Climb",
	"Altitude Display",
	"Altitude Text",
	"Elevation",
	"Elevation Display",

Lap Number

    "Lap Number",
    "Lap Number Display",

Lap Time

    "Lap Time",
    "Lap Time Display",
	"Lap Timer",

Lap Number / Time Combo

    "Lap",
    "Lap Background",
    "Lap Display",
    "Lap List",

Best Lap

    "Best Lap Number",	// Best-Lap-So-Far vs Best-Lap-Overall logic will be applied to this
    "Best Lap Time",	// Best-Lap-So-Far vs Best-Lap-Overall logic will be applied to this
    "Best Lap Background",
    "Best Lap Display",

[Candive]

Got it, thanks for the info. Obviously RaceRender's heritage is car racing and hence the automobile references. I get it. But this program has so much more potential; skiing, cycling, trekking/mountain climbing, sky diving, drones, and I am using it for scuba diving. Each of these sports have their own lingo and I'm not expecting you to populate your database with different naming conventions. It could get pretty big and ugly if you start taking different languages into consideration as well. Its a limitation but not a showstopper because one can easily delete any gauge once the template is applied to a project. Obviously the above list works for the default templates you created for the system which is fine. Now that I understand how it works, I'm happy. Thanks again for providing an explanation.