Logs and Dump Reports

Owned by DEVOPS
Oct 05, 2021
3 min read

There are several kinds of information logs available from the Editor.

Scene and Shader Dumps

If you are experiencing problems with your scene data or shaders, you can save everything to a special dump file and send it to CM Labs support (support@cm-labs.com) for more help.

To save a dump file:

  • Select Dump SceneGraph or Dump Shaders from the Tools > Debug menu.

A file browser prompts you to choose a filename and location for the saved file.

Application Logs

The Vortex® Studio Editor creates application logs which contain messages, warnings and errors.

At the start of each session (when the Editor launches), the Editor creates a new log file in the system %Temp% directory, and writes constantly throughout the session to log information similar to the following:

Tue Jun 17 21:21:58 2014 VxInfo{0}: VxApplicationConfigSerializer: loading 'C:/CM Labs/Vortex Editor 6.2/bin/moduleConfig.vxc'.
Tue Jun 17 21:21:58 2014 VxInfo{0}: VxExtensionFactory: Registering Application.Dynamics Visualizer {47e1f87d-6f03-57c7-95b4-e9373299555b}.
Tue Jun 17 21:21:58 2014 VxInfo{0}: VxSimulatorModuleFactory: Registering VxGraphics.VxGraphicsModuleOSG {bf5b2902-675c-5b1d-b7f7-88d16c78db5a}.
Tue Jun 17 21:21:58 2014 VxInfo{0}: VxExtensionFactory: Registering Input Device.Joystick {f55e4c48-2b2e-5619-bbd5-1275cf033e33}.
Tue Jun 17 21:21:58 2014 VxInfo{0}: VxSimulatorModuleFactory: Registering Input Device.SDL Joystick {5a6272d9-7802-54ec-bb83-51669d3f1063}.
Tue Jun 17 21:21:58 2014 VxInfo{0}: VxExtensionFactory: Registering Earthwork Systems.Dynamics Zone {f0ff0862-49ff-5bef-8927-6e95bfb3952d}.
Tue Jun 17 21:21:58 2014 VxInfo{0}: VxExtensionFactory: Registering Earthwork Systems.Dynamics Soil Materials {e86206cc-60df-53e2-9d8b-32aa1b38294a}.
...
Wed Jun 18 10:45:12 2014 VxInfo{0}: Engine::setRpmAtMaxPower: Not Implemented
Wed Jun 18 10:45:12 2014 VxInfo{0}: Engine::setRpmAtMaxTorque: Not Implemented
Wed Jun 18 10:45:14 2014 VxWarning{0}: VxExtensionFactory: 'Scripting.IDynamics Python' has been updated to 'Scripting.Dynamics Python'. Make sure you are using the right ICD!
Wed Jun 18 10:45:14 2014 VxWarning{0}: VxExtensionFactory: 'Scripting.IDynamics Python' has been updated to 'Scripting.Dynamics Python'. Make sure you are using the right ICD!
Wed Jun 18 10:45:14 2014 VxWarning{0}: VxBaseReference: No path found for Chassis.
Wed Jun 18 10:45:14 2014 VxWarning{0}: VxPersistence::absolutePathToRelative: cannot find a relative path from 'C:/../CM Labs/Vortex Editor 6.1/resources/VehicleSystems/LAV_BTT.csv' to ''.
Wed Jun 18 10:45:14 2014 VxWarning{0}: VxPersistence::absolutePathToRelative: cannot find a relative path from 'C:/../CM Labs/Vortex Editor 6.1/resources/VehicleSystems/LAV_TT.csv' to ''.
Wed Jun 18 10:45:14 2014 VxWarning{0}: VxPersistence::relativePathToAbsolute: input path is already absolute: 'C:/../CM Labs/Vortex Editor 6.1/resources/VehicleSystems/LAV_BTT.csv'.
Wed Jun 18 10:45:14 2014 VxWarning{0}: VxPersistence::relativePathToAbsolute: input path is already absolute: 'C:/../CM Labs/Vortex Editor 6.1/resources/VehicleSystems/LAV_TT.csv'.
Wed Jun 18 10:45:14 2014 VxWarning{0}: VxBaseReference: Path is too short... missing prefix?
Wed Jun 18 10:45:14 2014 VxWarning{0}: Chassis::setUpWorldAxis: the chassis must be set before calling this method.
...
Wed Jun 18 10:45:14 2014 VxWarning{0}: VxExtensionFactory: 'Devices.Joystick' has been updated to 'Input Device.Joystick'. Make sure you are using the right ICD!
Wed Jun 18 10:45:14 2014 VxWarning{0}: VxSimObject::addExtension: extension default_DynamicsMaterial Table_10556921 already part of Dump Truck
Wed Jun 18 10:45:14 2014 VxWarning{0}: VxExtensionSorter: There is a loop with connections of these extensions:
Wed Jun 18 10:45:14 2014 VxWarning{0}: [Dynamic Component]
Wed Jun 18 10:45:14 2014 VxWarning{0}: [Truck controller]
Wed Jun 18 10:45:14 2014 VxWarning{0}: VxExtensionSorter: There is a loop with connections of these extensions:
Wed Jun 18 10:45:14 2014 VxWarning{0}: [Dynamic Component]
Wed Jun 18 10:45:14 2014 VxWarning{0}: [Truck controller]
...
Wed Jun 18 10:52:01 2014 VxWarning{0}: IPythonExtension: Error running script in no owner.Actuator Controller:
Wed Jun 18 10:52:01 2014 VxWarning{0}: Error is: Traceback (most recent call last):
File "<string>", line 16, in on_add_to_owner
SystemError: error return without exception set

