Ashley's Forum Posts

  • If you weren't aware, we're writing the official Construct documentation on the Wiki. If you would like to contribute, please read Editing the Wiki.

    Right now the biggest problem with Construct is the documentation. A lot of new people have turned up recently (which is great!) but there's very little official documentation for them to go on, so it's not surprising a lot of people run in to difficulties. It's also critical this is done before 1.0, which is coming up nearer every build.

    I'm steadily writing up parts of the documentation but it is very time consuming. The following articles need some tender care:

    Object list - see XAudio2 for ideal plugin documentation

    Complete documentation of the Interface and related pages; especially List of Dialogs

    See also: Wanted Pages

    I'm basically now going to concentrate on finishing the documentation, but it's a lot of work for me alone! If you know anything about any of the subjects that need writing about, please - do make a start - even if it's just a few sentences. It will help MASSIVELY if other people get involved as well.

    Personally I think this is so important for the project I'm stopping work on Construct to get this done. That means at best, minimal bug fixes and coding. I won't be back to coding 100% until I'm satisfied with the state of our documentation. That means you can help - the next builds will obviously come up faster and have more in them if we can get the documentation done ASAP. So please - do make edits to the Wiki. And thanks to everyone who contributes!

    Remember - if you want to help - read Editing the Wiki!

  • The 'Trigger once' means it won't run the event again if it suddenly becomes true for two objects, instead of one. It just still counts as 'true' overall and won't re-trigger. Use a private variable to mark an object as fading (eg. set 'Is Fading' to 1), and change the event to say:

    + Health < 0

    + Is fading = 0

    -> Start fade

    -> Set Is fading to 1

    ...etc.

  • Are you using resources or loading from files?

    Did you say load from file "C:\Documents and Settings\Stuart\My Documents\My Code\Construct\something.ogg" (in which case it will always look for it there no matter where you move it), or just "something.ogg" (in which case it could look anywhere), or AppPath & "something.ogg" (in which case it looks in the same directory as your app even when its moved)?

  • This one seems OK judging from comments, we'll probably frontpage it today or tomorrow.

  • There are currently three plugins on the CVS which you can find here.

    We're planning on adding more, but frankly a lot of the plugins right now are a mess, and it would be counterintuitive to put their sources up. A lot of things do things not as best as they could so they're not an ideal sourcecode to learn anything from...

  • Can you upload a .cap?

  • It allows you to jump higher the longer you hold the jump key.

  • Odd, though, that you can still move left/right if you rename "Move Left" and "Move Right."

    If a control does not exist (as in, it was deleted or renamed to something else), the behavior reverts to the default controls. This is so even if you delete all the controls you can still use the default controls. If you rename "Move Left" to "My Control", it reverts to the default control, so if you change which key "My Control" is, it won't affect the behavior.

    Basically on startup plugins ask Construct what a key is by its control name, and if it's not found, it'll use a default.

  • newt, can you post an example of what's wrong?

    patryk1303: bugs marked as 'open' mean they are not yet fixed, and are awaiting a developer's attention (there are currently 91 other reports open...)

  • Download 0.98.7 now!

    Construct 0.98.7 has been released, fixing some of the problems in the 0.98.6 build. Don't forget you can help Construct too! Contributing to the Wiki documentation or donating via the main page helps support Construct.

    Here's the changelog:

    Behaviors

    • [FIX] Fade: with 'destroy afterwards' off and fade-out time zero, the object now no longer turns invisible.
    • [FIX] Platform: Strange 'bump' bug when an object goes into a plaform via the left or right
    • [FIX] Platform: Ignore input now ignores falling through platforms
    • [FIX] Physics: Hotspots are now considered (however the motion will still be from the centre of mass)

    Event Sheet Editor

    • [ADD] New toggle action and toggle condition options.
    • [FIX] Scrolling glitch where having an open event and scrolling just below it caused it to jump by 16 pixels
    • [FIX] Visual glitch with the line between events for else events
    • [FIX] Crash adding private/global variables in non-layout linked event sheets
    • [CHANGE] Comments no longer draw with a dark outline, making them stand out less
    • [CHANGE] Toggling an event now acts like removing all the actions and conditions (since they are crossed out)

    General

    • [FIX] Crash sometimes in the object bar when in event sheets
    • [FIX] Resizing issue with the global variable manager dialog
    • [CHANGE] Some runtime properties moved to a separate "Window" category

    Layout Editor

    • [ADD] Layer to the object tooltip
    • [FIX] Objects on locked layers can no longer be selected in any way
    • [FIX] Layer visible checks are now stricter
    • [CHANGE] Groups have been removed
    • [CHANGE] Until an issue in our UI library is resolved, there is no message box to prompt object or layer deletion. We will readd it in the next build hopefully

    Picture Editor

    • [FIX] Crash when pressing numpad without hotspot tool selected
    • [FIX] Secondary colour had some old code in it and was causing the colour to be random
    • [FIX] Fill tool now has a way to change the alpha value

    Plugins

    • [ADD] New Pairer object - beta
    • [ADD] Sprite: On Animation Frame Changed
    • [FIX] Sprite: Icon updates after editing it.
    • [CHANGE] Better drawing for Button, ListBox, BarChart, List controls
    • [CHANGE] Sprite: Adding a new sprite or double clicking a sprite brings up the image editor for the animation instead of just that one frame

    Runtime

    • [ADD] Debugger: entry for System object tracks VRAM usage in DirectX runtime. Will be useful in future for tracking VRAM usage over time when better VRAM controls are implemented.
    • [FIX] Families with object parameters now pair correctly (hopefully!)
    • [FIX] The repeat to was causing animations to act like they had pingpong enabled and stuff
    • [FIX] Debugger was not always on top for some reason
    • [FIX] Else now remembers the previous SOL, so if you have it within a 'for each' or something theres no logical errors

  • You could just tick "Invisible on startup" in their properties, or enable the "Destroy on startup" attribute.

  • The fade is activating. 'Start fade' makes it rewind to the beginning of the fade and play from there (when it's opaque). The condition 'Variable less than 0' isn't just true once. It's true all the time. The events are checked once every tick (generally 60-100 times per second), so you're repeating the 'start fade' action over and over again.

    Add the 'Trigger once' system condition below the condition, and it makes it true only once, even when it repeats. It makes it act like a trigger, so it runs just once the first time it's true, instead of every tick.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Well, anyone could theoretically come along and write a plugin for joypads or whatever. It's much easier to do that than to plunge in to the core codebase. It's not just us who are responsible for finding coders. You guys can look for people to fill the features you want too.

  • I know, I know. We can't keep adding new features before 1.0 though. There's already too much to do, we're all just part-time volunteer coders, and the more that gets added the more maintenance is required when inevitably there are bug reports. 1.0 is hopefully not that far off so we can start these kinds of projects afterwards. Alternatively, look to hire a coder to write this in the plugin SDK for you right now.

  • Application Properties, 'Controls' category.