Welcome! Hopefully you will be able to put up with us! Underneath our griping and complaining we really are a grateful bunch. (For the most part :P )
I love griping and complaining. It means you care about the product! It's my job to make sure we do something about your complaints and griping. And that's what I'll do!
LOL, get ready to feel a lot of love and welcome to Gamesalad.
PS two things I hate seeing from GS "very soon" and "next week",lol
Great to hear about all the communication and the (hopefully) more efficient development process. I know you said that you were just getting to know the team and you couldn't give us any real dates, but could you give us a very rough timeframe for Lau free? Like if it will be out within the next 6 months? Or a year?
And as others have said, if you search through all of our complaining, you will find the GameSalad community to be a great place
...but could you give us a very rough timeframe for Lau free? Like if it will be out within the next 6 months? Or a year?
I really can't give any time frame yet. But, philosophically speaking, I'm not convinced that we need to throw the entire Lua engine away to get the improvements we'd all like to see.
A lot of progress has been made on the lua-free native engine, but it's not ready for prime time yet. So, moving forward, should we focus all of our efforts on that? Or should we do what we can to blend the two engines together and optimize what we have? Tough questions for sure.
I will say that I won't put my weight behind any approach that pushes major improvements out by months. We need to turn stuff around faster than that.
That being said, I can't be more specific quite yet.
@PBGames I did the multi-player programming for Freelancer. I also led the development for an object-oriented database used as the back end for a game data pipeline. Also worked on an unannounced XBox 360 launch title that never made it.
Braydon_SFXMember, Sous Chef, PRO, Bowlboy SidekickPosts: 9,271
I really can't give any time frame yet. But, philosophically speaking, I'm not convinced that we need to throw the entire Lua engine away to get the improvements we'd all like to see.
What's this?! It looks like GameSalad might have made a really good hire. I was wondering why Lua was a problem. Isn't that what Corona uses?
Although, if Stephen is right, that's possibly another shift in direction for GameSalad. It's like watching a sports car stuck in the snow. One day it might take off and be amazing. But right now, it's a lot of tire spinning.
I did the multi-player programming for Freelancer.
Yup... looking like a good hire so far.
Then there's this...
NCsoft
NCsoft reminds me of Guild Wars, but that's ArenaNet. So I looked online to see the relation to Stephen. Oh no... Dungeon Runners! It was looking so good until then. Ha ha!
Freelancer is an amazing game though. "We don't run this establishment, but we have an understanding with the folks that do." So, I can look past Dungeon Runners... way past... I try not to look directly at it in general.
From what I remember, it was kinda a spoof on MMORPGs. I think the humor was appreciated by some, as I vaguely remember reading comments from people enjoying the game. But like so many games in the genre, it didn't survive.
That's why I liked Freelancer. I could run my own server. But considering that Microsoft pulled the plug on the matchmaking service, and I'm not sure if it's safe to run such old software on a publicly accessible computer, I'm not sure if that's a good idea for me to run a Freelancer server.
With your network gaming background, that might be a good place for you to focus... cross-platform multiplayer mobile gaming. Is that a new acronym... CPMMG?
I agree about the possibility of not throwing away the LUA engine. I know a couple of devs at my workplace use it and think its great, after talking to them about the latest update they thought that the update to LUAJIT was a really good move!
One thing that i'd like to suggest to improve performance is to introduce an atlas builder into Gamesalad. If all our project images could be combined when the app is published I think it'd make a really big difference!
Thanks for taking the time to introduce yourself, cant wait to see what you can do to improve on an already great piece of software!
I like you already Steven. You're direct and to the point and you have a sense of humor. Most of all you seem to have a passion and drive. These are the qualities that drive great things! Much success to you and you're vision.
Hi Steven, welcome! And what a great discussion you start. You did spook me, I was playing Elite on a commodore 64 emulator yesterday and then saw Freelancer here. Never saw it before. And in the video above some character has my name as well (Ludwig). Scaaaaaareeeeeey!!
I see you already made your fan base Looking forward to your input and progress on the engine!
@CodeWizard - Welcome! Sounds like we'll be seeing some really cool stuff coming up soon O:-) - Thomas P.S. Also.. you mentioned blending the two engines together. Do you really see that as a possibility? And if so, how (well) would it work?
@SnapFireStudios When I mention blending the two engines together, I don't mean making a nice engine smoothie.
What I mean is taking parts from the new native engine and bringing them into the current engine you're using. That way we can get improvements into your hands more quickly. This is because we're not waiting for all of the changes to be done and tested before sending them your way.
We're still having some internal discussions on this, but I'm definitely leaning toward improving the current engine through rapid iteration. Fix bugs, optimize systems, add features on a regular interval. You'll see improvements more quickly and there will be less risk on our end when delivering because the number of changes will be smaller per release.
The end result is the same: fixing performance problems, adding features, squishing bugs and reducing memory requirements. I'd personally like to get there in the most direct way possible and get changes in your hands as quickly as we can. Waiting on a massive rewrite is arguably not the best approach.
I'm happy to hear about your proposed philosophy of rapid iterations. This would give the community a better sense of how the program is growing over time and can be looked back at as a copious amount of easily defined benchmarks (speaking from a marketing perspective). It would help ease the discomfort of spending money to be Pro, seeing a new release with new bugs as well as old ones, and knowing that there likely won't be a fix for months. I can also see how this would make GameSalad more attractive to new users since a perception of constant visible growth is more attractive than a perception of irregular interstitial growth.
It'll be easier to let us know what was fixed as well which should make the necessary code altering on our end MUCH smoother and faster since we won't be guessing about what exactly broke and why.
To be honest about the native engine:
It feels much more like a brand that hasn't be introduced yet rather than a feature that hasn't been introduced yet. Quite frankly It's been way too long since it was announced and shown in an alpha state to not be a feature in some form or another. I personally don't care at all how you do it, so long as you do it in a way that helps make the platform more malleable for new features available in the mobile operating systems as well as improving performance and memory handling. A mix of LUA and what's already in the works is perfect, so long as it works.
What we want something that works extremely well. If you decide to go the hybrid route, I would consider ditching the name "Native Code Engine" and give it a new branding that sounds as exciting. Otherwise it'll be years before you hear the end of it.
I'm excited by your post. I like GS and my experience with the people who work there have for the most part been very good. I hope you bring the energy you bring here into the office with you. I can see some great things coming in the future if you do.
Comments
PS two things I hate seeing from GS "very soon" and "next week",lol
And as others have said, if you search through all of our complaining, you will find the GameSalad community to be a great place
A lot of progress has been made on the lua-free native engine, but it's not ready for prime time yet. So, moving forward, should we focus all of our efforts on that? Or should we do what we can to blend the two engines together and optimize what we have? Tough questions for sure.
I will say that I won't put my weight behind any approach that pushes major improvements out by months. We need to turn stuff around faster than that.
That being said, I can't be more specific quite yet.
Welcome to the forums! Woah! You worked at Microsoft? What did you do there?
I did the multi-player programming for Freelancer. I also led the development for an object-oriented database used as the back end for a game data pipeline. Also worked on an unannounced XBox 360 launch title that never made it.
My GameSalad Academy Courses! ◦ Check out my quality templates! ◦ Add me on Skype: braydon_sfx
Welcome!....I can't wait to see all the goodies that lie ahead!!! =D>
Although, if Stephen is right, that's possibly another shift in direction for GameSalad. It's like watching a sports car stuck in the snow. One day it might take off and be amazing. But right now, it's a lot of tire spinning. Yup... looking like a good hire so far.
Then there's this... NCsoft reminds me of Guild Wars, but that's ArenaNet. So I looked online to see the relation to Stephen. Oh no... Dungeon Runners! It was looking so good until then. Ha ha!
Freelancer is an amazing game though. "We don't run this establishment, but we have an understanding with the folks that do." So, I can look past Dungeon Runners... way past... I try not to look directly at it in general.
Aww, DR was a good game.
That's why I liked Freelancer. I could run my own server. But considering that Microsoft pulled the plug on the matchmaking service, and I'm not sure if it's safe to run such old software on a publicly accessible computer, I'm not sure if that's a good idea for me to run a Freelancer server.
With your network gaming background, that might be a good place for you to focus... cross-platform multiplayer mobile gaming. Is that a new acronym... CPMMG?
Yeah, there's a lot of reasons why a game doesn't "make it." Quality is oftentimes not the issue. But I am biased for sure!
I agree about the possibility of not throwing away the LUA engine. I know a couple of devs at my workplace use it and think its great, after talking to them about the latest update they thought that the update to LUAJIT was a really good move!
One thing that i'd like to suggest to improve performance is to introduce an atlas builder into Gamesalad. If all our project images could be combined when the app is published I think it'd make a really big difference!
Thanks for taking the time to introduce yourself, cant wait to see what you can do to improve on an already great piece of software!
Guru Video Channel | Lost Oasis Games | FRYING BACON STUDIOS
You did spook me, I was playing Elite on a commodore 64 emulator yesterday and then saw Freelancer here. Never saw it before. And in the video above some character has my name as well (Ludwig). Scaaaaaareeeeeey!!
I see you already made your fan base
Cheers!
Lump Apps and My Assets
- Thomas
P.S. Also.. you mentioned blending the two engines together. Do you really see that as a possibility? And if so, how (well) would it work?
Welcome too, @CodeWizard :-) Do you know Harry? ;-)
""You are in a maze of twisty passages, all alike." - Zork temp domain http://spidergriffin.wix.com/alphaghostapps
When I mention blending the two engines together, I don't mean making a nice engine smoothie.
What I mean is taking parts from the new native engine and bringing them into the current engine you're using. That way we can get improvements into your hands more quickly. This is because we're not waiting for all of the changes to be done and tested before sending them your way.
We're still having some internal discussions on this, but I'm definitely leaning toward improving the current engine through rapid iteration. Fix bugs, optimize systems, add features on a regular interval. You'll see improvements more quickly and there will be less risk on our end when delivering because the number of changes will be smaller per release.
The end result is the same: fixing performance problems, adding features, squishing bugs and reducing memory requirements. I'd personally like to get there in the most direct way possible and get changes in your hands as quickly as we can. Waiting on a massive rewrite is arguably not the best approach.
I most certainly will look very forward to see what you contribute to GameSalad.
Look forward to the new Lua improvements.
Regards,
Leonarddev
Welcome!
I think your attitude is a breath of fresh air if I'm honest.
DLTBGYD!
QS :
DDr. Sam Beckett never returned home...
Twitter: https://twitter.com/Quantum_Sheep
Web: https://quantumsheep.itch.io
Crossing my fingers for 2d liquid simulation and joints. Oh, and at least turn based multiplayer
Soooo many possibilities. Now that would be awesome.
Edit:
Welcome to the fold.
Really liking your no nonsense "Let's get !@#$% done" posts so far.
Good stuff. Looking forward to feeling your influence on things in the future (that's not a euphemism, no matter how it sounds)
I'm happy to hear about your proposed philosophy of rapid iterations. This would give the community a better sense of how the program is growing over time and can be looked back at as a copious amount of easily defined benchmarks (speaking from a marketing perspective). It would help ease the discomfort of spending money to be Pro, seeing a new release with new bugs as well as old ones, and knowing that there likely won't be a fix for months. I can also see how this would make GameSalad more attractive to new users since a perception of constant visible growth is more attractive than a perception of irregular interstitial growth.
It'll be easier to let us know what was fixed as well which should make the necessary code altering on our end MUCH smoother and faster since we won't be guessing about what exactly broke and why.
To be honest about the native engine:
It feels much more like a brand that hasn't be introduced yet rather than a feature that hasn't been introduced yet. Quite frankly It's been way too long since it was announced and shown in an alpha state to not be a feature in some form or another. I personally don't care at all how you do it, so long as you do it in a way that helps make the platform more malleable for new features available in the mobile operating systems as well as improving performance and memory handling. A mix of LUA and what's already in the works is perfect, so long as it works.
What we want something that works extremely well. If you decide to go the hybrid route, I would consider ditching the name "Native Code Engine" and give it a new branding that sounds as exciting. Otherwise it'll be years before you hear the end of it.
I'm excited by your post. I like GS and my experience with the people who work there have for the most part been very good. I hope you bring the energy you bring here into the office with you. I can see some great things coming in the future if you do.