lucid's Forum Posts

  • k just an update for anyone who was trying that stuff. none of my theories were right. keep me up to date if you can figure out what conditions cause crashes

  • not crashing for me rook, could you dropbox the two projects?

  • conditioning already has a few different meanings, one dealing with learning algorithms, another dealing with hair care.

  • Im not at home to test, and busy with crunchtime on another project at the moment, but you reminded me Metal_X someone else mentioned that in another thread. I have a theory, and there's an easy way to test it. Its a shot in the dark, but if someone has a moment to try, it'd be helpful

    Make two layouts, and on each layout have only one object, and have the object doing something in an 'always' condition.   They should be two different object types, and they should each be doing something the other object cannot do, like one be a canvas object clearing the canvas, and the other a text object setting text, for instance. If im right it should crash everytime you change layouts with a transition. If this doesn't work, I have a second theory, for this one add more objects to one layout than the other, and use the objects you added last to be doing those 'always' actions...

    I uave one more idea, but ill have to look at the actual code to choose which two actions to make the objects do to crash it.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I've always called it eventing, maybe even constructing

    visual programming could easily be confused with stuff like visual basic, and even sometimes using c++ with windows forms and/or mfc appwizard.

    but there's definitely people who call it programming and I've heard coding as well, though I would consider both of those a bit of a misnomer

    maybe visual scripting?

  • just found out about this

    completely unbelievable

    as an american, I'm pissed; if I were british, I'd be really pissed.

    I'm a little late hearing about this - but a British citizen, Richard O?Dwyer, is being extradited to the US for copyright infringement. Apparently, it isn't even illegal in the UK, at least not the way he did it.

    short response from president Barack Obama, and general overview by BBC

    interview with mother on wsws.org

    This whole thing is getting so far out of hand, it's ridiculous. The US "Justice" Dept is trying to enforce US law worldwide. Once again, this agreement to be able to extradite on a whim is based on 9/11 and terror, and now they're just using it as a means of control. It's very aggravating that only the powerhungry seem to rise to power. I suppose it's a an obvious correlation, but still inconvenient for the rest of us humans just trying to live our lives.

  • don't think it will help. just wanted to make sure it wasn't the problem :)

    so when you say you tried removing objects and such

    did you try removing everything from that layout? and as a blank layout still has problems?

    also you say drivers "should be ok"

    just be sure, and download the latest driver. it's a likely source of such a problem, if it's not just cap corruption or the like. new pc's are rarely up to date with drivers if you don't do it manually

  • the new version was released just yesterday

    if you click the about button (the little button with the 'i' just under the close button on the top right of the construct classic editor screen)

    there it should say r1.2 or r2. r2 is the new version

  • Is the new pc using the new version, and the old pc not?, if so would it be possible to install the new version on the old pc(without overwriting) and see if it causes the same problem?

  • yeah, what newt said. I still say there might be bloom, but it's so subtly it could also just be crappy video compression.

    Also, it has a vignette(cc vignette effect).

  • I can't tell from the still frame if anything special is going on with the light. At first glance I thought it was just nicely colored sprites, and alpha. Though it looks like there might be some additive blending(one of the built-in effects), saturation, or a tiny bit of bloom(CC bloom effect by Davioware, here) on that blueish sky back there.

    if those boxes at the bottom are bumpmapped or something I can't tell without video either.

    Do you have a link to a video, or the game title?

  • ...Just wondering, but if I start using this for a project I'm well into, will certain things not work correctly like how you see in much older builds of Classic?

    —, in the unlikely scenario that your project depends on line object collision being bounding box. The general consensus was that this was mostly useless for the line object, so it's not an option, the only collision type now is angled_box.   The panel, box, and sprite objects still have the option for bounding box collision.

    The only other problem I can see is if you had panel objects that you purposefully misplaced because of the old bug, so they would appear in the right place, you'll have to move them to where they are actually supposed to be.

  • I seems intuitive that it would add two.

    First, one would assume that On Collision is a triggered condition, as most conditions begin with the word "On" are.

    A green arrow appears before the condition name on the event sheet for triggered conditions:

    <img src="http://dl.dropbox.com/u/1013446/forumhelp/trigger.PNG" border="0" />

    in the screenshot below you can see this is not present on the On Collision condition.

    Since the condition is not triggered by each collision, and instead is evaluated once in the order it appears in the event sheet. Those actions are carried out one time, regardless of the number of colliding instances, and all instances are picked at the same time. This is useful, because you can do things like make a sound play once even in the event of multiple collisions, instead of playing twice at the same time, etc,

    If you need an action for each collision, you can still use a 'System: For Each Object' subevent to loop through each of the objects that are picked in the collision event - which results in the behavior you originally intended:

    <img src="http://dl.dropbox.com/u/1013446/forumhelp/bricks.PNG" border="0" />

  • Sorry for the lack of updates. Had about 2 1/2 weeks of unforeseen delays. Back on track, and things are progressing steadily again. I'll report back soon with a more complete status report and some screenshots. Thanks for your patience. I'll try my best to make sure this update is worth the wait.

  • is there anything specific anyone knows about when the crash happens? are there a specific set of circumstances that cause it to crash? is it only with transitions, etc. I'm not sure if I'll be able to figure out what's wrong with it, but I'll definitely take a look when I get a chance. Also, if someone could make a barebones cap that causes the crash, even if it's just a few events, it would be helpful.