Debugger ... Maybe ?

0 favourites
  • 12 posts
From the Asset Store
A Stacklands / Cultist Simulator game engine for C3. Includes detailed instructions, debugger console, spatial sfx,
  • Hey guys , I'm just shooting this idea to plugin makers and devs !

    C2 need an inpreview debugger ... that shows a message at the right of the screen whenever an event is executed , that would HUGELY help finding problems in the code !

    Post below if you think that's a good idea !

    Cheers !

  • Well, Ashley has said on several occasions that a debugger is on the to-do list. (it was also one of the options in the new feature vote a while back)

    There are many threads on the subject already, and as newt pointed out in one of them:

    Not sure how a debugger would work since even the preview runs off of another program... your browser.

    However the text object can be used with events fairly efficiently.edited><editID>Nimtrix</editID><editDate>2013-01-02 23:02:45</editDate></edited>

  • But having one by default would be as a gigantic help ! Better if a message would pop up for every action you would do !

    For example :

    In Event Sheet : Add 1 to Example

    Ingame : Added 1 to Example (10) <-- Variable Total Value

    That would be awesome !

    What do you think of that Ashley ?

  • While a debugger would be helpful - perhaps running on an extra layer that gets put on top at preview - messages for every single thing that happens would be unusable past anything but the simplest of games. There would be way, way too many mesages for a single frame, not to mention at 60fps.

    If you want to check if events are running, I generally have a ui element or something like it that has no other code rotate. It's a quick and easy debugging trick that works great.

    You could also make your own 'debugger messages' by putting a text object on a layer and appending the text via an action.

  • maybe open a cmd *the debugger* and post the messages there ?

  • ...You could also make your own 'debugger messages' by putting a text object on a layer and appending the text via an action.

    Yes, I typically add a 'DEBUGText' Text object and output to it what state messages I need. Not exactly a debugger, but usually quite adequate.

    ... messages for every single thing that happens would be unusable past anything but the simplest of games.

    Agreed.

    And see this article: Debuggers are for Losers. To quote: "... most of the time the debugger is not the best tool to find and remove defects."

  • I would pay another $100 for a debugger...yet since the preview mode runs outside of C2 in the browser I can't see any way of getting it to work without having something like

    Subscribe to Construct videos now

    running (I'm linking to YouTube as his site seems to be down).

    Maybe we don't need a full blown debugger with the ability to step through code (inside C2 I mean). Maybe we could get an extension to preview.js that has clearer list of all the objects and their values, as well as a simpler overview of where the program is currently pointing. I could live with not being able to step through my code if I could just add "runtime.sprite.player[0].X" to the Chrome watch window and see what the current value is. I'm sure something like that is possible now, but you have to wade through some pretty large objects to do it. The irony is we all keep asking for a debugger - we already have a debugger in our browsers, we just need a easier way to make sense of the data. Maybe that is a more realistic goal?

    You could also make your own 'debugger messages' by putting a text object on a layer and appending the text via an action.

    For those who might not have seen it yet, I highly recommend using the Chrome logger by wgfunstorm. It lets you spit out data and even arrays into the chrome console tab. Immensely helpful. (Note: I'm linking to the version I added array logging to - The regular version wgfunstorm is missing some files in the zip and he hasn't been on in a while to fix it).

  • I'm in desperate need of a debugger in C2. I'm spending hours and hours staring at lines of code and realising that I don't understand how C2 is interpreting them, since they 'should' work. I need a line-by-line stepper to see what's going on since this is now taking up most of my time. I'm resorting to sounds (a beep next to the actions so I can hear if they're even being reached) and text object to output numbers, but I'm still having real difficulties. But I guess if it's not feasible in C2... well it's making me think I need to find a different language, which is a shame because C2 is amazing in every other respect.

  • Doesn't chrome offer step by step debugging in the developer console for any js running in the page? Wouldn't this give some of the at functionality?

  • farflamex , that's what I wanted to do

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Yeah, basically, what we WANT is something like the VB debugger, where you can step through, line by line and check which line it's on and the values of variables. But then again, that's the best debugger I've worked with and I understand that it'd be difficult, if not impossible, to implement.

    In general I find C2 to be very good to use and it massively increases productivity. Unfortunately on bugs, I'm finding they're far harder to find than a normal programming language. It's sometimes next to impossible to work out which events are even being processed. Even a basic debugger would be nice.

  • Yup , You take the words from by mouth !

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)