• Hi Guest!

    We are extremely excited to announce the release of our first Beta1.1 and the first release of our Public AddonKit!
    To participate in the Beta, a subscription to the Entertainer or Creator Tier is required. For access to the Public AddonKit you must be a Creator tier member. Once subscribed, download instructions can be found here.

    Click here for information and guides regarding the VaM2 beta. Join our Discord server for more announcements and community discussion about VaM2.
  • Hi Guest!

    VaM2 Resource Categories have now been added to the Hub! For information on posting VaM2 resources and details about VaM2 related changes to our Community Forums, please see our official announcement here.
VaM Produce 69 The Second DLC Expansion and the Rise of the Third Season

Scenes VaM Produce 69 The Second DLC Expansion and the Rise of the Third Season

Download [199.47 MB]
你的显卡是什么呢?
我看出来了。模型和特效上面有红色光圈和黄色光圈。是不是显卡的问题呢?
我的机器配置是Win11、9950Ⅹ3D、MSI 5090、64G RAM,4tb M2 SSD,VAM是1.22.07(1.22.03也试了),玩其它游戏没问题,其它VAM的绝大部分人物和场景也没问题
 
你的显卡是什么呢?
我看出来了。模型和特效上面有红色光圈和黄色光圈。是不是显卡的问题呢?
问题解决,是NVIDIA控制面板里面的设置问题,其中“管理3D设置”里面的“各向异性过滤”要选“应用程序控制的”,这样画面和颜色就恢复正常了
 
是否有考虑风格化分开,比如古风系列,主要文件太大,加载太久。
你第一次进入这个场景后,在歌曲界面,任选一首歌,然后,保存这个场景。
重新启动vam,重新进入你保存的那个场景后,就会只出现一个>>>>蓝色按钮,然后点击蓝色按钮,直接快速进入歌曲选择界面。
 
是否有考虑风格化分开,比如古风系列,主要文件太大,加载太久。
Again, technical support for the current version has already been discontinued, and there will be no further maintenance or updates.

A brand-new Generation II will be released in September.

I want to clarify one point: the amount of style and content has nothing to do with loading time.

The upcoming Generation II contains more styles and content, yet its loading time has been dramatically reduced to just one-tenth of the current version.
 
Again, technical support for the current version has already been discontinued, and there will be no further maintenance or updates.

A brand-new Generation II will be released in September.

I want to clarify one point: the amount of style and content has nothing to do with loading time.

The upcoming Generation II contains more styles and content, yet its loading time has been dramatically reduced to just one-tenth of the current version.
That sounds exciting.

So, you won't be repeating the content from Seasons 1 and 2 in VAM Produce II, will you? Absolutely not. Repeating the Wishing Well content is fine.

Also, I'd like you to remove certain features, like the "Use Scene as a Stage" feature. This requires creating a separate scene, not placing it within your main scene.

And the "Use Scene as a Stage" feature isn't very useful, because many people don't have animation data for the WindowCamara atom. While they might have character dance animation data, without the WindowCamara animation, the character dancing there will look awkward and weird. In this scene, in some dance animations, there are some issues with the foot animation. For example, the feet don't touch the ground or clip through the ground. This may be related to the different character body shapes. But at this time, the animation of the windowscamara is very important, so that the flaws of the foot animation will not be revealed. Does the windowscamara animation take you a long time?

I'm really looking forward to your new work. In addition, I'm afraid that only by turning on low image quality can the scene load faster when it is first loaded when entering?
 
在进入这个场景之前,在另外的场景中,把所有配置调整为最低配置。进入场景后,场景画面出现时,再把画面质量调高,可以节省很多的加载时间。
 
That sounds exciting.

So, you won't be repeating the content from Seasons 1 and 2 in VAM Produce II, will you? Absolutely not. Repeating the Wishing Well content is fine.

Also, I'd like you to remove certain features, like the "Use Scene as a Stage" feature. This requires creating a separate scene, not placing it within your main scene.

And the "Use Scene as a Stage" feature isn't very useful, because many people don't have animation data for the WindowCamara atom. While they might have character dance animation data, without the WindowCamara animation, the character dancing there will look awkward and weird. In this scene, in some dance animations, there are some issues with the foot animation. For example, the feet don't touch the ground or clip through the ground. This may be related to the different character body shapes. But at this time, the animation of the windowscamara is very important, so that the flaws of the foot animation will not be revealed. Does the windowscamara animation take you a long time?

