Planned

anyone getting weird font errors in Lightform?

0

letters like 'F' and 'D' were being substituted with weird characters. didn't know if this was a known thing or not.

Comments

8 comments
  • Official comment

    Thanks for submitting the bug report within the app Gray. The bug report let our team figure out that this issues is affecting the MacPro5,1 which has the Intel(R) Xeon(R) CPU X5675. Now that we know this is occurring on this processor we can work on a fix for a future release. 

    Thanks for helping us improve Lightform!

  • like this.

     

  • done and done!

  • Hey Gray, thanks for reporting this. We have seen in the past and thought it was fixed for all users. 

    Could you submit a bug report with the purple question mark in the bottom right corner? This will help us gather more info to figure out what is going on and work on a fix. 

  • thanks for the update, Ehsan! should we expect an update soon? I can fight through most of it, knowing where buttons live and what they do. it doesn't seem to affect the functionality of the LF1. just an interface bug?

  • Of course. And yes, everything should function as expected. This seems to just be an interface bug corrupting text strings. 

  • Just received our LF1 earlier today and am trying it out tonight and had some issues and saw this thread.

    I am also seeing odd font UI issue's on a Mac Pro 3,1 running Mojave 10.14.1 with dual quad core 3.2ghz Intel Xeon X5482 processors. I also saw the note about some NVIDIA cards - this same machine is running an NVIDIA GeoForce GTX 680 w/ 2048MB RAM

    One issue I cant get past is scanning. It makes it through to where its processed the scans and is downloading them, and then consistently crashes.

    With this of note in the crash log:

    Application Specific Information:
    terminating with uncaught exception of type cv::Exception: OpenCV(3.4.3) /Users/kevin/Code/deps-source-builds/downloaded-sources/opencv/src/modules/imgproc/src/smooth.cpp:5241: error: (-215:Assertion failed) src.depth() == CV_8U && (cn == 1 || cn == 3 || cn == 4) in function 'medianBlur'

     

    Happy to provide extended crash logs and more info.

  • Hey Robert. Thanks for reporting this! This is super helpful. 

    It would be great if you could submit a bug report using the purple question mark in the app so we can collect a few more logs and look into what else might be going on. If you have any crash logs saved, you can paste them into the bug report. Thanks!

Please sign in to leave a comment.

Didn't find what you were looking for?

New post