From The Blog: Corona Labs annual update

There is no reason why you shouldn’t be able to compile with a recent version of Corona and get your app approved?

If you need a hand with anything just reach out to me (or another other dev here really) and I’m sure we’ll help you get your app back online.  Don’t let it (or your history) die…

Some of these posts surprise me a bit. I thought we were very clear that Corona Labs (the company) was ending and that Corona (the product) would go on and we are hoping there won’t be much of a noticeable difference.

I guess we didn’t succeed with that messaging.

Rob

Some of these posts surprise me a bit. I thought we were very clear that Corona Labs (the company) was ending and that Corona (the product) would go on and we are hoping there won’t be much of a noticeable difference.

 

I guess we didn’t succeed with that messaging.

 

Rob

Rob, you are right about this. To me, it’s still not obvious what will actually happen or how things will affect us. I think you have to be much clearer to avoid speculations and doomsday scenarios.

I don’t like to be picking on your wordings, but I believe that using sentences like “we are hoping there won’t be much of a noticeable difference” is one reason when it comes to causing speculations and wild guesses since they don’t leave any guarantees. It could just as well mean that we end up with very much noticeable differences because hoping wasn’t good enough. 

I also believe that the information about this could and should have been communicated better. Speaking for myself, it felt quite strange that I had to actively scan the forums to find this thread after seeing the initial “out of business” message in a random Facebook post. I checked my Facebook, Twitter, and the Corona Labs homepage first without finding anything more. Then went to the forums, didn’t see any posts that caught my eye there either. Of course it didn’t take long at all to find this thread, but just the fact that this information was “hidden” under the rather ordinary title “From The Blog: Corona Labs annual update” felt awkward. To me, these news are HUGE and definitely deserve more direct attention. Maybe you could have just sent an email to all registered Corona members to grab everyones attention and clarify things right from the start? I think that could have prevented a lot of the now ongoing speculations.

That said, keep up the good work. I really appreciate what you’re doing, and I’m strongly hoping for the best possible future of Corona!  :slight_smile:

By the way, @Rob, you said the forums were going to be migrated somewhere and/or changed. Will our profile statistics like how many points we have and how many posts we’ve made and post history remain or will some or all be lost?

  1. Likewise @Rob - good luck with everything outside of here!
  2. I’ve been aware of this for a long time and had discussions with some of the Corona engine developers (now ex- I guess) - who were extremely helpful in getting me started with work-arounds etc.
  3. It would be great if Patreon or some other platform could generate enough support funding for at least some core developers to consider Corona worthy enough to dedicate at least a portion of their time to keeping the engine updated. The question which really needs answering is:  How many  developers would this require and  how often would they be needed? That would depend on the current state of the engine code, whether any of it could be converted to pure Lua and if the current engine developers are willing (while holding down a permanent job?)

Point 3 here can only really be answered by the current CoronaLabs staff and obviously I wouldn’t want any NDA’s to be broken, but positive answers would certainly help build confidence in the future.

That’s why I’m not checking the forum that much the last days.

Hopefully when we move to another structure these posts will stop appearing :).

Our goal at a minimum is to save the posts. Profile stats etc. Maybe not as much.  If we can just move the database off of the expensive infrastructure to something more cost effective, then there shouldn’t be anything in the way of changes, other than possibly eventually breaking the ties to developer.coronalabs.com. If we end up changing software, which there is some desire to do, we will port as much as is reasonable.

Rob

3 is really a tough question to answer because there are so many scenarios ranging from getting people working on the engine out of passion to keep things successful. Hiring out one-time contracts for certain tasks. Hiring out on-going contracts.  There are a lot of possibilities.

Vlad’s time, given the things we know we have to do, is pretty allocated for the 6-9 months. If you want things done more faster, then either pitch in skills, or more donations to help fund project contracts. 

Rob

Hi Rob,

I’m a little confused: is Vlad’s Github the definitive place where we can support Corona development financially, or is this not yet final?

