Ashley's Forum Posts

  • Setting a colour filter on a sprite can tint a whole object, so if you want to tint just parts of an image, you can use separate sprites for the areas to be tinted on top of the main sprite.

  • If it was changed at all, some plugin developer might go and use the "proper" system of 0 degrees being right, and you will still find yourself adding to angles in places to make angles compatible. IMO keeping it 0 degrees right is the best way of ensuring things like Sprite angles, the Angle expression, angles of motion etc. all work the same way. Being able to set angle of motion to Sprite.Angle is a lot nicer than ((Sprite.Angle*-1+270)%360).

  • I'd prefer not to change it. Mathematically, 0 degrees is right. Consider that movement at 0 degrees is X + D cos(0) on the X axis and Y + D sin (0) on the Y axis. cos(0) is 1 and sin(0) is 0, meaning movement right on the X axis at an angle of 0 degrees. It is very much beneficial to keep it plainly mathematical like this: if you hack it so 0 degrees is up, the formula begin to look like cos(angle - 90), with a modification to the angle. This means you can no longer express in your events custom movement as being X + D cos(angle): you will have to also apply the hack to make it compatible with Construct's built in angles, and any modification would not be obvious to a game developer. Even worse if people can invent their own angle systems: in any given game, you simply would have no idea what an angle actually means (would 0 degrees mean up? left? down? south-south-west?). I certainly want to avoid situations where people have to invert, offset and normalise angles just to make them compatible with some other angle system, I've had to do that before for games and it's nontrivial.

  • This one's gonna be even better! (When it's done...................)

  • Actually I agree with you, I think import and export are underrated. Often it gets relegated to being a minor optional add on type thing but comprehensive import and export controls are a pretty major feature. I'll try and have something sorted for 1.0.

  • My test for build 0.87 worked, could you send me a crashing .cap to ashley@scirra.com? Thanks.

  • http://scirra.com/demos.php

    I especially like the realtime zoom, scroll the mousewheel for it <img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile">

    Oh and graphics/sound by Gamesare, www.gamesare.com

    This demo makes the most advanced use of the display engine so if you could try it out and let me know if the zoom messes anything up, I haven't tested this on any graphics cards other than my own. Cheers <img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile">

  • I've renamed this forum to the Documentation forum, the place where we can organise the development of documentation for Construct.

    Documentation is a very important part of Construct and we should have something substantial by the time 1.0 rolls around. I've decided the best place to collaboratively develop documentation is the Wiki:

    Construct Wiki

    Note (2nd January 2008): The Wiki has been moved to the above URL hosted on SourceForge since this thread was posted. Links in this thread to the old Wiki will not work.

    I really need everyone's help to pitch in and help get this done - even if you just sign on and add a doc for one property in the Sprite object, it's a start - if everyone did that, we'd be well on our way to documentation <img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile"> Thanks!

  • Hey everyone, we're planning on integrating Python scripting in to the IDE. This will allow you to either:

    • Write entire games using Python scripting.
    • Use normal event sheets as before, but include snippets of Python to perform complex loops, calculations or other areas difficult to express in events efficiently.

    You can find out about Python here:

    http://www.python.org/

    We won't be forgetting about events - they're just as important as scripting. So we won't be leaving events behind and making Construct a script only tool, but we won't be making Construct an events only tool with scripting bolted on. We're going to make them work together and make both useful.

    If you have any ideas on what you want to see in Python scripting, or what it should be able to do, get your ideas in here <img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile"> We should have it ready in a couple of builds, around 0.9, so have your say now <img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile">

  • http://downloads.sourceforge.net/constr ... irror=osdn

    Well, whaddya know, turns out coding Construct is a great way to procrastinate <img src="{SMILIES_PATH}/icon_wink.gif" alt=";)" title="Wink"> My exams finish Friday!

    I'm sorting out some extra coding help which should be helping boost future builds.

    Here's the changelog:

    • [FIX] Closing any project/template will no longer crash
    • [FIX] Dragging actions in Chrono view now uses a vertical caret instead of a horizontal one
    • [FIX] Crash in some animations when using sub-animations.
    • [FIX] MessageBox system action now has correct parameter order
    • [FIX] ComboBox bug whereby loading may produce a weird item
    • [FIX] Ctrl+C, Ctrl+V shortcuts now work in event sheet editor
    • [FIX] When deleting events relating to a deleted family, actions and conditions referring to the deleted family in object parameters are now also deleted.
    • [FIX] Crash saving/loading in Array object.
    • [FIX] Can no longer delete event sheets that a layout is using.
    • [FIX] Crash using families with movements in some circumstances.
    • [FIX] Animator bar clears when you close a project.
    • [FIX] Crash sometimes when pasting clones
    • [CHANGE] Groups and subevents did not indent far enough.
    • [CHANGE] Many dialogs standardized (same appearance)
    • [CHANGE] Mid and Find system expressions now use 1-based indices (previously 0-based, anything 0-based in Construct should be reported as a bug)
    • [CHANGE] Expressions ScrollXLeft, ScrollXRight, ScrollYTop and ScrollYBottom can now optionally take a layer param to get the values for a specific layer.
    • [ADD] Keyboard shortcuts to Animator Bar (delete, C, V (note control does not have to be held to copy/paste frames))
    • [ADD] New XHTMLTree control in Project bar to allow dragging and dropping (in future will expand Project Bar for more features)

  • That's a pretty good idea, I am fully aware of the shortcomings of the picture editor/animator bar, and there are some more improvements coming in 0.87...

    Specifying your own app would be cool I guess but it'd have to be something lightweight, I guess you dont want to sit around waiting for PSP to load up every time you edit your sprite. Also, it wouldn't allow for editing whole animations at a time, like the picture editor filmstrip does.

    All in all, if we fix copy/pasting so it's painless, why not just keep the graphics tool of your choice and just paste in stuff from that?

  • The cheapest cards that support pixel shader 2 - according to wikipedia - are the ATI Radeon 9500 and nVidia GeForce FX 5200 (or anything better than either of them). I can find a 5200 new for about �15, and both appear to be going on ebay for around a tenner.

  • If you want to create a closed-source commercial game in Construct, that's fine. The GPL requirements of having to provide source code apply only to Construct itself, not anything you make with it.

  • Yeah I'll tidy up the button object and release its source soon. It was written with an older version of the SDK though so it might not be quite as well organised.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I looked in to this bug a bit and error 998 is returned when the DLL being loaded crashes. So for some reason the plugins are crashing when they are loading. The only thing to do is to debug it, but it works for me and everyone else, so I don't know what to do :S

    The only thing I can think of is to completely uninstall, delete all Construct related files, delete the folder HKEY_CURRENT_USER\Software\Construct from the registry (in regedit), and reinstall Construct again, installing both the CRT and DirectX update. There's an outside chance installing this update might help as well.