![]() |
rtVTK
0.6.0
|
Q: What are the mouse controls for rtVTK?
A: Left mouse rotates the camera, middle button translates the scene, and right button is dolly the camera in or out. You can find the list of shortcut keys in the menu “Help > Using rtVTK...”.
Q: The camera is very sensitive and jumpy when the camera is near the image. Can I fix that?
A: Yes. On the main window pane to the right, click Advanced Settings. Adjust the speed sliders to values that feel comfortable. Positive values are more sensitive while negative values are less sensitive.
Q: I don't have a middle mouse button. How can I translate the scene without one?
A: This will be addressed in a future release.
Q: What is idle for?
A: Idle allows progressive renderer plugins to execute its calculations and after every second elapsed the plugin will draw the latest calculations to the screen. Idling can be CPU intensive. glRenderer and rlRenderer do not have idle functionality because they are not progressive renderers.
Q: rtVTK tells me that a plugin is missing?
A: This is caused by not having glRenderer or rlRenderer in the plugins folder of the application (.dll files for Windows, .dylib files for OS X and libpluginname.so for Linux). Just download the files from the website and copy them into the plugins folder and rtVTK should be able to load now.
Q: Where is the cbox ray log file?
A: That file should be in the scenes directory. It is the precomputed ray trees and the type of each ray. Use rlRenderer to load the .rl file and view the ray trees.
Q: I'd like to read more about ray tracing and rtVTK. Do you have more information?
A: Yes, the website www.rtVTK.org has further information and we also highly recommend that you read the research paper, which can be found on the website. Also, rtVTK is open source software; analyzing the source code is a great way to learn about how a program works. rtVTK is designed for custom plugins so go ahead and try making your own plugins!
Q: rtVTK gives me a warning that "timers cannot be stopped from another thread". What's wrong?
A: This is due to the way our user interface handles rtVTK, and has no effect on the application itself.
Q: Why doesn't the maximize button work properly?
A: Because there isn't supposed to be one - this is a known issue with 64-bit Linux distros. Sometimes the window manager ignores our Motif and NetWM hints and forces a maximize button, for which rtVTK does not provide support.
See also: Using rtVTK