bricks

[claus82]

It's been a while. I hope you enjoy. Images were sent to whatsapp so maybe they lost their resolution.
it was useful as exercise for mirror-weld-cleanup passages reminder
I wanted to use other renderer as povray but it seems I am not able to use it, Imean export pov project (or render and so on...) so rendered using cycles using blender 4
Sorry I did not put preview but my account was troublesome this time.

https://drive.google.com/file/d/1wSsEDqk...p=drivesdk


https://drive.google.com/file/d/1Bhs-M5v...p=drivesdk


https://drive.google.com/file/d/10Ld6INZ...p=drivesdk


https://drive.google.com/file/d/1j3Yirlh...p=drivesdk


https://drive.google.com/file/d/1MTpDr3b...p=drivesdk


https://drive.google.com/file/d/1oaHutJx...p=drivesdk


https://drive.google.com/file/d/13SIcOCj...p=drivesdk


Cheers to all
Claudio

[micheus]

Thanks for sharing Claudio.
I edited your post to add the "gdrive" tag so we can see the image preview directly on the forum. As you can see, there are two images that you need to check the sharing polices.

(...) Imean export pov project (or render and so on...)
(...)

About that. Have you setup the POV-Ray plugin after you installed the POV-Ray program?
Or that is something not related to Wings3D, since you would be able to export the .pov file and load it into the POV-Ray standalone program.

[claus82]

Thanks for sharing Claudio.
I edited your post to add the "gdrive" tag so we can see the image preview directly on the forum. As you can see, there are two images that you need to check the sharing polices.

(...) Imean export pov project (or render and so on...)
(...)

About that. Have you setup the POV-Ray plugin after you installed the POV-Ray program?
Or that is something not related to Wings3D, since you would be able to export the .pov file and load it into the POV-Ray standalone program.

About pics' permission: done.


About the POVRAY setup

I go to "Edit - Plugin Preferences - Povray(.pov)..."

I saw that the povray executable is installed in /usr/bin/ path, but but W3D does not see the executable. 

Inside the preferences tab I add manually the path to the "Executable" option, but it does not work.

My actual OS is Xubuntu
Distributor ID: Ubuntu
Description: Ubuntu 24.04.2 LTS
Release: 24.04
Codename: noble


Cheers

[micheus]

Please take a look at this short tutorial: POV-Ray install
Right side you find the instructions for Linux. Just, notice it includes old version of POV-Ray, but that changes anything in the process.

Please let me know if you still didn't get it working.

[claus82]

Please take a look at this short tutorial: POV-Ray install
Right side you find the instructions for Linux. Just, notice it includes old version of POV-Ray, but that changes anything in the process.

Please let me know if you still didn't get it working.

No way man.
The "povray" file should be found inside the path but it is not seen through the path browser of W3D.
I selected "all formats" and "all files" but nothing
I launch the render and I obtain "Rendering Error"

Down here what happens


STEPS:
1-launch W3D
2-add a cube
3-go to "File-Render-Povray" 
4-press ok inside the dialogue window

This is what I get:
wings-2.4.1
Reading preferences from: /home/claudio/.var/app/com.wings3d.WINGS/config/Wings3D/Preferences.txt
OpenCL not available: {opencl_failed_previously,
                          "/home/claudio/.var/app/com.wings3d.WINGS/cache/Wings3D/opencl_tmp.txt"}
Could not initialize OpenCL: env lighting limited

Vendor:    Intel
Renderer:  Mesa Intel® HD Graphics 4600 (HSW GT2)
Version:    4.6 (Compatibility Profile) Mesa 25.0.5 (git-a89e40440

Rendering Job started <0.167.0>:
> /home/claudio/povray-3.6/povray untitled_export.pov +W320 +H240 +FN +ountitled.png

Rendering Job returned: 159
Export time:    0.027"
Render time:    0.338"
Total time:      0.365"
Rendering error: 159

[edb]

Hello claus82

It seems its a bug because the file dialog is taking *.* literally and isn't showing files without extensions.

Try renaming povray to povray.exe or povray.prog to see if it helps.

[edb]

I've also made a patch that should fix the file chooser so the file filter is now "*" on non-Windows environments so that renaming the binary won't be needed.

patch_file_chooser.tar

[claus82]

Thanks man.
I removed the 24.04 because I had used the minimal installation and I thought it could be without some libraries and so on... Yet I installed the 22.04 and there is the same problem.
Concerning your solution I tried to rename the file and give an extension, but the executable was not found evenin this case.
I will try to find the proper place where to put the patch file and I will let you know.
For the moment thank you!

[claus82]

Hello!
Well, actually it does not find the file.
How sad. Thanks anyway man
I tried to rename and to restart but nothing.
Cheers

[micheus]

Hello!
Well, actually it does not find the file.
How sad. Thanks anyway man
I tried to rename and to restart but nothing.

The problem is not the fix. It's working working in the development environment as you can see bellow. I believe the problem is the method of install that is not working fine. Please, replace the wings_job.beam file directly in Wings3D installed folder - look for the ebin folder where it must be exists. It must be something like that for Windows: C:\Program Files\wings3d_2.4.1\lib\wings-2.4.1\ebin and for Linux: /usr/lib/erlang/lib/wings-2.4.1/ebin


I've been noticed that the Install Plugin & Patch options is working fine for files under the plugins folder and its subfolders. I have to take a look on that.