Ashley's Forum Posts

  • Yeah, check out the "Zoom X/Y" and "Zoom X/Y rate" properties/actions for layers

  • So what did you try and what didn't work about it? Try including a bit more information...

  • Python's been improved a good deal in the past few builds, I think.

  • It's worth noting events are "interpreted", but it's a grey area between interpretation and compilation. Actions, conditions and expressions are run in compiled plugin code, but the overall event sheet is interpreted (ie. choosing when to run which actions, conditions and expressions).

    Since running events happens at the same time as rendering the screen, though, I doubt many games are limited in speed by events. Rendering usually takes longer, which means you get your events processed "for free".

  • You have earned the title: "Mr. Poll"

  • OK, that should do the trick...

  • Yeah, sorry R0J0hound, forgot to SVN update your changes! (not used to having someone else commit code!) Updated build coming right up...

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Mipey, can you post your .cap of that?

  • FYI check the latest build 0.99.84. The XBox360 issue should be fixed, and the installer no longer launches the other two setups when run with /silent or /verysilent - it's a completely hands-free setup now (it doesn't attempt to install the VCRedist or DX update though).

  • Download Construct 0.99.84 (unstable)

    This is an

    unstable build. You can help Construct's development by downloading it, trying it out, testing and reporting bugs. If you have projects you want to work on without possible bugs getting in the way, stick to stable builds.

    Link to previous build (0.99.83) changelog

    Intermediate build to keep things moving. Thanks to R0J0hound who has submitted several fixes for this build (hope they work ). I'm not sure if David's platform fixes from the last build are included - there's some confusion over its submission to the codebases, but I rebuilt Platform anyway, so let me know if anythings better (or worse?).

    Changelog

    Behaviors

    • [CHANGE] Ball behavior: adjusted bounce/move-out-when-trapped algorithm. It's different, not sure it's any better, but might solve some problems people have been having.

    Editor

    • [FIX] Layout editor object tooltips no longer cut last letter off layer name

    Effects

    • [FIX] Crispify shader is back (not sure where it went!)

    Installer

    • [CHANGE] Skips VC2005 redist and DirectX setups if /silent or /verysilent flags used on installer; should allow easier deployment to networks since there should be no prompts during install this way (the machines still need the VC2005 redist and DirectX updated to August 2008 - these setups are saved in the Construct installation directory or you can deploy them another way)

    Plugins

    • [FIX] On some machines the XBox 360 controller object would fail to load at startup. Possibly fixed same issue with Bone movement
    • [FIX] Possible array crash in comparing X or XY

    Python

    • [FIX] Script editor action names now better match the runtime (R0J0hound)
    • [FIX] Crash accessing private variables from Python (R0J0hound)
    • [CHANGE] 'global' system expression changed to 'globalvar' since 'global' is a reserved keyword in Python; allows access to global variables by name and index (R0J0hound)

    Runtime

    • [FIX] Crash drawing Sprites on non-SSE2 processors (R0J0hound)
    • [FIX] Incorrect sprite rotation when setting a corner filter (R0J0hound)
    • [FIX] Issue with XBox360 suddenly losing input should be fixed

  • (we're not biased, either )

  • Yeah, let's not squash the cog folks

  • This runs fine for me if I change everything to Ball behaviors and remove the custom bounce event (relying on the built in bounce-off-solids options). I think it's just the custom movement not working nicely here.

  • To be honest, this is why I don't really hold with opensource - too many basic installation issues, and no useable deployment options.

    Fair criticism. I'll have a look at modifying the installer for the next build - I'll launch the DirectX and VC Redist setups as silent so they don't have to be clicked away (they need to be installed anyway). Would that help? As for the XBox360 controller issue, it might be a bug in the build, which version are you using? If you don't need XBox360 controller input, you can safely delete the .csx file and simply not use it.

    I know open source has a reputation for DIY, but I don't think that's an excuse to be lazy - if there's a simple thing we can provide to simplify deployment we definitely should. Otherwise a lot of people might simply not use the program, which is pointless given all the work on the main program itself. So I'm open to suggestion and criticism, anyway.

  • Don't forget the installer creates the shortcuts too - you'll have to create the shortcuts yourself.