LDraw.org Discussion Forums
[LDView] LDView 4.4 Beta 4 test release - Printable Version

+- LDraw.org Discussion Forums (https://forums.ldraw.org)
+-- Forum: LDraw Programs (https://forums.ldraw.org/forum-7.html)
+--- Forum: LDraw Editors and Viewers (https://forums.ldraw.org/forum-11.html)
+--- Thread: [LDView] LDView 4.4 Beta 4 test release (/thread-24607.html)

Pages: 1 2 3


LDView 4.4 Beta 4 test release - Travis Cobbs - 2021-05-08

I have posted a test release for LDView 4.4 Beta 4 to GitHub:

https://github.com/tcobbs/ldview/releases/tag/v4.4_Beta4

This release mainly contains bug fixes since Beta 3, along with a few new features. The Mac version should work better on macOS Big Sur, and has an updated icon (as well as updated LDR and MPD icons on Big Sur).

One of the bug fixes with the most potential to introduce unexpected problems involves a change to the curve smoothing. It now does not try to smooth out two facets that are joined by both a conditional line and an edge line. This can happen (for example) when a curved primitive like a torus extends to the edge of a part. This happens on part 88293, which is the part that was included in the original bug report that caused me to fix the problem. I suspect that it happens in other parts also. I would greatly appreciate it if people would let me know if they see any regressions in LDView's curve smoothing.

Note: because of this new behavior, I expanded the angle over which curves can be smoothed. This improves (for example) the hair on the Bart Simpson minifig head, and probably improves other parts as well. However, it's possible that I went too far, and it will result in areas being smoothed that shouldn't be, so please be on the lookout for that as well.

The ChangeHistory.html file that is included in the release lists all of the changes since LDView 4.3. In the macOS version, ChangeHistory.html is in the dmg. In the Windows version, ChangeHistory.html gets installed to wherever you install LDView (C:\Program Files\LDView by default). I'm actually not sure where it goes in the Linux version. Please see my Alpha 6 announcement for a list of what I feel are the most important changes relative to LDView 4.3.

Please let me know about any problems you find. The preferred way to do that is with LDView's GitHub Issues tracker. However, if you do not want to create a GitHub account so that you can do that, you can reply to this message.

My hope is that this is the last beta release before an official LDView 4.4 release.


RE: LDView 4.4 Beta 4 test release - Bertrand Lequy - 2021-05-09

Beta installed. I'll let you know if something goes wrong.


RE: LDView 4.4 Beta 4 test release - Bertrand Lequy - 2021-05-09

I got a problem with this part : 98138p19

I don't know why but the 2 following lines
1 226 .5 0 -1.5 -1.1 0 0 0 1 0 0 0 1.1 3-4chrd.dat

1 226 .5 0 -4.25 -1.1 0 0 0 1 0 0 0 -1.1 3-4chrd.dat

are not rendered correctly (maybe a 3-16chrd or a 1-4chrd instead of a 3-4chrd).

I inlined the prims with LDDP and the issue disappeared


EDIT I had a problem with this one too :98138p8f

where the line

1 0 0 0 0 -2.5 0 0 0 1 0 0 0 2.5 1-16ndis.dat

doesn't appear in the render

No problem after inlining it.

EDIT2 : And with this one : 3010pzo

the lines

1 16 0 12 -10 0 0 11.7 11.7 0 0 0 1 0 48\1-12ndis.dat
1 16 0 12 -10 0 0 -11.7 11.7 0 0 0 1 0 48\1-12ndis.dat

don't render properly.

here again inlining solve the issue (at first I used an old unofficial file since this one has been released as official in the last update that's why I chande this line)


RE: LDView 4.4 Beta 4 test release - Travis Cobbs - 2021-05-09

Thanks for the report. Unfortunately, I'm not able to reproduce any of these problems. All three parts render correctly for me, on both Mac and in Windows (with primitive substitution enabled). Assuming that you are in Windows, can you export the LDView tree from your registry and email it to the LDView email address? I'll see if some setting you have is causing the problem. (If I can reproduce the problem, hopefully I can fix it.)

Also, try setting UseStrips=0 on the command line (or in the Windows Registry) to see if it makes a difference.


RE: LDView 4.4 Beta 4 test release - Bertrand Lequy - 2021-05-09

(2021-05-09, 19:55)Travis Cobbs Wrote: Thanks for the report. Unfortunately, I'm not able to reproduce any of these problems. All three parts render correctly for me, on both Mac and in Windows (with primitive substitution enabled). Assuming that you are in Windows, can you export the LDView tree from your registry and email it to the LDView email address? I'll see if some setting you have is causing the problem. (If I can reproduce the problem, hopefully I can fix it.)

Also, try setting UseStrips=0 on the command line (or in the Windows Registry) to see if it makes a difference.

I tried with 3010pzo without using commnd line and still have the issue. I'll see later with UseStrips=0 later.

When I talked about render, I should have say render of the exported pov file. no rendering problem using LDView, it was obvious for me, but it wasn't obvious for any reader, sorry.


RE: LDView 4.4 Beta 4 test release - Travis Cobbs - 2021-05-10

(2021-05-09, 20:11)Bertrand Lequy Wrote: I tried with 3010pzo without using commnd line and still have the issue. I'll see later with UseStrips=0 later.

When I talked about render, I should have say render of the exported pov file. no rendering problem using LDView, it was obvious for me, but it wasn't obvious for any reader, sorry.

Thanks. For future reference, just to be clear, LDView is a rendering program that renders LDraw models in real-time. It can also export them to POV, which can then render them with higher quality. I am able to reproduce the POV export problem in those parts.


RE: LDView 4.4 Beta 4 test release - Philippe Hurbain - 2021-05-10

(2021-05-08, 6:40)Travis Cobbs Wrote: This happens on part 88293, which is the part that was included in the original bug report that caused me to fix the problem. I suspect that it happens in other parts also. I would greatly appreciate it if people would let me know if they see any regressions in LDView's curve smoothing.

Note: because of this new behavior, I expanded the angle over which curves can be smoothed. 
Much appreciated changes. I'll keep my eyes peeled to see if this causes other problems.


RE: LDView 4.4 Beta 4 test release - Travis Cobbs - 2021-05-10

(2021-05-10, 7:32)Philippe Hurbain Wrote: Much appreciated changes. I'll keep my eyes peeled to see if this causes other problems.

Thanks. Just to be clear on the change, I updated the code that processes conditional lines for use in smoothing, and made it so that if there is an edge line in the same place as a conditional line, it ignores that conditional line during smoothing. This was a relatively minor change, and while it will affect file loading somewhat when smoothing is enabled, hopefully it won't be much. Also, it means that if an edge line partially overlaps a conditional line, the conditional line will still be included in the smoothing calculations.


RE: LDView 4.4 Beta 4 test release - Bertrand Lequy - 2021-05-17

I've encoutered a similar problem after exporting a part to pov today : 19474-f3, some triangles weren't corectly exported or rendered.

In fact the problem is on the subpart : u9418
it seem that four 1-16ndis.dat are cut by the x/z plane and that the +y pixels aren't rendered.

Once again, inlining the primitive using LDDP solved the issue.


RE: LDView 4.4 Beta 4 test release - Travis Cobbs - 2021-05-17

(2021-05-17, 20:26)Bertrand Lequy Wrote: I've encoutered a similar problem after exporting a part to pov today : 19474-f3, some triangles weren't corectly exported or rendered.

In fact the problem is on the subpart : u9418
it seem that four 1-16ndis.dat are cut by the x/z plane and that the +y pixels aren't rendered.

Once again, inlining the primitive using LDDP solved the issue.

Thanks. I'll investigate. The previous chrd issue was caused by the clipping plane needing to swap to the opposite side of the origin for all chrd primitives that were more than half circles, so the fix was easy. (Note that this was always broken.) Hopefully this is a similar issue, with a similar fix.