If this is the final place to pitch in with money, could a blog post be made so it’s on the front page for all to see?

Thanks,

Thomas

I’m really sad about it …

But I have an objective question: I am using Corona in important projects, among them a course at the Pontifical Catholic University of Rio de Janeiro.

Testing the generation of builds for Android, I found that it is not working. See log below.

What could be happening?

I appreciate any information or guidance

PS: I also tested using the “stable version” (218.3326) and I was also unable to generate the build

11:04:38.552  

11:04:38.552  Corona Simulator 2020.3575 (Feb 15 2020 03:11:04)

11:04:38.552  

11:04:56.133  

11:04:56.133  Copyright © 2009-2020  C o r o n a   L a b s   I n c .

11:04:56.133  Version: 3.0.0

11:04:56.133  Build: 2020.3575

11:04:56.133  Platform: GT-I9300 / x64 / 10.0 / Intel® HD Graphics 4000 / 4.0.0 - Build 10.18.10.4358 / 2020.3575 / pt_BR | BR | pt_BR | pt

11:04:56.144  Loading project from:   C:\Users\Public\TS21\Corona\Sample Code\GettingStarted\HelloWorld

11:04:56.144  Project sandbox folder: C:\Users\Fernando\AppData\Local\Corona Labs\Corona Simulator\Sandbox\helloworld-718C1AF531ADB1DDAB7F1D538D5054A2\Documents

11:05:44.049  Testing credentials for ‘C:\Users\Public\TS21\Corona\Native\Corona\mac\bin\CoronaBuilder.app\Contents\Resources\debug.keystore’: 

11:05:46.403  Picked up JAVA_TOOL_OPTIONS: -Duser.language=en

11:05:50.913  Using custom build id from app bundle: 00000 (AppSettings.lua)

11:05:50.913  

11:05:50.913  Using custom Build Id 00000

11:06:01.990  @ver > NUL

11:06:01.990  Exception in thread “main” javax.net.ssl.SSLException: Received fatal alert: protocol_version

11:06:01.990  at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)

11:06:01.990  at sun.security.ssl.Alerts.getSSLException(Alerts.java:154)

11:06:01.990  at sun.security.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:1959)

11:06:01.990  at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1077)

11:06:01.990  at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1312)

11:06:01.990  at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1339)

11:06:01.990  at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1323)

11:06:01.990  at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:563)

11:06:01.990  at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)

11:06:01.990  at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1300)

11:06:01.990  at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)

11:06:01.990  at org.gradle.wrapper.Download.downloadInternal(Download.java:66)

11:06:01.990  at org.gradle.wrapper.Download.download(Download.java:51)

11:06:01.990  at org.gradle.wrapper.Install$1.call(Install.java:62)

11:06:01.990  at org.gradle.wrapper.Install$1.call(Install.java:48)

11:06:01.990  at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:69)

11:06:01.990  at org.gradle.wrapper.Install.createDist(Install.java:48)

11:06:01.990  at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:107)

11:06:01.990  at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)

11:06:01.990  Picked up JAVA_TOOL_OPTIONS: -Duser.language=en

11:06:02.318  Android build failed (1) after 12 seconds

Hi Thomas.

For now, until May 1, the official way to support ongoing Corona development is to spend money in the marketplace. Pay for your splash screen, buy ad plugins, support third-party developers.  I know it’s a hard concept to think of it as “I’m only buying X plugin for 2 months”, but you shouldn’t think of it in those terms. The question you should ask is how much are you willing to spend a year to fund Corona development. If that’s say $10 / month, your $99 splash screen is pretty much that level of support. Any money you spend in the Marketplace is gong to fund development.

Now Vlad has setup a donation site on GitHub. This will be the official place after May 1. There may be Patreons, Kickstarters, GoFundMe’s etc. but for now, the GitHub site is the main one. Because we have morals, Corona Labs is currently paying us. Asking for fundraisers now feels like double dipping and of course those funds will go further if we don’t have to draw on those funds until after May 1.

