 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 18/10/2018 à 00:01, dick balaska a écrit :
> On 10/16/2018 05:54 PM, Le_Forgeron wrote:
>
>>
>> On animation, the previous image is kept but darkened as new background.
>>
>
> I like that.
>
> That is an interesting render pattern in your sample image. Which is that?
>
Render_Block_Size=16
Render_Block_Step=3
Render_Pattern=4
with 12 threads, and 256 as height & width.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 10/16/18 5:54 PM, Le_Forgeron wrote:
> Le 10/10/2018 à 22:35, Le_Forgeron a écrit :
...
>
> There is LibSDL2 port (exclusive for linkage with LibSDL1.2), as well as
> a basic X11 (without alpha, as alpha is not handle by X11 core).
>
> The same binary can be used to choose the X11 or libsdl via command
> switch -y (2 for X11, 3 & 4 for libsdl, 1 for text), when more than one
> is detected. (-y is also --preview )
>
...
>
Playing some with your current hgpovray38 (45eb09ed7) with the thought
of creating a re-based branch of your windowing changes I can merge into
my version of POV-Ray.
Issue 1)
I can get an x11 window and a sdl2 window, but not an sdl window though
it looks like 'make' created and linked x11, sdl and sdl2. The options
which seemed to work were -y | --preview [x11 | sdl | text]. Is your
intention not to enable 'sdl1.2' if sdl2 is present or all 4 options as
it seemed to me you were saying above?
Issue 2)
I'm also attaching an image from the x11 option. I three times got
something like it where one block didn't update. On the first two
POV-Ray core dumped on closing the window/program exit. On the last -
for the attached image - POV-Ray closed the display (used +p) on
detecting but the POV-Ray process itself didn't exit. Wasn't burning any
CPU, it was just hung and I had to use the kill command from the command
line.
If I get some time next week I'll see if I can a debug compile to hang,
crash or both for more informatino. I had no trouble with SDL2 windows.
Ubunut 18.04 - same set up as you as far as I know.
Aside: Ignore the image's *_segfault.png suffix. I named it thinking
POV-Ray would crash on exit as had the previous two cases, but then it
hung instead.
Issue 3)
The x11 option is opening the preview on the screen where the command is
issued. The sdl2 option seems to always be opening on the primary
screen. Not dug any here though so perhaps something my screen dual
screen set up. The current 3.8 master follows your x11 preview screen
behavior in opening on the screen where the command was issued.
Bill P.
Post a reply to this message
Attachments:
Download 'x11_segfault.png' (53 KB)
Preview of image 'x11_segfault.png'
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2/2/19 12:16 PM, William F Pokorny wrote:
> On 10/16/18 5:54 PM, Le_Forgeron wrote:
> ...
>
> Playing some with your current hgpovray38 (45eb09ed7) with the thought
...
> Issue 2)
> I'm also attaching an image from the x11 option. I three times got
> something like it where one block didn't update. On the first two
> POV-Ray core dumped on closing the window/program exit. On the last -
> for the attached image - POV-Ray closed the display (used +p) on
> detecting but the POV-Ray process itself didn't exit. Wasn't burning any
> CPU, it was just hung and I had to use the kill command from the command
> line.
>
> If I get some time next week I'll see if I can a debug compile to hang,
> crash or both for more informatino. I had no trouble with SDL2 windows.
> Ubunut 18.04 - same set up as you as far as I know.
>
Not a compile with debugging, but had another hang at the very end with
+p. I used cntl-c this time to try and exit the hung process. Got
messages a little different though not sure if of much more use:
==== [Paused... Press p to resume] ====================================
Press p, q, enter or press button 1 over displayed image to continue...
POV-Ray finished
^Cterminate called after throwing an instance of
'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::lock_error>
>'
what(): boost: mutex lock failed in pthread_mutex_lock: Invalid argument
/home/pokorny/bin/pJG: line 21: 26191 Aborted (core dumped)
/run/shm/tmpDir/tmpUser/MyJG/bin/povray $@
>
>
Reminded again of :
https://github.com/POV-Ray/povray/issues/142
though I've not seen any hangs in your code as yet with sdl2 previews -
just x11 thus far.
---
The usual exit - where no blocks left 'un-displayed?' - and a cntl-c is
used instead of (p, q, enter or mouse 1) at the end normally shows:
==== [Paused... Press p to resume] ====================================
Press p, q, enter or press button 1 over displayed image to continue...^C
povray: received signal SIGINT: Interrupt; requested render cancel
POV-Ray finished
---
On the windows opening only on certain screens have found in further
playing the sdl2 and x11 options will both use my second screen if the
width is such that it fits on screen 1 but not screen 0. In other words,
both options seem to look for a screen size where the preview image will
fit if the first screen looked at isn't large enough.
Bill P.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 02/02/2019 à 18:16, William F Pokorny a écrit :
> On 10/16/18 5:54 PM, Le_Forgeron wrote:
>> Le 10/10/2018 à 22:35, Le_Forgeron a écrit :
> ...
>>
>> There is LibSDL2 port (exclusive for linkage with LibSDL1.2), as well as
>> a basic X11 (without alpha, as alpha is not handle by X11 core).
>>
>> The same binary can be used to choose the X11 or libsdl via command
>> switch -y (2 for X11, 3 & 4 for libsdl, 1 for text), when more than one
>> is detected. (-y is also --preview )
>>
> ...
>>
>
> Playing some with your current hgpovray38 (45eb09ed7) with the thought
> of creating a re-based branch of your windowing changes I can merge into
> my version of POV-Ray.
>
> Issue 1)
> I can get an x11 window and a sdl2 window, but not an sdl window though
> it looks like 'make' created and linked x11, sdl and sdl2. The options
> which seemed to work were -y | --preview [x11 | sdl | text]. Is your
> intention not to enable 'sdl1.2' if sdl2 is present or all 4 options as
> it seemed to me you were saying above?
It is not my intent. It was not my intent.
It is the direct consequence of libsdl being what they are.
They moved from 1.2 to 2.0, breaking backward compatibility of API, yet
keeping some identical signature (function name & parameter type) and
that has consequences : the initialization must be the one from the
library you intent to use, but having the same name, the linker might
pick either (i.e. the other one... ) so you cannot declare linkage for
both libraries (shared) at the same time.
I said linkage... well, guess who reuse the same name, in the same
workspace, with different values between both versions ?
You cannot even compile correctly if you get include from both libraries
in the same source. (they kept the SAME include-defence name, even when
the file are different... no mix of version at compilation time either)
hence, the detection during configure.
-X11 is the base (and you can have Xcursor if you dare as an option, but
it must be explicit), needed by both libsdl 1.2 and libsdl 2.0
(also if you have Xpm support, you get color icons, otherwise b&w old ones)
- if libsdl2.0 is there, it get selected, otherwise fallback to
libsdl1.2 if present.
>
> Issue 2)
> I'm also attaching an image from the x11 option. I three times got
> something like it where one block didn't update. On the first two
> POV-Ray core dumped on closing the window/program exit. On the last -
> for the attached image - POV-Ray closed the display (used +p) on
> detecting but the POV-Ray process itself didn't exit. Wasn't burning any
> CPU, it was just hung and I had to use the kill command from the command
> line.
Yep, I have also such kind of issues on X11 window, and despite having
focused on updating only the updated block, there might be some deeper
problem in current code (I oversimplified the old X11 code of povray,
dropping all the palette stuff and the double image buffering, and I'm
not sure I even merged late correction to scaled down window).
Lately, I even try to reinstall the setjmp/longjmp system, but it was a
worst idea. Handling X11 Destroy is still a problem (hit the close
button while rendering... and hope! Not a satisfying state)
>
> If I get some time next week I'll see if I can a debug compile to hang,
> crash or both for more informatino. I had no trouble with SDL2 windows.
> Ubunut 18.04 - same set up as you as far as I know.
Yes SDL2 is working fine, but THERE IS NO ICON ! ("it's not SDL2
problem" to read a ppm to make the RGBImage to use as icon, painful
mentality, when they have sound engines around)
Me ranting ? Maybe.
>
> Aside: Ignore the image's *_segfault.png suffix. I named it thinking
> POV-Ray would crash on exit as had the previous two cases, but then it
> hung instead.
>
> Issue 3)
> The x11 option is opening the preview on the screen where the command is
> issued. The sdl2 option seems to always be opening on the primary
> screen. Not dug any here though so perhaps something my screen dual
> screen set up. The current 3.8 master follows your x11 preview screen
> behavior in opening on the screen where the command was issued.
The opening on primary of SDL2 is not my design.
If you feel good at it, go and propose your changes.
X11 is more liberal, and the opening is delegated to the window manager
on the display. On dual-screen, it usually stays near the active cursor,
but you can set your preference to change it (in the limit of the window
manager capabilities): there is CLASS name and usual stuff for user
preference.
My problem(s) so far with X11 are:
- I'm not confident on multithreaded update of window
- the handling of the event queues, in both directions, at the end of
life (on empty scene to render, it might be some race condition and it
is painful to understand)
- destruction & reallocation of resources by two programs (i.e. two
consecutive run) seems to hit on the same pointers/window id/... which
can become messy when the first one ends with a broken pipe and
unprocessed events. (such as getting a creation of the second processed
before the deletion of the first .... which collides and fuck the second
process at random)
(remember the window id are a shared resource in the X11 screen, which
can be referred by whatever processes know them)
On the good side of X11, it's far easier to redirect over modern ssh.
>
> Bill P.
>
>
Jérôme.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2/5/19 3:55 PM, Le_Forgeron wrote:
> Le 02/02/2019 à 18:16, William F Pokorny a écrit :
...
Thanks for the detailed background.
>
> The opening on primary of SDL2 is not my design.
> If you feel good at it, go and propose your changes.
>
Understand and I don't feel good at it, but might hack at some point.
> X11 is more liberal, and the opening is delegated to the window manager
> on the display. On dual-screen, it usually stays near the active cursor,
> but you can set your preference to change it (in the limit of the window
> manager capabilities): there is CLASS name and usual stuff for user
> preference.
Good to know.
>
> My problem(s) so far with X11 are:
> - I'm not confident on multithreaded update of window
> - the handling of the event queues, in both directions, at the end of
> life (on empty scene to render, it might be some race condition and it
> is painful to understand)
> - destruction & reallocation of resources by two programs (i.e. two
> consecutive run) seems to hit on the same pointers/window id/... which
> can become messy when the first one ends with a broken pipe and
> unprocessed events. (such as getting a creation of the second processed
> before the deletion of the first .... which collides and fuck the second
> process at random)
> (remember the window id are a shared resource in the X11 screen, which
> can be referred by whatever processes know them)
>
> On the good side of X11, it's far easier to redirect over modern ssh.
>
...
> Jérôme.
>
OK. Thinking, for now, I'll try to create a branch from your work for my
working version of POV-Ray. Day to day using just the defaulted SDL2
routinely. I can that way at least look for buggy or interesting
behavior related to SDL2. Plus, I might be able to try one or more of
the experiments I had in mind off your SDL2 update given I failed to get
an SDL2 version working on my own.
Bill P.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
BGimeno <bru### [at] gmail com> wrote:
> I have tried to compile the latest version 3.8.0.9861167 alpha and as in
> the official version that I compiled I still have the problem that it
> does not show the image while it is generated. While compiling it shows
> the following message,
>
> Built-in features:
> I/O restrictions: enabled
> X Window display: disabled
> Supported image formats: gif tga iff ppm pgm hdr png jpeg tiff
> Unsupported image formats: openexr
>
> Compilation settings:
> Build architecture: x86_64-pc-linux-gnu
> Built/Optimized for: x86_64-pc-linux-gnu (using -march=native)
> Compiler vendor: gnu
> Compiler version: g++ 7
> Compiler flags: -pipe -Wno-multichar -Wno-write-strings
> -fno-enforce-eh-specs -Wno-non-template-friend -s -O3 -ffast-math
> -march=native -pthread
> Libraries: -ltiff -ljpeg -lpng -lz -lrt -lm -lboost_thread
> -pthread -lboost_system
>
>
>
> Note that in the Built-in features the X Windows display is disabled.
>
> I have followed the detailed instructions in
> https://github.com/POV-Ray/povray/blob/master/unix/README.md
> and I think that the dependencies listed do not include the necessary X
> server or XCygwin or X11 or XDisplay or whatever it is called.
>
> Can someone tell me what is needed to complete the installation?
>
> Thank you very much
> B. Gimeno
Sorry to necro this thread but ...
Is this issue being addressed in the current 3.8 branch? I'm compiling
povray-3.8.0-alpha.10064268 on a Ubuntu-based distro after being advised it's
the most stable of the development versions. However, as others have posted
using either SDL1.2 or 2.0 throws errors in the compilation phase. I could
simply bash-script up a solution to invoke something like LXImage when the
render completes but having it "built in" is so convenient. :)
Just curious where this is at. I have some time now, retired and under
"lockdown" from the pandemic, to spend some time working on this problem.
However, if the 3.8 branch is no longer being actively developed (perhaps in
favor of 4.x?), or the SDL problem is addressed in another development version,
I'd like to know.
Any response is appreciated. Cheers.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
"Jeff Houck" <jho### [at] northrimnet> wrote:
> ...
> Sorry to necro this thread but ...
>
> Is this issue being addressed in the current 3.8 branch? I'm compiling
> povray-3.8.0-alpha.10064268 on a Ubuntu-based distro after being advised it's
> the most stable of the development versions. However, as others have posted
> using either SDL1.2 or 2.0 throws errors in the compilation phase.
> ...
> Any response is appreciated. Cheers.
re latest alpha compilation errors, was discussed here:
<http://news.povray.org/povray.beta-test/thread/%3C5c6b6863%241%40news.povray.org%3E/>
(I've posted a patch there too, hopefully making the BASH scripting unnecessary)
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Jeff Houck" <jho### [at] northrimnet> wrote:
> BGimeno <bru### [at] gmailcom> wrote:
> > I have tried to compile the latest version 3.8.0.9861167 alpha and as in
> > the official version that I compiled I still have the problem that it
> > does not show the image while it is generated. While compiling it shows
> > the following message,
> >
> > Built-in features:
> > I/O restrictions: enabled
> > X Window display: disabled
> > Supported image formats: gif tga iff ppm pgm hdr png jpeg tiff
> > Unsupported image formats: openexr
> >
> > Compilation settings:
> > Build architecture: x86_64-pc-linux-gnu
> > Built/Optimized for: x86_64-pc-linux-gnu (using -march=native)
> > Compiler vendor: gnu
> > Compiler version: g++ 7
> > Compiler flags: -pipe -Wno-multichar -Wno-write-strings
> > -fno-enforce-eh-specs -Wno-non-template-friend -s -O3 -ffast-math
> > -march=native -pthread
> > Libraries: -ltiff -ljpeg -lpng -lz -lrt -lm -lboost_thread
> > -pthread -lboost_system
> >
> >
> >
> > Note that in the Built-in features the X Windows display is disabled.
> >
> > I have followed the detailed instructions in
> > https://github.com/POV-Ray/povray/blob/master/unix/README.md
> > and I think that the dependencies listed do not include the necessary X
> > server or XCygwin or X11 or XDisplay or whatever it is called.
> >
> > Can someone tell me what is needed to complete the installation?
> >
> > Thank you very much
> > B. Gimeno
>
> Sorry to necro this thread but ...
>
> Is this issue being addressed in the current 3.8 branch? I'm compiling
> povray-3.8.0-alpha.10064268 on a Ubuntu-based distro after being advised it's
> the most stable of the development versions. However, as others have posted
> using either SDL1.2 or 2.0 throws errors in the compilation phase. I could
> simply bash-script up a solution to invoke something like LXImage when the
> render completes but having it "built in" is so convenient. :)
>
> Just curious where this is at. I have some time now, retired and under
> "lockdown" from the pandemic, to spend some time working on this problem.
> However, if the 3.8 branch is no longer being actively developed (perhaps in
> favor of 4.x?), or the SDL problem is addressed in another development version,
> I'd like to know.
>
> Any response is appreciated. Cheers.
FIXED
Well, it was fairly simple to fix when using SDL1.2. I added:
using namespace std:
to povray-3.8.0-alpha.10064268/unix/disp_sdl.cpp:
using namespace std;
using namespace vfe;
using namespace vfePlatform;
and it all compiles and works fine. I spent most of my time doing C programming
and not C++ so the namespace solution didn't jump out at me at first.
I'll leave changing over to SDL2 for later. It appears I'd have to mess about
with the m4 files ... ;)
Cheers.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 27/03/2020 à 19:01, Jeff Houck a écrit :
> "Jeff Houck" <jho### [at] northrimnet> wrote:
>> BGimeno <bru### [at] gmailcom> wrote:
>>> I have tried to compile the latest version 3.8.0.9861167 alpha and as in
>>> the official version that I compiled I still have the problem that it
>>> does not show the image while it is generated. While compiling it shows
>>> the following message,
>>>
>>> Built-in features:
>>> I/O restrictions: enabled
>>> X Window display: disabled
>>> Supported image formats: gif tga iff ppm pgm hdr png jpeg tiff
>>> Unsupported image formats: openexr
>>>
>>> Compilation settings:
>>> Build architecture: x86_64-pc-linux-gnu
>>> Built/Optimized for: x86_64-pc-linux-gnu (using -march=native)
>>> Compiler vendor: gnu
>>> Compiler version: g++ 7
>>> Compiler flags: -pipe -Wno-multichar -Wno-write-strings
>>> -fno-enforce-eh-specs -Wno-non-template-friend -s -O3 -ffast-math
>>> -march=native -pthread
>>> Libraries: -ltiff -ljpeg -lpng -lz -lrt -lm -lboost_thread
>>> -pthread -lboost_system
>>>
>>>
>>>
>>> Note that in the Built-in features the X Windows display is disabled.
>>>
>>> I have followed the detailed instructions in
>>> https://github.com/POV-Ray/povray/blob/master/unix/README.md
>>> and I think that the dependencies listed do not include the necessary X
>>> server or XCygwin or X11 or XDisplay or whatever it is called.
>>>
>>> Can someone tell me what is needed to complete the installation?
>>>
>>> Thank you very much
>>> B. Gimeno
>>
>> Sorry to necro this thread but ...
>>
>> Is this issue being addressed in the current 3.8 branch? I'm compiling
>> povray-3.8.0-alpha.10064268 on a Ubuntu-based distro after being advised it's
>> the most stable of the development versions. However, as others have posted
>> using either SDL1.2 or 2.0 throws errors in the compilation phase. I could
>> simply bash-script up a solution to invoke something like LXImage when the
>> render completes but having it "built in" is so convenient. :)
>>
>> Just curious where this is at. I have some time now, retired and under
>> "lockdown" from the pandemic, to spend some time working on this problem.
>> However, if the 3.8 branch is no longer being actively developed (perhaps in
>> favor of 4.x?), or the SDL problem is addressed in another development version,
>> I'd like to know.
>>
>> Any response is appreciated. Cheers.
>
> FIXED
>
> Well, it was fairly simple to fix when using SDL1.2. I added:
>
> using namespace std:
>
> to povray-3.8.0-alpha.10064268/unix/disp_sdl.cpp:
>
> using namespace std;
> using namespace vfe;
> using namespace vfePlatform;
>
> and it all compiles and works fine. I spent most of my time doing C programming
> and not C++ so the namespace solution didn't jump out at me at first.
>
> I'll leave changing over to SDL2 for later. It appears I'd have to mess about
> with the m4 files ... ;)
>
> Cheers.
>
>
My 0.02c : Please have a look at hgpovray38 fork, where SDL2 is
available. Hope this can help a bit.
https://github.com/LeForgeron/povray
Sadly, linking to support both SDL1.2 and SDL2 is not possible.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> My 0.02c : Please have a look at hgpovray38 fork, where SDL2 is
> available. Hope this can help a bit.
>
> https://github.com/LeForgeron/povray
>
> Sadly, linking to support both SDL1.2 and SDL2 is not possible.
Thank you for the link. I'll be sure to take a look at it. :)
Cheers.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
