Mr Wolf's Forum Posts

  • Construct only keeps the current layout in VRAM unless you change that setting. Constantly loading everything off the HDD on-demand doesn't seem to be a good idea as constant HDD use is never good. Storing some stuff in regular RAM would be a great feature IMO if it works like I think it does and there'd be no HDD searching/reading.

    I have more to say on this, but I'll wait for your reply. There's a topic in the Construct Discussion about lots of frames and animations and stuff that is directly related to your issue.

  • I think Construct should be tapping into the vast amount of regular RAM everyone has. What if it stores some stuff in regular RAM then puts it in VRAM when needed? I'm not sure what would help exactly, but VRAM is strained while RAM is hardly touched...

    Edit: Things that aren't stored in VRAM would kind of have to be put in RAM so as not to be loading off the HDD constantly.

  • Also, your only 3 posts are about this. Very suspicious. I would recommend no one just download this. Do some research to see if it is safe.

  • Is there anyway they can just save it from a cache or something? That wouldn't be desirable.

  • will construct 2 be construct 1 .cap compatible?

    Nope.

  • Because they should really spawn the correct size, not make me change it every time one spawns. Anyway, I found a way to work around this whole thing.

  • Persist files are extremely annoying. It just fills folders (and my desktop) with worthless spam files. I don't think anyone would care if they have to actually open up the layout they were working on. I'd actually prefer to start with everything clean and closed. At least make persist files optional, please. I don't think anyone really likes them...

    /rant lol

    If you do or do not like them, please comment. =)

  • The 360 plugin, as its name implies, only works for the 360 pad.

    The Xbox 360 Controller Plugin is currently bugged too...

  • I thought it might just be an April Fool's thing, but I kind of liked the HD version actually. I've only seen screenshots of the original, though, so I should DL this.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Construct seems to act weird when spawning new objects.

    For example:

    I have a Bullet object I created on one layout and I'm using it on another layout too (and it'll be used on pretty much every layout since it's a bullet...). I was on the second layout and changed the properties of the bullet to make it bigger. When bullets shoot from the gun, they are set to the properties of the bullet object created on the first layout and therefore, the bullet size did not change.

    This seems...bad. Is there a way to actually control these objects besides remembering which object was originally created on which layout? Maybe there could be added a control thing to change properties of the "Object Base" rather than having the base object contained in one of the layouts? =/

  • That's because there aren't even 30 forum regulars...

  • I'm on. W00t!

  • I would suggest predicting where the ball and the opponents paddle will go using interpolation, and fixing any discrepancies whenever the next bit of information comes in. The ball should follow some pretty straightforward rules of motion and bouncing, so the predictive algorithm wouldn't be too complex. I think most action internet games have some form of prediction.

    FPS games, for example, try to have very good netcode to limit the effects of lag.

  • I second this request.

  • Good point. A lot of game special effects (in 3D games especially) use lower resolution images then scale up, but it probably wouldn't work well for static images. He could still try it though and see.