[LDPE] 1.8.76 Released (rotation bugfix / edger2 defaults / slashes)


[LDPE] 1.8.76 Released (rotation bugfix / edger2 defaults / slashes)
#1
Hey,

this release finally fixes the annoying bug regarding rotations with the manipulator.
Thanks to Philo and Fredrik I was able to find all the root causes for this.

[Image: imgDuke2.png]

As always, you can download LDPE from this page:

http://nilsschmidt1337.github.io/ldparteditor/

Changelog:

(2 new features and 1 bug fix)

With this release you will be able to...
  • ...be warned about "slashes" in subfile references and you can "Quick Fix" it.
  • ..."Exclude Unmatched Edges" by default in Edger2.

The following critical issue is fixed:

  1. The 3D manipulator orientation got polluted during rotation.

The program was tested intensively with "real world" files.
However, something can go wrong in about 140.000 lines of code.

Installation on Windows:

  1. Download and extract LDPartEditor_win32_x64.zip
  2. Run LDPartEditor-1.8.76.msi
  3. Start LDPartEditor from the start menu
Installation on Linux:

  1. Download and extract LDPartEditor_linux_x64.zip
  2. Install ldparteditor_1.8.76-1_amd64.deb
  3. Start LDPartEditor from the menu or via launcher
Installation on Mac OS X:

  1. Download and extract LDPartEditor_mac_x64.zip
  2. Mount LDPartEditor-1.8.76.dmg
  3. Drag LDPartEditor.app to the Applications folder
  4. Copy ldparteditor.sh to your home folder
        4a. Open a Terminal.app and run ./ldparteditor.sh
        4b. Or open a Terminal.app and run /Applications/LDPartEditor.app/Contents/MacOS/LDPartEditor

I listen carefully to your requests and possible complaints. Please leave me a message, with your thoughts and wishes to further improve the software.

LDPE is a 3D CAD application: The overall system requirements are higher. While I recommend to use a powerful 64-bit multicore system, it could be possible, to run LDPE on older machines as well.

System Requirements:

Minimum System Requirements:
  • OpenGL 2.1 compatible Graphics Card
  • Operating System (64-bit): Windows [7 or newer], Linux [e.g. Ubuntu Linux >=14.4], Mac OS X [>=10.6]
  • CPU: Multicore-Processor e.g. Intel Core 2 Duo or AMD Athlon II (>2.0Ghz)
  • RAM: 4GB
  • Video-Memory: 1 GB
  • Free Disk Space: 150 MB
Recommended Requirements:
  • Operating System (64bit): Windows 7,8,10,11, Linux [e.g. Ubuntu Linux >=14.4], Mac OS X [>=10.6]
  • OpenGL 3.3 compatible Graphics Card
  • CPU: Multicore-Processor with 4 cores (or more)
  • RAM: >4 GB
  • Video-Memory: >1 GB
  • Free Disk Space: 500 MB
  • For a faster start, LDPartEditor and the LDraw™ library should be installed on an SSD.
Reply
RE: [LDPE] 1.8.76 Released (rotation bugfix / edger2 defaults / slashes)
#2
(2024-03-15, 17:37)Nils Schmidt Wrote: ...be warned about "slashes" in subfile references and you can "Quick Fix" it.

Well, how shall I put it? This was a "Quick Fix" as I asked for it just yesterday. Big Grin 

w.
LEGO ergo sum
Reply
RE: [LDPE] 1.8.76 Released (rotation bugfix / edger2 defaults / slashes)
#3
(2024-03-15, 17:37)Nils Schmidt Wrote: this release finally fixes the annoying bug regarding rotations with the manipulator.
Yeah !!! this is great news! Heart
Reply
RE: [LDPE] 1.8.76 Released (rotation bugfix / edger2 defaults / slashes)
#4
Excellent news on the rotation bug! I have a few feature requests. Where would you prefer getting them?
Reply
Feature requests
#5
(2024-03-16, 9:02)Fredrik Hareide Wrote: Excellent news on the rotation bug! I have a few feature requests. Where would you prefer getting them?

Just write it here as a reply. I will create issues on github then.
Reply
RE: [LDPE] 1.8.76 Released (rotation bugfix / edger2 defaults / slashes)
#6
(2024-03-15, 20:08)Willy Tschager Wrote: Well, how shall I put it? This was a "Quick Fix" as I asked for it just yesterday. Big Grin 

w.

Agree! I even did not have the chance to ask for this featue and it is here! :-)

