[LDView] LDView 4.7 Released

[Travis Cobbs]

LDView 4.7 is now available.

You can download this release from the LDView Downloads Page.

You can see the Change History here.

[Orion Pobursky]

Nice. I'll have to rebuild our LDView binaries and test it out on the PT (when I get back from vacation).

[Magnus Forsberg]

LDView 4.7 is now available.

Once I have clicked on the random colour button I can't get a new set of random colours. 
They stay the same, no matter what I do to refresh, or reload the part.

[Travis Cobbs]

Once I have clicked on the random colour button I can't get a new set of random colours. 
They stay the same, no matter what I do to refresh, or reload the part.

That's actually intentional, and was made that way in the previous version (4.6). From the change history:

Updated so that random colors produce the same colors each time you load a given model. (That was the original intended behavior. This feature is designed for parts authors, so having new colors show up every time they reload can be distracting.)

If the old behavior is truly desired, you can submit an issue on GitHub. Or if you don't want to create a GitHub account to do that, let me know here, and I can submit an issue.

[Magnus Forsberg]

That's actually intentional, and was made that way in the previous version (4.6). From the change history:


If the old behavior is truly desired, you can submit an issue on GitHub. Or if you don't want to create a GitHub account to do that, let me know here, and I can submit an issue.

What's the point of calling it "Random Colors" if the colours are not randomized?

I might understand it as a model builder, but not as an part designer, working on dat-files.
Randomizing colors is the simplest way of detecting overlapping tris/quads using the same vertices. Sure, I might find them if I use Edger2, but a visual inspection is qucker.

I wish to have the old Reload behaviour back. Could you please make an issue for me?
 
Maybe like this?
Toggle Random Color to turn off/on the same set of colours.
Click Reload to get a set of new random colours every time.

Or, is it possible to have different behaviour working on dat- and ldr-files?

(I didn't use 4.6 version. I now moved from 4.5 to 4.7)

[Travis Cobbs]

Issue created:

https://github.com/tcobbs/ldview/issues/106

[Takeshi Takahashi]

I have been encountered some crashes when loading LDraw files on my PC:

• CPU: AMD Ryzen 7 5800H
  
• Memory: 32GB
  
• GPU: Integrated Radeon Graphics, AMD Software Adrenalin Edition 25.8.1 (newest)
  
• OS: Windows 11 25H2
  

The LDView app closes suddenly without any error messages.

I thought this issue occurs randomly, but finally the transparent section have something to do with the crash.
For example, current official 3081cc01.dat causes it as a minimal reproducible condition.
If the file is modified with the glass colour from 47(Trans-clear) to 15(White), the issue vanishes.

I understand that some error log file help your debug, so could you let me know where the log file is stored?

[Travis Cobbs]

I have been encountered some crashes when loading LDraw files on my PC:

• CPU: AMD Ryzen 7 5800H
  
• Memory: 32GB
  
• GPU: Integrated Radeon Graphics, AMD Software Adrenalin Edition 25.8.1 (newest)
  
• OS: Windows 11 25H2
  

The LDView app closes suddenly without any error messages.

I thought this issue occurs randomly, but finally the transparent section have something to do with the crash.
For example, current official 3081cc01.dat causes it as a minimal reproducible condition.
If the file is modified with the glass colour from 47(Trans-clear) to 15(White), the issue vanishes.

I understand that some error log file help your debug, so could you let me know where the log file is stored?

Someone else recently had a similar issue (with a part that included transparency). The issue went away from them when they updated their drivers. Could you see if updating your drivers fixes the problem?

[Takeshi Takahashi]

Someone else recently had a similar issue (with a part that included transparency). The issue went away from them when they updated their drivers. Could you see if updating your drivers fixes the problem?

Unfortunately, my GPU drivers are up-to-date.