Martin Ridgers 889b2d647c Implementation of Trace's important events. Some events are only traced once. CPU scope names or log format strings for example. Those trace-once events get lost if a user then connects to trace late (or reconnects a second time). To combat that important events are traced to a separate stream internally so that they can be identified, cached off to one side, and resent when a connection is first established. ...

#rb johan.berg
#rnx

[CL 14572080 by Martin Ridgers in ue5-main branch]

2020-10-26 03:29:23 -04:00

..

Apple

Updating copyright for Engine Runtime.

2019-12-26 14:45:42 -05:00

Windows

Merge Release-Engine-Staging to Main @ CL# 14467590

2020-10-09 22:42:26 -04:00

ABTesting.cpp

Remove unused private fields - Automation

2020-09-02 09:24:31 -04:00

CookStats.cpp

Updating copyright for Engine Runtime.

2019-12-26 14:45:42 -05:00

CountersTrace.cpp

Implementation of Trace's important events. Some events are only traced once. CPU scope names or log format strings for example. Those trace-once events get lost if a user then connects to trace late (or reconnects a second time). To combat that important events are traced to a separate stream internally so that they can be identified, cached off to one side, and resent when a connection is first established.

2020-10-26 03:29:23 -04:00

CpuProfilerTrace.cpp

Implementation of Trace's important events. Some events are only traced once. CPU scope names or log format strings for example. Those trace-once events get lost if a user then connects to trace late (or reconnects a second time). To combat that important events are traced to a separate stream internally so that they can be identified, cached off to one side, and resent when a connection is first established.

2020-10-26 03:29:23 -04:00

CsvProfiler.cpp

Merging using //UE5/Main_to_//UE5/Release-Engine-Staging @14384769

2020-09-24 00:43:27 -04:00

CsvProfilerTrace.cpp

Implementation of Trace's important events. Some events are only traced once. CPU scope names or log format strings for example. Those trace-once events get lost if a user then connects to trace late (or reconnects a second time). To combat that important events are traced to a separate stream internally so that they can be identified, cached off to one side, and resent when a connection is first established.

2020-10-26 03:29:23 -04:00

ExternalProfiler.cpp

Updating copyright for Engine Runtime.

2019-12-26 14:45:42 -05:00

Histogram.cpp

Updating copyright for Engine Runtime.

2019-12-26 14:45:42 -05:00

InstanceCounter.cpp

Updating copyright for Engine Runtime.

2019-12-26 14:45:42 -05:00

LoadTimeTracker.cpp

Updating copyright for Engine Runtime.

2019-12-26 14:45:42 -05:00

MallocProfiler.cpp

Updating copyright for Engine Runtime.

2019-12-26 14:45:42 -05:00

MiscTrace.cpp

Implementation of Trace's important events. Some events are only traced once. CPU scope names or log format strings for example. Those trace-once events get lost if a user then connects to trace late (or reconnects a second time). To combat that important events are traced to a separate stream internally so that they can be identified, cached off to one side, and resent when a connection is first established.

2020-10-26 03:29:23 -04:00

PlatformFileTrace.cpp

Merging using //UE5/Main_to_//UE5/Release-Engine-Staging @14384769

2020-09-24 00:43:27 -04:00

ProfilingHelpers.cpp

Updating copyright for Engine Runtime.

2019-12-26 14:45:42 -05:00

ScopedDebugInfo.cpp

Updating copyright for Engine Runtime.

2019-12-26 14:45:42 -05:00

TraceAuxiliary.cpp

Implementation of Trace's important events. Some events are only traced once. CPU scope names or log format strings for example. Those trace-once events get lost if a user then connects to trace late (or reconnects a second time). To combat that important events are traced to a separate stream internally so that they can be identified, cached off to one side, and resent when a connection is first established.

2020-10-26 03:29:23 -04:00