Ashley's Forum Posts

  • BTW, XAudio2 has always timescaled audio - the new option is simply to turn it off

  • It might be useful to say what you need help with.

  • That's not right, 'every' doesn't make sense under a 'repeat' condition.

    Try:

    • do something
    • use the function object to call a function after a delay
    • in the function add a 'repeat 2 times' condition

  • No worries. It's cool. Just trying to pre-empt any unwarranted rule-making, but this was needed and I agree with all of it

  • So making a canvas of only 8x8 and stretching it to fill the entire display works great! Doesn't effect the quality at all, but runs much faster and uses barely any extra VRAM!

    Sort of - a canvas always uses as much VRAM as the size of the canvas itself - it's needed for pixel by pixel processing on the canvas. You are saving the VRAM of the source texture that way, but don't think you're getting all that for free! I said before, I recommend you don't make canvases larger than the size of the window.

  • No method is unhackable. Good crackers can modify the code inside your local copy of the EXE to bypass validation entirely (online or offline), for example. All you can do is make it more difficult. Think of a version of your program written with no validation at all, then think of a cracker working to make your validated app look like that. (Also, it's not too hard to locate particular strings eg. your personal details in an EXE with a hex editor, so unless you used encryption that's easily subverted too).

    Settle on something simple enough that you don't waste days on it, but keeps script kiddies off your back, IMO. Also remember, the more popular your application, the more likely expert crackers will give it a shot. Small scale apps probably don't need ******** protection - but that's not to say someone's not going to pwn it anyway.

  • I don't usually advocate "volunteer moderation", but this is all true and well said. So behold; it be sticky.

  • For example can the canvas grab everything below it, including other effects.

    Yep, and this is what Davioware meant, for fullscreen effect processing. You want to set it to grab the layout before drawing (it means "grab layout before drawing the canvas"). That means it works like this:

    Layout (everything beneath the canvas) is fully drawn

    Canvas takes a snapshot of that

    Canvas processes an effect (assuming you added one) and draws on top of everything

    End result: you see everything with an effect applied.

    'Grab after drawing' means it takes a snapshot after the canvas has already drawn itself. That's useful for frame feedback effects, such as an effect mixing the previous frame and the current frame (usually the canvas has to be semitransparent for that to work).

  • Please see this for information on reporting bugs. You can attach files to the bug tracker.

  • I tried to play Subject 66 a few days ago and that writes a file to the hard drive and windows said no way. I had to run in administrator mode to get it to play I'm sure it would do the same thing for registry keys.

    Vista and 7 allow the application access to certain parts of the registry and disk. For example, an application can write to temporary files without security privileges, but not your Windows directory.

    If the application steps outside this boundary, Windows hits the user with a UAC prompt. You just have to know what you're allowed to do, and you can avoid it. It's fully documented on MSDN, Microsoft want everyone to know what these limitations are so applications are more secure.

    Then when they buy a full version off you, compile a customized copy of it just for them

    Try that when you're selling 10,000 copies.

  • Windows defender would probably pick up any attempt to modify the registry

    I doubt it would since almost all applications modify the registry as a matter of routine. Bearing in mind almost any system you come up with can be cracked, I'd come up with some basic system that writes something to the registry, simply to prevent casual piracy where you can copy/paste files to someone else and it works.

  • I couldn't repro, and the bug was automatically closed due to no response (maybe the bot was overzealous, it looks like you did respond there). Re-open it, closed bugs are permanently ignored and won't be looked at again. However, if I can't reproduce it, there's basically nothing I can do. Do you know any particular software/hardware that affects it? Judging from the tracker history, I didn't have enough information to act on it.

    "Will you fix <insert bug here>?" is a common question that comes up from lots of people following new builds. Of course we want to fix all problems if we can. The best you can do is ensure there's an open tracker item about it, and provide as much information as possible so a developer can reproduce the issue and investigate. If it's really causing you problems (eg. collisions don't work or similar) set the priority higher and someone might be more likely to look at it. But we can't guarantee anything.

  • Well, make a .cap in an early version, load it in 0.99.7, and if anything's different, put the .cap on the tracker with the usual details (repro/expected/result).

  • I haven't touched any of the layer effect code for months myself, so I don't see why this would have suddenly changed. Have you got a before/after .cap that demonstrates an actual difference? Are you sure you're not setting it up wrong?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • The runtime stretches the texture like the layout editor shows. Canvases have always used as much VRAM as their overall size is (I wouldn't recommend canvases bigger than the size of the window), so this doesn't affect that.