Downloads:

1,817

Downloads of v 3.7.0.20161121:

1,537

Last Update:

21 Nov 2016

Package Maintainer(s):

Software Author(s):

  • Persistence of Vision Raytracer Pty. Ltd.

Tags:

pov-ray povray raytracer graphics 3d admin

POV-ray

3.7.0.20161121 | Updated: 21 Nov 2016

Downloads:

1,817

Downloads of v 3.7.0.20161121:

1,537

Maintainer(s):

Software Author(s):

  • Persistence of Vision Raytracer Pty. Ltd.

POV-ray 3.7.0.20161121

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install POV-ray, run the following command from the command line or from PowerShell:

>

To upgrade POV-ray, run the following command from the command line or from PowerShell:

>

To uninstall POV-ray, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade pov-ray -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade pov-ray -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure pov-ray installed
  win_chocolatey:
    name: pov-ray
    state: present
    version: 3.7.0.20161121
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'pov-ray' do
  action    :install
  version  '3.7.0.20161121'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: pov-ray,
    Version: 3.7.0.20161121,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller pov-ray
{
   Name     = 'pov-ray'
   Ensure   = 'Present'
   Version  = '3.7.0.20161121'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'pov-ray':
  provider => 'chocolatey',
  ensure   => '3.7.0.20161121',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install pov-ray version="3.7.0.20161121" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator flcdrg on 24 Nov 2016.

Description

The Persistence of Vision Ray-Tracer creates three-dimensional, photo-realistic images using a rendering technique called ray-tracing. It reads in a text file containing information describing the objects and lighting in a scene and generates an image of that scene from the view point of a camera also described in the text file. Ray-tracing is not a fast process by any means, but it produces very high quality images with realistic reflections, shading, perspective and other effects.

Licensing

This installs both the AGPL3-licensed application and the editor DLLs which implement the optional codemax code editor not covered by the AGPL3. The DLLs are provided pursuant to the license that applied to the previous version of POV-Ray (v3.62) and may only be used under those terms.

Note

The POV-ray installer has no option for system-wide installs, completely ignoring users other than the installing user. See here and here for details. Until the POV-ray developers resolve the problem, there are two (partial) work-arounds for multi-user systems:

  1. Include all required user files in the default user profile. This measurably slows down initial logins and increases (future) user profile size whether or not POV-Ray is used and does not make POV-Ray functional for other, existing users. POV-Ray will work regardless of the calling application (Explorer, etc.).
  2. Establish a "launcher" script. This does not touch the default user profile and works for existing and future users. However, if a user starts POV-Ray without using the script (e.g. from inside another application), it will be broken for that user going forward. Also, if registry editing is blocked, the POV-Ray application may not recognize the editor installation. These can (usually) be mitigated by configuring other applications to call POV-Ray via the script.

This Chocolatey package follows work-around (2). The "launcher" establishes necessary files/settings on first run, but as it is not official, it may not always function as expected. Testing is recommended. Some other Chocolatey packages for applications that can use POV-Ray may be designed to utilize the script. The package parameter (below) will have the package installer also follow work-around (1).

Package Parameters

The following package parameter can be set:

  • /default - The POV-Ray user files and settings will be included in the default user profile.

This parameter can be passed to the installer with the use of -params.
For example :
choco install pov-ray -params '"/Default"'


tools\chocolateyInstall.ps1
$packageName = 'POV-Ray'
$Version = '3.7'

# First download/install the _Application_ (one OSS license)
$InstallArgs = @{
   packageName = 'POV-Ray Application'
   installerType = 'exe'
   url = 'http://www.povray.org/redirect/www.povray.org/ftp/pub/povray/Official/povwin-3.7-agpl3-setup.exe'
   checkSum = '2B1331641B6F96113C2DBA951BE80D99EB548639480399CABB5E3A60DCE5BDC8'
   checkSumType = 'sha256'
   silentArgs = '/S'
   validExitCodes = @(0)
}
Install-ChocolateyPackage @InstallArgs

# Then download/install the _Editor DLLs_ (a different OSS license)
$InstallArgs2 = @{
   packageName = "POV-Ray Editor"
   installerType = 'exe'
   url = 'http://www.povray.org/download/povwin-3.7-editor.exe'
   checkSum = '9265F0D3337F956AE42C1BC19B475182C3C5E543E96DF2287450AFB9738B6030'
   checkSumType = 'sha256'
   silentArgs = '/S'
   validExitCodes = @(0)
}
Install-ChocolateyPackage @InstallArgs2

# Make POV-Ray appear in "Programs and Features" for all users.
Write-Debug 'Moving uninstall registry key from user to machine.'
$UserUninstall = "HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\POV-Ray for Windows v$Version"
$SystemUninstall = 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\'
Copy-Item $UserUninstall $SystemUninstall -Recurse
Remove-Item $UserUninstall -Recurse

# Prevent POV-Ray from "inferring" its location for each user.
Write-Debug 'Setting POV-Ray "Home" for all users.'
$RegPath = "HKLM:\Software\POV-Ray\v$Version\Windows"
New-Item $RegPath -Force | Write-Debug
$RegValue = Join-Path $env:ProgramFiles "\POV-Ray\v$Version"
New-ItemProperty -Path $RegPath -Name 'Home' -Value $RegValue -force | Write-Debug

$UserArguments = @{}
# Parse the packageParameters using good old regular expression
if ($env:chocolateyPackageParameters) {
    $match_pattern = "\/(?<option>([a-zA-Z]+)):(?<value>([`"'])?([a-zA-Z0-9- _\\:\.]+)([`"'])?)|\/(?<option>([a-zA-Z]+))"
    $option_name = 'option'
    $value_name = 'value'
 
    if ($env:chocolateyPackageParameters -match $match_pattern ){
        $results = $env:chocolateyPackageParameters | Select-String $match_pattern -AllMatches
        $results.matches | % {
        $UserArguments.Add(
            $_.Groups[$option_name].Value.Trim(),
            $_.Groups[$value_name].Value.Trim())
    }
    }
    else
    {
        Throw 'Package Parameters were found but were invalid (REGEX Failure)'
    }
  
} else {
    Write-Debug 'No Package Parameters Passed in'
}

