Jump to content


  • Content count

  • Joined

  • Last visited

About TallBear

  • Rank


  • Gender
  • Steam Name
  • Location
    Charlotte, NC, USA

Recent Profile Visitors

75 profile views
  1. Closed steam pre-release. Yes or no? [EDITED]

    Spoiling is a very good reason to have a NDA... and I see a few reasons for one... 1) There's a whole trend going on right now where people will watch a game (alpha, beta, release) of a game streamed vs buying it. I can see why some companies "ban" the game from being streamed (even the release version). Persona 5 did this. People got their twitch, youtube, etc channels/accounts banned for streaming it. Granted this got a LOT of hate from the gaming community.. but some companies look at streaming as akin to piracy. I don't think this is their real reason though for Universim. That being said, streaming can also be an effective way of "free" advertisement. In the end, it's all up to the company on if they feel it's worth it or not. Being a kickstart backer doesn't guarantee one to all phases of development (unless a company promised that to backers) 2) The other reason for the NDA is not to spoil a launch - often to prevent negative press/pr. So if the game may not be what it's hyped to be, too many bugs, they don't want to spoil sales/pre orders. This is also VERY industry standard to do. 3) Piracy is another reason for an NDA. For example, v0.0.25 is ALL over the torrent and pirate web sites. This happened because anyone can buy it. By locking it down to a small, fixed number of people, the chance of piracy before the steam release is lessened and easier to track who released it. I wouldn't call whats coming out in August a "beta" unless 99% of all the features are in game. I'd call it "closed Alpha 2 or 3" (or something with Alpha in it). Then again steam is VERY clear that early release games are not finished and may never be - "buy at own risk". Either way, it's not a finished product. Signing an NDA *really* doesn't affect anyone as a tester - except it spoils people not being able to go "hey! look at what I'm playing FIRST before anyone else!" (bragging rights).. and I don't really see that as a reason not to sign a nda. To foster good relations, all kickstart backers, who have been active in testing/feedback, should be allowed to test the steam early release before aug 28th , and I think an NDA is very valid (and very industry standard). This will only help the developers to deliver a more polished product by Aug. Don't forget aug 28th isn't just early access on steam.. I believe it's early access on a number if digital distribution services. I think that's why they house info/feed back on social media and on these forums. They want the information as centralized as possible. Basically, I think they are just "releasing" the game as is on the 28th of Aug, and people will just be buying an alpha test of the game, and it will be polished over the next year.. and to be honest.. there's REALLY only one reason to push a game like this out so fast: They probably exceeded (or have come very close) their budget for the game and need more sales to further develop it and make a profit.... and this is becoming more and more common these days with smaller, independent studios with less cash reserves vs the big companies.
  2. Can't go much beyond 35-40 population?

    I did edit my save game file, on one playthrough, when I had 40 nuggets, and set all the nuggets over 10 "years" old back to 10 years old. That let the game get up to about 90.... With 90, and ALL those buildings, the game started to "chunk" and slow down a bit. Eventually this will need to be optimized as people will eventually have 100-500 nuggets on a planet LOL
  3. Memory Leak?

    Yeah that tells me the problem isn't the save but in some sort of data structure the game is using that gets inefficient with memory over time when the simulation is running. Clearly the game is capable of recovering that memory when you load a game as that "restarts" the simulation It could very well be at this stage memory is just not being used (and properly cleaned up) at this point in the development stage, but I wanted to bring it to your attention I mean if it's intentional the game uses THAT much, then that's ok, but they you'd all need to raise the minimum memory requirement of the game to 16GB ram minimum with 32 recommenced. Plus compressing memory in windows 10 DOES eat up some cpu cycles. Normally this isnt an issue but with a CPU intensive game like this, it could be a problem. And windows won't bother to compress memory unless it really has to. I didn't pay too much attention to compressed memory as ONLY windows 10 does that.. windows 7/8/8.1 don't compress memory.. and I also disabled the ability for windows 10 to compress memory. If I ever run out of memory, this machine can handle me adding more chips to bring the ram to 32GB I also have an apple here running the latest OS X. And my PC dual boots windows 10 & linux if you need any testing done on those platforms
  4. Memory Leak?

    @MagecoerlinKilling everyone stopped the memory "leak" cold.. so it's not in the planet, animals, weather, etc Wiping out all the nuggets stops the "leak" but does not reduced memory used (even if all buildings destroyed). The game is reserving memory for SOMETHING and just not letting it go until you load another game (that stops the current simulation and re loads a save into a new session). This will cause HUGE problems with people who have 8GB ram, and even some people with 16GB. I only noticed this because when debugging a game, I look at not only the game itself, but what resources it's using in the operating system Im not privy to the source code so unless I find something obvious in game, the rest of this is on you guys to find The devs could be allocating too much memory for an array or other things (persistent data structure problems, etc) and failing to release that memory while the simulation is running A temporary work around: Simply save and re load a game (once every 2-4 hrs of playtime. More often for people with 8GB ram - less often for people with 16-32GB RAM), this reduces memory use somewhat similar to when the game is started fresh. As long as a player re loads (or closed the game, and re loads their save), memory use can be kept down, but in the end this still needs to be fixed. However.....Someone should be able to run the game for 80hrs non stop without memory going crazy ..and with that, it's 1:56am where I am. So It is time to zzzzzzz
  5. Memory Leak?

    After 30 mins... Working set 5GB, Commit 9.2GB. I saved then killed everyone. Now ill step away and let it just run and see what happens.
  6. Memory Leak?

    Also this may not be a "leak".. it could just be VERY sloppy memory management in the game.. but either way, it would have to be fixed
  7. Even with 1 pump, a lake drains faster than rain can refill (tested by running a game for 5-6 hrs). Granted you can pump from more than 1 lake a time, but this will eventually cause issues down the line. rain should refill a lake providing the player doesn't OVER pump it
  8. Memory Leak?

    @Magecoerlin 1) Memory leak is happening NO MATTER what.. playing normally vs just letting the simulation run non stop.. I just finished playing for 4-5 hrs normally and the above screenshots of the games memory is of that playthrough 2) Done.. attached to this email 3) Make sure you use the RESOURCE manager in windows to look at memory, task manager ONLY shows the working set not total commit. Windows will usually page out working set (what's in active ram to the page file and keep working set of a program around 2-5GB depending on the physical ram of the system). If the page file fills up, THEN the working set will grow like crazy. Commit = TOTAL memory used (what's in physical memory and what's in the page file) 4) You're welcome! I've been coding games since 1986 5) I'll go do that right now.. ill play for 30mins.. kill EVERYONE.. then just let it run Memorytestgame4.rar Keep in mind, if I exit the game, and load the save, memory use will be back to "normal" the "leak" seems to happen over time.. I'll do the above test right now where I kill everyone after 30 mins
  9. Balance issue? or intended? Once you start getting around 35-40 population, nuggets die faster than they can reproduce.. this drops population back down to 25-30 and it's a MASSIVE struggle to even get it past 30-35 again... 1/2 of my playthroughs, the deaths continue.. population drops to 20-25, buildings fall apart, etc... This happens even if no disasters wipe people out Now if a tornado pops and kills 10-20 nuggets... especially younger ones.. well then it's all over.. the older ones cant reproduce fast enough Either re-balance them to mate faster or maybe a god power to let people "spawn" 2 yr old nuggets for like 50 power
  10. Find my lost nugget

    This bugs out a lot... If you wait too long after the mail is built, the child will grow up and already be in town and you can't complete it Also, sometimes it doesn't assign the child to a hut making it almost impossible to find
  11. Wild Animal Attacks/Guard Bug?

    Make a bunch of them.. the towers have a very limited radius.. I have about 6 of them in my game... once I balance them, they kill 99.9% of hostile animals that try to come into my village
  12. My nuggets are going WAY WAY far away to gather food (from bushes).. and I have plenty of food in storage and in restaurants.. and I have plenty of farms, fisheries, and hunters... they shouldn't be gathering once a food resource building is built unless there's a food emergency The problem is.. this is all they end up doing later on.. and it makes it hard for them to build new buildings etc... The same issue happens for wood and stone... they go FAR away when there's plenty close by
  13. Memory Leak?

    Same new game as above.. it's now 45 mins later... population 33... 11GB commit, 3.7GB working (working set is down because windows has just paged out an additional GB to the swap file) And another 45 mins later.. population 39... 13GB commit, 4.8GB working... this is about 3 hrs total play After another 2 hrs, 21GB comitt and 5.9GB working
  14. Memory Leak?

    @MagecoerlinOh and the save wont upload. the forums allow only a file size max of 3.91MB and the save files of the game are around 17-20MB Can I email it to you? Even then , the game still uses more ram that it should even on START UP with a brand new game: 4GB commit, and 2.5GB working Now if I exit the game, start the game back up, and reload my save, memory drops back down to around 4.5GB commit, and 2.5GB working. I decided to start a new game to test things, after 60-90 mins of play usage is 7.15GB commit and 4.4GB working, Ill be happy to send you the save, but I highly doubt the save is the issue (especially since I started a new game). If it's leaking memory, the issue will be within the program itself. Part of the things I'm doing is im DELIBERATELY trying to break the game. I'm trying to do everything a player might do when it's released in August (like just letting it run for 6 hrs non stop, running the population over 100, tons of buildings, etc, etc).. but even if someone had a population of 500, the game shouldn't use up THAT much memory This is a screenshot of the system resource monitor in windows after 90 mins of game play with about a population of 25 My system: Alienware Aurora R4 Windows 10 x64 (all video and system drivers current) 16 GB RAM, 4 4GB pagefiles split between C, D, E, and F (16GB total) Intel i7-2600K OCed to 4.9GHz (2) Nividia 1080ti 12GB VRAM each (I run the game in single gpu mode though) 2560x1600 Resolution Display Drives... C: 1TB, D: 6TB, E: 1.5TB, F: 16TB. The game resides on my E: drive
  15. [TWITTER] "..."

    @Kerby84 I was mostly talking about the people on twitter who havent backed nor even played the game who are expecting a full release with unrealistic expectations (and yes even some kickstart backers who expect a FULL game on Aug 28th - which won't happen unless V0.0.25 is a REAL hobbled down version of what they are really working on).. but if v0.0.25 is ALL they had actually coded by April.. well then what you will get on Aug 28th will be a more "robust alpha test" than you have now. And also this really IS normal for a game. It's just that most games, gamers do NOT see a game through the entire process of development. Most gamers just hear about a game, then maybe see a review from a beta test done 2-3 months before release and then they buy it or dont buy it. Most companies come up with a concept, and often times that concept does not make it through to the final game (often times because coding the concept is more challenging than originally thought or budgetary issues crop up - or both). You all are dealing with a smaller company that came up with a concept that would normally be made by a company like EA, Ubisoft, etc (50-100+ devs working on a game). So development, from a small company like this, actually would take 4-5+ years. I dont need to have been here since 2014 to know what's going on. I've read the history. I've been designing and coding games since the 80s (1986 to be precise), and while, yes this does "suck", I assure you, it's very normal. I've worked for very large to independent studios over the years. I've also backed various smaller dev companies directly (as an angel investor) or via kickstarter, and what I'm seeing here has happened countless times. There's also many kickstarter games that fail and never get launched. Investing in anything is a risk. The only difference is kickstart backers don't see a monetary return on your investment. Typical game investors could care less about the game. They just want their money back with interest (this is how the gaming industry has worked for ages).. They just care if the game sells well...They don't care if the final product if different from the concept that was pitched...kickstart backers pose a unique "problem" because they want to be involved in every, single, tiny, step.. I'm not saying those expectations are wrong. I'm just saying they pose a challenge - mainly because most, not all, but most, kickstart backers have unrealistic expectations of software development. Most dev companies have the freedom to go ANYWHERE with a game.. but with kickstart backers, they kind of get forced into the direction of the concept, and if they have issues making the game like the concept... well drama happens. The above being said....From what I've read, they could have communicated to the kickstarter people, a lot more and better, along the way as to why the direction has changed (or appears to have changed) and where they plan to go. That's the biggest criticism I could give them as they should know kickstart backers want to be involved and be testers along the way. Also keep in mind that they may reserve a LOT of features for internal testing. V.0.0.25 may be JUST the coding branch they show to the public for testing while a lot of other features remain internal only on a different coding branch. I hope this is the case because it would mean a much more robust version in august. They did hint at this in the stream. Now whether that's fact or PR hype is another story. As far as a "god game".. well look at black and white. I've played all of them. B&W was very much a "building simulation" game with a LOT of resource management, but it was also a god game - one of the best God games ever made. In fact, every god game I've played are both to a degree. The "god" aspects are really easy to implement into the game. TBH the building simulation would be one of the more difficult things to code, and they already have almost all the god powers in the game. They need to refine those powers, and add in things like editing the world via raising and lowering land, letting players add water (lakes etc). Then they need to add the ability to "colonize" other planets and maybe have alien races as a "disaster" to attack planets. Right now the game is "sloppy", and with the pace they are going, I don't see them getting a TRULY finished product until 2019 unless, like I said above, unless they are keeping a version to themselves that they are not showing anyone (which they did hint at). I hope this helps. I'm not trying to bash you, or the developers. I'm just trying to give you, and other people a realistic take on things.