Ashley's Forum Posts

  • Why allocate a new Perlin then delete it in one function? It's slower, and you risk leaking memory if Get() threw an exception, you may as well just have it as a local.

    To debug a plugin, make sure you've built a debug runtime version of your plugin and that it's in the IDE's runtime plugins folder. Then, locate the Temp.exe that the IDE creates for previews, which should be somewhere under your Users Appdata folder (eg. C:\Users\<username>\AppData\Local\Scirra or something like that - AppData is a hidden folder so you need to make sure Windows doesn't hide hidden folders). In Visual Studio's project settings, set the debugger target to be that Temp.exe file, then click Start Debug. It should launch Temp.exe and start debugging your plugin.

    Note Temp.exe is replaced every time you preview, so make sure if you change the .cap you hit preview, close it, then start the debug. Also, if you change your code you need to rebuild your plugin and put it back in the plugins directory, otherwise you'll get a "symbols don't match" error.

  • Sounds like fun

  • Did you run the full installer, including the "optional" DirectX updates? (which are badly named because Construct actually requires them)

  • Fixed! Took a couple of hours to work it out, but it was a good catch - thanks for finding it. There was a fairly subtle multithreading issue which was a bit of a headache, but it affected all loaded sounds of any format, so pretty important to fix!

    Attached is the runtime version of XAudio2.csx. Paste it over your Plugins\Runtime copy and it should be fixed. (the edittime plugin has not changed)

  • I'm afraid I can't find the files you say you emailed me in the bug report (this is why I ask all possible files are attached or uploaded to permanent storage). Not sure why I can't find them - might've been junked or auto deleted or something

    If you re-send them or (preferably) upload/attach them then I can have a look at a quick update.

  • Do you mean bug 2863906? I'll see if I can get a hotfix for it at least.

  • I have an 8800GT too. I guess I'll switch back to ATI when I get my next computer, my 8800 tends to overheat, forcing a reboot.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • You've got the AppPath bit right. You just need to do the same thing when adding in the Sprite value, put & either side of it:

    AppPath & "se\chain" & Sprite('PegSound') & ".wav"

    Remember:

    • "" (two double-quotes) in a string turns in to ", ie: "hello ""world"" " gives: hello "world"
    • Anything "in quotes" never changes, ie.: "You have Sprite('health') health" will literally give the text: You have Sprite('health') health

  • Yes, you should always use the angle functions for angles - I think in Construct angles can, at times, go over 360 and below 0 anyway (eg. 405 would be 45 degrees) so straight comparison as numbers will never be reliable. However, the angle functions always work properly with any angle inputs, taking in to account wrapping and angles outside the 0-360 range.

    If you want to check if an angle is equal to a number, for example, you'd have to just check the anglediff() expression and see if it is within 1 degree (say) of the desired angle. As mentioned above, both anglediff(46, 45) and anglediff(406, 45) are 1, so it takes in to account wrapping, which you cannot do by ordinary comparisons.

  • Lucid is right - basically, because the source code is open, some Prof-UIS files are available on the CVS. However, you cannot download these and go and use them in other C++ projects. Since none of these files are at all used in neither the runtime nor the plugin SDK (which deliberately hides all UI code) then you don't need to worry about Prof-UIS licences at all if you're distributing a game or plugin.

    In retrospect it was a bad decision to go with Prof-UIS - since we have to pay for upgrades, which is always difficult for an open source project. But since we made the decision MFC (a free library with Visual Studio) now has the same features - so in Construct 2, we'll definitely be using that.

  • Don't use greater than/less than tests on angles - it never works properly. They always have problems with the crossover between 0/360 degrees. That's what the angle-specific expressions, like anglediff, are for.

  • What is alpha clipping and how does it work?

  • This is not possible, you cannot change the name of the variable you want at runtime. You could try another data storing object, like Hash Table.

  • What codec are the .WAV files? Could you post them so we can try them out too?