Write-Output "Copying libraries and settings..."
if ($UserArguments.ContainsKey('Default')) {
   Write-Output 'You requested to establish a default user profile.'
   # if installing as system, relative path to default doesn't work against $env:USERPROFILE
   $defaultProfile = Join-Path ([Environment]::GetFolderPath("commondesktopdirectory")) '..\..\default'
   copy-item (Join-Path $env:USERPROFILE "\Documents\POV-Ray") (join-path $defaultProfile "Documents") -recurse

   # Use Active Setup so all users will start POV-Ray with initialization settings
   #   See: http://www.itninja.com/blog/view/an-active-setup-primer
   $ActiveSetupKey = 'HKLM:\Software\Microsoft\Active Setup\Installed Components'
   New-Item -Path $ActiveSetupKey -Name $packageName -Value $packageName -Force | Write-Debug
   New-ItemProperty -Path (Join-Path $ActiveSetupKey $packageName) -Name "Version" -Value $Version -Force | Write-Debug
   # REG.EXE is often blocked, and WMIC is faster than loading PoSh at login.  
   #   For WMIC reference see: https://stackoverflow.com/questions/22265482/registry-edit-from-batch
   $WMICcmd = 'wmic.exe /NAMESPACE:\\root\default Class StdRegProv Call SetDWORDValue hDefKey="&H80000001" sSubKeyName="Software\POV-Ray\v3.7\Windows" sValueName="FreshInstall" uValue="1" > nul'
   New-ItemProperty -Path (Join-Path $ActiveSetupKey $packageName) -Name "StubPath" -Value $WMICcmd -Force | Write-Debug
} 
copy-item (Join-Path $env:USERPROFILE "\Documents\POV-Ray") (Join-Path $env:ProgramFiles "POV-Ray\v$Version\NewUserFiles") -recurse

