FreeBSD client errors
by Marc Schraffenberger · in Torque Game Engine · 05/25/2004 (5:31 am) · 1 replies
I have compiled both HEAD and 1.2.2 on FreeBSD 5.2.1
Both seem to compile with no problems what-so-ever.
Both the HEAD and 1.2.2 start up, but once I join or
start a server, I see a couple frames of the game
but then it seg faults.
I would appreciate any insight into what the errors could mean, and how I could go about fixing them. Thanks.
Here are the tails of the output from the console:
HEAD
----
*** Initial Control Object
Could not locate texture: starter.fps/data/shapes/player/crossbow
Could not locate texture: starter.fps/data/shapes/player/clip
Mapping string: Kork to index: 13
Fatal: (ts/tsSortedMesh.cc @ 84) TSSortedMesh::render: rendering of non-indexed meshes no longer supported
Nonzero exit code: 1, triggering SIGSEGV for core dump
% Segmentation fault (core dumped)
... or sometimes ...
*** Initial Control Object
Could not locate texture: starter.fps/data/shapes/player/crossbow
Could not locate texture: starter.fps/data/shapes/player/clip
Mapping string: Kork to index: 13
Fatal: (ts/tsMaterialList.cc @ 129) TSMaterialList::getFlags: index out of range
Nonzero exit code: 1, triggering SIGSEGV for core dump
% Segmentation fault (core dumped)
Release_1_2_2
-------------
*** Initial Control Object
Could not locate texture: starter.fps/data/shapes/player/crossbow
Could not locate texture: starter.fps/data/shapes/player/clip
Mapping string: Kork to index: 13
Fatal: (ts/tsMesh.cc @ 307) TSMesh::render: rendering of non-indexed meshes no longer supported
Nonzero exit code: 1, triggering SIGSEGV for core dump
% Segmentation fault (core dumped)
... or sometimes ...
*** Initial Control Object
Could not locate texture: starter.fps/data/shapes/player/crossbow
Could not locate texture: starter.fps/data/shapes/player/clip
Mapping string: Kork to index: 13
Fatal: (ts/tsSortedMesh.cc @ 84) TSSortedMesh::render: rendering of non-indexed meshes no longer supported
Nonzero exit code: 1, triggering SIGSEGV for core dump
% Segmentation fault (core dumped)
Both seem to compile with no problems what-so-ever.
Both the HEAD and 1.2.2 start up, but once I join or
start a server, I see a couple frames of the game
but then it seg faults.
I would appreciate any insight into what the errors could mean, and how I could go about fixing them. Thanks.
Here are the tails of the output from the console:
HEAD
----
*** Initial Control Object
Could not locate texture: starter.fps/data/shapes/player/crossbow
Could not locate texture: starter.fps/data/shapes/player/clip
Mapping string: Kork to index: 13
Fatal: (ts/tsSortedMesh.cc @ 84) TSSortedMesh::render: rendering of non-indexed meshes no longer supported
Nonzero exit code: 1, triggering SIGSEGV for core dump
% Segmentation fault (core dumped)
... or sometimes ...
*** Initial Control Object
Could not locate texture: starter.fps/data/shapes/player/crossbow
Could not locate texture: starter.fps/data/shapes/player/clip
Mapping string: Kork to index: 13
Fatal: (ts/tsMaterialList.cc @ 129) TSMaterialList::getFlags: index out of range
Nonzero exit code: 1, triggering SIGSEGV for core dump
% Segmentation fault (core dumped)
Release_1_2_2
-------------
*** Initial Control Object
Could not locate texture: starter.fps/data/shapes/player/crossbow
Could not locate texture: starter.fps/data/shapes/player/clip
Mapping string: Kork to index: 13
Fatal: (ts/tsMesh.cc @ 307) TSMesh::render: rendering of non-indexed meshes no longer supported
Nonzero exit code: 1, triggering SIGSEGV for core dump
% Segmentation fault (core dumped)
... or sometimes ...
*** Initial Control Object
Could not locate texture: starter.fps/data/shapes/player/crossbow
Could not locate texture: starter.fps/data/shapes/player/clip
Mapping string: Kork to index: 13
Fatal: (ts/tsSortedMesh.cc @ 84) TSSortedMesh::render: rendering of non-indexed meshes no longer supported
Nonzero exit code: 1, triggering SIGSEGV for core dump
% Segmentation fault (core dumped)
Torque Owner Marc Schraffenberger
The same thing happens. Some of them I can
move and spin a bit, but eventually it crashes
with the same messages as in my post above.