Re: update / new features
Jean-Pierre Delange via ntg-context <[email protected]> Wed, 29 Jul 2026 15:17:26 +0200
| Newsgroups | gmane.comp.tex.context |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============2418069589443796255==
Content-Type: multipart/alternative;
boundary="------------ivWEmNYBfj0qSMqSrF2xrWNF"
Content-Language: fr
This is a multi-part message in MIME format.
--------------ivWEmNYBfj0qSMqSrF2xrWNF
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Hi Hans,
I have now run your gyroid test under WSL/Linux, using the separate=20
ConTeXt LMTX installation:
*
ConTeXt LMTX: |2026.07.29 11:46|
*
LuaMetaTeX: |2.11.09|
*
platform: |linux-64| under WSL
*
processor: AMD Ryzen 5 5600
*
RAM: 32 GB
The output was generated correctly and looks very good.
For the initial calculation, the log reports:
|implicit mesh: 3,691,602 vertices 1,230,534 triangles mesh generation:=20
5.062 seconds triangle rendering: 0.295 seconds MetaPost total: 5.474=20
seconds ConTeXt runtime: 6.773 seconds |
The cleanup message reports about 596 MB of temporary data.
On the second run, with the cache being reused, the figures dropped to:
|MetaPost total: 0.014 seconds ConTeXt runtime: 0.249 seconds |
So on this machine the cached run is roughly 27 times faster than the=20
initial run.
The complete |context gyroid-test.tex| command performed both runs=20
automatically and was measured with |/usr/bin/time -v| as:
|wall-clock time: 7.10 seconds maximum resident set size: 432,172 kB CPU=20
usage: 88% |
This means that, on this Ryzen 5 5600 machine, the initial calculation=20
is about twice as fast as the approximately 14 seconds you reported,=20
while the cached run is also somewhat faster than your 0.45 seconds.
The bitmap output remains compact and responsive in the PDF viewer,=20
despite the mesh containing more than 1.2 million triangles.
JP
Le 29/07/2026 =C3=A0 14:46, Hans Hagen via ntg-context a =C3=A9crit=C2=A0=
:
> On 7/29/2026 12:57 PM, Jean-Pierre Delange via ntg-context wrote:
>> Hi Hans,
>>
>> I installed the new ConTeXt LMTX version in a separate Windows=20
>> directory, so as not to interfere with my existing installation:
>>
> > ...
> >
>> I then copied |luametafun-threed.tex| to a separate test directory=20
>> and compiled it with:
>>
>> |context luametafun-threed.tex |
>>
>> The compilation completed successfully and produced a 15-page PDF.=20
>> The 3D examples that were rendered =E2=80=94 including the Menger spon=
ge and=20
>> the parametric and postprocessed spheres =E2=80=94 look very good.
>>
>> The final statistics were:
>>
>> |MetaPost: 3.051 seconds Total ConTeXt runtime: 3.760 seconds 15=20
>> processed and shipped pages Lua memory: 169 MB used, 173 MB maximum |
>>
>> Some individual figures were also quite fast:
>
> a few have cache =3D true set, so that helps
>
>> |Menger sponge: 2,400 triangles rendering time: 0.612 seconds=20
>> Parametric sphere: 20,000 triangles rendering time: about 0.145=E2=80=93=
0.149=20
>> seconds |
>
> on the average parametrics plot are fast (could be sped up if really=20
> needed) but implcits are more expsnsive as there we generate 8 samples=20
> per cube around points
>
>> The log also reports substantial temporary memory clean-ups, for=20
>> example about 160 MB for the Menger sponge and about 412 MB for the=20
>> parametric spheres. The more complex implicit/intersection example=20
>> reaches roughly 1 GB of temporary data, as described in the manual.=20
>> Nevertheless, the complete document compiled quickly on this machine.
>> I noticed three minor issues:
>
> indeed, we operate on a sometimes 2500 x 2500 bit map, with zbuffering=20
> that can go deep (esp with transparency enabled) with high res color=20
> (doubles), normal vectors etc, and that all comes at a price; if=20
> really needed we can compile with floats which saves a bit; the super=20
> sampling of (here 2) quadruples it;
>
> however, the mesh is the same;
>
> Here's a test:
>
> \nologbuffering
>
> \startMPpage
> lmt_scene_start [
> =C2=A0=C2=A0=C2=A0 width=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D =
10cm,
> =C2=A0=C2=A0=C2=A0 resolution=C2=A0=C2=A0 =3D 150,
> =C2=A0=C2=A0=C2=A0 supersample=C2=A0 =3D 2,
> =C2=A0=C2=A0=C2=A0 crop=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=3D true,
> =C2=A0=C2=A0=C2=A0 projection=C2=A0=C2=A0 =3D "perspective",
> =C2=A0=C2=A0=C2=A0 eye=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 =3D "auto", % (-8,32,0),
> =C2=A0=C2=A0=C2=A0 fov=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 =3D 80,
> =C2=A0=C2=A0=C2=A0 light=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D =
(0,-1,-2),
> =C2=A0=C2=A0=C2=A0 intensity=C2=A0=C2=A0=C2=A0 =3D 1.1,
> =C2=A0=C2=A0=C2=A0 cache=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D =
true,
> =C2=A0=C2=A0=C2=A0 name=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=3D "example",
> ] ;
>
> lmt_scene_material [
> =C2=A0=C2=A0=C2=A0 name=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D "surface",
> =C2=A0=C2=A0=C2=A0 diffuse=C2=A0=C2=A0 =3D (.9,.2,.2),
> =C2=A0=C2=A0=C2=A0 specular=C2=A0 =3D (.5,.5,.5),
> =C2=A0=C2=A0=C2=A0 shininess =3D 25,
> =C2=A0=C2=A0=C2=A0 opacity=C2=A0=C2=A0 =3D 1,
> =C2=A0=C2=A0=C2=A0 ambient=C2=A0=C2=A0 =3D .25,
> ] ;
>
> lmt_scene_implicit [
> =C2=A0=C2=A0=C2=A0 id=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D "gyroid",
> =C2=A0=C2=A0=C2=A0 material =3D "surface",
> =C2=A0=C2=A0=C2=A0 code=C2=A0=C2=A0=C2=A0=C2=A0 =3D "sin(x)*cos(y) + si=
n(y)*cos(z) + sin(z)*cos(x)",
> =C2=A0=C2=A0=C2=A0 dfdx=C2=A0=C2=A0=C2=A0=C2=A0 =3D "cos(x)*cos(y) - si=
n(z)*sin(x)",
> =C2=A0=C2=A0=C2=A0 dfdy=C2=A0=C2=A0=C2=A0=C2=A0 =3D "cos(y)*cos(z) - si=
n(x)*sin(y)",
> =C2=A0=C2=A0=C2=A0 dfdz=C2=A0=C2=A0=C2=A0=C2=A0 =3D "cos(z)*cos(x) - si=
n(y)*sin(z)",
> =C2=A0=C2=A0=C2=A0 xmin=C2=A0=C2=A0=C2=A0=C2=A0 =3D -2pi,
> =C2=A0=C2=A0=C2=A0 xmax=C2=A0=C2=A0=C2=A0=C2=A0 =3D=C2=A0 2pi,
> =C2=A0=C2=A0=C2=A0 ymin=C2=A0=C2=A0=C2=A0=C2=A0 =3D -2pi,
> =C2=A0=C2=A0=C2=A0 ymax=C2=A0=C2=A0=C2=A0=C2=A0 =3D=C2=A0 2pi,
> =C2=A0=C2=A0=C2=A0 zmin=C2=A0=C2=A0=C2=A0=C2=A0 =3D -2pi,
> =C2=A0=C2=A0=C2=A0 zmax=C2=A0=C2=A0=C2=A0=C2=A0 =3D=C2=A0 2pi,
> %=C2=A0=C2=A0=C2=A0=C2=A0 xmin=C2=A0=C2=A0=C2=A0=C2=A0 =3D -pi,
> %=C2=A0=C2=A0=C2=A0=C2=A0 xmax=C2=A0=C2=A0=C2=A0=C2=A0 =3D=C2=A0 pi,
> %=C2=A0=C2=A0=C2=A0=C2=A0 ymin=C2=A0=C2=A0=C2=A0=C2=A0 =3D -pi,
> %=C2=A0=C2=A0=C2=A0=C2=A0 ymax=C2=A0=C2=A0=C2=A0=C2=A0 =3D=C2=A0 pi,
> %=C2=A0=C2=A0=C2=A0=C2=A0 zmin=C2=A0=C2=A0=C2=A0=C2=A0 =3D -pi,
> %=C2=A0=C2=A0=C2=A0=C2=A0 zmax=C2=A0=C2=A0=C2=A0=C2=A0 =3D=C2=A0 pi,
> =C2=A0=C2=A0=C2=A0 nx=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D 150,
> =C2=A0=C2=A0=C2=A0 ny=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D 150,
> =C2=A0=C2=A0=C2=A0 nz=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D 150,
> =C2=A0=C2=A0=C2=A0 normal=C2=A0=C2=A0 =3D "smooth",
> ] ;
>
>
> lmt_scene_render ;
>
> lmt_scene_stop ;
>
> \stopMPpage
>
> This takes 14 seconds runtime here but as we cache only .45 seconds=20
> after that. It's kind of hard to predict at my end what a modern=20
> machine with more cpu cache would need.
>
>> =C2=A01.
>>
>> =C2=A0=C2=A0=C2=A0 At the beginning of the run, ConTeXt reports:
>>
>> |modules > '3d' is not found |
>
> ok, we can remove the module line (we tested with a module first as=20
> that was easier before integration)
>
>> and the final statistics mention one missing module, |*-3d|. However,=20
>> the internal 3D LuaMetaFun support is loaded correctly through |mlib-=20
>> thr.lmt|, and this does not prevent the document from compiling.
>> 2. One internal reference remains unresolved:
>>
>> |fig:threed:process:3 |
>>
>> which appears as =E2=80=9CFigure ??=E2=80=9D in the PDF.
>
> thanks, fixed
>
>> =C2=A03.
>>
>> =C2=A0=C2=A0=C2=A0 Near the end of the compilation, the log reports:
>>
>> |luatex warning > mplib: run script: cannot open : Invalid argument |
>
> you probably miss the stl file
>
>> I had copied only |luametafun-threed.tex| to the test directory, so I=20
>> suspect that the final STL example could not find |luametafun-threed-=20
>> sphere.stl|. The PDF was still produced, but the last STL figure was=20
>> not rendered correctly. I will repeat the test after copying the=20
>> accompanying STL file as well.
>> As a first impression, the rendering performance on this Windows=20
>> machine is very good, and the visual quality of the generated=20
>> bytemaps is excellent.
>
> yes, and the alternative, vector based meshing not only bloats a pdf,=20
> but us also much more heavy on the viewer (stalls in the worst case)=20
> and is also less reliable
>
>> I am now preparing the same separate installation and test under WSL=20
>> and native Ubuntu, so that I can compare the three environments on=20
>> the same hardware.
>
> Good. Thanks,
>
> Hans
>
> -----------------------------------------------------------------
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 Hans Hagen | PRAGMA ADE
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 tel: 038 477 53 69 | www.pragma-ad=
e.nl | www.pragma-pod.nl
> -----------------------------------------------------------------
> _______________________________________________________________________=
____________=20
>
> If your question is of interest to others as well, please add an entry=20
> to the Wiki!
>
> maillist : [email protected] /=20
> https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
> webpage=C2=A0 : https://www.pragma-ade.nl / https://context.aanhet.net=20
> (mirror)
> archive=C2=A0 : https://github.com/contextgarden/context
> wiki=C2=A0=C2=A0=C2=A0=C2=A0 : https://wiki.contextgarden.net
> _______________________________________________________________________=
____________=20
>
--------------ivWEmNYBfj0qSMqSrF2xrWNF
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE html>
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUTF=
-8">
</head>
<body>
<p>Hi Hans,</p>
<p>I have now run your gyroid test under WSL/Linux, using the
separate ConTeXt LMTX installation:</p>
<ul>
<li>
<p>ConTeXt LMTX: <code>2026.07.29 11:46</code></p>
</li>
<li>
<p>LuaMetaTeX: <code>2.11.09</code></p>
</li>
<li>
<p>platform: <code>linux-64</code> under WSL</p>
</li>
<li>
<p>processor: AMD Ryzen 5 5600</p>
</li>
<li>
<p>RAM: 32 GB</p>
</li>
</ul>
<p>The output was generated correctly and looks very good.</p>
<p>For the initial calculation, the log reports:</p>
<pre><code class=3D"language-text">implicit mesh:
3,691,602 vertices
1,230,534 triangles
mesh generation: 5.062 seconds
triangle rendering: 0.295 seconds
MetaPost total: 5.474 seconds
ConTeXt runtime: 6.773 seconds
</code></pre>
<p>The cleanup message reports about 596 MB of temporary data.</p>
<p>On the second run, with the cache being reused, the figures
dropped to:</p>
<pre><code class=3D"language-text">MetaPost total: 0.014 seconds
ConTeXt runtime: 0.249 seconds
</code></pre>
<p>So on this machine the cached run is roughly 27 times faster than
the initial run.</p>
<p>The complete <code>context gyroid-test.tex</code> command
performed both runs automatically and was measured with <code>/usr/=
bin/time
-v</code> as:</p>
<pre><code class=3D"language-text">wall-clock time: 7.10 seconds
maximum resident set size: 432,172 kB
CPU usage: 88%
</code></pre>
<p>This means that, on this Ryzen 5 5600 machine, the initial
calculation is about twice as fast as the approximately 14 seconds
you reported, while the cached run is also somewhat faster than
your 0.45 seconds.</p>
<p>The bitmap output remains compact and responsive in the PDF
viewer, despite the mesh containing more than 1.2 million
triangles.</p>
<p>JP</p>
<p><br>
</p>
<div class=3D"moz-cite-prefix">Le 29/07/2026 =C3=A0 14:46, Hans Hagen=
via
ntg-context a =C3=A9crit=C2=A0:<br>
</div>
<blockquote type=3D"cite"
cite=3D"mid:[email protected]">On
7/29/2026 12:57 PM, Jean-Pierre Delange via ntg-context wrote:
<br>
<blockquote type=3D"cite">Hi Hans,
<br>
<br>
I installed the new ConTeXt LMTX version in a separate Windows
directory, so as not to interfere with my existing installation:
<br>
<br>
</blockquote>
> ...
<br>
>
<br>
<blockquote type=3D"cite">I then copied |luametafun-threed.tex| to =
a
separate test directory and compiled it with:
<br>
<br>
|context luametafun-threed.tex |
<br>
<br>
The compilation completed successfully and produced a 15-page
PDF. The 3D examples that were rendered =E2=80=94 including the M=
enger
sponge and the parametric and postprocessed spheres =E2=80=94 loo=
k very
good.
<br>
<br>
The final statistics were:
<br>
<br>
|MetaPost: 3.051 seconds Total ConTeXt runtime: 3.760 seconds 15
processed and shipped pages Lua memory: 169 MB used, 173 MB
maximum |
<br>
<br>
Some individual figures were also quite fast:
<br>
</blockquote>
<br>
a few have cache =3D true set, so that helps
<br>
<br>
<blockquote type=3D"cite">|Menger sponge: 2,400 triangles rendering
time: 0.612 seconds Parametric sphere: 20,000 triangles
rendering time: about 0.145=E2=80=930.149 seconds |
<br>
</blockquote>
<br>
on the average parametrics plot are fast (could be sped up if
really needed) but implcits are more expsnsive as there we
generate 8 samples per cube around points
<br>
<br>
<blockquote type=3D"cite">The log also reports substantial temporar=
y
memory clean-ups, for example about 160 MB for the Menger sponge
and about 412 MB for the parametric spheres. The more complex
implicit/intersection example reaches roughly 1 GB of temporary
data, as described in the manual. Nevertheless, the complete
document compiled quickly on this machine.
<br>
I noticed three minor issues:
<br>
</blockquote>
<br>
indeed, we operate on a sometimes 2500 x 2500 bit map, with
zbuffering that can go deep (esp with transparency enabled) with
high res color (doubles), normal vectors etc, and that all comes
at a price; if really needed we can compile with floats which
saves a bit; the super sampling of (here 2) quadruples it;
<br>
<br>
however, the mesh is the same;
<br>
<br>
Here's a test:
<br>
<br>
\nologbuffering
<br>
<br>
\startMPpage
<br>
lmt_scene_start [
<br>
=C2=A0=C2=A0=C2=A0 width=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
=3D 10cm,
<br>
=C2=A0=C2=A0=C2=A0 resolution=C2=A0=C2=A0 =3D 150,
<br>
=C2=A0=C2=A0=C2=A0 supersample=C2=A0 =3D 2,
<br>
=C2=A0=C2=A0=C2=A0 crop=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 =3D true,
<br>
=C2=A0=C2=A0=C2=A0 projection=C2=A0=C2=A0 =3D "perspective",
<br>
=C2=A0=C2=A0=C2=A0 eye=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 =3D "auto", % (-8,32,0),
<br>
=C2=A0=C2=A0=C2=A0 fov=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 =3D 80,
<br>
=C2=A0=C2=A0=C2=A0 light=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
=3D (0,-1,-2),
<br>
=C2=A0=C2=A0=C2=A0 intensity=C2=A0=C2=A0=C2=A0 =3D 1.1,
<br>
=C2=A0=C2=A0=C2=A0 cache=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
=3D true,
<br>
=C2=A0=C2=A0=C2=A0 name=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 =3D "example",
<br>
] ;
<br>
<br>
lmt_scene_material [
<br>
=C2=A0=C2=A0=C2=A0 name=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D "surface"=
,
<br>
=C2=A0=C2=A0=C2=A0 diffuse=C2=A0=C2=A0 =3D (.9,.2,.2),
<br>
=C2=A0=C2=A0=C2=A0 specular=C2=A0 =3D (.5,.5,.5),
<br>
=C2=A0=C2=A0=C2=A0 shininess =3D 25,
<br>
=C2=A0=C2=A0=C2=A0 opacity=C2=A0=C2=A0 =3D 1,
<br>
=C2=A0=C2=A0=C2=A0 ambient=C2=A0=C2=A0 =3D .25,
<br>
] ;
<br>
<br>
lmt_scene_implicit [
<br>
=C2=A0=C2=A0=C2=A0 id=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D "gyro=
id",
<br>
=C2=A0=C2=A0=C2=A0 material =3D "surface",
<br>
=C2=A0=C2=A0=C2=A0 code=C2=A0=C2=A0=C2=A0=C2=A0 =3D "sin(x)*cos(y) =
+ sin(y)*cos(z) + sin(z)*cos(x)",
<br>
=C2=A0=C2=A0=C2=A0 dfdx=C2=A0=C2=A0=C2=A0=C2=A0 =3D "cos(x)*cos(y) =
- sin(z)*sin(x)",
<br>
=C2=A0=C2=A0=C2=A0 dfdy=C2=A0=C2=A0=C2=A0=C2=A0 =3D "cos(y)*cos(z) =
- sin(x)*sin(y)",
<br>
=C2=A0=C2=A0=C2=A0 dfdz=C2=A0=C2=A0=C2=A0=C2=A0 =3D "cos(z)*cos(x) =
- sin(y)*sin(z)",
<br>
=C2=A0=C2=A0=C2=A0 xmin=C2=A0=C2=A0=C2=A0=C2=A0 =3D -2pi,
<br>
=C2=A0=C2=A0=C2=A0 xmax=C2=A0=C2=A0=C2=A0=C2=A0 =3D=C2=A0 2pi,
<br>
=C2=A0=C2=A0=C2=A0 ymin=C2=A0=C2=A0=C2=A0=C2=A0 =3D -2pi,
<br>
=C2=A0=C2=A0=C2=A0 ymax=C2=A0=C2=A0=C2=A0=C2=A0 =3D=C2=A0 2pi,
<br>
=C2=A0=C2=A0=C2=A0 zmin=C2=A0=C2=A0=C2=A0=C2=A0 =3D -2pi,
<br>
=C2=A0=C2=A0=C2=A0 zmax=C2=A0=C2=A0=C2=A0=C2=A0 =3D=C2=A0 2pi,
<br>
%=C2=A0=C2=A0=C2=A0=C2=A0 xmin=C2=A0=C2=A0=C2=A0=C2=A0 =3D -pi,
<br>
%=C2=A0=C2=A0=C2=A0=C2=A0 xmax=C2=A0=C2=A0=C2=A0=C2=A0 =3D=C2=A0 pi=
,
<br>
%=C2=A0=C2=A0=C2=A0=C2=A0 ymin=C2=A0=C2=A0=C2=A0=C2=A0 =3D -pi,
<br>
%=C2=A0=C2=A0=C2=A0=C2=A0 ymax=C2=A0=C2=A0=C2=A0=C2=A0 =3D=C2=A0 pi=
,
<br>
%=C2=A0=C2=A0=C2=A0=C2=A0 zmin=C2=A0=C2=A0=C2=A0=C2=A0 =3D -pi,
<br>
%=C2=A0=C2=A0=C2=A0=C2=A0 zmax=C2=A0=C2=A0=C2=A0=C2=A0 =3D=C2=A0 pi=
,
<br>
=C2=A0=C2=A0=C2=A0 nx=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D 150,
<br>
=C2=A0=C2=A0=C2=A0 ny=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D 150,
<br>
=C2=A0=C2=A0=C2=A0 nz=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D 150,
<br>
=C2=A0=C2=A0=C2=A0 normal=C2=A0=C2=A0 =3D "smooth",
<br>
] ;
<br>
<br>
<br>
lmt_scene_render ;
<br>
<br>
lmt_scene_stop ;
<br>
<br>
\stopMPpage
<br>
<br>
This takes 14 seconds runtime here but as we cache only .45
seconds after that. It's kind of hard to predict at my end what a
modern machine with more cpu cache would need.
<br>
<br>
<blockquote type=3D"cite">=C2=A01.
<br>
<br>
=C2=A0=C2=A0=C2=A0 At the beginning of the run, ConTeXt reports:
<br>
<br>
|modules > '3d' is not found |
<br>
</blockquote>
<br>
ok, we can remove the module line (we tested with a module first
as that was easier before integration)
<br>
<br>
<blockquote type=3D"cite">and the final statistics mention one
missing module, |*-3d|. However, the internal 3D LuaMetaFun
support is loaded correctly through |mlib- thr.lmt|, and this
does not prevent the document from compiling.
<br>
2. One internal reference remains unresolved:
<br>
<br>
|fig:threed:process:3 |
<br>
<br>
which appears as =E2=80=9CFigure ??=E2=80=9D in the PDF.
<br>
</blockquote>
<br>
thanks, fixed
<br>
<br>
<blockquote type=3D"cite">=C2=A03.
<br>
<br>
=C2=A0=C2=A0=C2=A0 Near the end of the compilation, the log repor=
ts:
<br>
<br>
|luatex warning > mplib: run script: cannot open : Invalid
argument |
<br>
</blockquote>
<br>
you probably miss the stl file
<br>
<br>
<blockquote type=3D"cite">I had copied only |luametafun-threed.tex|
to the test directory, so I suspect that the final STL example
could not find |luametafun-threed- sphere.stl|. The PDF was
still produced, but the last STL figure was not rendered
correctly. I will repeat the test after copying the accompanying
STL file as well.
<br>
As a first impression, the rendering performance on this Windows
machine is very good, and the visual quality of the generated
bytemaps is excellent.
<br>
</blockquote>
<br>
yes, and the alternative, vector based meshing not only bloats a
pdf, but us also much more heavy on the viewer (stalls in the
worst case) and is also less reliable
<br>
<br>
<blockquote type=3D"cite">I am now preparing the same separate
installation and test under WSL and native Ubuntu, so that I can
compare the three environments on the same hardware.
<br>
</blockquote>
<br>
Good. Thanks,
<br>
<br>
Hans
<br>
<br>
-----------------------------------------------------------------
<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 Hans Hagen | PRAGMA ADE
<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 tel: 038 477 53 69 | <a class=3D=
"moz-txt-link-abbreviated" href=3D"http://www.pragma-ade.nl">www.pragma-a=
de.nl</a> | <a class=3D"moz-txt-link-abbreviated" href=3D"http://www.prag=
ma-pod.nl">www.pragma-pod.nl</a>
<br>
-----------------------------------------------------------------
<br>
_________________________________________________________________________=
__________
<br>
If your question is of interest to others as well, please add an
entry to the Wiki!
<br>
<br>
maillist : <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:ntg=
[email protected]">[email protected]</a> /
<a class=3D"moz-txt-link-freetext" href=3D"https://mailman.ntg.nl/m=
ailman3/lists/ntg-context.ntg.nl">https://mailman.ntg.nl/mailman3/lists/n=
tg-context.ntg.nl</a>
<br>
webpage=C2=A0 : <a class=3D"moz-txt-link-freetext" href=3D"https://=
www.pragma-ade.nl">https://www.pragma-ade.nl</a> / <a class=3D"moz-txt-li=
nk-freetext" href=3D"https://context.aanhet.net">https://context.aanhet.n=
et</a>
(mirror)
<br>
archive=C2=A0 : <a class=3D"moz-txt-link-freetext" href=3D"https://=
github.com/contextgarden/context">https://github.com/contextgarden/contex=
t</a>
<br>
wiki=C2=A0=C2=A0=C2=A0=C2=A0 : <a class=3D"moz-txt-link-freetext" h=
ref=3D"https://wiki.contextgarden.net">https://wiki.contextgarden.net</a>
<br>
_________________________________________________________________________=
__________
<br>
</blockquote>
</body>
</html>
--------------ivWEmNYBfj0qSMqSrF2xrWNF--
--===============2418069589443796255==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : [email protected] / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
--===============2418069589443796255==--