Thanks!
Reply
RE: [LDPE] 1.8.76 Released - merge triangle issue
#7
A minor one: sometimes, the triangle to quad conversion tool doesn't use the selected triangles, but another nearby one... See 


...and otherwise, the rotation bugfix works great!!!
Reply
RE: [LDPE] 1.8.76 Released - merge triangle issue
#8
(2024-03-18, 12:17)Philippe Hurbain Wrote: A minor one: sometimes, the triangle to quad conversion tool doesn't use the selected triangles, but another nearby one... See 
...and otherwise, the rotation bugfix works great!!!

Thanks, Philo. I created an issue (#1025).
Reply
RE: [LDPE] 1.8.76 Released (rotation bugfix / edger2 defaults / slashes)
#9
(2024-03-15, 17:37)Nils Schmidt Wrote:
  1. The 3D manipulator orientation got polluted during rotation.
...but there can still be problems (though it does work a LOT better Wink )
Got the rotate while moving bug...
Reply
Rotate while moving bug
#10
(2024-03-18, 20:06)Philippe Hurbain Wrote: ...but there can still be problems (though it does work a LOT better Wink )
Got the rotate while moving bug...

Got it. I documented the problem in issue #1026.
Reply
RE: [LDPE] 1.8.76 Released (rotation bugfix / edger2 defaults / slashes)
#11
If I've seen it correct you haven't updated the copyright date for the loading screen... ;-)
Reply
RE: [LDPE] 1.8.76 Released (rotation bugfix / edger2 defaults / slashes)
#12
Nils,

* The need to save after running Edger before you are able to do some more editing is back.
* Parts opened from the LDraw root folder are no longer read-only.
* Creating a new part you have to name it and save a copy again, before you can work on a blank page.

w.
LEGO ergo sum
Reply
RE: [LDPE] Move subfile to manipulator precision
#13
Sometimes, move subfile to manipulator has a precision issue:
Reply
Root cause for precision issue / workaround
#14
(2024-03-22, 9:25)Philippe Hurbain Wrote: Sometimes, move subfile to manipulator has a precision issue:

It seems to be an issue when you move the manipulator to the average point of a selection.
I can try to inrease the accuracy for this case (especially when the selection contains only a single vertex). I created issue #1027.

Temporary Workaround:
(when you want to move the manipulator to a vertex position)

1. Select the vertex
2. "Move the manipulator to the average point of the selection."
3. "Move the manipulator to the nearest vertex." (this is precise)

Finally, you can move a subfile to the manipulator with maximum precision.
Reply
RE: Root cause for precision issue / workaround
#15
(2024-03-22, 17:40)Nils Schmidt Wrote: It seems to be an issue when you move the manipulator to the average point of a selection.
I can try to inrease the accuracy for this case (especially when the selection contains only a single vertex). I created issue #1027.

Temporary Workaround:
(when you want to move the manipulator to a vertex position)

1. Select the vertex
2. "Move the manipulator to the average point of the selection."
3. "Move the manipulator to the nearest vertex." (this is precise)

Finally, you can move a subfile to the manipulator with maximum precision.
Thanks for the workaround!
Reply
RE: [LDPE] 1.8.76 Released (rotation bugfix / edger2 defaults / slashes)
#16
(2024-03-19, 21:00)Max Martin Richter Wrote: If I've seen it correct you haven't updated the copyright date for the loading screen... ;-)

Thanks. I updated it last week.
Reply
RE: Root cause for precision issue / workaround
#17
(2024-03-22, 18:04)Philippe Hurbain Wrote: Thanks for the workaround!

It will be solved in the next release. I implemented a solution today.
Reply
Rotate while moving bug fixed
#18
(2024-03-18, 20:06)Philippe Hurbain Wrote: ...but there can still be problems (though it does work a LOT better Wink )
Got the rotate while moving bug...

I was able to fix it and will deliver a solution with the upcoming release 1.8.77.

One way of mitigating this issue in the current version:

1. Switch to the "Rotate" mode (key "3")
2. Move the cursor away from the manipulator, without pressing any button. This will release the "stuck" rotation.
3. Switch back to the "Move" mode (key "2")
Reply
merge triangle issue solved
#19
(2024-03-18, 12:17)Philippe Hurbain Wrote: A minor one: sometimes, the triangle to quad conversion tool doesn't use the selected triangles, but another nearby one... See
...and otherwise, the rotation bugfix works great!!!

I was able to fix this. The root cause was that the triangle to quad conversion looked at nearby triangles to find a better match outside of the selection scope if they shared the same colour.
Reply
« Next Oldest | Next Newest »



Forum Jump:


Users browsing this thread: 1 Guest(s)