the Sim Settlements forums!

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Favorite screenshots?

That is beautiful :D
Thanks- I often times seek to escape the moment at an overlook somewhere. :smile

From a techinical standpoint, since it's around Corvega, the framerate does dip,but doesn't completely tank. I'm hoping the update from Bethesda will untie the VM from the framerate and allow it to use true multi-threads as opposed to round-robin-frames on a single thread/core.
 
Thanks- I often times seek to escape the moment at an overlook somewhere. :smile

From a techinical standpoint, since it's around Corvega, the framerate does dip,but doesn't completely tank. I'm hoping the update from Bethesda will untie the VM from the framerate and allow it to use true multi-threads as opposed to round-robin-frames on a single thread/core.
Im terrified and hopeful at the same time about this patch. It feels very ominous to me.
 
Im terrified and hopeful at the same time about this patch. It feels very ominous to me.
As an intermittent developer, I would split team, but I think I see one of the problems... using here as an example, when I first started this project awhile back I was focused on too much too soon. Instead of the 'get it to work' then 'optimize later' path, I tried to combine everything at the get go. Trying to code in a way that was both efficient time and code size wise. That was a mistake, as it made the coding un-necessarily diffucult early on. Now it's more of a 50-50 spread- get it too work and make it initially as efficient as I can in a given time as I can always come back later and refactor and/or optimize(or even remove into separate command line apps).

My biggest concern is momentum... if too many problems arise too soon it could slam down on enthusiasm while others try and fill the gap with tech support and bug fixes.

To combat this... I would(and I've heard the team is going this direction) make it very very modular- so that each user base could only use the modules they want. This allows a solid 'fall back' when something new goes south- just remove it from the load order and your back in business without giving up the whole package.
 
Top