Ashley's Forum Posts

  • Judging by the animator bar you've done everything right. Perhaps the shader uses something the card doesn't support, or it could be a bug in Construct, but I don't think so - it just compiles the effect and sends it to the graphics card. Do 1.1 shaders work OK?

  • http://ati.amd.com/support/driver.html

    Assuming you're on XP:

    http://ati.amd.com/support/drivers/xp/r ... 00-xp.html

    Installing these should make your card run as good as it can. Let me know if it works.

  • Hmm, what is your graphics card or graphics chip if its onboard? That's the crucial thing. Also, you should find your latest drivers and install them, that can fix a lot of problems. If you are certain you have the latest drivers and it still doesn't work, it may just be your graphics hardware sucks - if it's nVidia or ATI though, I'd be more worried.

    I've run advanced Construct games like the RTS demo with no problems on an old SiS 650 chipset - sure it ran slow, but displayed correctly. So if you have latest drivers etc, I'd suspect it's your hardware.

  • Yes, every new version is 100% compatible with the last.

  • OK if you've already downloaded it, restart Construct and the autoupdater will ask you to download the new files.

    The link is updated so new downloaders wont have any problem.

  • Bummer... worked for me with my usual final checks. I'll have something sorted tonight.

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

    Our most stable build ever! Python will be in the next build (I'll see to it) and SDL will be coming up some time soon as well - ideally, both next build.

    A slew of bugfixes, changes and additions:

    • [FIX] Instability/crashes with 'Create relative image point' / 'Create relative pivot point' actions
    • [FIX] Wrong display of physics hinge actions
    • [FIX] Bug with layouts with empty names
    • [FIX] Improved stability of picture editor.
    • [FIX] Crashes using repeat/for/while/for-each system conditions with subevents
    • [FIX] RTS movement occasionally hanging the runtime
    • [FIX] Crash using two RTS movements with different cell size settings
    • [FIX] Layer scroll rate taken in to account when testing mouseovers.
    • [FIX] Stability of layouts and renaming them
    • [FIX] Layout names sometimes got deleted when double clicking project bar due to the renaming caret
    • [FIX] 3D box works at runtime
    • [FIX] Multiple triggers in group no longer cause oddities
    • [FIX] Families now work with more conditions
    • [FIX] When double clicking an object in the event sheet editor families are selectable
    • [FIX] Crash on Vista minimapping a Tiled Background (and updated RTS demo on site)
    • [FIX] Fix to object parameters
    • [FIX] 'Go to layout' crashes; also now 1-based instead of 0-based index
    • [FIX] Crash passing 0 to Common Dialog's SelectedFile expression
    • [FIX] Crash in Array object's 'For each' condition
    • [FIX] Crash editing object icons
    • [FIX] Set Layer Opacity was not working.
    • [CHANGE] Finally managed to get rid of that menu fade everyone complained about!
    • [CHANGE] Numbers displayed as text never have a trailing dot (eg. "3." now becomes "3").
    • [ADD] Physics: added 'None' as a collision mask, which disables physics collisions.
    • [ADD] Double-clicking a comment edits it.
    • [ADD] 'Repeat/for/while/for-each/On loop' loops now try to detect infinite loops - you will be prompted after one million iterations. This only happens when previewing, but allows you to easily terminate the application if you made a mistake.
    • [ADD] 'Run layout' and 'Debug layout' to test just one layout.
    • [ADD] Comprehensive new updating built-in allows for runtime, plugin and IDE fixes to be received without reinstalling a new build
    • [ADD] New 'RTS basics' template (thanks Flon24 for graphics)
    • [ADD] Set skid recovery rate action in car movement.

  • Physics and other movements don't tie in particularly well at the moment: currently, if you move it with a mouse movement or such, it has the effect of teleporting a series of positions along the line you move it, rather than having a velocity and force applied. It's one of the improvements we need to make to the physics engine.

  • A bug. Should be fixed in next build.

  • Variables go in single quotes, eg. Global('Myvar'). You should try the ghost shooter tutorial, it teaches you things like this <img src="{SMILIES_PATH}/icon_wink.gif" alt=";)" title="Wink" />

  • Under the 'Layers' category in the System object for both actions and expressions, you'll find 'Set opacity' and 'Get opacity'.

  • It's something I just haven't got round to yet. I think I'll just drop it, the new version has a live updater which can grab new plugin and runtime releases between builds.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • You can rename event sheets in the dialog where you add and remove them from the list. Single click a selected item to rename it, like renaming a file in windows explorer.

    Can you send me your .cap that runs out of memory? I need to be able to reproduce it.

  • Yikes! Beats me right now, the code for that part is a direct wrapper to the physics engine. It might be a rounding error. The worrying thing is the same thing happened when I swapped Set Velocity for Set Force <img src="{SMILIES_PATH}/icon_sad.gif" alt=":(" title="Sad" />

  • I think I've fixed this now, when the next build comes out let me know if it works!