Still no idea why sometimes the player object gets stuck on slopes. And I mean really stuck, only movement that works is jumping. then is back to normal after i land.

blackant I had the same problem. renaming the file to .zip and extracting manually solves it. but PixelMonkey might wanna look into it.

Do you have the example's capx ? I'm trying this on a new project, but sometimes the player rectangle gets stuck on slopes, no idea why...

that's pretty much it.

For example, I have one character, with animations separated in folders for better reference. each folder is a different weapon. When I want to add a new one, I have to duplicate the animations one by one, or recreate them, also one by one. Very time consuming, when I could only duplicate all in one folder, and paste over the parts of the image that change.

and search in project is as simple as it sounds. Even if all objects are organized in folders and families, finding *that* specific one sometimes is a chore.

Download link?

I've searched the Internet from the inside out already, and still haven't found an answer. No, putting DirectX dlls in NW's folder won't work. No I won't upgrade the OS unless it is to install Linux

WebGL works on browsers, but not on Node-Webkit. What is wrong here?

+1

Developing a NES-esque game, where tiles are sizes 8*8 or 16*16 is currently an eyebleed

Just like the title suggests.

Since I updated to r188, I can't preview my projects.

Normally I preview in Node Webkit because of the increased performance and because it's closer to a PC version.

Somehow preview does not work anymore, not even in the browser.

I'm using Windows XP SP3 32 bit. I have a core 2 duo 2.20 GHz with 4GB ram.

Node Webkit fails to initialize with error 0xc0000005.

The browser fails for whatever reason. I don't have a firewall, I don't have server software, nothing that could interfere.

If I export as a website, though, it works.

both NW and C2 un/reinstalled a thousand times, in different orders, folders, configurations... nothing solved my problem.

rolling back to 186.2, where all was good.

by the way, on a VM it gets even worse, it gives directX errors. I guess I can't use Linux after NW stopped being part of C2. That was a terrible decision IMHO.

I would not say it is a bug, but i have the same problem with bullet behaviors. When the application can not keep the frame rate, collisions are skipped along with the frames where they should happen. C2 is the first engine where i see this happen, and this is bad! collisions should be handled before the frames are rendered, and even if the frames are discarded collisions should ALWAYS be taken into account or most games will break under slowdown (think about unexpected disk access peaks, for example)

Great plugin. Keep up the amazing work! I think I'll buy it after the update.

+1

want to buy it, but i'm reluctant about how it integrates with the editor. can we get videos or screens on the matter?

Is anyone else interested? Also, any questions, comments, critiques? Let me hear from you, community.

What do you expect of such a game? What would you like to see?