I'm really looking forward to your new work. In addition, I'm afraid that only by turning on low image quality can the scene load faster when it is first loaded when entering?
Generation II will include all the content from the current version, plus full Seasons 3 and previews of S4, along with an entirely new DLC. On mainstream hardware, scene loading can be completed within 2 minutes, and memory requirements are reduced to just one-third of the current version. While the graphics, scene quality, and visual effects have been greatly enhanced, the hardware requirements are actually lower. Under the same conditions, FPS performance is significantly improved, and it comes with native support for VR/XR.
 
1755713760941.png


full
full
full
 
Okay... Thank you for your reply. Thank you.

But I also have a sincere suggestion for you: when you create Season 5 content, I hope you'll only include Season 5 content in the scenarios. Also, include any DLC content you deem essential. Thank you again.

I'm just personally averse to duplication. Of course, the background of the scene can be repeated. However, the song and dance should not be repeated in the scene. Thank you.
 
Okay... Thank you for your reply. Thank you.

But I also have a sincere suggestion for you: when you create Season 5 content, I hope you'll only include Season 5 content in the scenarios. Also, include any DLC content you deem essential. Thank you again.

I'm just personally averse to duplication. Of course, the background of the scene can be repeated. However, the song and dance should not be repeated in the scene. Thank you.
Sorry, but I don’t quite understand your proposal. Could you explain what you’re trying to say? Your request sounds as if you’re asking Netflix to release a completely separate Netflix app on the app store every time they launch a new show or a new season of an existing one.
 
I suppose you might be concerned that if the scene’s content becomes too large, it could cause performance issues—for example, making scene loading times longer.


But I think this is one of the biggest technical misconceptions: performance isn’t affected by the sheer amount of content, but rather by the resources that need to be preloaded during the initial scene load. At any given moment, in terms of content, the only thing present in the scene is the track you’re currently running. You can think of each track as something that’s pulled from a repository only when needed.

Gen II completely rebuilt the scene structure, changing everything that used to be preloaded into an on-demand system to fix the issues of the past architecture.

In short, at least in Gen II, whether P69 has one track or ten thousand tracks, performance will not be affected in any way.
 
Okay... Thank you for your reply. Thank you.

But I also have a sincere suggestion for you: when you create Season 5 content, I hope you'll only include Season 5 content in the scenarios. Also, include any DLC content you deem essential. Thank you again.

I'm just personally averse to duplication. Of course, the background of the scene can be repeated. However, the song and dance should not be repeated in the scene. Thank you.
If your suggestion is simply based on personal preference—say, you only want new content and aren’t interested in the older tracks—then unfortunately, this scene isn’t made just for you alone. The earlier content is still loved by many others, and from the creator’s perspective, it represents completed work. Out of respect for that work, it should be preserved. If you’re no longer interested in it or feel you don’t need it, you can simply choose to ignore it.

Also, the idea of “duplicate content” needs some clarification—there is no “duplication” between Gen II and the current version, because Gen II will completely replace the existing version.
 
If your suggestion is simply based on personal preference—say, you only want new content and aren’t interested in the older tracks—then unfortunately, this scene isn’t made just for you alone. The earlier content is still loved by many others, and from the creator’s perspective, it represents completed work. Out of respect for that work, it should be preserved. If you’re no longer interested in it or feel you don’t need it, you can simply choose to ignore it.

Also, the idea of “duplicate content” needs some clarification—there is no “duplication” between Gen II and the current version, because Gen II will completely replace the existing version.
Your scene is great, but it loads incredibly slowly. It takes at least five minutes to enter, and I even skipped the beginning. It's still quite time-consuming, and sometimes it crashes. It really detracts from the experience.

And besides, don't you think your scene has too many buttons? Every additional button makes the scene heavier. And when you're creating new content, don't you find it cumbersome to have so many buttons? Fewer buttons would make the scene smaller and load faster. And if you removed all the previous songs and only included the new season's tracks, wouldn't that mean a lot less buttons? If people want to see the previous songs, they can just download your previous work.

That would be better for everyone.

But this is just my personal suggestion, for reference only. I don't really care how you arrange it. And I'm not talking about seasons three and four, I'm talking about season five. I recommend doing this for season five.

But if it were me, I'd definitely separate the songs for each season without hesitation. After all, anything can be stored as a pre-file, right?
 
