Does anyone here using povray 3.7 on openSUSE 12.1?
I am looking for a kind soul’s help to find a povray 3.7 rpm for openSUSE 12.1 64bit
As you might probably aware of, the available povray version in the openSUSE repo is version 3.61
and is not compatible as a plugin maybe to blender 2.59 with the povray 3.7 integration.
Right now I am using yafaray to blender 2.49 in openSUSE 11.3 but I am planning to remove the
openSUSE 11.3 on my machine to make room for a larger space, that is why I am looking for an alternative
raytracer.
> Does anyone here using povray 3.7 on openSUSE 12.1?
I have been known to play around with it on occasion, as well as being a
part of that community as well.
> I am looking for a kind soul’s help to find a povray 3.7 rpm for
> openSUSE 12.1 64bit As you might probably aware of, the available povray
> version in the openSUSE repo is version 3.61 and is not compatible as a
> plugin maybe to blender 2.59 with the povray 3.7 integration.
You won’t find a 3.7 RPM yet as 3.7 is still in beta - the POVray team
only distributes 3.7 in source form right now for Linux.
> Right now I am using yafaray to blender 2.49 in openSUSE 11.3 but I am
> planning to remove the openSUSE 11.3 on my machine to make room for a
> larger space, that is why I am looking for an alternative raytracer.
I’m not sure I understand why moving from 11.3 to something else
(presumably upgrading to 12.1?) limits you using Yafray with Blender - of
course, POVray 3.61 is a good release as well and one that you could use
unless you have a specific need for features in 3.7 (do you?). What’s
pushing you to use 3.7?
To clarify it is not Yafray, I am using in 11.3, what I am using is theYafaRay 0.1.1 to blender 2.49 exporter
I compiled this before and I can do the rendering using YafaRay from inside blender.
I am planning to remove 11.3 from my machine to make room for a larger space. This machine I am using has
11.3 and 11.4 Now planning to install 12.1 along side with 11.4. Right now I am getting used to the new blender version 2.5x
and I found out that this new blender version has POVRay 3.7 exporter that got my interest.
Edit:
It seems the only way to get 3.7 is to compile it myself. I was avoiding it to not add more load on my machine’s hard drive and on top of that I am not a good compiler (amateur).
> To clarify it is not Yafray, I am using in 11.3, what I am using is
> theYafaRay 0.1.1 to blender 2.49 exporter I compiled this before and I
> can do the rendering using YafaRay from inside blender.
Ah, I see.
> I am planning to remove 11.3 from my machine to make room for a larger
> space. This machine I am using has 11.3 and 11.4 Now planning to install
> 12.1 along side with 11.4. Right now I am getting used to the new
> blender version 2.5x and I found out that this new blender version has
> POVRay 3.7 exporter that got my interest.
POVRay 3.7 isn’t difficult to build, though there is an issue with
getting the configuration right on 64-bit systems. There’s a note about
that at http://povray.org/beta/source/ (see the note about 64-bit systems
and requiring boost_thread-mt).
The supporting libraries are all in the OSS repository for openSUSE.
You’ll need the relevant -devel packages as well if you want to build it.
I didn’t know tha tthere was a 3.7 exporter in Blender now, so I’ll have
to check that out.
I had the time compiling POV-Ray 3.7RC3 using checkinstall.
I was able to successfully made an RPM for openSUSE 12.1
I installed it using yast and tested with the blender 2.59 from openSUSE 12.1 repo.
Using the blender povray exporter I tried to test to render, but the result is all black.
I may have to do more digging to find a way to make this work.
Any input/thoughts/suggestions will be appreciated.
> I had the time compiling POV-Ray 3.7RC3 using checkinstall.
> I was able to successfully made an RPM for openSUSE 12.1 I installed it
> using yast and tested with the blender 2.59 from openSUSE 12.1 repo.
> Using the blender povray exporter I tried to test to render, but the
> result is all black.
> I may have to do more digging to find a way to make this work.
>
> Any input/thoughts/suggestions will be appreciated.
I may have some time this weekend to play around with it - glad to hear
you got the compile to work.
I did not do any modification when I compiled it. The checkinstall used /usr/local and I had to
create some directory in /usr/local to finish checkinstall. Any tips you can give me the right
way to do it in openSUSE will be much appreciated.
As a side note:
I did some googling with the black screen output rendering from blender 2.59 to povray
and I found same problems without a solution.
I want to try the blender-2.61-linux-glibc27-x86_64.tar.bz2 but I am not sure if it will
find povray 3.7 when I extract and use it. Any hint as to the right place to save the extracted
tarball with the possibility of finding the povray 3.7 installed rpm?
On 2012-01-18 16:26, conram wrote:
> I did not do any modification when I compiled it. The checkinstall used
> /usr/local and I had to
> create some directory in /usr/local to finish checkinstall. Any tips
> you can give me the right
> way to do it in openSUSE will be much appreciated.
Checkinstall may have problems to complete. My trick is to do first a “make
install”, that creates the directories that would fail, then run
checkinstall to create the rpm.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Update on povray 3.7 to blender.
I downloaded the latest blender 5.61 tarball
and extracted to /home/me/.local
and did a quick test rendering using the povray 3.7 plugin
and it worked. My guess is, the black screen that I previously posted
is on blender 2.59. version.
> robin_listas;2431787 Wrote:
>> On 2012-01-18 16:26, conram wrote:
>> > I did not do any modification when I compiled it. The checkinstall
>> used
>> > /usr/local and I had to create some directory in /usr/local to finish
>> > checkinstall. Any tips you can give me the right way to do it in
>> > openSUSE will be much appreciated.
>>
>> Checkinstall may have problems to complete. My trick is to do first a
>> “make install”, that creates the directories that would fail, then run
>> checkinstall to create the rpm.
>>
>> –
>> Cheers / Saludos,
>>
>> Carlos E. R.
>> (from 11.4 x86_64 “Celadon” at Telcontar)
>
> Thanks for the info. I will try it next time.
>
> Update on povray 3.7 to blender.
> I downloaded the latest blender 5.61 tarball and extracted to
> /home/me/.local and did a quick test rendering using the povray 3.7
> plugin and it worked. My guess is, the black screen that I previously
> posted is on blender 2.59. version.
On Wed, 18 Jan 2012 20:43:05 +0000, Carlos E. R. wrote:
> On 2012-01-18 16:26, conram wrote:
>> I did not do any modification when I compiled it. The checkinstall used
>> /usr/local and I had to create some directory in /usr/local to finish
>> checkinstall. Any tips you can give me the right way to do it in
>> openSUSE will be much appreciated.
>
> Checkinstall may have problems to complete. My trick is to do first a
> “make install”, that creates the directories that would fail, then run
> checkinstall to create the rpm.
Can you clarify what you mean here, Carlos? I’ve tried checkinstall with
a few things myself and had trouble, and reading this, it sounds like you
run ‘make install’ and then run ‘make install’ under checkinstall - am I
understanding correctly?
On 2012-01-19 01:24, Jim Henderson wrote:
> On Wed, 18 Jan 2012 20:43:05 +0000, Carlos E. R. wrote:
> Can you clarify what you mean here, Carlos? I’ve tried checkinstall with
> a few things myself and had trouble, and reading this, it sounds like you
> run ‘make install’ and then run ‘make install’ under checkinstall - am I
> understanding correctly?
Yep, that is correct
I haven’t used it for a year, but the last times I used it, that’s what I
had to do. I reported a bugzilla or two on it.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
In 11.3 I never had the issue compiling with checkinstall.
Carlos, please clarify it again what Jim said about
run ‘make install’ and then run ‘make install’ under checkinstall
When I first read your post about this, I was thinking of running
.configure/make/makeinstall/checkinstall then replacing the app generated by makeinstall
with the app. rpm created by checkinstall.:\
On Thu, 19 Jan 2012 01:38:06 +0000, Carlos E. R. wrote:
> On 2012-01-19 01:24, Jim Henderson wrote:
>> On Wed, 18 Jan 2012 20:43:05 +0000, Carlos E. R. wrote:
>
>> Can you clarify what you mean here, Carlos? I’ve tried checkinstall
>> with a few things myself and had trouble, and reading this, it sounds
>> like you run ‘make install’ and then run ‘make install’ under
>> checkinstall - am I understanding correctly?
>
> Yep, that is correct
>
> I haven’t used it for a year, but the last times I used it, that’s what
> I had to do. I reported a bugzilla or two on it.
Cool, thanks. I’d had some problems trying to use it to build an image
in Studio. That may well help.
> Carlos, please clarify it again what Jim said about
>> run ‘make install’ and then run ‘make install’ under checkinstall
> When I first read your post about this, I was thinking of running
> configure/make/makeinstall/checkinstall then replacing the app
> generated by makeinstall
> with the app. rpm created by checkinstall.:\
Clarify again? Three times? It is very clear, I substitute the checkinstall
phase with make install, then checkinstall. Then I install the rpm just
made with the rpm command.
Saying it 4 times will not make it clearer…
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
