The upcoming Produce 69 II, set to release in September, will have native support for VR and XR.Any word on the update for VR?
我的机器配置是Win11、9950Ⅹ3D、MSI 5090、64G RAM,4tb M2 SSD,VAM是1.22.07(1.22.03也试了),玩其它游戏没问题,其它VAM的绝大部分人物和场景也没问题你的显卡是什么呢?
我看出来了。模型和特效上面有红色光圈和黄色光圈。是不是显卡的问题呢?
问题解决,是NVIDIA控制面板里面的设置问题,其中“管理3D设置”里面的“各向异性过滤”要选“应用程序控制的”,这样画面和颜色就恢复正常了你的显卡是什么呢?
我看出来了。模型和特效上面有红色光圈和黄色光圈。是不是显卡的问题呢?
是否有考虑风格化分开,比如古风系列,主要文件太大,加载太久。即将于 9 月发布的《Produce 69 II》将原生支持 VR 和 XR。
你第一次进入这个场景后,在歌曲界面,任选一首歌,然后,保存这个场景。是否有考虑风格化分开,比如古风系列,主要文件太大,加载太久。
Again, technical support for the current version has already been discontinued, and there will be no further maintenance or updates.是否有考虑风格化分开,比如古风系列,主要文件太大,加载太久。
That sounds exciting.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.
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.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?
Okay... Thank you for your reply. 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.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.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.
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.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?
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.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.