Your scene is great, but it loads incredibly slowly. It takes at least five minutes to enter, and I even skipped the beginning. It's still quite time-consuming, and sometimes it crashes. It really detracts from the experience.

And besides, don't you think your scene has too many buttons? Every additional button makes the scene heavier. And when you're creating new content, don't you find it cumbersome to have so many buttons? Fewer buttons would make the scene smaller and load faster. And if you removed all the previous songs and only included the new season's tracks, wouldn't that mean a lot less buttons? If people want to see the previous songs, they can just download your previous work.

That would be better for everyone.

But this is just my personal suggestion, for reference only. I don't really care how you arrange it. And I'm not talking about seasons three and four, I'm talking about season five. I recommend doing this for season five.

But if it were me, I'd definitely separate the songs for each season without hesitation. After all, anything can be stored as a pre-file, right?

Please stop wasting our time on the current version. I’ve made it very clear: both technical support and improvement suggestions have already been discontinued. We need to focus on the release of Generation II in September. If you didn’t read my detailed reply earlier, let me explain it again—

ON THE TECHNICAL SIDE, SCENE LOADING TIME HAS NOTHING TO DO WITH THE AMOUNT OF CONTENT!

That said, as I’ve already made clear in my previous replies, both loading time and hardware requirements have been resolved in the upcoming Generation II. The content in Generation II is twice that of the current version, yet loading speed has been reduced to within 1 minute 30 seconds to 2 minutes, and memory requirements have been cut down to one-third of the current version. I am repeating this once more to correct your mistaken belief that “it’s the richness of content causing slow scene loading and other issues.”


So, can we please stop wasting time on problems that have already been solved?
 
Last edited:
Screenshot 2025-08-21 083333.png
Screenshot 2025-08-21 083443.png


As for your complaint about the UI being too complicated—maybe so. That’s exactly why Generation II has completely redesigned the entire UI. I’ve done my best to make it simpler and easier to use, while also giving it more powerful functionality than the current version.

This Generation II, which will be released in September,

  • Contains TWICE the content of the current version —— Sorry, but it really does have this much content, and nothing will be cut.
  • Scene loading time has been cut down to one-third to one-half of the current version —— Yes, technically speaking, both in theory and in practice, scene loading time, performance, and stability have nothing to do with the amount of content.
  • Memory usage has been reduced to one-third, and while delivering fancier visual effects and richer scene elements, it actually lowers the hardware requirements. This means performance in terms of frame rate has improved compared to the current version.
The above is not just my own estimation—Generation II has already been tested over the past month by nearly a hundred testers on my Discord, across a wide range of different hardware setups.

If even that doesn’t satisfy you, I’m sorry—but as an amateur creator, my abilities are limited, and I honestly don’t feel I have the obligation or the energy to produce and maintain a completely free scene according to your ideas.

So my advice is that this scene simply isn’t for you. Just leave it alone, and I encourage you to go ahead and create one based on your own vision.
 
Last edited:
For you—and for anyone else who may still misunderstand this scene from a technical perspective—let me give one final example to explain why scene loading time, performance, and stability have nothing to do with the scale of content:

When you install YouTube on your phone, what you’re installing is just an app. Every time you open the app, you’re not loading the countless trillions of videos on YouTube—you’re simply opening the app, and the app pulls in whichever video you click on through its servers.

Produce 69, whether in the current version or in Generation II, works just like that. When you load the scene, you are not loading any of the content stored in the “database.” Whether there are 10 tracks or 10,000 tracks, they all remain in the repository until you actually click on a specific track to pull it out.

To optimize and improve the loading time, what needs to be optimized is the app itself, not the reduction of content. Generation II is an “app” rebuilt from scratch as an empty scene, with a design architecture and operating mechanism completely different from the current version.

The most important change is that it no longer attempts to preload all environment assets and resources during the initial load. Instead, all resources are now loaded on demand—they are read only when needed, and removed and released from memory when no longer required.

I hope this clears up the doubts in your mind.
 
For you—and for anyone else who may still misunderstand this scene from a technical perspective—let me give one final example to explain why scene loading time, performance, and stability have nothing to do with the scale of content:

When you install YouTube on your phone, what you’re installing is just an app. Every time you open the app, you’re not loading the countless trillions of videos on YouTube—you’re simply opening the app, and the app pulls in whichever video you click on through its servers.

