Wings v2.2.5 shuts down after the render completes, the rendered image displays then Wings closes expectantly
The scene renders stand alone fine
Just create a scene with a simple object, uv and lights and try to render with 800x600 res
Persistence of Vision™ Ray Tracer Version 3.7.0.8.unofficial (g++ 8 @
i686-pc-linux-gnu)
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
I've created a cube, unwrapped it, created a texture and added one point light, but no crash.
Which kind of lights did you added? The object was more complex?
This crashes for me
I know the unwrapping is wrong.. I was just trying something.... KT doesn't work and Thea is running under Wine so povray is the only quick option..
I don't have opencl but I can't see that being the issue
Erlang/OTP 21 [erts-10.2.4] [source] [smp:2:2] [ds:2:2:10] [async-threads:1]
Eshell V10.2.4 (abort with ^G)
1> wings-2.2.5
Reading preferences from: /home/pi/.config/Wings3D/Preferences.txt
OpenCL not available: {opencl_failed_previously,
"/home/pi/.cache/Wings3D/opencl_tmp.txt"}
Could not initialize OpenCL: env lighting limited
its something to do with image size, at 640x480 it renders fine
if I render at 800x600 and jpg I do get an error:
Quote:Render Time:
Photon Time: 0 hours 0 minutes 0 seconds (0.000 seconds)
using 5 thread(s) with 0.000 CPU-seconds total
Radiosity Time: No radiosity
Trace Time: 0 hours 0 minutes 1 seconds (1.082 seconds)
using 2 thread(s) with 1.116 CPU-seconds total
JPEG parameter struct mismatch: library thinks size is 372, caller expects 376
JPEG parameter struct mismatch: library thinks size is 372, caller expects 376
Render failed
it should create a erl dump as after that error Wings fails to close properly and I have to kill the process.. its over 2.5meg
the dump:
https://drive.google.com/file/d/1SoEyfpw...sp=sharing
edit
I'm getting the impression its the png and jpg headers being different versions? but its strange the 640x480 will save.. its way beyond me lol
ok... its nothing to do with Povray, its the image viewer, if the image is bigger than the viewer window Wings crashes, its also the same in 2.2.4
No. It looks like something with Linux.
Your exported
.pov file you attached in the previous post can be rendered in the povray standalone app?
I'm under Windows and I used it and added the parameters
"+W800 +H600 +FJ" to the option in its toolbar. Rendered fine.
Render an UV mapped object from Wings3D with those settings is OK too. Here is my log in the W3D console and the image is correctly loaded in viewer:
Quote:Rendering Job started <0.7603.0>:
> f:/PROGRA~1/POV-Ray/v3.7/bin/PVENGI~2.EXE "Wheel Unwrapping_export.pov" +W800 +H600 +FJ +o"Wheel Unwrapping.jpg" /NR /EXIT
Rendering Job returned: 0
Export time: 0.569"
Render time: 4.213"
Total time: 4.782"
Rendering Job ready
Loading rendered image
Did you try other file format as
.png?
Windows works fine with Povray, I installed it to try
2.2.4 also crashed with Raspbian
its something to do with the jpg, png, tga version difference between Raspbian and Wings, I get the impression its something to do with the header files being different versions but I don't know what to look for
I can create a screen capture and save it as an external file png or bmp and it will be viewable
but for some strange reason any other image crashes if its bigger than the viewer window
I can't view a imported image from the outliner
I have no idea whats going on, I'll wait and see if anyone else has issues, if it had been a different linux version it would be easier to pursue
Its not Povray or the plugin.. its the image viewer itself
Are you using an external image viewer?
I'm asking that because you can set that in the Preferences dialog.
Its only the render view, I still can't load a texture image and view it, it still uses the inbuilt viewer
edit:
An image plane will load with a huge jpg image, but I can't select it to view from the outliner
I think I should cull this topic to image viewer as Povray or the plugin aren't the issue.. and wait and see if Phil92 has issues
ok I have something:
Quote:The program 'Erlang' received an X Window System error. This probably
reflects a bug in the program. The error was 'BadDrawable (invalid
Pixmap or Window parameter)'. (Details: serial 19376 error_code 9
request_code 62 minor_code 0) (Note to programmers: normally, X errors
are reported asynchronously; that is, you will receive the error a
while after causing it. To debug your program, run it with the --sync
command line option to change this behavior. You can then get a
meaningful backtrace from your debugger if you break on the
gdk_x_error() function.)