Packaging error with Victory Plugin

An empty project is not packaged, if enabled Victory Plugin. Packaging crashed.

MainFrameActions: Packaging (Windows (32-bit)): Project.Build: ********** BUILD COMMAND STARTED **********
MainFrameActions: Packaging (Windows (32-bit)): BuildCommand.Execute: ERROR: BUILD FAILED

MainFrameActions: Packaging (Windows (32-bit)): Program.Main: ERROR: AutomationTool terminated with exception:
MainFrameActions: Packaging (Windows (32-bit)): Program.Main: ERROR: Exception in AutomationUtils.Automation: You are attempting to compile on a machine that does not have a supported compiler!

MainFrameActions: Packaging (Windows (32-bit)): Stacktrace: в AutomationTool.UE4Build.Build(BuildAgenda Agenda, Nullable1 InDeleteBuildProducts, Boolean InUpdateVersionFiles, Boolean InForceNoXGE, Boolean InUseParallelExecutor, Boolean InForceNonUnity, Boolean InForceUnity, Boolean InShowProgress, Dictionary2 PlatformEnvVars)
MainFrameActions: Packaging (Windows (32-bit)): в Project.Build(BuildCommand Command, ProjectParams Params, Int32 WorkingCL)
MainFrameActions: Packaging (Windows (32-bit)): в BuildCookRun.DoBuildCookRun(ProjectParams Params)
MainFrameActions: Packaging (Windows (32-bit)): в BuildCommand.Execute()
MainFrameActions: Packaging (Windows (32-bit)): в AutomationTool.Automation.Execute(List1 CommandsToExecute, CaselessDictionary1 Commands)
MainFrameActions: Packaging (Windows (32-bit)): в AutomationTool.Automation.Process(String[] CommandLine)
MainFrameActions: Packaging (Windows (32-bit)): в AutomationTool.Program.MainProc(Object Param)
MainFrameActions: Packaging (Windows (32-bit)): в AutomationTool.InternalUtils.RunSingleInstance(Action`1 Main, Object Param)
MainFrameActions: Packaging (Windows (32-bit)): в AutomationTool.Program.Main()
MainFrameActions: Packaging (Windows (32-bit)): ProcessManager.KillAll: Trying to kill 0 spawned processes.
MainFrameActions: Packaging (Windows (32-bit)): Program.Main: AutomationTool exiting with ExitCode=Error_Unknown
MainFrameActions: Packaging (Windows (32-bit)): Domain_ProcessExit
MainFrameActions: Packaging (Windows (32-bit)): copying UAT log files…
MainFrameActions: Packaging (Windows (32-bit)): RunUAT.bat ERROR: AutomationTool was unable to run successfully.
MainFrameActions: Packaging (Windows (32-bit)): BUILD FAILED
PackagingResults:Error: Error Unknown Error

Hello Anilarion,

On Ranma’s plugin page he states: " If you want to package my plugin for Win32 Shipping or Win64 Development you can merge these binaries with the main plugin installation above!" Have you merged the two binaries? This may be causing the issue.

Hello ,
I merged binaries, but it is compiled in any format as Win32 Development or Win64 Shipping. This problem appeared in UE 4.10. In 4.9 it is well. UE4.10 doesn’t work with VS 2013, and work with VS2015. But VS2015 doesn’t work with Victory Plugin. I’m confused.

The plugin was written by Ranma. If there is an issue with the plugin not working with VS2015 I would suggest contacting him directly and bringing this to his attention. In the meantime you may try staying in 4.9 where you are able to package your game.

Unfortunately, a huge patch was made in 4.10. Is there a way to rollback the version of the project?

Anilarion,

Unfortunately, there is not a way to rollback your version of the engine for your project. It’s suggested that when you upgrade your version of the engine, that you create a copy of the project just in case anything goes wrong. If you feel that it’s not necessarily the plugin that’s causing an issue, feel free to upload the full error logs from your project as a .txt file so I can look over the full picture.

If there happens to be something going on with the plugin, please contact , who is the creator of the plugin.

Thank you!

Hey Anilarion,

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will offer further assistance.

Thank you!

262794-victory.png

how to fix!