Produce 69, whether in the current version or in Generation II, works just like that. When you load the scene, you are not loading any of the content stored in the “database.” Whether there are 10 tracks or 10,000 tracks, they all remain in the repository until you actually click on a specific track to pull it out.

To optimize and improve the loading time, what needs to be optimized is the app itself, not the reduction of content. Generation II is an “app” rebuilt from scratch as an empty scene, with a design architecture and operating mechanism completely different from the current version.

The most important change is that it no longer attempts to preload all environment assets and resources during the initial load. Instead, all resources are now loaded on demand—they are read only when needed, and removed and released from memory when no longer required.

I hope this clears up the doubts in your mind.
Thank you. No one can surpass you in vam scene production. If there is anything, let’s talk about it later.
 
For you—and for anyone else who may still misunderstand this scene from a technical perspective—let me give one final example to explain why scene loading time, performance, and stability have nothing to do with the scale of content:

When you install YouTube on your phone, what you’re installing is just an app. Every time you open the app, you’re not loading the countless trillions of videos on YouTube—you’re simply opening the app, and the app pulls in whichever video you click on through its servers.

Produce 69, whether in the current version or in Generation II, works just like that. When you load the scene, you are not loading any of the content stored in the “database.” Whether there are 10 tracks or 10,000 tracks, they all remain in the repository until you actually click on a specific track to pull it out.

To optimize and improve the loading time, what needs to be optimized is the app itself, not the reduction of content. Generation II is an “app” rebuilt from scratch as an empty scene, with a design architecture and operating mechanism completely different from the current version.

The most important change is that it no longer attempts to preload all environment assets and resources during the initial load. Instead, all resources are now loaded on demand—they are read only when needed, and removed and released from memory when no longer required.

I hope this clears up the doubts in your mind.
Maybe the complex background environment is the real reason for the slow loading. Maybe you can put 10,000 songs in the scene, but don't design the environment sub-scenes too complicated.
 
Maybe the complex background environment is the real reason for the slow loading. Maybe you can put 10,000 songs in the scene, but don't design the environment sub-scenes too complicated.

Don’t worry—Generation II has a carefully designed on-demand loading system that completes resource loading in a highly efficient chained process, while completely avoiding engine I/O issues to ensure everything is loaded correctly. On top of that, all existing stage environments, along with over 30 newly designed stages in Generation II, have been fully rebuilt at the Blender/Unity level and specifically optimized for VAM.

Some environments that may look very complex—such as the Ancient Egypt stage—are actually made up of a single asset, with a file size of only 30 MB.

Take the mermaid stage in the current version—the underwater environment adds up to roughly 600 MB in file size. After being rebuilt in Generation II, it’s reduced to just 70 MB—without removing any elements or sacrificing visual quality.

The current version has already undergone extensive optimizations to allow VAM to deliver results beyond expectations, but those optimizations were all done within the VAM framework. Generation II, however, starts its optimizations from the polygons of the models themselves.
 
Last edited:
Generation II isn’t all about VAM scene making—it’s actually being developed following the standard workflow of a full game production. While releasing it as is would place no strain at all on mid- to high-end hardware, to ensure compatibility with a broader range of systems, every single resource in Generation II has been systematically rebuilt and optimized from nearly every angle.

And when I say every, I mean it—the number of newly introduced assets in Generation II reaches into the thousands compared to the original.

image.png

For example, even a simple cave model has been pre-split into several objects in advance, based on its intended use in actual VAM scenes, to maximize rendering culling efficiency and reduce the load on the GPU.

image3.png

And to smoothly present a full 1:1 scale model of New York’s Times Square in VAM, it would take several weeks to rebuild and optimize this model of over 6 million polygons.

image2.png

As for how strict the optimizations in Generation II are from the very bottom level—even the ground itself is not spared.
 
Desktop 2025.06.25 - 15.55.30.01.00_02_02_24.Still003.png

That’s why we’re able to present in VAM the breathtaking spectacle of tens of thousands of zebras thundering across the African savanna in a great migration,

1c46c1055705b91bbb0bbb04574f960c (1).png

or even a full-scale battlefield scene with thousands of infantry and cavalry charging and clashing.

If there was a goal in building Generation I, it was to push VAM’s potential as far as possible. Generation II takes that goal a step further—to squeeze out every last drop of capability from the “ancient” 2018 version of the Unity engine it runs on.
 
Last edited:
Back
Top Bottom