oosyrag's Recent Forum Activity

  • You can also store data in localstorage, or an array.

  • An occasional reset event, maybe between every couple of stable releases wouldn't be a bad thing. It would have a similar effect to what this thread did actually - drum up interest again for people to clean up suggestions, re allocate votes, see what's new ect., and prompt Ashley to reserve some time to review suggestions. I wanted to say Ashley&co. but I'm pretty sure he's literally the only one to deal with suggestions.

    A reset would clean up the clutter. The old ones will still be there for you to resubmit in the new one, if you aren't afraid of a little work to show you still care. If you keep resubmitting, they'll get more visibility than the masses of junk posts.

    They've implemented quite a few suggestions from the suggestions site. Again it's a matter of expectations of what you expect them to get done with it.

  • I vaguely recall this concept had been explored pretty extensively. It might be worthwhile necroing the thread you found or tagging the owner of the example. If it was a dropbox link the file is likely still there, just the link needs updating.

    If my memory didn't fail me, R0J0hound was involved in the particular thread I was thinking about, and he's definitely still lurking around on these forums.

  • I wonder how a crash would corrupt a save file, unless it literally happened during saving or the hard drive itself got damaged.

    You can try to send the file to support to see if they can help you.

    Also check if you're actually trying to load a .c3p file. You can't load an exported project in the editor. Sorry if that sounds silly, but that is attempted more regularly than I would believe possible.

  • So... change your sprite size? Or change the viewport size.

  • I now have an idea for a little app... Swipe right for yay, swipe left for nay, with the understanding that it's for "minor suggestions" only and bigger suggestions that aren't focused in scope, too long to read, or otherwise unclear should get the nay treatment. Anyone can add any amount of ideas, with adjustable threshold setting for number of yays required for a suggestion to even show up in your feed. You don't automatically get a yay on your own idea, gotta have it randomly show up as you go through everyone else's ideas. One vote per person per issue. Low interest ideas automatically get removed from the pool after a certain ratio of amount of views with no interest.

    Add a way to view a list of all suggestions sorted by interest, and optionally culled suggestions.

    But then there wouldn't be any real way to handle duplicate suggestions. Not that the current site really does either though.

  • Did you create an account just to answer a one year old question with the same answer that was already given in the first reply to the OP? I'm actually really super curious if you're a person or an amazing bot.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Yes, but I believe the ram usage for a text based object like an array is generally negligible. At some point you will not be able to hold an infinite amount of data in memory, but that should be given.

    You're more likely going to run into cpu limitations first when trying to process the all the data in huge arrays, which again emphasizes minimizing the scope of whatever you are doing to only what is relevant at any given point.

  • Normally I maximize the use of instances, given that all the instances of the object in question logically have the same scope or function as far as events go.

    However, if using all separate objects works and makes it easier for you, there is no reason not to unless you can actively notice or measure a performance difference.

    I don't think 100 objects would have any measurable impact on performance. On the other hand, slider bars objects are html form elements and those don't always play by the rules. Anyways I wouldn't bother worrying about performance.

    I'd go crazy building events for 100 separate objects if I could do it just for one instead though. Then again, you've got families to make up for that as well. This engine gives you a lot of flexibility to work in whatever way you feel most comfortable.

  • Hmm if you need to keep track of modifications to the noise, then you might want to have it in an array after all. I personally would still approach it by recording only what is necessary rather than everything at once though.

    Again, you could break it into chunks, Minecraft style, where you keep an array instance per chunk and have a system to keep track of the relative location of each array/chunk

  • I am filling one z axis of the array with perlin noise values so I have a feeling that if I broke the map into many arrays that the noise wouldn't be so perliny on chunk edges

    With the same seed, as long as you're consistent with your coordinate system, there should not be any seams at whatever chunk edge you define.

  • Well I can't answer the array size limitation question... but I can say normally I wouldn't store what is I'm assuming your entire world's procedurally generated values in an array to begin with. You should be able to look up a value at any given position for a particular seed any time you want, so just get the relevant values as you need them from a function.

    Alternatively, if you must have the values in an array, you can split your arrays into chunks (can still be a single array object, with multiple instances). Use x/y instance variables to keep track of the relative position of each array, and have each array's size be whatever you're comfortable with that doesn't crash.

    I'm just guessing here, but I think the array size limitation is based on your system, so I'd stay well away from that threshold if I were you, since your end users' systems might not be as capable as your own.

oosyrag's avatar

oosyrag

Member since 20 Feb, 2013

Twitter
oosyrag has 39 followers

Trophy Case

  • 12-Year Club
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Forum Hero Made 1,000 posts in the forums
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • Enduring Visitor Visited Construct.net 90 days in a row
  • Unrelenting Visitor Visited Construct.net 180 days in a row
  • Continuous Visitor Visited Construct.net 365 days in a row
  • RTFM Read the fabulous manual
  • Email Verified

Progress

22/44
How to earn trophies