File: troubleshooting.xml

package info (click to toggle)
k3d 0.4.3.0-3
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 51,716 kB
  • ctags: 81,610
  • sloc: cpp: 283,698; ansic: 64,095; xml: 61,533; sh: 9,026; makefile: 5,282; python: 431; perl: 308; awk: 130
file content (68 lines) | stat: -rw-r--r-- 2,840 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
<appendix id="Troubleshooting">
<title>Troubleshooting</title>

<sect1 id="trouble_strange_characters">
<title>The &k3d; hierarchy window is empty or shows strange characters</title>
<para>
You're using a GTK+ theme with Unicode texts. Just try switching to another theme, <emphasis>Metal</emphasis> should work. 
</para>
</sect1>

<sect1 id="trouble_windows_minimized">
<title>When I create a document, windows are opened minimized and can't be re-opened ?!?</title>
<para>
It happens when &k3d; application is closed with minimized windows, with Restore Window Size/Position option turned on.
To turn it off, open Application Window > Tools > Options dialog. Then exit &k3d; and launch it again, open a new document, 
the windows will open with default sizes. 
</para>
</sect1>

<sect1 id="trouble_bitmapviewer">
<title>Bitmap Viewer doesn't work</title>
<para>
The default viewer is not available on your computer: open Application Window > Tools > Options > Applications dialog, 
and set the command for your favorite image editor or viewer followed by %p which will be replaced by the image name.
If the program is not in the system's path, you'll have to write full path. Example on the Win32 platform:
</para>
<programlisting>
"c:\Program Files\Accessories\mspaint" %p
</programlisting>
<para>
Quotes needed because of the space in 'Program Files'. 
</para>
</sect1>

<sect1 id="trouble_render_textures">
<title>Some textures don't render at all, what happens ?</title>
<para>
BMRT or Aqsis don't support indexed bitmaps, that is 8-bit per pixel pictures, like GIF files.
If you're using NetPBM version >= 9.25, edit the configuration file netpbm.conf you'll find in 
<filename>k3d/share/</filename> directory and add -truecolor option in the following line to force 24-bit format:
</para>
<programlisting>
&lt;writer command="pnmtotiff -none -truecolor %p" format="TIFF RGB" filename="(\.tif$|\.tif\.|\.tiff$|\.tiff\.)"/&gt;
</programlisting>
<para>
Else convert your textures to a 24-bit picture format.
</para>
</sect1>

<sect1 id="trouble_badvalue_crash">
<title>K-3D crashed with a Gdk-ERROR **: BadValue message</title>
<para>
Typically, BadValue errors are what happens when the X server gets data it can't handle
- in general, they shouldn't happen because the GTK+ layer is supposed to trap dumb mistakes
before they get through to xlib, but occaisionally something gets through.
</para>
<para>
There's a way to lookup the error codes, though I don't remember it off the top of my head.
A more useful piece of troubleshooting would be to run the app in a debugger. 
Even more useful would be run your X server in synchronous mode when you do it, since X events
can run asynchronously, meaning that the debugger backtrace might or might-not leave you
looking at the true culprit.
</para>
<para>
</para>
</sect1>

</appendix>