Pro users: Paying while waiting for updates
InLikeFlynn
Member Posts: 171
I think pro users shouldn't have to pay for this month while we wait for the update. We should get an extension to our subscriptions. My self and a few others on here have problems we need to fix and we've been told to be patient.
This is a bit like a hired cab driver asking you to be patient and keep paying while he learns how to drive. As a developer, I get that bugs happen and that GS is still in beta, but there is something seriously wrong with charging people for a time based service while they can't really use it.
Please either fix things more often than every month or don't charge us for times like this. Also, it's never cool to ask people to be patient while you are charging them for time.
This is a bit like a hired cab driver asking you to be patient and keep paying while he learns how to drive. As a developer, I get that bugs happen and that GS is still in beta, but there is something seriously wrong with charging people for a time based service while they can't really use it.
Please either fix things more often than every month or don't charge us for times like this. Also, it's never cool to ask people to be patient while you are charging them for time.
Comments
he's rite.. it's like hiring a plumber who came to my house with broken tool and charging me to run back home to get his tools... i said plumber because of Mario of course.
I wonder a thing, if you don't buy pro and just copy the rules form the GC template, will it work?
______________
http://www.thatgameforum.com/
http://gshelper.com/
http://www.youtube.com/user/GameSaladCookbook#p/
http://gamesalad.com/wiki/
_____________
http://www.thatgameforum.com/
http://gshelper.com/
http://www.youtube.com/user/GameSaladCookbook#p/
http://gamesalad.com/wiki/
I'm hoping they will take the moral high road with their paying users, and not charge for time when their software quality is significantly below what we've come to expect. For me it's been basically unusable.
Otherwise doesn't act the same as 2 opposite rules, so they can't always be replaced. The viewer doesn't work on my iPod 1st gen, so I've been trying to publish all day to test that way. Publishing also hasn't worked for me all day (2 different error messages and a never ending load bar). The main reason I'm trying to update in the first place is to fix a crash problem cause by 0.9.4. When I add actors to the project file from 0.9.4 GS crashes when I try to load viewer on any device.
'Priority technical support' takes longer than the 2 days I read somewhere, and 2 days doesn't seem very quick to begin with. I sent them my broken project on June 23, they got back on the 27th, and I asked them to look at it if the update would be more than a week away. They still haven't gotten back to me. 17 days and counting is not priority support.
This functionality isn't anywhere near the level it was when I paid my $500. I just hope they ask "Is it right for us to charge for this software at the moment?" Easier said than done. I tried changing my code as you suggest here, but when I asked for help on the forums you told me to wait:
It seems that the otherwise bug is mainly an issue when dealing with a boolean or a touch release as a condition. This was stated in the "Did 0.9.5 break 'Otherwise'? post by From my own experience, boolean conditions don't always create this bug in 0.9.5. Tracking down the problematic "otherwises" isn't too hard since the problem hits you in the face while your game is running. For right now you can leave in your rules as they are and just comment them out. Then create the rules necessary to recreate the effects of the code you commented out so that you can still test your work accurately. Make sure to put a note behavior in your actor that reminds you of what you did so when the bug is resolved you can make your code tighter again.
I know it's frustrating, I'm feeling it too, but I'm working on a massive project and it took me less than an hour to resolve the otherwise bug so that I could continue developing.
It seem to me that Otherwise can't always be simulated with other rules. If you're into programming, it's the same as comparing an 'if' and 'else'. There's a reason we have both, and that's because they do different things that can't always be done another way. Often 'if' can be used to meet the same ends as 'else', but not always. If we asked the GS programmers to program without using else for a month they would have a very difficult time. I suspect they wouldn't want to pay for software that disables 'else' functionality.
The other problem is that my work around can't be tested on devices because GS crashes when I try to use viewer. I also had trouble publishing to test that way. I contacted tech support weeks ago and they haven't helped me. It's not otherwise by itself, its the combination of otherwise, GS crashes, publishing problems, no tech support.