-
Notifications
You must be signed in to change notification settings - Fork 594
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash After Using ImageOptim on Resources Referenced in .ccb Files #433
Comments
Here's a test case: https://anonfiles.com/file/88b27972523248708dac5a2953f2c8a6 If you open ScreenOriginal it's all good. Open ScreenCrash and you'll get the expected crash. |
Unfortunately CoccosBuilder is no longer maintained. :( I have my own branch of the project and can have a look at the issue over the weekend. Cheers, |
Ah I didn't even realise. Oh well, it's not such a big deal anyway - the workaround I'm using is:
There's not much work left to be done on this project, so this will get me to the end of it at least! So no need to worry yourself with it for my sake. I imagine that SpriteBuilder will eventually add Cocos2dx compatibility. Cheers, |
Hey I had a look at this and it's down to ImageOptim converting it to a monochrome image and CocosBuilder not being able to re-size it due to failing to create a bitmap context to render into. A fix can be found in here if you want it: BertMcDowell@8c0085d Cheers, |
I'm using CocosBuilder 3.0 (Alpha 4), and it seems that after using ImageOptim on some images referenced in .ccb files the program crashes. To produce, I just open the .ccbproj and go to open a .ccb file.
If I checkout the version of the image before ImageOptim was used on it, it works fine (until it finds another file it has a problem with). If I checkout all the files then it works fine. I've tried deleting the cache too. No luck. It seems that not all of the images cause problems, as I can open some screens without problems.
The output from System.log is here: http://pastebin.com/7m589aFS
Is there some other log I can provide?
The text was updated successfully, but these errors were encountered: