Elliott's Recent Forum Activity

  • Bundling it in with something like Jekyll would be very interesting for Github pages, but I have no idea how that would work with Ruby

    Here's a non rhetorical question.

    Would an exporter sdk still be doable? This was one of the promises of C2 as part of its "modularity" if they ever finished the html5 framework.

    I love an update on the state of modularity - I'm taking it as a nice idea, and definitely one that has the userbase backing, but one that Scirra was never quite engaged with due to the underlying architecture change it would present.

    Given that the editor SDK won't be around until after the full C3 launch (September?) I think we can cross off any other SDKs

    In an ideal world, Construct would be an IDE for another engine.

    I don't think it's a stretch to say that the majority of Construct developers use the software for it's event sheet system rather than HTML5.

    Scirra is unmatched with regards to visual coding. It baffles me that none of the bigger players haven't produce anything even close to this; even similar tier future products like GMS2 and Fusion 3 are laughably behind Scirra in this regard.

    Construct is miles ahead of the competition with regards to input, but the output simply doesn't scale and despite technologies being cross-device friendly , quickly falls apart in the real world.

    I trust Scirra, you don't make software this good without knowing what you're doing. HTML5 is the future, AWP and instant apps are proof of the ever shifting progress away from native. I'll stick around for this ride, but I'd love Scirra's thoughts on what's been brought up so far.

    I'm not so sure Fraktal, now that Scirra has adopted a subscription model it's vital that the tool evolves with the developer. A one-off-payment model thrives on the new customer, which for C2 would be novice game developers. C3 is entirely about retention, and because of this needs features that make experienced users stay; they're simply worth more money.

    c3 is an editor that is aimed only at game editor devs.

    This is a great quote and I think sums up C3 perfectly - the crux of the community divide stems from the perceived lack of progress between 2 and 3.

    It's a fantastic piece of kit and I'm happy with it, but I'm more excited for the real features to come in. For the last 2 years Scirra have been focused on building an editor for a new platform - the web.

    Now that that's out of the way, I'm looking forward to what they can accomplish focusing on the game aspect of a game IDE.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Customize Chrome > More Tools > Add to Desktop

  • I haven't noticed any lag, however C3 does load noticeably quicker than C2, which surprised me.

  • Constructs seemingly luck based approach to ad fufillment on mobile (I'm assuming due to wrappers, as the vendors are highly popular) has always made me wary of investing too much time into a mobile game.

    I would be very interested if Scirra were to get more hands on with ad networks, as they appear to be doing with IAP.

  • I believe there's a not so subtle insinuation that because C3 is also a browser based HTML5 game engine that runs on a subscription model, it will also go bankrupt.

    A bit passive aggressive for my taste, and it's shame about Goo, they look genuinely impressive and seemed to have some very big users (Nike?!).

  • This would have been helpful, but I can see the reason for it's exclusion.

    Following off of this - can we have an "Inherit Viewport" setting for layout and margin dimensions? The most annoying part of starting a new project is all the fiddling (10s of seconds!) between the project and layout menus.

    Small request, would make my day.

  • Now that we have events to text, and we know the Scirra team have expressed interest in trying a text to events parser, I pray that we're one step closer to a text editor based version of the event sheet.

    Being able to type an event sheet, I'd buy C3 for that alone. Add some decent code hinting and I'm a customer for life.

    I was surprised with how much I enjoyed being able to dock windows literally anywhere, and split existing views (want two side panels to act as event sheets, you can!); off the back of this, I'd love the following:

    1) Save custom layouts to use from the settings menu.

    2) Being able to dock the preview window.

    C3 also has an odd and slightly annoying habit of launching the preview window in the bottom right hand corner of my screen; but this is on a second monitor for a Surface Pro 4, which are absolute bastards when it comes to dual monitors...

  • I'd enjoy this, but a the ability to load local stylesheets from within C3 instead relying on the developer console or a third party plugin would be great and solve this completely.

    For what it's worth:

    .eventSheetRootView:empty+.eventSheetMiniTutorial {

    display: none;

    }

  • The visual UI complaints are largely fixable with a handful of CSS changes, you can get a reasonable dark theme going in a few minutes:

Elliott's avatar

Elliott

Early Adopter

Member since 27 May, 2012

None one is following Elliott yet!

Connect with Elliott

Blogs