LifePlay v4.1 Released!

Windows (64-bit):

MEGA - MIXDROP - NOPY - UPLOADHAVEN

Windows (32-bit):

MEGA - MIXDROP - NOPY - RACATY - UPLOADHAVEN

Linux:

MEGA - MIXDROP - NOPY - RACATY - UPLOADHAVEN

Update Only: (requires v4.0 Stable or later)

Windows (64-bit):

MEGA - MIXDROP - NOPY - RACATY - UPLOADHAVEN

Windows (32-bit):

MEGA - MIXDROP - NOPY - RACATY - UPLOADHAVEN

Linux:

MEGA - MIXDROP - NOPY - RACATY - UPLOADHAVEN

Change Log:

This update adds no new content and focuses entirely on fixing crashes and bugs, the most notably of which that have been fixed are:

- The crashes some people have when going into a new building and the game starts to load NPCs there.

- Fix an issue with average attractiveness for both men and women dropping to 0 as a result of a data reading bug, causing a huge percentage of obese NPCs. If you have this issue before, make sure to go to Esc > NPC Distribution & Beauty Standards) and Reset Default when loading your old save.

- An issue some people report about NPCs' moaning being silent during sex (I actually was never be able to reproduce this on my game so I assumed it was save-related, nevertheless, I put in some extra code whenever a sex scene starts to make sure everyone has a 'voice' assigned before fun time)

- Minimize startup / start menu crashes as much as possible by optimizing the initial loading process a bit more. These are usually quite rare and random and the game usually starts fine simply by trying again, still it's good to minimize them as first impression counts after all.

(For those curious of the cause of the new location loading crashes last update and why it was so unpredictable and inconsistent across different PCs (mine and many others never had any crashes at all, but for those that had them, they were so frequent that the game was unplayable): It turns out the crashes were caused by a coding flaw that must have existed in the game for years but has never been exposed till now. When you go into a new location, there are two aspects of the game that are loaded concurrently in two separate processes. Firstly: The objects in the building itself as well as a little analysis to identify what type of building this is. Secondly: The characters and their clothes, including the uniforms. Now, at first glance, the two loading processes seem independent enough to happen simutaneously, but they're NOT, cause the game needs to know what type of building this is before knowing which uniform to load. Up until to the v4.0 overhaul, this flaw was never exposed because the old clothes were so heavy and took ages to load, so the first process always beat the second process by far and the game always knows which building type before it gets to loading the uniforms (since normal NPCs are loaded before 'working here' NPCs). The new clothes in v4.0 however are much better optimized so for many fast PCs (not neccessarily high-end, maybe you just have fewer background processes, etc) possibly running the game on a SSD drive, it suddenly became possible for the second process to get to the uniform loading stage, not knowing what to do and crash, before the first process get to the 'identify building type' stage. Mine and the other crash-free PCs were just not as fast (again, not neccessarily low-end, just maybe having more background processes, mine probably wasn't loading fast because as the dev, I have Unreal Engine running in background while playtesting the game) so everything ended up going according to plan. The fix was therefore to make sure that the building type is identified first, before any loading takes place. As an extra safety measure, I also make sure that if somehow in any circumstances, the game is asked to put someone in uniform but not knowing what type of building it is for, instead of freaking out and crashing, it just dresses this person completely randomly.)