VRM4U
VRM4U copied to clipboard
ruyo
UE5.0.3 DOESN'T PACKAGE AND PERMANENTLY MAKES A PROJECT UNABLE TO PACKAGE EVEN AFTER PLUGIN IS REMOVED!
Describe the bug Ruyo you literally closed my previous trouble ticket when I mentioned I DID make the project in C++ using Visual Studio 2019 AND IT DIDN'T FIX IT. That's why I mention "Building the project in Visual Studio 2019 didn't fix this issue either." This didn't fix it. Your plugin has a glitch that PERMANENTLY makes projects unable to be packaged even after your plugin has been removed from the project folder.
"I'm unable to package my game in UE5.0.3. I enabled the code from https://github.com/ruyo/VRM4U/releases for UE5.0.3 into the project folder instead of the engine folder. It worked fine. I then after closing the project overwrote that code with the source from https://github.com/ruyo/UnrealEngine_VRM4UPlugin. Then I opened the project disabled the plugin, restarted, then enabled it again, and restarted. The plugin worked fine except when I try to package it. I've narrowed it down it IS the plugin causing my game not to package when I did these steps with a brand new project that packaged fine right before I enabled the plugin. There is no models or anything else in the project for the Third person character project. It gives in red a "UATHelper: Packaging (Windows): ERROR: Cook failed." and "PackagingResults: Error: Cook failed." Building the project in Visual Studio 2019 didn't fix this issue either. Even just existing inside the Project file causes it to get the "PackagingResults: Error: Cook failed.". I had it in the project file in a new folder called Plugins and I also tried deleting the "latest" folder to try to fix this. The plugin even after removed permanently makes the project unable to package."
Screenshots, log In Yellow: UATHelper: Packaging (Windows): WARNING: Warning: Plugin 'VRM4U' does not list plugin 'IKRig' as a dependency, but module 'VRM4U' depends on 'IKRig'. UATHelper: Packaging (Windows): WARNING: Warning: Plugin 'VRM4U' does not list plugin 'IKRig' as a dependency, but module 'VRM4ULoader' depends on 'IKRig'. PackagingResults: Warning: Warning: Plugin 'VRM4U' does not list plugin 'IKRig' as a dependency, but module 'VRM4U' depends on 'IKRig'. PackagingResults: Warning: Warning: Plugin 'VRM4U' does not list plugin 'IKRig' as a dependency, but module 'VRM4ULoader' depends on 'IKRig'.
In Red: UATHelper: Packaging (Windows): ERROR: Cook failed. PackagingResults: Error: Cook failed.
UnrealEngine Version: UE5.0.3
These are the steps I took, but I made this for UE4 so there are slight differences like where to go to package your project. VRM4U Packaging File.pdf
Did you regenerate the solution file correctly? If you rebuild after that, it should work correctly. If it still does not work, delete the intermediate file and try again. This is a UE specification. It is not a bug in the plugin.
#227 The same applies when installing plugins.
Did you regenerate the solution file correctly? If you rebuild after that, it should work correctly. If it still does not work, delete the intermediate file and try again. This is a UE specification. It is not a bug in the plugin.
#227 The same applies when installing plugins.
I don’t know what you mean by regenerate the solution file correctly. I sent you a PDF going over the exact steps I did with slight changes due to it being UE5.0.3 because of the location where to package it. Was there anything you can see in that which could cause this issue? Currently anything this plugin touches permanently causes it to get the cook error and not be able to package it. I tried it on a brand new project with nothing else activated or imported except the plugin. Even after deleting the plugin from the project folder the error remained and a brand new project packaged no problem before I activated the plugin. So I know IT IS the plugin causing the issues. Even when I migrate assets to a new project that has never had this plugin I can see when it packages it, it references assets imported from the plugin (my models that were in the previous project but not that one) when they are not in the project causing it to get the same error. So it permanently messed up some of my assets that were ever in a project that had this plugin too.
UPDATE: So it looks like the assets that don’t rely on this plugin inside of the project are able to package once sent to a project that never had this plugin but I had to remove any possible thing that could reference the plugin and I converted the project to UE5.1.