Ashley's Forum Posts

  • Yeah, I'd really like this too (I have no idea how it's ordered at the moment, it looks random), but I think we're planning on changing it to a button that opens a dialog with alphabetically sorted names, and a 'search bar' like in the event wizard dialog. But that's when we get round to it.

  • Try making it always set text ="Score :" +(str(PlayerSprite.value('Killcount")))

    That'd work to display the string, but is identical to the & syntax used in the original post. As Aeal said, with just the events you described you're showing a private variable that never changes, so you need to add 1 when you kill something

  • Sweet

  • Can someone confirm the new version (download same link again) can do "Center view on me" properly?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • The only difference this build is that 'Set Timescale' immediately affects the value returned by 'TimeDelta', as opposed to only taking effect next tick. This is actually really useful, because you can set timescale to 0 to pause, and still have timedelta'd scrolling around and such. However, it means the place you set the timescale is important. Because you have events involving timedelta following the set timescale action, those will all be affected immediately.

    So all you need to do is move your 'Set timescale' action to the end. Either move the event down to the bottom of the list, or add a deferred change (I set another global variable 'TimeScaleToSet' instead of setting the timescale, then at the end of the events list, always set the timescale to 'TimeScaleToSet').

  • OK, I've reuploaded a version with the fixed "Center view on me" attribute. Same download link. Give it half an hour to propagate across the SF download servers then it should be working. Let me know if it works out.

  • Woops, forgot to take some debugging code out which broke center view on me. Just use "Always - scroll to object" for now.

  • Download 0.97.7 now!

    We've all been really busy lately, all of us being in full-time education with courses which are pretty demanding on our time, but nevertheless we still have been doing some small updates. And here they are. This should keep you ticking over till Christmas, when we should have some more time

    Don't forget you can support Construct's development (and maybe prevent the coders from the horrors of starving/becoming homeless/not having any beer money) by donating via the main page.

    Here's the full log of changes.

    Behaviors

    • [ADD] Bullet movement: Set Range
    • [ADD] Fade: Maximum opacity (eg. fade an object in to 50% opacity)
    • [FIX] RTS movement: 'Stop' action caused other moving units to also stop if they collided with it afterwards
    • [FIX] Turret movement: occasionally made turrets disappear

    Event sheet editor

    • [ADD] Icons in the right click menu
    • [FIX] Crash in parameters dialog in standalone event sheets
    • [FIX] Event groups no longer show '&' as an underscore in title and description
    • [FIX] Some cases of actions and conditions with expressions involving private variables could not be inserted
    • [CHANGE] Event Wizard now shows helpful text in the text at the top relating to the object/action/condition being added
    • [CHANGE] Some items in the right click menu moved/removed for clarity

    General

    • [FIX] Can no longer drag non-layout objects
    • [FIX] Can no longer cut/copy/paste non-layout objects
    • [ADD] Move up/move down buttons in manage variables dialog for global variables and private variables.
    • [ADD] System object: 'Number is between...' condition.
    • [FIX] All instances now selected when an object is clicked in the Object Bar
    • [CHANGE] 'Run without PS' on by default in Application Properties. Too many people were making games without thinking about shader versioning, resulting in a lot of people seeing error messages. Default behavior is now to run with unsupported shaders disabled: MAKE SURE YOU TEST what it looks like by setting 'Simulate shader' to PS 0.0 and running your game. If you want to absolutely require a pixel shader version, turn off 'Run without PS' (not recommended). More info under 'Effects' on the wiki.

    Plugins

    • [ADD] Box object: antialiased drawing (see comparison)
    • [ADD] Dropshadow: Set Offset action
    • [ADD] Minimap: Textured points
    • [FIX] Tiled background: seaming occured when zoomed out a long way with non-power-of-two texture.
    • [FIX] Box object: 'compare private variable' broken.
    • [FIX] Box object: hot spot now re-centred when you change a box's size. Before it did not change which made for some inconvenient maths. This may affect existing applications.
    • [FIX] Mouse & Keyboard: releasing the right mouse button triggered 'On middle button released'
    • [FIX] Sprite object: Crash using 'Spawn object' to create an object destroyed by its 'Destroy when...' shader setting
    • [FIX] Particles: now renders particle sizes according to zoom level

    Runtime

    • [FIX] Crash using 'For each' with a family and the family having a movement
    • [FIX] Changing to fullscreen mode from windowed mode still allowed an invisible caption to be dragged, causing a glitched display
    • [FIX] Family movement triggers did not trigger or select objects properly (eg. Family of bullet movements 'Projectiles': On Range Exceeded followed by 'Activate fade behavior' would not have worked)
    • [CHANGE] Runtime treats layouts smaller than the window differently: they are now centred on a black background as opposed to resizing the layout.
    • [CHANGE] 'Set Timescale' now affects the value returned by TimeDelta immediately, allowing non-timescale affected events (eg. set timescale to 1.0, run events, set timescale to old value)
    • [CHANGE] Runtime now uses the August 2008 D3DX release. It was previously using the August 2006 release, which is probably widely installed so standalone EXEs would be unlikely to prompt to install a DirectX update. However, XAudio2 requires a newer DirectX version, so we have upgraded to the latest version. This means it is fairly likely standalone EXEs will prompt end users to update their DirectX installation - there is not much we can do about this, but with time, it will become less of an issue as it propogates wider. The error message is now "You need the August 2008 DirectX update in order to run this application. Click 'OK' to open the DirectX download page, where you can install the August 2008 DirectX End-User Runtime. Press 'Cancel' to exit the application."

  • I think he was typing pseudo-code. It should work if you use Sprite('lastX') instead of just lastX on its own.

  • Nice engine!

    How about using a single sprite holding all letters in an animation? You could have a zero-speed animation so it doesn't change frame, and use frames 1-26 as letters, etc. Then you only need one object.

  • In the 'Angle' category of the Sprite's actions, there's a few actions like 'Set angle towards position' and 'Rotate towards position'. For example, Set angle towards MouseX, MouseY will make the object look at the mouse.

  • No, there's no limit at all.

  • I acknowledge we need better documentation. All us developers are pretty busy at the moment though - it will eventually get done - but that's why we need other people (who do know this stuff!) to pitch in and help write the documentation. It's all on a wiki so it can be done collaboratively, and I can assign anyone editor rights who requests on the forum. Myself and the other devs will eventually get round to it if it's not finished come 1.0, but it's much more efficient if we can spend our time writing code rather than writing docs. Still, eventually, it will all be completed.

  • See GetToken and NumTokens in System Expressions. Shouldn't be too hard to figure out how to do it from that.

  • Yeah, getting the latest driver always helps - especially built-in controllers like the Intel you have. Also, I'm surprised it manages to run at all with 47mb VRAM! I'd recommend a card with at least 64mb to run Construct - it does use a fair bit of VRAM, which is why you get errors opening several applications.