Re: Bugs and Crashes, Build 12042
Posted: Thu Jun 11, 2015 8:12 pm
The FoW slow-down is related to how I'm handling "light" in the tile map, while not trying the engine updates too many quads when changing properties, gonna switch it over to a shader system and see if that helps. If that doesn't work may chunk the map into quadrants. Will be a fun exercise in profiling/optimization 
Can you tell if the Door sounds occur when the crew is right next to the door? It does open (and sound) if they move toward the door in a straight line and land on the tile just before the door, but not going through. Something I should fix, but will require additional destination check, low priority ...
I plan to test on more android devices this weekend.
Edit: door sounds may be the dog? did I mention that already? with dog enabled I heard door sounds a lot, maybe I'll turn off door sounds from pets ...
----
Cocos2d-x is a great engine for what it's meant for: simple- to medium-core games. It's moved from an Objective-C port to mostly c++11 (except memory management is retain/release) with an eye toward the future (c++14/17, and entity component system). It has Javascript & Lua bindings so you can write all or most of your game in either of those as well and effectively get native performance. Documentation can be lacking, but it's improving. It's code-focused, but they are working to bring CocoStudio to become more capable as editor, and third-party support is decent.
Unity is a great cookie-cutter engine, if you stay in it's boundaries it's pretty awesome for getting things done, but once you veer outside (which Galaxies has done) it can be very annoying. The editor is great as is the Asset Store, and you can do visual effects more easily all inside the single editor (cocos2d-x requires external tools).
I've only really used a few others, so there are plenty of interesting options out there besides cocos2d-x, I just happened to get involved and enjoy the community over there. Point is you may find Unreal, HaxeFixel, LibGDX, Godot, GameMaker, or another engine to be better. Cocos2d-x isn't necessarily great; Engine choice is alway a "depends" issue and often personal preference.
Edit: In fact there's a some interesting discussions as of late. Most people at least are fine using c++, but many are curious if the engine could improve toward prototyping and failing quickly and adding ECS, in case anyone's interested.
http://discuss.cocos2d-x.org/t/cocos2d- ... ion/21547/
http://discuss.cocos2d-x.org/t/add-enti ... d-x/21809/

Can you tell if the Door sounds occur when the crew is right next to the door? It does open (and sound) if they move toward the door in a straight line and land on the tile just before the door, but not going through. Something I should fix, but will require additional destination check, low priority ...
I plan to test on more android devices this weekend.
Edit: door sounds may be the dog? did I mention that already? with dog enabled I heard door sounds a lot, maybe I'll turn off door sounds from pets ...
----
Cocos2d-x is a great engine for what it's meant for: simple- to medium-core games. It's moved from an Objective-C port to mostly c++11 (except memory management is retain/release) with an eye toward the future (c++14/17, and entity component system). It has Javascript & Lua bindings so you can write all or most of your game in either of those as well and effectively get native performance. Documentation can be lacking, but it's improving. It's code-focused, but they are working to bring CocoStudio to become more capable as editor, and third-party support is decent.
Unity is a great cookie-cutter engine, if you stay in it's boundaries it's pretty awesome for getting things done, but once you veer outside (which Galaxies has done) it can be very annoying. The editor is great as is the Asset Store, and you can do visual effects more easily all inside the single editor (cocos2d-x requires external tools).
I've only really used a few others, so there are plenty of interesting options out there besides cocos2d-x, I just happened to get involved and enjoy the community over there. Point is you may find Unreal, HaxeFixel, LibGDX, Godot, GameMaker, or another engine to be better. Cocos2d-x isn't necessarily great; Engine choice is alway a "depends" issue and often personal preference.
Edit: In fact there's a some interesting discussions as of late. Most people at least are fine using c++, but many are curious if the engine could improve toward prototyping and failing quickly and adding ECS, in case anyone's interested.
http://discuss.cocos2d-x.org/t/cocos2d- ... ion/21547/
http://discuss.cocos2d-x.org/t/add-enti ... d-x/21809/