99455.dat part missing in LPub3d fade steps?

[Trevor Sandy]

Kevin - I've made some changes to the fade step functionality in the just released v2.0.8. Let me now if your issue is resolved with this release or not?

Cheers,

Unfortunately, I'm still having the exact same problem.  Faded parts not showing up at all, and a crash when rebuilding the Fade Color Parts List.  Here are the last entries in the log file, if it's any help:

2016-08-05T14:29:49.965 STATUS  lpub.h void Gui:tatusMessage(bool, QString) @ln 613 "Page display ready."
2016-08-05T14:30:33.206 INFO  threadWorkers.cpp bool ColourPartListWorker::processArchiveParts(const QString&) @ln 976 "Processing Unofficial Library - Parts Count: 2358"
2016-08-05T14:30:37.418 INFO  threadWorkers.cpp bool ColourPartListWorker::processArchiveParts(const QString&) @ln 1020 "Finished Unofficial Library"
2016-08-05T14:30:37.716 INFO  threadWorkers.cpp bool ColourPartListWorker::processArchiveParts(const QString&) @ln 976 "Processing Official Library - Parts Count: 13502"

I again refreshed the Official and Unofficial parts archives, but still the same issue.

I don't know if it's relevant, but every time I reset the Fade Files Cache, it reports "0 items removed" even after stepping through many pages of successfully faded steps.

Thank you.

Kevin

Well I'm completely stumped on why your fade step generation keeps crashing    

Try the fade generations a few times... It did complete the unofficial archive which but failed on cycle 2 of 3 - capturing the files from the official archive. Anyway, for now, use the provided fadestep list - the installation replaces your old one. You can see the generation date as Aug 01, 2016. 

Can you send the entire log? You can see in there if fade files are being generated or not.

Fore the fade parts not showing up, did you clear you model cache before generating ? It's the LPub3D directory created where you store you model file. If there are already renderings (old ones without fade parts displayed), LPub3D will not create new ones. So you might think the problem still exist when, if fact, it does not. Can you check this?

Cheers,