Wed Jun 18 10:52:01 2014 VxWarning{0}: sys.path is: C:/CM Labs/Vortex Editor 6.2/bin/;C:/CM Labs/Vortex Editor 6.2/bin/;C:/CM Labs/Vortex Editor 6.2/bin/;C:\Users\SamuraiGG\AppData\Local\Temp\Vortex\release\VxPython\Python27;C:\Users\SamuraiGG\AppData\Local\Temp\Vortex\release\VxPython\Python27\python.zip
Wed Jun 18 10:52:01 2014 VxWarning{0}: VxExtensionFactory: 'Scripting.IDynamics Python' has been updated to 'Scripting.Dynamics Python'. Make sure you are using the right ICD!
Wed Jun 18 10:52:01 2014 VxWarning{0}: VxBaseReference: No path found for lower_frame.
...
Wed Jun 18 11:23:29 2014 VxWarning{0}: VxTriangleMeshData::buildHalfEdges - ignored 15 degenerate triangles.
Wed Jun 18 11:23:30 2014 VxWarning{0}: VxSimObject::addExtension: extension default_DynamicsMaterial Table_11820838 already part of RootScene
Wed Jun 18 11:23:30 2014 VxWarning{0}: VxCSVTable load cannot open file: C:/Vortex-6.1/STAGE/x64_win32_vc10/resources/VehicleSystems/LAV_TT.csvWed Jun 18 11:23:30 2014 VxWarning{0}: CSV file C:/Vortex-6.1/STAGE/x64_win32_vc10/resources/VehicleSystems/LAV_TT.csv has not been found for the torque table
Wed Jun 18 11:23:30 2014 VxWarning{0}: VxCSVTable load cannot open file: C:/Vortex-6.1/STAGE/x64_win32_vc10/resources/VehicleSystems/LAV_BTT.csvWed Jun 18 11:23:30 2014 VxWarning{0}: CSV file C:/Vortex-6.1/STAGE/x64_win32_vc10/resources/VehicleSystems/LAV_TT.csv has not been found for the torque table
Wed Jun 18 11:23:31 2014 VxWarning{0}: VxExtensionSorter: There is a loop with connections of these extensions:
Wed Jun 18 11:23:31 2014 VxWarning{0}: [LAV Controller]
Wed Jun 18 11:23:31 2014 VxWarning{0}: [Differential Lock]
Wed Jun 18 11:23:31 2014 VxWarning{0}: [Dynamic Component]

You can identify these log files in the TEMP% directory by looking for files that are prefixed with VortexEditor_ and contain the name of the computer (for example, C:\Users\SamuraiGG\AppData\Local\Temp\VortexEditor_Warrior247_5848.log where SamuraiGG is your user name and Warrior247 is your computer's name).