$ShortcutArgs = @{
   ShortcutFilePath = Join-Path ([Environment]::GetFolderPath("commondesktopdirectory")) "Launch $packageName v$Version.lnk"
   TargetPath = Join-Path (Split-Path -parent $MyInvocation.MyCommand.Definition) 'Launch POV-Ray.bat'
   IconLocation = (Join-Path $env:ProgramFiles "POV-Ray\v$Version\bin\POV-Ray.ico")
}

Install-ChocolateyShortcut @ShortcutArgs
tools\chocolateyUninstall.ps1
$AppName = 'POV-Ray'

$RegistryLocation = 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall'

$unexe = Get-ItemProperty "$RegistryLocation\*" | 
                     Where-Object { $_.displayname -match $AppName} |
                     Select-Object -ExpandProperty UninstallString

$UninstallArgs = @{
   packageName = $AppName
   fileType = 'exe'
   file = $unexe
   silentArgs = '/S'
   validExitCodes = @(0)
}

Uninstall-ChocolateyPackage @UninstallArgs

$PathsToDelete = @(
'HKLM:\Software\POV-Ray'
'HKLM:\Software\Microsoft\Active Setup\Installed Components\POV-Ray'
'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\POV-Ray for Windows v3.7'
Join-Path $env:ProgramFiles 'POV-Ray'
Join-Path $env:USERPROFILE '\..\default\documents\POV-Ray'
Join-Path ([Environment]::GetFolderPath("commondesktopdirectory")) "Launch POV-Ray v3.7.lnk"
)

Foreach ($path in $PathsToDelete) {
   if (Test-Path $path) {
      Remove-Item $path -Recurse -Force
   }
}

tools\Launch POV-Ray.bat
@echo off

:: This script was tested for POV-Ray v3.7 on Win7x64 where the files 
:: in the four, user-profile folders from the initial install have been
:: copied into the POV-Ray program folder.  It should work for Win8-10.

if exist "%userprofile%\Documents\POV-Ray\v3.7\include\colors.inc" goto _Launch

echo Initializing POV-Ray user configuration.

:: REG.EXE is often blocked, and WMIC is faster than PoSh.  See: https://stackoverflow.com/questions/22265482/registry-edit-from-batch
SET "HKCU=&H80000001"
SET KEY=Software\POV-Ray\v3.7\Windows
SET ValName=FreshInstall
SET Val=1
SET Success=Registry entry complete.
SET Fail=Registry entry failed. Viewing may work, but editor functions will not be available.
wmic.exe /NAMESPACE:\\root\default Class StdRegProv Call SetDWORDValue hDefKey="%HKCU%" sSubKeyName="%KEY%" sValueName="%ValName%" uValue="%Val%" > nul && echo %Success% || echo %Fail%

echo Copying user files...
echo Please be patient, this may take a minute.

SET "NUF=%ProgramFiles%\POV-Ray\v3.7\NewUserFiles"
robocopy "%NUF%" "%userprofile%\Documents\POV-Ray" /mir /NFL /NDL /NJH /nc /ns /np
IF %ERRORLEVEL% LSS 8 goto _Launch
echo Initializing failed.  POV-Ray is unlikely to work properly.
pause

:_Launch
shift
set params=%1
if [%1]==[] goto afterloop
:loop
shift
if [%1]==[] goto afterloop
set params=%params% %1
goto loop
:afterloop
start "Launching POV-Ray" "%ProgramFiles%\POV-Ray\v3.7\bin\pvengine64.exe" %params%

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
POV-ray 3.7 280 Thursday, April 28, 2016 Approved

This package has no dependencies.

Discussion for the POV-ray Package

Ground Rules:

  • This discussion is only about POV-ray and the POV-ray package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or POV-ray, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus