FAQ - Frequently asked questions

Table of content

FAQ

  • PovClipse nags it can not find standard Povray include files like colors.inc or MegaPOV ones like mechsim.inc
  • Usage

    My 'Povray Render settings' window does not show the configuration settings
    A specific render configuration has to be selected in order to display its settings.
    Select the 'Render Configurations' root entry in the tree menu on the left and use a right-click to bring up the popup menu. Select 'New' to create a new render configuration.
    The 'Render Message View' window does not contain any line after rendering completes
    This is probably a permission issue preventing Povray from writing the console output text files.
    Please check the Povray documentation chapter "3.2.7.12 Adding or Changing Allowed Directories" (http://www.povray.org/documentation/view/3.6.1/600/). You have to include the path to your workspace in the [Permitted Output Paths] section in order to allow Povray to create the console output text files.
    The editor does not recognize MegaPOV keywords
    You have opened a MegaPOV scene file using the Povray instead of the MegaPOV mode.
    Right-click on the file in the navigator and select "Open with -> PovClipse (MegaPOV)"
    PovClipse nags it can not find standard Povray include files like colors.inc or MegaPOV ones like mechsim.inc
    Plese see the next entry "Povray or MegaPOV does not find the standard include files on Unix and OS X", it is the very same issue.
    Povray or MegaPOV does not find the standard include files on Unix and OS X
    The default Povray and MegaPOV include path is built using the preference setting for the Povray and MegaPOV executeable: [POVRAY_EXECUTEABLE_PATH]/../include.
    While this is correct for Windows systems it might be incorrect for Unix / Linux or Mac OS X systems. In this case use the "Povray library" and "MegaPOV library" preference options to change the (incorrect) default to the correct includedirectory.
    When trying to import projects the "Projects" list remains empty
    If you have choosen a root directory or archive file and the "Projects" list remains empty or the desired project is not listed, chances are good that you have already a Project having the very same name in your workspace.
    Move the existing project out of the way (rename or delete it) and start the project import wizard again, this time the desired project should be listed.
    Why should I use the project layout folders?
    The project layout folders offers a way to structure your Povray scene project in a consistant way.
    If you always store your *.pov files in the folder scene and your data files (images, height field data, fonts...) in the folder data you can easily orient your self, even if you had the last look at the project a couple of years ago.
    On the other hand, if you store all files in one directory you will end up browsing the directoy and asking yourself "Was that image used for something in the scene or was it an rendering output?"
    You know it for sure that the image was rendered if you find it in the output directory!
     

    Error messages

    Eclipse shows error message like 'Plug-in com.wm.povclipse was unable to load class com.wm.[SOME_CLASS_NAME]'
    Sounds like you are running Eclipse using Java 1.4 or 1.3. Check the Eclipse logfile ([WORKSPACE]/.metadata/.log), the line beginning with 'java.version' tells you the java version used by Eclipse.
    As PovClipse needs Java 5 or 6 you have to install one of these Java versions.
    If you have it already installed tell Eclipse to use it by specifying the Eclipse command line parameter '-vm PATH_TO_JAVAW_EXECUTEABLE'.
    Please check the Eclipse documentation for more information on this topic.
    PovClipse doesn't do anything and Eclipse log shows error message like 'java.lang.NoClassDefFoundError'
    Sounds like you are running an Eclipse version prior to 3.2.

    Please note that the Eclipse 3.2 Milestone builds are not supported! Supports starts with the Eclipse 3.2 final version.

     

    Supported operating systems

    Does PovClipse support Linux?
    Well, officially PovClipse does not support any Linux distribution.
    This is due to the testing effort, not because PovClipse uses any operating system depending code.
    However, PovClipse seems to be pretty stable on Linux as well, I have feedback from users running PovClipse on Fedora Core 4, Ubuntu 6.10 and SuSE 10.2
    Does PovClipse support MacOS X?
    PovClipse does not officially support MacOS X, because the PovClipse Team (which is only me as developer and tester) do not have access to a Mac machine.
    However, PovClipse seems to be pretty stable on a Mac as well, I have feedback from users running PovClipse on MacOS X 10.4.8 (Intel).
    The bad thing is that there is no Povray Mac executable, you have to compile one yourself using the Povray Unix sources. But ***please*** do not ask me how to do this, as mentioned I do not have a Mac machine and can therefore not support you! Please check the Povray community on this issue.
     

    Log files

    Where do I find the Eclipse log file?
    You will find the Eclipse log file in your workspace directory:
    [WORKSPACE]/.metadata/.log
    Where do I find the PovClipse log file?
    You will find the PovClipse log file in your workspace directory:
    [WORKSPACE]/.metadata/.plugins/com.wm.povclipse/PovClipse.log
    How can I change the PovClipse log level threshold?
    In order to change the logging threshold you have to specify the commandline parameter povclipse.loglevel followed by the desired threshold when starting Eclipse.
    The supported threshold values are:
    • FATAL (logs errors only)
    • WARN (log errors and warnings)
    • INFO (default, log error, warnings and performance measurements)
    • DEBUG (all of the above plus debugging information)
    • TRACE (all of the above plus very detailed debugging information)
    Please note that setting the DEBUG threshold will cause serious performance losses. The TRACE level will make PovClipse extremely slow, this level is used for searching bugs only!

    Example (sets the log level "DEBUG", the Eclipse workspace and the French language):
    eclipse.exe -povclipse.loglevel DEBUG -data "C:\MyPovClipseWorkspace" -nl fr
     

    Forum and bug reporting

    Is there an open discussion forum?
    Yes, please use the forum on the PovClipse Sourceforge page: Open Discussion forum
    How should I report a bug?
    Please use the bug tacking system at the PovClipse Sourceforge page: Bug tracking
    How should I request a new feature?
    Please use the feature tracking system at the PovClipse Sourceforge page: Feature tracking
     

    Donation

    Why should I donate?
    Please see the Donation page for why a donation to this project is highly appreciated.

    Hosted by SourceForge.net Logo