@Vlads & @Rob, Here is the data after reboot from a hard crash caused by your Debug test verison.
@Vlads and @Rob, some good news. Although the graphic errors still occur, both the new Patched version and the Last Public Release DO NOT cause a hard crash.
@Vlads, @Rob, appreciate your attempts to fix. I will use the patched version for now - is there anything else you’d like me to try? Although this solves the hard crash problem, any idea about how to track-down the graphic glitches?
Also, looking online I see that the 2018 13" MacBook Pro uses: Intel Iris Plus integrated graphics 655 with 128MB of eDRAM
However, the 15" MacBook Pro uses: Radeon Pro discrete graphics with 4GB of video memory
Based upon @bmrpeal’s comments above, if you are seeking to find a system to duplicate the issues, you might want to consider getting the 13", as the ATI branded cards in the 15" seem to work for bmrpeal. The issue ‘appears’ from here to be related to the Intel graphics chipset. But then again, no one has yet reported from a 2018 MacBook Pro 15".
Btw, crash log you provided leads to weird places:
com.acronis.fileprotector
com.paragon-software.filesystems.ntfs
Where are you running it from. Is is hard drive or some other storage?
@Vlads,
> Paragon is my NTFS driver, as my project drive is formated via NTFS. Never had a problem with it, ever.
> Acronis is my backup software - it operates in background and it is widely used and known to be reliable.
Is it necessary that I put my project on the internal drive and turn off my backup software?
It’s worth trying.
Personally, talking generally, I have experienced thousands of problems trying to use ntfs on Macos … Many problems!, from computer freezing to involuntary reboots. I think Mac is completely incompatible with any ntfs version, wherever.
Can’t agree with that, have used Paragon NTFS for years with no problems. Although that doesn’t include running Corona projects from an NTFS drive.
@dodi_games, I’ve been using Paragon’s NTFS drivers with numerous drives on 4 different Mac configurations in the past 4 years. It works flawlessly, and wonderfully - so I concur with @nick_sherman’s comment.
Feel free to contact me with a private message if you want to get it working - I’d be happy to help you try.
@vlads, @Rob, moving my project to the internal non-NTFS drive appeared to solve the HARD crash problem - except, however, that Corona Simulator did CRASH. Here is the crash log: https://pastebin.com/4RapHxTn
@vlads,@Rob, I suppose that once you solve the Corona crash problem here, it will work again fine on NTFS. That’s my 99.9% educated guess because the CRASH occurs regardless of whether or not NTFS is used. It’s just that on NTFS, it causes a HARD CRASH. Hope this info helps. Very much appreciate your continued pursuit to solve this crash problem.
Hey! This is actually “good” news, because it shows traceback pointing to actual Corona. Could you please try running Debug & Patched builds I posted above, and see if they are crashing? Here’s links if you deleted em:
@vlads, as I wrote above, the Patched version did not crash - the graphics were still corrupted. The log included in my last post was for your Debug version.
https://pastebin.com/WaRGpkPZ
https://pastebin.com/DTXTggk1
Here is the crash logs when used Corona Simulator Debug.
bc_new_theway, what is your experience with “patched” one?
Here is the crash logs when used Corona Simulator Patched.
No thanks, I’m very good with my storage mechanism. What I wanted to explain is the way in which a software is used and for what it was created. Ex, if Corona SDK was created to run on Windows and Mac with its normal features, I do not see the reason for wanting to do things outside of the basic norm. I consider it unnecessary to have my new super computer, but to use it, I want to connect to the Tesla car that was put in orbit, use its radio and return to my computer in a fast and efficient way to listen Alien Radio 1040 when Windows or Mac have not created their computers to operate by default in that way. It is pure opinion. I’m writing with much respect, all of you has a lot of programming experience than I. Now, if it’s about not losing data, I can talk to you, from my facets as a music producer, graphic artist, as far as I am now I learned that the discs are not eternal, that they have to be changed even if they are in good condition, that you can not have the data stored on a single disc and pray that it will not be damaged. I have a good clone computer that I mount myself, has an external disk of 2T SSD that is where I keep everything, believe me everything, especially the musical content of all my work, my life, which at least every two years I sell half price and buy a new one to continue with the cycle. Also the most important thing for me is in a cloud that allows me to download, edit and upload from Windows or Mac. On the Mac I also have an external disk that contains everything, but the disk is for Mac and only for the Mac.
Everyone has their needs and their way of doing things differently from others.
If Corona SDK was created to work efficiently from the internal drive of each computer and an error occurs because some user wants to do things in a different way I consider that it is not the responsibility of the engineers to restructure an entire software because there is a crash when someone use a disc not compatible with a system from a third-party program that allows me to use it.
I repeat, I am saying this as an opinion and my words are with great respect for all who read them.
@dodi_games, you were clear and respectful. Everyone has their own reasons for configuring their setup, as do you. Thank you for your lengthy explaination, but it wasn’t necessary. If you want to discuss it further, please open a new topic - today, we discovered that @Vlads new patch no longer hard-crashes the system. The remaining issue is unrealted to our system configuration.
@Vlads, thank you for solving the hard-crash with the patch. Will the patch be made available in a daily build soon?
What else can we do to help you solve the graphic glitch/error?