Rob

@fjefferson. Welcome to the community forums. The Forums are the best place to ask this question. 

However, our forums use different discussion topics called “threads” so discussions can be focused. When you ask an unrelated question on a different discussion, it’s called “Hijacking” and it’s now allowed. 

Please create a new topic with your question. This thread is to discussion Corona’s open source future.

Thank you for your cooperation.

Rob

Hi Rob,

Thanks for the clarification, I understand your points well and will support!

Regarding Earnings for Marketplace Vendors: will only those vendors with earnings above the minimum payout amount be imbursed, or will it be all vendors with outstanding earnings; when can vendors expect payments to be processed?

Thanks :slight_smile:

Payments are usually processed within a few days after submission. I’ll check with the CFO regarding minimum amounts.

Rob

@Rob,

At some point, Apple is bound to make another OS upgrade that will render my Corona apps useless without an ongoing, modern integration. Apple will, IMHO, kill Corona SDK as a cross-platform solution that remains continually stable. With that said, I hope that I’m wrong. I plan to use Corona SDK as long as possible, so I must become a Corona Native developer.

Can you create a video that helps us see, in the best way possible, how to change into a Corona Native developer? I’m a dinosaur assembly language programmer from the 80s. But the process as I’ve seen it still wasn’t clear enough to help me switch over, or I would have done so.

I applaud your new work to try and make the Native work-flow easier, like I’m using it now. Or did I misunderstand your post?

Why do you think we’re not working towards employing Apple’s Metal? I think it is totally doable.
Also, I don’t understand why do you want to move towards Corona Native. Corona Simulator would get offline support. Build would be fully offline, with plugins collected from the hard drive. There’s already a prototype of it. All “com.coronalabs” plugins would be available for download for free (including paid plugins) as long as Github supports, and you can download puchased plugins from the store from 3rd party developers right now too.
 
I don’t see what the gloom is about, [member=’ troylyndon’]. It’s going to be fine. I fully intend to get crowdfunding going, and start from bottom up. Work on the engine full time, and if I would get over some threshold, I’ll hire contractor and developers. I have full on hope on supporting Switch at some point, but first: Apple’s Metal (probably via MoltenVK), AndroidX and modern Windows.

@vlad, your response is MUSIC to my ears. :slight_smile:

It helps when you read what has been said before you make your own predictions :slight_smile: nice reply vlad!

Earlier in this thread @ michaelflad mentioned that I’d been looking into doing a Vulkan backend, which in theory would streamline Metal integration, via the MoltenVK library just mentioned by @ vlads.

Vulkan is quite a strange beast, coming from OpenGL or older flavors of DirectX. It is as verbose as everyone says. It also deliberately offers very few conveniences, in keeping with its MO of shucking overhead wherever possible.

Some time early last year I worked my way through the Vulkan tutorial, as well as all but the most recent of Maister’s blogs, to get a general idea of what Vulkan is and some of what comes up in practice. Alongside this, I did some investigation of where things might go in the Corona source, stubbing out some of the bits in question, but then got cold feet and went no further.  :slight_smile:

As a clumsy digression, lately I’ve pondered–and this predates the announcements behind this thread–streaming a few projects every now and then. I’m still cutting my teeth on OBS, but otherwise hoping to start soon. Quite a few things come to mind, to explore and / or refine, as I’m getting my feet wet. Plugins and open source dabbling should feature prominently.

The upshot of this being that I’d like to dive into Vulkan on said streams. It would put my feet to the fire, certainly. I’ve been away from it a while, so some review is definitely in order, but maybe a few weeks in? Of course, how well any of this goes remains to be seen!  :stuck_out_tongue:

Anyhow, the aforementioned Vulkan tutorial is quite methodical, culminating after many steps in a shaded, textured rectangle. In the best-case scenario, one could track the process exactly and wind up with the shiny Corona result. Actual development might not be quite so rosy, but it seems a reasonable plan of attack.