Rich's Recent Forum Activity

  • OK, that actually looks promising, but I'd think it'd be better implemented by a separate plugin, as it looks fairly configurable. If anyone is willing to have a shot, I can modify Image Manipulator to transfer back/forth from such a plugin, and we could even modify Sprite/Canvas to copy to/from it.

  • I added a 'destroy' action for the next build.

  • How vast are we talking? I'd think it'd be best to keep the landscapes in memory and clear out anything else, if one layout really is going to be a problem for VRAM.

  • This sounds like a bug, can you reproduce it again?

  • Just a note, if you destroy an object, anything to do with it - behaviors or things you added to it, like hinges) should be removed automatically. It shouldn't be possible to cause a memory leak, without doing something like adding to a hash table/creating loads of objects (and not destroying them). If you come across a leak, make sure you report it.

  • You should report every crash you get, they're always bugs.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • 			color = GetPixelColor(x,y);
    
    				n= (long)((rand()/(float)RAND_MAX - 0.5) * level);
    				color.rgbRed = (BYTE)max(0,min(255,(int)(color.rgbRed + n)));
    
    				n= (long)((rand()/(float)RAND_MAX - 0.5) * level);
    				color.rgbGreen = (BYTE)max(0,min(255,(int)(color.rgbGreen + n)));
    
    				n= (long)((rand()/(float)RAND_MAX - 0.5) * level);
    				color.rgbBlue = (BYTE)max(0,min(255,(int)(color.rgbBlue + n)));
    
    				SetPixelColor(x,y,color);
    [/code:331kxyxb]
    
    That's the code to add noise (note that I used an external library written by an image expert, I didn't do it myself).  If you have an algorithm for the above noise I could probably add it.
  • I agree, it's best to separate physics movement from any other behavior or movement system for now, as other behaviors and movement eventing don't work well with it.

  • A lot of undo crashes and problems have been fixed in recent builds. There's not much left to do with it (though some actions do remain un-undoable!).

  • It's impossible to say without looking at the .cap to see what you're doing.

  • Only use pathfinding actions once, or whenever it's necessary. Using them every tick will cause lag.

  • I've been struggling to zoom lately on my laptop, good idea .

Rich's avatar

Rich

Member since 20 Feb, 2008

None one is following Rich yet!

Trophy Case

  • 16-Year Club

Progress

16/44
How to earn trophies