Package Details: wings3d 2.3-2

Git Clone URL: https://aur.archlinux.org/wings3d.git (read-only, click to copy)
Package Base: wings3d
Description: 3D modeler using the winged edge data structure
Upstream URL: http://www.wings3d.com/
Keywords: 3d modeler
Licenses: GPL-2.0-or-later
Submitter: sangy
Maintainer: xiota
Last Packager: xiota
Votes: 4
Popularity: 0.000002
First Submitted: 2021-07-28 00:39 (UTC)
Last Updated: 2024-03-12 09:26 (UTC)

Dependencies (5)

Required by (0)

Sources (1)

Latest Comments

1 2 3 Next › Last »

ozz commented on 2024-03-12 12:30 (UTC)

@xiota OK, but every public release is a version. Any change is a "thing". None of the package tools could detect that it had been modified therefore I did not know it had been modified. This more in reference to the comments, it doesn't matter so much now.

xiota commented on 2024-03-12 08:58 (UTC) (edited on 2024-03-12 09:27 (UTC) by xiota)

Did not previously bump pkgrel because there was no need for anyone who had successfully built the package to rebuild.

Bumping now because most recent update changes resulting package.

ozz commented on 2024-03-12 07:01 (UTC) (edited on 2024-03-12 07:02 (UTC) by ozz)

Yes, the maintainer patched it but didn't update the package release version (pkgrel should be "2").

furrykef commented on 2024-03-12 05:38 (UTC)

Working fine for me. (I'm posting this mainly so the most recent comment doesn't make it look like the package is broken.)

ozz commented on 2024-01-15 21:39 (UTC) (edited on 2024-01-15 21:40 (UTC) by ozz)

Is it just me or is this broken?

To successfully compile it needs the following patch from upstream git:

diff --git a/plugins_src/import_export/wpc_yafaray.erl b/plugins_src/import_export/wpc_yafaray.erl
index e3ecb184..a36e79a2 100644
--- a/plugins_src/import_export/wpc_yafaray.erl
+++ b/plugins_src/import_export/wpc_yafaray.erl
@@ -4008,8 +4008,8 @@ export_blend_mat_shader(F, Name, Mat, ExportDir, YafaRay) ->

     Blend_Value = proplists:get_value(blend_value, YafaRay, ?DEF_BLEND_VALUE),

-    uniprintln(F, "  <material1 sval=\"""w_""\~ts\"/>~n"
-                  "        <material2 sval=\"""w_""\~ts\"/>~n"
+    uniprintln(F, "  <material1 sval=\"w_\~ts\"/>~n"
+                  "        <material2 sval=\"w_\~ts\"/>~n"
                   "        <blend_value fval=\"~.10f\"/>~n",
             [Blend_Mat1,Blend_Mat2,Blend_Value]),
     foldl(fun ({modulator,Ps}=M, N) when is_list(Ps) ->

xiota commented on 2023-10-22 00:53 (UTC)

Adopted to update / fix. Anyone who wants to comaintain, let me know.

slomomojo commented on 2023-10-21 18:49 (UTC)

Sorry, I've been away most of the year with health issues so I'm no longer maintaining this. I should have released it back into the wild months ago.

ozz commented on 2023-07-21 02:50 (UTC) (edited on 2023-07-21 02:54 (UTC) by ozz)

I flagged this as out-of-date but I don't know if it's maintained any more? It's not really out of date as far as official releases but this official build didn't work. I have been using my own build for a long time and just tried to install this but got an error on file verification (the patch file IIRC). I'm not sure the patch is even needed any more(?). The latest git code seems to run OK but I don't know about the official release. Maybe the fix can be back-ported.

rezder commented on 2022-12-29 21:26 (UTC)

Hi Slomomojo I am looking forward to a solution, So I looked into this even though I am only wings user. Are you sure that the 3d is not causing the problem.

The erlang code is looking for wings not wings3d and often directories is used as packagenames. During make you add the srcdir without the 3d to ERL_LIBS are you sure erlang can finde the installed package without somthing similar at the current location and name.

I believe that erlang only looks in /usr/lib/erlang. I tried to add the 3d directory to ER_LIBS and looked for with code:lib_dir(wings) and code:lib_dir(wings3d) only 3d returned somthing. Feel free to ignore every as I only have time not knowledge. Good luck.

slomomojo commented on 2022-11-07 03:06 (UTC)

No update yet. Still looking for a solution...