 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi there,
I have released qtpovray-3.80.1 for Linux.
https://github.com/dickbalaska/qtpovray/releases/tag/v3.80.1
I have debian 9 (stretch) x64 packages on my site and
Ubuntu 16 (xenial) and 18 (bionic) x86 and x64 packages on launchpad.
It is also rumored to build and run on Slackware 14.1
The application is divided into 3 packages.
1) qtpovray - the main executable (1.3M)
2) qtpovray-includes - POV-Ray include files (284K)
3) qtpovray-extras - Help files, insert menus, sample scenes (31M)
The launchpad site is forqued.
https://launchpad.net/~qtpovray
Ubuntu 16 is in the qtpovray ppa
and ubuntu 18 is in the ppa2 ppa.
(It generates a key, loses the key, and for bionic, insists on using
that key to diff the previous version and dies when it can't find it. To
release the next version, I have to create another ppa. Super lame. For
xenial, you just have to see a "missing key" warning, slightly lame. A
known issue for three weeks now.)
I still struggle to get the Windows edition building. My multiplatform,
platform independent Makefile isn't. (If a super-project has two
library subprojects, the second library skips the compile phase and goes
to the build-the-lib-from-non-existent-objects phase. libpovray builds,
libvfe doesn't.)
--
dik
Rendered 328976 of 330000 (99%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
This sounds great! :)
Does it run on Linux Mint 18.3 64-bit?
Strongly considering doing a dual-boot on my laptop.
Is there a link to the features / differences of official POV-Ray? (sorry,
it's been a while)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 07/19/2018 10:12 AM, Bald Eagle wrote:
> This sounds great! :)
>
> Does it run on Linux Mint 18.3 64-bit?
Yes. It looks like this:
http://www.buckosoft.com/qtpovray/g/qtpovrayInMint18.3.png
canonical fixed the keyserver issue, so it all works now.
Mint 18.3 is ubuntu 16, which is what I run. qtpovray installs clean. yay.
> Strongly considering doing a dual-boot on my laptop.
I switched to Linux last year. I see no reason to go back to Windows. I
need Windows for Quicken and Turbotax; I run my old Windows 8 in a
VirtualBox window to access them.
>
> Is there a link to the features / differences of official POV-Ray?
(sorry,
> it's been a while)
It includes the last published POV-Ray 3.8 alpha that was tagged.
The only difference would be in the default locations of files.
Instead of /etc/povray/3.7 , I use /etc/qtpovray/3.8
Similarly, /usr/share/povray-3.7 becomes /usr/share/qtpovray-3.8
The main features are described here:
http://www.buckosoft.com/qtpovray/
--
dik
Rendered 328976 of 330000 (99%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
So after loading Mint onto at least 50 laptops at work, I now have it on my home
laptop, with dual boot. :)
Now I just sort of have to get back into the swing of _using_ Linux.
I have done the following so far:
oem@oem-Inspiron-N5110 ~/Desktop $ sudo add-apt-repository
ppa:qtpovray/qtpovray[sudo] password for oem:
You are about to add the following PPA:
qtpovray is a GUI/IDE for developing POV-Ray scenes
More info: https://launchpad.net/~qtpovray/+archive/ubuntu/qtpovray
Press Enter to continue or Ctrl+C to cancel
Executing: /tmp/tmp.Xm1qzSUTJw/gpg.1.sh --keyserver
hkp://keyserver.ubuntu.com:80
--recv-keys
30976367
gpg: requesting key 30976367 from hkp server keyserver.ubuntu.com
gpg: key 30976367: public key "Launchpad PPA for qtpovray" imported
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
oem@oem-Inspiron-N5110 ~/Desktop $ sudo apt-get update
Ign:1 http://packages.linuxmint.com sylvia InRelease
Hit:2 http://packages.linuxmint.com sylvia Release
Hit:3 http://archive.ubuntu.com/ubuntu xenial InRelease
Hit:4 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:5 http://security.ubuntu.com/ubuntu xenial-security InRelease
Hit:6 http://archive.canonical.com/ubuntu xenial InRelease
Get:7 http://ppa.launchpad.net/qtpovray/qtpovray/ubuntu xenial InRelease [18.0
kB]
Hit:8 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
Get:10 http://ppa.launchpad.net/qtpovray/qtpovray/ubuntu xenial/main Sources
[688 B]
Get:11 http://ppa.launchpad.net/qtpovray/qtpovray/ubuntu xenial/main amd64
Packages [952 B]
Get:12 http://ppa.launchpad.net/qtpovray/qtpovray/ubuntu xenial/main i386
Packages [952 B]
Get:13 http://ppa.launchpad.net/qtpovray/qtpovray/ubuntu xenial/main
Translation-en [588 B]
Fetched 21.2 kB in 2s (8,942 B/s)
Reading package lists... Done
.....aaaaaand now what?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Oh, look:
http://www.buckosoft.com/qtpovray/developer.html
So, I went to my Downloads folder and did:
$ sudo apt install \
git \
qt5-qmake \
qt5-default \
libboost-dev \
libboost-date-time-dev \
libboost-thread-dev \
libz-dev \
libpng-dev \
libjpeg-dev \
libtiff-dev \
libopenexr-dev
Which seemed to go fine.
Then I did:
oem@oem-Inspiron-N5110 ~/Downloads/qtpovray-3.80.1 $ git clone
https://github.com/dickbalaska/qtpovray.git && \
> git checkout qtpovray && \
> qmake && \
> make -j4
Cloning into 'qtpovray'...
remote: Counting objects: 36093, done.
remote: Compressing objects: 100% (317/317), done.
remote: Total 36093 (delta 222), reused 299 (delta 135), pack-reused 35636
Receiving objects: 100% (36093/36093), 166.26 MiB | 3.13 MiB/s, done.
Resolving deltas: 100% (16875/16875), done.
Checking connectivity... done.
fatal: Not a git repository (or any of the parent directories): .git
Uh oh, piskeddios.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 07/20/2018 08:58 PM, Bald Eagle wrote:
>
>
>
> .....aaaaaand now what?
>
>
>
Ugh, you got a little ahead of me. I didn't think you were going to do
this for a bit. You didn't need to do any of that extra stuff in this
and your next post.
Total steps:
sudo add-apt-repository ppa:qtpovray/qtpovray
sudo apt update
sudo apt install qtpovray qtpovray-includes qtpovray-extras
I will be publishing another version RSN. I don't have a .desktop file
which, in ubuntu/Unity I don't care; but in Kubuntu/Mint puts qtpovray
in the correct menu.
With those three steps above, you will get notified like any other
package when I've updated.
--
dik
Rendered 328976 of 330000 (99%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 07/20/2018 09:27 PM, Bald Eagle wrote:
> Oh, look:
> http://www.buckosoft.com/qtpovray/developer.html
>
> So, I went to my Downloads folder and did:
>
> $ sudo apt install \
> git \
> qt5-qmake \
> qt5-default \
> libboost-dev \
> libboost-date-time-dev \
> libboost-thread-dev \
> libz-dev \
> libpng-dev \
> libjpeg-dev \
> libtiff-dev \
> libopenexr-dev
>
> Which seemed to go fine.
Unnecessary unless you want to build it. (developer)
>
> Then I did:
>
> oem@oem-Inspiron-N5110 ~/Downloads/qtpovray-3.80.1 $ git clone
> https://github.com/dickbalaska/qtpovray.git && \
cd qtpovray && \
>> git checkout qtpovray && \
>> qmake && \
>> make -j4
> Cloning into 'qtpovray'...
> remote: Counting objects: 36093, done.
> remote: Compressing objects: 100% (317/317), done.
> remote: Total 36093 (delta 222), reused 299 (delta 135), pack-reused 35636
> Receiving objects: 100% (36093/36093), 166.26 MiB | 3.13 MiB/s, done.
> Resolving deltas: 100% (16875/16875), done.
> Checking connectivity... done.
> fatal: Not a git repository (or any of the parent directories): .git
>
>
>
> Uh oh, piskeddios.
copy/paste failure?
--
dik
Rendered 328976 of 330000 (99%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
dick balaska <dic### [at] buckosoft com> wrote:
> Total steps:
> sudo add-apt-repository ppa:qtpovray/qtpovray
> sudo apt update
> sudo apt install qtpovray qtpovray-includes qtpovray-extras
did the last step, opened a new terminal, typed qtpovray, and followed the setup
directions, now I get a message in the POV-Ray console when I try to render the
checkered plane scene by pressing the green arrow:
chdir: /home/oem/Documents
command:
No input file provided
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 07/20/2018 10:19 PM, Bald Eagle wrote:
> dick balaska <dic### [at] buckosoftcom> wrote:
>
>> Total steps:
>> sudo add-apt-repository ppa:qtpovray/qtpovray
>> sudo apt update
>> sudo apt install qtpovray qtpovray-includes qtpovray-extras
>
> did the last step, opened a new terminal, typed qtpovray, and followed the setup
> directions, now I get a message in the POV-Ray console when I try to render the
> checkered plane scene by pressing the green arrow:
>
> chdir: /home/oem/Documents
> command:
> No input file provided
>
>
Ok, flaw in my tutorial. Either type the name of the file in the text
box, or right-click "Select for Render" in the Resource view.
http://www.buckosoft.com/qtpovray/render.html
--
dik
Rendered 328976 of 330000 (99%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Never you mind me. I did the read the wordy thing, and sounded it all out all
by myself, and did the righty clicky thing and there was much qtpovray joy.
OK. Downloaded, installed, running.
What a day.
I'm gonna call it for the day. Thanks for the help - no worries.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
dick balaska <dic### [at] buckosoftcom> wrote:
> I have released qtpovray-3.80.1 for Linux.
> https://github.com/dickbalaska/qtpovray/releases/tag/v3.80.1
great.
> It is also rumored to build and run on Slackware 14.1
"out of the box", no.
make[1]: Entering directory `/tmp/QTP/qtpovray-3.80.1/qt/libpovray'
g++ -c -include povray -pipe -O2 -march=native -mtune=native -fPIC -fPIC
-std=gnu++11 -w -D_REENTRANT -DQT_DEPRECATED_WARNINGS -DTRY_OPTIMIZED_NOISE
-DBUILD_X86 -DQT_NO_DEBUG -DQT_CORE_LIB -I. -I../../source -I../../platform/unix
-I../../platform/x86 -I../../unix/povconfig -I../../vfe -isystem
/usr/include/qt5 -isystem /usr/include/qt5/QtCore -I.
-I/usr/lib64/qt5/mkspecs/linux-g++ -o
tmp/QTP/qtpovray-3.80.1/source/base/image/openexr.o
...../../source/base/image/openexr.cpp
In file included from ../../source/base/image/openexr.cpp:49:0:
/usr/include/OpenEXR/ImfRgbaFile.h:50:23: fatal error: ImfHeader.h: No such file
or directory
#include <ImfHeader.h>
^
compilation terminated.
make[1]: *** [tmp/QTP/qtpovray-3.80.1/source/base/image/openexr.o] Error 1
make[1]: Leaving directory `/tmp/QTP/qtpovray-3.80.1/qt/libpovray'
make: *** [sub-qt-libpovray-make_first-ordered] Error 2
still needs adding the 'INCLUDEPATH += "/usr/include/OpenEXR"' line to the
'libpovray.pro' file to make it work. not to worry though, it is easy to patch
from the (unwritten as yet :-)) qtpovray.SlackBuild script.
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 07/21/2018 09:36 AM, jr wrote:
>
>> It is also rumored to build and run on Slackware 14.1
>
> "out of the box", no.
>
> make[1]: Entering directory `/tmp/QTP/qtpovray-3.80.1/qt/libpovray'
> g++ -c -include povray -pipe -O2 -march=native -mtune=native -fPIC -fPIC
> -std=gnu++11 -w -D_REENTRANT -DQT_DEPRECATED_WARNINGS -DTRY_OPTIMIZED_NOISE
> -DBUILD_X86 -DQT_NO_DEBUG -DQT_CORE_LIB -I. -I../../source -I../../platform/unix
> -I../../platform/x86 -I../../unix/povconfig -I../../vfe -isystem
> /usr/include/qt5 -isystem /usr/include/qt5/QtCore -I.
> -I/usr/lib64/qt5/mkspecs/linux-g++ -o
> tmp/QTP/qtpovray-3.80.1/source/base/image/openexr.o
> ...../../source/base/image/openexr.cpp
> In file included from ../../source/base/image/openexr.cpp:49:0:
> /usr/include/OpenEXR/ImfRgbaFile.h:50:23: fatal error: ImfHeader.h: No such file
> or directory
> #include <ImfHeader.h>
> ^
> compilation terminated.
> make[1]: *** [tmp/QTP/qtpovray-3.80.1/source/base/image/openexr.o] Error 1
> make[1]: Leaving directory `/tmp/QTP/qtpovray-3.80.1/qt/libpovray'
> make: *** [sub-qt-libpovray-make_first-ordered] Error 2
>
> still needs adding the 'INCLUDEPATH += "/usr/include/OpenEXR"' line to the
> 'libpovray.pro' file to make it work. not to worry though, it is easy to patch
> from the (unwritten as yet :-)) qtpovray.SlackBuild script.
Or, Slackware could update to a post-Ming Dynasty copy of OpenEXR which
correctly uses
#include "ImfHeader.h"
:)
I do want to make a note somewhere of how to work around Neolithic
OpenEXR...
Or, the customer is always right and I'll figure out how to make a
qtpovray.SlackBuild. In all my years of Slackware, I never did that. I
always just downloaded source and built.
--
dik
Rendered 328976 of 330000 (99%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
dick balaska <dic### [at] buckosoftcom> wrote:
> On 07/21/2018 09:36 AM, jr wrote:
> >> It is also rumored to build and run on Slackware 14.1
> > "out of the box", no.
> > still needs adding the 'INCLUDEPATH += "/usr/include/OpenEXR"' line to the
> > 'libpovray.pro' file to make it work. not to worry though, it is easy to patch
> > from the (unwritten as yet :-)) qtpovray.SlackBuild script.
>
> Or, Slackware could update to a post-Ming Dynasty copy of OpenEXR which
> correctly uses
> #include "ImfHeader.h"
>
> :)
>
> I do want to make a note somewhere of how to work around Neolithic
> OpenEXR...
Slackware users recommend clay tablet(s) + stylus. ;-)
> Or, the customer is always right and I'll figure out how to make a
> qtpovray.SlackBuild. In all my years of Slackware, I never did that. I
> always just downloaded source and built.
you could. or, providing you don't mind deviation from Slackware "policy" to
install under '/usr/', I can post one in a day or two (rigged to install under
'/usr/local/' where all my povray stuff goes).
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
"jr" <cre### [at] gmailcom> wrote:
> dick balaska <dic### [at] buckosoftcom> wrote:
> > Or, the customer is always right and I'll figure out how to make a
> > qtpovray.SlackBuild. In all my years of Slackware, I never did that. I
> > always just downloaded source and built.
>
> you could. or, providing you don't mind deviation from Slackware "policy" to
> install under '/usr/', I can post one in a day or two (rigged to install under
> '/usr/local/' where all my povray stuff goes).
on second thoughts, perhaps you *should* write the package script. I just found
out that your 'Makefile's do not honour the 'DESTDIR' variable. ouch. have fun..
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Well, I've played around with this, and it is of course different - but I think
that even after giving it some time to get past the adjustment phase, I find
certain things a bit awkward.
The right-click to "select for rendering" is a real mistake waiting to happen -
I think most folks are used to rendering the scene in the selected tab, and even
if this was the original default POV-Ray, I think that would be the intuitively
expected behaviour.
I currently have a scene NOT in the /home/oem/documents directory that I'd like
to edit and render. It's not at all clear how to do that.
The use of the screen real estate doesn't seem conducive to writing scenes - at
least for me. I don't really need to see the file directory the whole time, nor
even the message pane. Though having the option to put the message pane as a
vertical strip where the file directory currently is would be nice I think.
Vertically stacking the scene tabs rather than trying to cram them on screen
horizontally would be the best way to arrange them I think - even with the
official distribution (I know, it's a Windows editor...)
Adding some additional color options would be great, or at least having the full
range of available coloring in the usual Win editor - colored numerical values,
x, y, z, vectors, and other reserved keywords.
The docking behaviour of the render window took a bit of time to grapple with.
I mistakenly docked it above the coding tabs and it was pretty challenging to
get it resized and put back into the default position. It's also "always on
top" which I think should be an option that can be toggled.
The resource filter thing is also a bit confusing. It seems to do the opposite
of what the description implies ... but that could just be me.
Clicking the "NEW" button/icon tries to open something "under" the currently
selected filename instead of "in" the current directory.
"Insert" button/icon currently does nothing that I can see.
I do very much like the line numbering - that's much better than just showing
what line the cursor is currently on.
I also like the option to put some of the comments and keywords in BOLD text.
Thanks for getting this all set up and running :) I'm happy to have started
the switch from M$, and look forward to (re)learning some of the pre- and
post-render commands that can be used, and other helpful tools as well.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 07/29/2018 02:09 PM, Bald Eagle wrote:
Thank you for the feedback.
> Well, I've played around with this, and it is of course different - but I think
> that even after giving it some time to get past the adjustment phase, I find
> certain things a bit awkward.
>
> The right-click to "select for rendering" is a real mistake waiting to happen -
> I think most folks are used to rendering the scene in the selected tab, and even
> if this was the original default POV-Ray, I think that would be the intuitively
> expected behaviour.
I can change it to a "soft default". If no file is "select for
rendering", then use the current displayed file. I've actually caught
myself doing this with the multiple virgin virtual machines I've been
running. (open a file, click render, um what? oh yeah...)
http://www.buckosoft.com/qtpovray/bugzilla/show_bug.cgi?id=4
(My next band is going to be called Virgin Virtual Machines)
>
> I currently have a scene NOT in the /home/oem/documents directory that I'd like
> to edit and render. It's not at all clear how to do that.
Currently, you can create another workspace, which is probably not what
you want to do.
http://www.buckosoft.com/qtpovray/bugzilla/show_bug.cgi?id=5
>
> The use of the screen real estate doesn't seem conducive to writing scenes - at
> least for me. I don't really need to see the file directory the whole time, nor
> even the message pane. Though having the option to put the message pane as a
> vertical strip where the file directory currently is would be nice I think.
You can do that now.
http://www.buckosoft.com/qtpovray/g/qtpovrayVerticalConsole.png
>
> Vertically stacking the scene tabs rather than trying to cram them on screen
> horizontally would be the best way to arrange them I think - even with the
> official distribution (I know, it's a Windows editor...)
The file list gives you a vertical list of the files, if you had some
organization. It sounds like you're scatterbrained. ;)
http://www.buckosoft.com/qtpovray/bugzilla/show_bug.cgi?id=6
>
> Adding some additional color options would be great, or at least having the full
> range of available coloring in the usual Win editor - colored numerical values,
> x, y, z, vectors, and other reserved keywords.
I agree. I always wanted to revisit that. I miss having a red "=+"
>
> The docking behaviour of the render window took a bit of time to grapple with.
> I mistakenly docked it above the coding tabs and it was pretty challenging to
> get it resized and put back into the default position.
That's a feature of the Qt toolkit. I agree it can be tedious. I've
wished I could blame it on my slow PC not keeping up, but my PC isn't
slow. I like to move the render window to my other monitor, which is
far, and that is tedious too. (If the mouse gets ahead of the window, it
loses it.)
> It's also "always on
> top" which I think should be an option that can be toggled.
I *may* be able to do something about that.
http://www.buckosoft.com/qtpovray/bugzilla/show_bug.cgi?id=7
>
> The resource filter thing is also a bit confusing. It seems to do the opposite
> of what the description implies ... but that could just be me.
Hmm, I'll re-read the doc. qtpovray is modeled on eclipse, which uses
an *exclude* filter system. I prefer that to Qt's built in filter
system which is an *include* model.
>
> Clicking the "NEW" button/icon tries to open something "under" the currently
> selected filename instead of "in" the current directory.
I'll look at this further.
>
> "Insert" button/icon currently does nothing that I can see.
If you open the configure dialog, are the checkmarks all green?
http://www.buckosoft.com/qtpovray/configDirs.html
and
http://www.buckosoft.com/qtpovray/g/qtpovPreferencesSystem.png
Did you install qtpovray-extras?
>
> I do very much like the line numbering - that's much better than just showing
> what line the cursor is currently on.
>
> I also like the option to put some of the comments and keywords in BOLD text.
>
>
>
> Thanks for getting this all set up and running :) I'm happy to have started
> the switch from M$, and look forward to (re)learning some of the pre- and
> post-render commands that can be used, and other helpful tools as well.
Do you want to do post-render shellouts? I don't support that (yet).
It might just work, but I never do that. I at least have to test it.
http://www.buckosoft.com/qtpovray/bugzilla/show_bug.cgi?id=8
Thanks again for being a valued customer. :)
--
dik
Rendered 328976 of 330000 (99%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hello,
I installed qtpovray in my lubuntu 16.04 using the ppa for automatic updates.
After my first test using "optics.pov" i got this parse error from the povray's
output:
"Parse Error: Macros require #version 3.1 or later but #version 3.00 is set.
at File: colors.inc Line: 167 Col: 2"
Very rare message. The colors.inc file is standard; i have not touched in any way. I
don't know how to fix this because the #version directive was not modified at all.
--
hugo giulietti <hug### [at] gmailcom>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 31.07.2018 um 12:03 schrieb hugo giulietti:
> Hello,
>
> I installed qtpovray in my lubuntu 16.04 using the ppa for automatic updates.
> After my first test using "optics.pov" i got this parse error from the povray's
output:
>
> "Parse Error: Macros require #version 3.1 or later but #version 3.00 is set.
> at File: colors.inc Line: 167 Col: 2"
>
> Very rare message. The colors.inc file is standard; i have not touched in any way. I
don't know how to fix this because the #version directive was not modified at all.
>
That's seriously odd. Please verify that line 13 of `colors.inc` reads
`#version 3.5;`
If that's not the case, for some obscure reason you have a far outdated
version of the file.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 07/31/2018 07:32 AM, clipka wrote:
> Am 31.07.2018 um 12:03 schrieb hugo giulietti:
>> Hello,
>>
>> I installed qtpovray in my lubuntu 16.04 using the ppa for automatic updates.
...
>>
>
> That's seriously odd. Please verify that line 13 of `colors.inc` reads
> `#version 3.5;`
>
> If that's not the case, for some obscure reason you have a far outdated
> version of the file.
>
Also check the environment variable POVINI is not pointing at an old
povray.ini file which might itself be pointing to old include libraries.
'echo $POVINI' in an xterm window to check.
Bill P.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
It reads #version 3.5
xD I installed qtpovray just 2-3 hours ago! It's updated! (i hope so...)
I have not modified anything. Just run a test and the error comes up into the command
output.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I think that qtpovray is using the pre-configured default path
/usr/share/qtpovray-3.8/include
Also, the error is indicating the reserved word "Macro" at column 2 requires a version
>= 3.0 but version in use is 3.7
On Tue, 31 Jul 2018 07:44:04 -0400
William F Pokorny <ano### [at] anonymousorg> wrote:
> On 07/31/2018 07:32 AM, clipka wrote:
> > Am 31.07.2018 um 12:03 schrieb hugo giulietti:
> >> Hello,
> >>
> >> I installed qtpovray in my lubuntu 16.04 using the ppa for automatic updates.
> ...
> >>
> >
> > That's seriously odd. Please verify that line 13 of `colors.inc` reads
> > `#version 3.5;`
> >
> > If that's not the case, for some obscure reason you have a far outdated
> > version of the file.
> >
>
> Also check the environment variable POVINI is not pointing at an old
> povray.ini file which might itself be pointing to old include libraries.
>
> 'echo $POVINI' in an xterm window to check.
>
> Bill P.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On second test, using "cornell.pov" (it is not using "includes") the output says that
i am using
an old version but the actual version is 3.7.
The output result cornell.png is a pure black image.
Here is the output command pane:
chdir: /home/hugo/source/povray
command: +Icornell.pov
Persistence of Vision(tm) Ray Tracer Version 3.8.0-alpha.9606898.unofficial
This is an unofficial version compiled by:
Dick Balaska - qtpovray edition <dic### [at] buckosoftcom>
The POV-Ray Team is not responsible for supporting this version.
POV-Ray is based on DKBTrace 2.12 by David K. Buck & Aaron A. Collins
Copyright 1991-2018 Persistence of Vision Raytracer Pty. Ltd.
Primary Persistence of Vision(tm) Ray Tracer Version 3.8.0-alpha.9606898.unoffic
ial Architects/Developers: (Alphabetically)
Chris Cason Thorsten Froehlich Christoph Lipka
With Assistance From: (Alphabetically)
Nicolas Calimet Jerome Grimbert James Holsenback Christoph Hormann
Nathan Kopp Juha Nieminen William F. Pokorny
Past Contributors: (Alphabetically)
Steve Anger Eric Barish Dieter Bayer David K. Buck
Nicolas Calimet Chris Cason Aaron A. Collins Chris Dailey
Steve Demlow Andreas Dilger Alexander Enzmann Dan Farmer
Thorsten Froehlich Mark Gordon Jerome Grimbert James Holsenback
Christoph Hormann Mike Hough Chris Huff Kari Kivisalo
Nathan Kopp Lutz Kretzschmar Christoph Lipka Jochen Lippert
Pascal Massimino Jim McElhiney Douglas Muir Juha Nieminen
Ron Parker William F. Pokorny Bill Pulver Eduard Schwan
Wlodzimierz Skiba Robert Skinner Yvo Smellenbergh Zsolt Szalavari
Scott Taylor Massimo Valentini Timothy Wegner Drew Wells
Chris Young
Other contributors are listed in the documentation.
Support libraries used by POV-Ray:
ZLib 1.2.8, Copyright 1995-2012 Jean-loup Gailly and Mark Adler
LibPNG 1.2.54, Copyright 1998-2012 Glenn Randers-Pehrson
LibJPEG 8, Copyright 1991-2016 Thomas G. Lane, Guido Vollbeding
LibTIFF 4.0.6, Copyright 1988-1997 Sam Leffler, 1991-1997 SGI
Boost 1.58, http://www.boost.org/
OpenEXR 2.2.0 and IlmBase 2.2.0, Copyright (c) 2002-2011 Industrial Light &
Magic.
Parser Options
Input file: cornell.pov
Remove bounds........On
Split unions.........Off
Library paths:
/usr/share/qtpovray-3.8/include
Clock value: 0,000 (Animation off)
Image Output Options
Image resolution.....800 by 600 (rows 1 to 600, columns 1 to 800).
Output file..........cornell.png, 24 bpp PNG
Dithering............Off
Graphic display......On (gamma: sRGB)
Mosaic preview.......Off
Continued trace......Off
Information Output Options
All Streams to console..........On
Debug Stream to console.........On
Fatal Stream to console.........On
Render Stream to console........On
Statistics Stream to console....On
Warning Stream to console.......On
Parse Warning: The scene finished parsing with a language version set to v3.1 or
earlier. Full backward compatibility with scenes requiring support for bugs in POV-Ray
version v3.1 or earlier is not guaranteed. Please use POV-Ray v3.5 or earlier if your
scene depends on rendering defects caused by these bugs.
----------------------------------------------------------------------------
Parser Statistics
----------------------------------------------------------------------------
Finite Objects: 31
Infinite Objects: 0
Light Sources: 9
Total: 40
----------------------------------------------------------------------------
Parser Time
Parse Time: 0 hours 0 minutes 0 seconds (0.001 seconds)
using 1 thread(s) with 0.-01 CPU-seconds total
Bounding Time: 0 hours 0 minutes 0 seconds (0.000 seconds)
using 1 thread(s) with 0.-01 CPU-seconds total
----------------------------------------------------------------------------
Render Options
Quality: 9
Bounding boxes.......On Bounding threshold: 3
Antialiasing.........Off
----------------------------------------------------------------------------
Render Statistics
Image Resolution 800 x 600
----------------------------------------------------------------------------
Pixels: 480000 Samples: 0 Smpls/Pxl: 0,00
Rays: 480000 Saved: 0 Max Level: 1/5
----------------------------------------------------------------------------
Ray->Shape Intersection Tests Succeeded Percentage
----------------------------------------------------------------------------
Box 2031 2031 100,00
Triangle 832055 443671 53,32
Bounding Box 7826984 2598210 33,20
----------------------------------------------------------------------------
----------------------------------------------------------------------------
----------------------------------------------------------------------------
Render Time:
Photon Time: No photons
Radiosity Time: No radiosity
Trace Time: 0 hours 0 minutes 1 seconds (1.827 seconds)
using 4 thread(s) with 0.-04 CPU-seconds total
POV-Ray finished
On Tue, 31 Jul 2018 07:03:38 -0300
hugo giulietti <hug### [at] gmailcom> wrote:
> Hello,
>
> I installed qtpovray in my lubuntu 16.04 using the ppa for automatic updates.
> After my first test using "optics.pov" i got this parse error from the povray's
output:
>
> "Parse Error: Macros require #version 3.1 or later but #version 3.00 is set.
> at File: colors.inc Line: 167 Col: 2"
>
> Very rare message. The colors.inc file is standard; i have not touched in any way. I
don't know how to fix this because the #version directive was not modified at all.
>
> --
> hugo giulietti <hug### [at] gmailcom>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 18-07-31 à 08:38, hugo giulietti a écrit :
> On second test, using "cornell.pov" (it is not using "includes") the output says
that i am using
> an old version but the actual version is 3.7.
>
> The output result cornell.png is a pure black image.
>
> Render Time:
> Photon Time: No photons
> Radiosity Time: No radiosity
> Trace Time: 0 hours 0 minutes 1 seconds (1.827 seconds)
> using 4 thread(s) with 0.-04 CPU-seconds total
> POV-Ray finished
>
>
>
>
Very strange. cornel.pov IS a radiosity scene, but it say "No radiosity".
Make sure to add
#version 3.7;
or
#version version;
as the first line of your scene.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 31.07.2018 um 14:03 schrieb hugo giulietti:
> I think that qtpovray is using the pre-configured default path
>
> /usr/share/qtpovray-3.8/include
>
> Also, the error is indicating the reserved word "Macro" at column 2 requires a
version >= 3.0 but version in use is 3.7
Technically, the `#version` setting at the point in question is (or
should be) 3.5.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 31.07.2018 um 13:49 schrieb hugo giulietti:
>
> It reads #version 3.5
Then the error shouldn't be happening. Are you sure that's indeed the
very file that is pulled in?
Please try adding the following line just below the `#version 3.5;` in
`colors.inc`:
#debug concat("version in colors.inc is ",str(version,0,2),"\n")
Then try again rendering `optics.pov`. You should get a message reading
`version in colors.inc is 3.50`.
If the message doesn't appear, a different `colors.inc` is pulled in.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Confirmed using /usr/share/qtpovray-3.8/include/colors.inc
The message does appear and say :
Statistics Stream to console....On
Warning Stream to console.......On
version in colors.inc is 3,00
Parse Error: Macros require #version 3.1 or later but #version 3.00 is set.
at File: colors.inc Line: 167 Col: 2
Fatal error in parser: Cannot parse input.
Render failed
On Tue, 31 Jul 2018 21:49:29 +0200
clipka <ano### [at] anonymousorg> wrote:
> #debug concat("version in colors.inc is ",str(version,0,2),"\n")
--
hugo giulietti <hug### [at] gmailcom>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
It is my fault, Alain. I did not mention that the scene file was refused to
render because some radiosity's declarations; so i deleted all the "radios
ity{}" block and reder again just for confirm the "#version" issue
BUT if i re-render the scene file *with* "radiosity{}" block empty, the th
ings does not changes in any way.
On Tue, 31 Jul 2018 13:25:44 -0400
Alain <kua### [at] videotronca> wrote:
> Le 18-07-31 à 08:38, hugo giulietti a écrit :
> > On second test, using "cornell.pov" (it is not using "includes") the ou
tput says that i am using
> > an old version but the actual version is 3.7.
> >
> > The output result cornell.png is a pure black image.
> >
>
>
> > Render Time:
> > Photon Time: No photons
> > Radiosity Time: No radiosity
> > Trace Time: 0 hours 0 minutes 1 seconds (1.827 seconds)
> > using 4 thread(s) with 0.-04 CPU-seconds total
> > POV-Ray finished
> >
> >
> >
> >
>
>
> Very strange. cornel.pov IS a radiosity scene, but it say "No radiosity".
>
> Make sure to add
> #version 3.7;
> or
> #version version;
>
> as the first line of your scene.
--
hugo giulietti <hug### [at] gmailcom>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 31.07.2018 um 23:49 schrieb hugo giulietti:
>
> Confirmed using /usr/share/qtpovray-3.8/include/colors.inc
>
> The message does appear and say :
>
> Statistics Stream to console....On
> Warning Stream to console.......On
> version in colors.inc is 3,00
So you currently have
#version 3.5;
#debug concat("version in colors.inc is ",str(version,0,2),"\n")
in that `colors.inc`, right?
Then that's certainly a bug. Somehow the `#version` statement fails to
set the correct effective language version.
I also notice that the debug message says `3,00`, rather than `3.00`. Is
that a typo, or is that in the actual message?
In the latter case, that's another bug.
Oh, can you please try the following in an empty .pov file:
#declare Foo = 3.14;
#declare Bar = 314/100;
#debug concat("Foo is ", str(Foo,0,2), "\n")
#debug concat("Bar is ", str(Bar,0,2), "\n")
This /should/ output
Foo is 3.14
Bar is 3.14
but I have a hunch that it might output
Foo is 3,00
Bar is 3,14
in which case I guess I know what the problem may be.
Say, your name sounds italian, and in Italy they normally use commas as
decimal separators (just as they do here in Germany), right?
@dick: Are you actively changing the C/C++ locale in qtpovray, or do you
happen to know whether Qt does so by default? (buzzword `setlocale`)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 01.08.2018 um 10:33 schrieb clipka:
> @dick: Are you actively changing the C/C++ locale in qtpovray, or do you
> happen to know whether Qt does so by default? (buzzword `setlocale`)
Never mind that question. According to StackOverflow, QCoreApplication
(on Unix/Linux) does indeed invoke
setlocale(LC_ALL,"")
which screws up things. The suggested solution is to invoke
setlocale(LC_ALL,"C")
right after initialization of QCoreApplication or QApplication. See here:
https://stackoverflow.com/questions/25661295/why-does-qcoreapplication-call-setlocalelc-all-by-default-on-unix-linux
Unfortunately there is no portable way to fix this in POV-Ray itself,
short of completely re-writing all code that currently depends on the
C/C++ locale setting. At the moment, there is probably a host of such
locale-dependent sections in the POV-Ray source code, only very few of
which have already been identified as such.
The C and C++ standards guarantee that at program startup the locale is
set to the "C" locale, and all locale-dependent code in POV-Ray relies
on this remaining unchanged.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 07/31/2018 06:03 AM, hugo giulietti wrote:
> Hello,
>
> I installed qtpovray in my lubuntu 16.04 using the ppa for automatic updates.
> After my first test using "optics.pov" i got this parse error from the povray's
output:
>
> "Parse Error: Macros require #version 3.1 or later but #version 3.00 is set.
> at File: colors.inc Line: 167 Col: 2"
>
> Very rare message. The colors.inc file is standard; i have not touched in any way. I
don't know how to fix this because the #version directive was not modified at all.
>
Do you have other versions of POV-Ray installed?
Where did you get optics.pov from?
I assume you are trying optics.pov from
file:///usr/share/qtpovray-3.8/scenes/advanced/optics.pov
I assume you installed qtpovray-includes and qtpovray-extras
since you have colors.inc and optics.pov
What happens if you try "Basic scene 01 - Checkered plane" from the
insert menu?
I just tried it on two machines and it was fine.
ubuntu 16.04, which is my primary workstation
and
mint 18.3 which is a clean "install from the ppa" machine (no compiling,
no multiple working versions)
cornell.pov worked for me too.
file:///usr/share/qtpovray-3.8/scenes/radiosity/cornell.pov
---------------------------------------------------------------
What cpu are you using?
You don't have the "Dynamic optimizations:" in the banner. i.e.
Support libraries used by POV-Ray:
ZLib 1.2.8, Copyright 1995-2012 Jean-loup Gailly and Mark Adler
LibPNG 1.2.54, Copyright 1998-2012 Glenn Randers-Pehrson
LibJPEG 8, Copyright 1991-2016 Thomas G. Lane, Guido Vollbeding
LibTIFF 4.0.6, Copyright 1988-1997 Sam Leffler, 1991-1997 SGI
Boost 1.58, http://www.boost.org/
OpenEXR 2.2.0 and IlmBase 2.2.0, Copyright (c) 2002-2011 Industrial
Light &
Magic.
Dynamic optimizations:
CPU detected: Intel,SSE2,AVX,AVX2,FMA3
Noise generator: avx2fma3-intel (hand-optimized by Intel)
Parser Options
Input file: cornell.pov
Remove bounds........On
Split unions.........Off
Library paths:
/usr/share/qtpovray-3.8/include
Clock value: 0.000 (Animation off)
...
-------------------------------------------------------------------
This is a really strange problem. It's like the parser is broken.
Like clipka said, in your colors.inc problem, the version is set at line
#13, yet is reporting something different at line #167. This makes no
sense (so far).
https://github.com/dickbalaska/qtpovray/blob/qtpovray/distribution/include/colors.inc
--
dik
Rendered 328976 of 330000 (99%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 08/01/2018 05:02 AM, clipka wrote:
> Am 01.08.2018 um 10:33 schrieb clipka:
>
>> @dick: Are you actively changing the C/C++ locale in qtpovray, or do you
>> happen to know whether Qt does so by default? (buzzword `setlocale`)
>
> Never mind that question. According to StackOverflow, QCoreApplication
> (on Unix/Linux) does indeed invoke
>
> setlocale(LC_ALL,"")
>
> which screws up things. The suggested solution is to invoke
>
> setlocale(LC_ALL,"C")
>
> right after initialization of QCoreApplication or QApplication. See here:
>
>
https://stackoverflow.com/questions/25661295/why-does-qcoreapplication-call-setlocalelc-all-by-default-on-unix-linux
>
Reading that, it seems that I need to wrap POV-Ray with
setlocale(LC_ALL,"C") and let Qt be Qt. Like, call setlocale when
creating a session. Hmm, that will be messy; when getting a message from
POV-Ray I would have to setlocale(LC_ALL, "") and then set it back to
"C" after processing the message.
But, iirc, the povray parser doesn't like umlauted characters ("C"
locale) so maybe I should just force "C" all through the program and
abandon hope of spiffy translations.
>
> Unfortunately there is no portable way to fix this in POV-Ray itself,
> short of completely re-writing all code that currently depends on the
> C/C++ locale setting. At the moment, there is probably a host of such
> locale-dependent sections in the POV-Ray source code, only very few of
> which have already been identified as such.
>
> The C and C++ standards guarantee that at program startup the locale is
> set to the "C" locale, and all locale-dependent code in POV-Ray relies
> on this remaining unchanged.
>
--
dik
Rendered 328976 of 330000 (99%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 01.08.2018 um 11:53 schrieb dick balaska:
> On 08/01/2018 05:02 AM, clipka wrote:
>> Am 01.08.2018 um 10:33 schrieb clipka:
>>
>>> @dick: Are you actively changing the C/C++ locale in qtpovray, or do you
>>> happen to know whether Qt does so by default? (buzzword `setlocale`)
>>
>> Never mind that question. According to StackOverflow, QCoreApplication
>> (on Unix/Linux) does indeed invoke
>>
>> setlocale(LC_ALL,"")
>>
>> which screws up things. The suggested solution is to invoke
>>
>> setlocale(LC_ALL,"C")
>>
>> right after initialization of QCoreApplication or QApplication. See here:
>>
>>
https://stackoverflow.com/questions/25661295/why-does-qcoreapplication-call-setlocalelc-all-by-default-on-unix-linux
>>
>
> Reading that, it seems that I need to wrap POV-Ray with
> setlocale(LC_ALL,"C") and let Qt be Qt. Like, call setlocale when
> creating a session. Hmm, that will be messy; when getting a message from
> POV-Ray I would have to setlocale(LC_ALL, "") and then set it back to
> "C" after processing the message.
No, that would just risk screwing up things even more. Unfortunately,
the locale is global to the entire process, not thread-local, so you
can't just tamper with it while there's other threads running and
potentially invoking locale-dependent code.
From what I understand, Qt has its own locale mechanism, and only calls
`setlocale(LC_ALL,"")` for (a) Unix/Linux tradition and (b) to probe a
thing or two during QCoreApplication initialization; it doesn't seem to
need it to /remain/ set to that at all.
So once QApplication or QCoreApplication has been initialized, it should
be safe to just invoke `setlocale(LC_ALL,"C")` once and never touch the
C/C++ locale again afterwards.
There's a potential workaround for GNU/Linux machines in invoking
`uselocale()` during thread initialization, which sets the locale for
the individual thread only. However, this function is not part of the
C/C++ standard.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
My locale is set wide system to spanish. Just for confirm, i added this lines to
cornell.pov:
#version 3.7;
#debug concat("version in cornell.pov is ",str(version,0,2),"\n")
#declare Foo = 3.14;
#declare Bar = 314/100;
#debug concat("Foo is ", str(Foo,0,2), "\n")
#debug concat("Bar is ", str(Bar,0,2), "\n")
and the output result is:
Render Stream to console........On
Statistics Stream to console....On
Warning Stream to console.......On
version in cornell.pov is 3,00
Foo is 3,00
Bar is 3,14
Parse Warning: In POV-Ray v3.5 and later a radiosity{}-block will automatically turn
on radiosity if the output quality is set to 9 or higher. Read the documentation to
find out more about radiosity changes!
It's clear. My decimal separator is a spanish "," (comma) rather the english "."
(point)
On Wed, 1 Aug 2018 10:33:07 +0200
clipka <ano### [at] anonymousorg> wrote:
> Am 31.07.2018 um 23:49 schrieb hugo giulietti:
> >
> > Confirmed using /usr/share/qtpovray-3.8/include/colors.inc
> >
> > The message does appear and say :
> >
> > Statistics Stream to console....On
> > Warning Stream to console.......On
> > version in colors.inc is 3,00
>
> So you currently have
>
> #version 3.5;
> #debug concat("version in colors.inc is ",str(version,0,2),"\n")
>
> in that `colors.inc`, right?
>
> Then that's certainly a bug. Somehow the `#version` statement fails to
> set the correct effective language version.
>
>
> I also notice that the debug message says `3,00`, rather than `3.00`. Is
> that a typo, or is that in the actual message?
>
> In the latter case, that's another bug.
>
>
> Oh, can you please try the following in an empty .pov file:
>
> #declare Foo = 3.14;
> #declare Bar = 314/100;
> #debug concat("Foo is ", str(Foo,0,2), "\n")
> #debug concat("Bar is ", str(Bar,0,2), "\n")
>
> This /should/ output
>
> Foo is 3.14
> Bar is 3.14
>
> but I have a hunch that it might output
>
> Foo is 3,00
> Bar is 3,14
>
> in which case I guess I know what the problem may be.
>
>
> Say, your name sounds italian, and in Italy they normally use commas as
> decimal separators (just as they do here in Germany), right?
>
>
> @dick: Are you actively changing the C/C++ locale in qtpovray, or do you
> happen to know whether Qt does so by default? (buzzword `setlocale`)
--
hugo giulietti <hug### [at] gmailcom>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I will create a "C" locale version and push that out tonight.
On 08/01/2018 04:22 PM, hugo giulietti wrote:
> My locale is set wide system to spanish. Just for confirm, i added this lines to
cornell.pov:
>
> #version 3.7;
> #debug concat("version in cornell.pov is ",str(version,0,2),"\n")
> #declare Foo = 3.14;
> #declare Bar = 314/100;
> #debug concat("Foo is ", str(Foo,0,2), "\n")
> #debug concat("Bar is ", str(Bar,0,2), "\n")
>
>
> and the output result is:
>
>
> Render Stream to console........On
> Statistics Stream to console....On
> Warning Stream to console.......On
> version in cornell.pov is 3,00
> Foo is 3,00
> Bar is 3,14
> Parse Warning: In POV-Ray v3.5 and later a radiosity{}-block will automatically turn
on radiosity if the output quality is set to 9 or higher. Read the documentation to
find out more about radiosity changes!
>
> It's clear. My decimal separator is a spanish "," (comma) rather the english "."
(point)
--
dik
Rendered 328976 of 330000 (99%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 1 Aug 2018 05:33:20 -0400
dick balaska <dic### [at] buckosoftcom> wrote:
> On 07/31/2018 06:03 AM, hugo giulietti wrote:
> > Hello,
> >
> > I installed qtpovray in my lubuntu 16.04 using the ppa for automatic updates.
> > After my first test using "optics.pov" i got this parse error from the povray's
output:
> >
> > "Parse Error: Macros require #version 3.1 or later but #version 3.00 is set.
> > at File: colors.inc Line: 167 Col: 2"
> >
> > Very rare message. The colors.inc file is standard; i have not touched in any way.
I don't know how to fix this because the #version directive was not modified at all.
> >
>
> Do you have other versions of POV-Ray installed?
>
> Where did you get optics.pov from?
>
> I assume you are trying optics.pov from
> file:///usr/share/qtpovray-3.8/scenes/advanced/optics.pov
>
> I assume you installed qtpovray-includes and qtpovray-extras
> since you have colors.inc and optics.pov
>
Hi,
I have installed povray 3.7 from the Ubuntu repos, using the standard software
manager Synaptics. The optics.pov (and all demo scene files) are from this
installation.
I did not know that there is qtpovray-includes and qtpovray-extras. I have not
installed this packages. I will install these after posting this writing.
The installation of qtpovray installed a folder with *.inc files in:
/usr/share/qtpovray-3.8/include, so it is using that
folder.
> What happens if you try "Basic scene 01 - Checkered plane" from the
> insert menu?
>
> I just tried it on two machines and it was fine.
> ubuntu 16.04, which is my primary workstation
> and
> mint 18.3 which is a clean "install from the ppa" machine (no compiling,
> no multiple working versions)
>
> cornell.pov worked for me too.
> file:///usr/share/qtpovray-3.8/scenes/radiosity/cornell.pov
>
> ---------------------------------------------------------------
> What cpu are you using?
>
> You don't have the "Dynamic optimizations:" in the banner. i.e.
>
> Support libraries used by POV-Ray:
> ZLib 1.2.8, Copyright 1995-2012 Jean-loup Gailly and Mark Adler
> LibPNG 1.2.54, Copyright 1998-2012 Glenn Randers-Pehrson
> LibJPEG 8, Copyright 1991-2016 Thomas G. Lane, Guido Vollbeding
> LibTIFF 4.0.6, Copyright 1988-1997 Sam Leffler, 1991-1997 SGI
> Boost 1.58, http://www.boost.org/
> OpenEXR 2.2.0 and IlmBase 2.2.0, Copyright (c) 2002-2011 Industrial
> Light &
> Magic.
>
> Dynamic optimizations:
> CPU detected: Intel,SSE2,AVX,AVX2,FMA3
> Noise generator: avx2fma3-intel (hand-optimized by Intel)
>
> Parser Options
> Input file: cornell.pov
> Remove bounds........On
> Split unions.........Off
> Library paths:
> /usr/share/qtpovray-3.8/include
> Clock value: 0.000 (Animation off)
> ...
>
> -------------------------------------------------------------------
I'm using an very old 1-core cpu AMD Sempron LE-1150 2.0 Ghz without AVX,AVX2,FMA3
support *but* with SSE2 instructions. I don't know why these was not detected.
>
> This is a really strange problem. It's like the parser is broken.
> Like clipka said, in your colors.inc problem, the version is set at line
> #13, yet is reporting something different at line #167. This makes no
> sense (so far).
>
https://github.com/dickbalaska/qtpovray/blob/qtpovray/distribution/include/colors.inc
>
> --
> dik
> Rendered 328976 of 330000 (99%)
I think that the "macro" declaration in line 167 needs a "#version" > 3.1 but the
"detected" version is 3.0. Resolving
the version issue will resolve the macro issue. (I'm guessing)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 02.08.2018 um 00:15 schrieb hugo giulietti:
> Hi,
> I have installed povray 3.7 from the Ubuntu repos, using the standard software
manager Synaptics. The optics.pov (and all demo scene files) are from this
installation.
> I did not know that there is qtpovray-includes and qtpovray-extras. I have not
installed this packages. I will install these after posting this writing.
> The installation of qtpovray installed a folder with *.inc files in:
/usr/share/qtpovray-3.8/include, so it is using that
> folder.
The `qtpovray` package probably pulled in the other packages already.
Anyway, the include files are not at fault here. We've nailed down the
culprit to the locale settings.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Yeah! Solved.
Now qtpovray is working at 100% after the software actualization! Thanks dick, thanks
clipka!
On Wed, 1 Aug 2018 17:01:46 -0400
dick balaska <dic### [at] buckosoftcom> wrote:
> I will create a "C" locale version and push that out tonight.
>
>
> On 08/01/2018 04:22 PM, hugo giulietti wrote:
> > My locale is set wide system to spanish. Just for confirm, i added this lines to
cornell.pov:
> >
> > #version 3.7;
> > #debug concat("version in cornell.pov is ",str(version,0,2),"\n")
> > #declare Foo = 3.14;
> > #declare Bar = 314/100;
> > #debug concat("Foo is ", str(Foo,0,2), "\n")
> > #debug concat("Bar is ", str(Bar,0,2), "\n")
> >
> >
> > and the output result is:
> >
> >
> > Render Stream to console........On
> > Statistics Stream to console....On
> > Warning Stream to console.......On
> > version in cornell.pov is 3,00
> > Foo is 3,00
> > Bar is 3,14
> > Parse Warning: In POV-Ray v3.5 and later a radiosity{}-block will automatically
turn on radiosity if the output quality is set to 9 or higher. Read the documentation
to find out more about radiosity changes!
> >
> > It's clear. My decimal separator is a spanish "," (comma) rather the english "."
(point)
>
> --
> dik
> Rendered 328976 of 330000 (99%)
--
hugo giulietti <hug### [at] gmailcom>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
