RayKst's Forum Posts

  • It probably won't be 2D. What they probably meant is old school gameplay;

  • Yeah Neon Glow. It might as well replace current Glow effect which sorta doesn't work very well, like compared to Classic one;

  • It's wrong to judge it only by it's goal value. The guys are seasoned developers, from what i saw, behind classics like D&D, Wizardry, Ultima etc. If the game has value enough and apeal to enough gamers, they could ask 20 mil. What's left is to know if it indeed has value enough to demand that sum :D

  • Yeah. They should at least make an observation on current support of mobile for html5/webgl games. Which is very poor indeed. Yeah there's firefox mobile and stuff but it's use % is 0.06%. A way to go yet.

  • Making medium to big , even small apps in JS is a pain. I'd never go that path if possible. One of reasons why C2 is so powerful is that it abstracts away JS so that you don't have to pull your hair out fighting with JS, like trying to properly modularize your code without turning it a mess of (function(){}()) and sh*t like that. One thing is making a C2 plugin with JS. Great. Another entirelly is making an entire app in it, much less an entire game engine :) Kudos to Ashley on that.

  • Only engine that gets near C2 productivity and easyness is Unity no doubt. That's why it's the most popular among us indies. Only Unity is 3D focused; If it were 2D i must admit i would have to leave C2 :O

  • +1 On this. #1 could be fairly easy or very complex depending on ashley's code. Anyway it's a nice addition. Solo layer button is very helpful too. Best of all for me would be #3 . Purge unused objects. Things can get messy fast if you forget to remove object type every time. One thing is removing from scene other is from project. Maybe delete to remove from scene and shift+delete to remove from project entirelly;

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • Well pixel rounding will not help with that. It's about texture sampling. Zeus wants nearest neighbor, that is, no filtering. It's just a simple tweak on opengl.

  • A standard magic wand, specially for a pixel paint type of editor is easy to implement, i think it's not out of the world to add it to C2. The functionality is similar to 'Fill'. Of course if you need anything more fancy you better use something like Paint.NET , PS etc.

  • HTML5 made no promises. It's peoples expectations that are being hurt. For games i think HTML5 is more than powerful enough right now. For apps it still falls short. Though there's many talented people working on it. The critical thing about HTML5 is support. That's the thing.

  • Ashley : Would this be usable for C2 ?

  • I've discovered this thing called App.JS. It embeds Chromium inside a desktop shell via Chromium Embed Framework (CEF) and uses Node.JS . In short it's a 'make desktop apps with html5, css, js' framework. So in theory it could be faster than Awesomium since CEF is more lightweight. It supports webgl so i had to try to run C2 in it. I succeeded. More or less. It does indeed support webgl, and the particles example ran fine. But it caps at 30fps here on my machine. A good thing is that it starts much much faster than awesomium but uses more disk space. And uses less RAM. It could, be a replacement for Awesomium but further investigations are needed. The fact that it runs at half fps than awesomium intrigues me though. I had to remove this lines from c2runtime.js for it to run with webgl:

    /*if (tempgl.getSupportedExtensions().toString() === "OES_texture_float,OES_standard_derivatives,WEBKIT_WEBGL_lose_context")

                             {

                                ??console.log('webgl not supported');

                                ??use_webgl = false;

                             }*/

    So maybe there's no full suport for webgl yet...

    Anyway here's the files if anyone wants to hack it too: Download

  • ^ This. Perfect

  • OP idea is valid since you can't really "resize the sprite in Construct 2 itself". One thing is resizing the image to half the size. Other is rendering the image at half the size. The result can be the same, but the image is effecivelly resized in one , and stays the same size in the other case.

  • Waiting anxiously :)