A few questions about desktop build

Solar2D General Questions/Discussion
#1

Hi,

Not too long ago some of my friends asked me if I could work as a programmer for a little pc game they want to make, since I’ve been into video game development for a couple years. That same day I got an email from Corona labs, announcing support for building Mac and Win32 desktop apps (how convenient :) ).

I’m very excited about this and I’d like to ask a few question. First, has there been any news about when will this be available? Is this update coming in a few weeks or is it still months away? If I’ll have to wait for like 6 months I will probably have to find something else to make this game.

Also I would like to start working on the game right away. And when desktop builds arrive, can I just change controls to keyboard input and the game will be ready for desktop computers?

I think that’s all I’d like to ask for now.

Thanks in advance!

#2

I’m sure a Corona person will provide some additional info here, but to answer #1, all of the info that is public says that OSX/Windows is/will be in private beta. Here’s a link demoing some Mac builds. This doesn’t give a timeframe, and I doubt anybody from Corona would give you a definitive estimate, but it gives you something to go on.

As far as #2, you can program for keyboard keys right now. I have controls mapped to keyboard keys as a general rule, as it makes it way easier to debug without clicking like crazy with my mouse. Some might say this is counter-intuitive because you need to kick the tires of your touch functionality implementation, but I feel that’s always best done on-device, and not through the simulator. One mouse click does not equal one finger tap/press!

HTH

#3

Well, I have my bets on Corona, since I’ve worked with it before.

Since they were already showing some examples, I think/ hope this update will come in a month or two. And when it does, I’ll just build my project for the pc.

As for the keyboard input…that’s something I never used before (yes, I was clicking the on-screen touch buttons like crazy, or just compiled and installed the game on my device).

How can I map game controls to the keyboard? Are there any examples of this in the SDK APIs?

#4

Well I can’t say anything officially other than we are not to a closed beta yet. 

Rob

#5

Very exciting stuff, nonetheless!

#6

The docs for the key API are pretty well-done and straight forward. They are your best bet to get started mapping keyboard strikes. 

http://docs.coronalabs.com/api/event/key/index.html

Incidentally, one would presume that getting your games working on an Ouya or a Gamestick would mean they would translate nearly 1:1 to x86 or OSX builds. That opinion isn’t backed up by any science, knowledge, or tea-leaves. Just seems to make sense logically!

#7

Cool! Looks simple enough. I’ll implement keyboard controls soon.

Alright, but if I make a game now, that same code will work if I build it for desktop pc’s as well? (Other than smartphone exclusive stuff like touchscreen input and accelerometer)

Or would I have to start over?

#8

No worries - the same code will work! Well, for 95% tot 99% of the code at least.

#9

Great, I’ll get to work then. Thanks everyone!

#10

Are there any updates on Mac App and Win32 App support that was announced in March? I would love to start experimenting with Steam deployment-not to mention get a Greenlight started! (Since, I’ve never put a game on Steam, I’m waiting to make sure the Corona SDK Win32 build will work with Steam.)

Most of our apps already have HD visuals as well as Ouya, FireTV and GameStick controller compatibility so my fingers are crossed for a smooth port to Steam!

#11

OS-X builds are in a closed beta now.  The Windows x86 builds are getting closer. 

Rob

#12

dont forget full screen, thx

#13

I’m sure a Corona person will provide some additional info here, but to answer #1, all of the info that is public says that OSX/Windows is/will be in private beta. Here’s a link demoing some Mac builds. This doesn’t give a timeframe, and I doubt anybody from Corona would give you a definitive estimate, but it gives you something to go on.

As far as #2, you can program for keyboard keys right now. I have controls mapped to keyboard keys as a general rule, as it makes it way easier to debug without clicking like crazy with my mouse. Some might say this is counter-intuitive because you need to kick the tires of your touch functionality implementation, but I feel that’s always best done on-device, and not through the simulator. One mouse click does not equal one finger tap/press!

HTH

#14

Well, I have my bets on Corona, since I’ve worked with it before.

Since they were already showing some examples, I think/ hope this update will come in a month or two. And when it does, I’ll just build my project for the pc.

As for the keyboard input…that’s something I never used before (yes, I was clicking the on-screen touch buttons like crazy, or just compiled and installed the game on my device).

How can I map game controls to the keyboard? Are there any examples of this in the SDK APIs?

#15

Well I can’t say anything officially other than we are not to a closed beta yet. 

Rob

#16

Very exciting stuff, nonetheless!

#17

The docs for the key API are pretty well-done and straight forward. They are your best bet to get started mapping keyboard strikes. 

http://docs.coronalabs.com/api/event/key/index.html

Incidentally, one would presume that getting your games working on an Ouya or a Gamestick would mean they would translate nearly 1:1 to x86 or OSX builds. That opinion isn’t backed up by any science, knowledge, or tea-leaves. Just seems to make sense logically!

#18

Cool! Looks simple enough. I’ll implement keyboard controls soon.

Alright, but if I make a game now, that same code will work if I build it for desktop pc’s as well? (Other than smartphone exclusive stuff like touchscreen input and accelerometer)

Or would I have to start over?

#19

No worries - the same code will work! Well, for 95% tot 99% of the code at least.

#20

Great, I’ll get to work then. Thanks everyone!