-
Hi Guest!
We have recently posted a VaM2 2024 Progress Update on Patreon!
Check out the details here: https://www.patreon.com/posts/vam2-august-2024-111164439 -
Hi Guest!
We are excited to announce a new feature on the Hub: Favorites!
You can now add resources to your favorites, and organize your favorites into collections! You can check out the details in our official announcement!
- Author Shadow Venom
- Creation date
- Hub-Hosted VAR
- CC BY-NC-SA
Shadow Venom
Thank you for your rating and kind feedback. Increasing physical memory and using an SSD may improve your experience.
Shadow Venom
Thank you for your rating and kind feedback!
Shadow Venom
Thank you for your rating and kind feedback! Enjoy!
Shadow Venom
Thank you for your rating and kind feedback!
Shadow Venom
Thank you for your rating and kind feedback! The next update will include more tracks and the surprises you are looking forward to.
Shadow Venom
Thank you for your rating and kind feedback!
Shadow Venom
The scene doesn't have a facial expression plugin. I think what you're referring to is the issue of strange changes in the character's facial expressions. This is usually caused by conflicts between AA morphs and other morphs. This problem can not only affect this scene but also occasionally occur in other scenes. To resolve it, if you want a quick and simple solution, you can directly remove all var packages related to AA morphs from your addon library.
Thank you for your feedback and rating. Feel free to let me know if I can assist you further.
Thank you for your feedback and rating. Feel free to let me know if I can assist you further.
Shadow Venom
Thank you for your rating!
Shadow Venom
Yes, this is a feature that has been requested for a long time but hasn't been implemented until now. But here you go!
Shadow Venom
Thank you for your kindness, and I really hope you can smoothly experience this scene. So, if possible, I'd like to try providing you with some solutions.
First, let's confirm again that your VAM client version is 1.22.0.1 or above, and you have downloaded all the necessary dependency files.
Next, the most likely reason for the issue is virtual memory. You should have plenty of physical memory, but VAM requires more than just physical memory, especially for scenes that demand a high cache requirement. This is often overlooked because smaller scenes have lower demands on both physical and virtual memory. However, when encountering such a scene, issues are more likely to occur.
For this scene, the actual memory usage will vary depending on your hardware. However, based on my observation (with 64GB of physical memory), the peak memory usage typically reaches around 60GB, combining both physical and virtual memory. After cache migration, the physical memory usage is around 20GB, with the remaining 40GB handled by virtual memory. When tested on a laptop with only 16GB of physical memory, it typically occupies around 10GB of physical memory, with the rest handled by virtual memory. Despite this, with proper memory optimization during gameplay, it still runs smoothly. In fact, a significant portion of this scene was created on a tablet with 16GB of physical memory.
If I don't set virtual memory correctly or if there's insufficient hard disk space, even with plenty of spare physical memory (64GB), VAM still frequently crashes when running the scene.
First, you need to enable virtual memory in the system advanced settings of the Windows operating system and set the configuration to automatic allocation. More importantly, ensure that your hard drive has enough free space for virtual memory usage.
Even if you have 256GB of physical memory, you still need to do this because when VAM was in development and eventually released, having 32GB of physical memory wasn't mainstream in the hardware configurations of that time, unlike today where high-end configurations typically start at 64GB as standard.
So, to maximize compatibility with the hardware available at that time, VAM was configured to prefer using virtual memory even when there was plenty of physical memory available. During operation, it continually moves cache files from physical memory to virtual memory. If it encounters obstacles due to insufficient virtual memory settings or hard disk space during this process, it's highly likely to cause the game to crash.
Please first check if the issue is related to virtual memory. This problem is more common with higher-end hardware because, as mentioned earlier, we tend to overlook the role and necessity of virtual memory when we assume we have enough physical memory. If this doesn't solve your problem, please let me know.
First, let's confirm again that your VAM client version is 1.22.0.1 or above, and you have downloaded all the necessary dependency files.
Next, the most likely reason for the issue is virtual memory. You should have plenty of physical memory, but VAM requires more than just physical memory, especially for scenes that demand a high cache requirement. This is often overlooked because smaller scenes have lower demands on both physical and virtual memory. However, when encountering such a scene, issues are more likely to occur.
For this scene, the actual memory usage will vary depending on your hardware. However, based on my observation (with 64GB of physical memory), the peak memory usage typically reaches around 60GB, combining both physical and virtual memory. After cache migration, the physical memory usage is around 20GB, with the remaining 40GB handled by virtual memory. When tested on a laptop with only 16GB of physical memory, it typically occupies around 10GB of physical memory, with the rest handled by virtual memory. Despite this, with proper memory optimization during gameplay, it still runs smoothly. In fact, a significant portion of this scene was created on a tablet with 16GB of physical memory.
If I don't set virtual memory correctly or if there's insufficient hard disk space, even with plenty of spare physical memory (64GB), VAM still frequently crashes when running the scene.
First, you need to enable virtual memory in the system advanced settings of the Windows operating system and set the configuration to automatic allocation. More importantly, ensure that your hard drive has enough free space for virtual memory usage.
Even if you have 256GB of physical memory, you still need to do this because when VAM was in development and eventually released, having 32GB of physical memory wasn't mainstream in the hardware configurations of that time, unlike today where high-end configurations typically start at 64GB as standard.
So, to maximize compatibility with the hardware available at that time, VAM was configured to prefer using virtual memory even when there was plenty of physical memory available. During operation, it continually moves cache files from physical memory to virtual memory. If it encounters obstacles due to insufficient virtual memory settings or hard disk space during this process, it's highly likely to cause the game to crash.
Please first check if the issue is related to virtual memory. This problem is more common with higher-end hardware because, as mentioned earlier, we tend to overlook the role and necessity of virtual memory when we assume we have enough physical memory. If this doesn't solve your problem, please let me know.
Shadow Venom
Thank you my friend.
Shadow Venom
The next one is on its way. XD
Shadow Venom
Thank you for your feedback, please enjoy yourself.
Shadow Venom
Thank you, my buddy. You and other creators on the hub always bring me a lot of inspiration and motivation for my creations, both old and new.
Shadow Venom
Thank you for your feedback! I just made an update and hopefully fixed the issues you mentioned.
Shadow Venom
Thank you for your feedback and rating!
Shadow Venom
Thank you for your feedback and rating!
Shadow Venom
Thank you for your feedback and rating!
Shadow Venom
Thank you for your feedback and rating!
Shadow Venom
This project is based on the works of many creators on Hub, and it is supported by them. All of these works are shared for free, so this scene itself inherits this spirit of sharing. Thank you for your feedback and rating!