-
fn main() {
App::new()
.add_plugins(DefaultPlugins)
.run();
} This is the result of building and running with This is the content of the binary file. When using MinimalPlugins, .log files are not generated. It seems that .log files are generated by RenderPlugin, but I'm not certain. This is my system information: SystemInfo { os: "Windows 11 Pro", kernel: "22631", cpu: "13th Gen Intel(R) Core(TM) i9-13900KF", core_count: "24", memory: "63.8 GiB" } |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
I don't think this is related to Bevy, since Bevy is unable to log to file at moment. See #5342. I'm also using Windows 11 and never got this log. This maybe be generated by the IDE you are using (if Visual Studio) or you have some build system which does this. |
Beta Was this translation helpful? Give feedback.
-
Latest discovery: Running in Windows Sandbox does not produce a .log file. Additionally, running binaries built by others on my physical machine does generate a .log file. Therefore, it can be concluded that it is related to my hardware (as the Windows system has been freshly reinstalled). Another confirmed point is that the .log file is generated by the Bevy RenderPlugin, but only under specific circumstances. So, what could be the reason for this? (This image displays the test results of a Bevy game binary compiled by someone else, running on my computer, sourced from: https://github.com/Dreamtowards/Ethertum) |
Beta Was this translation helpful? Give feedback.
-
The .log file is unexpectedly in binary format, so I am unable to extract information from it. (I am frustrated.) I have uploaded the file. Is there anyone who can understand it? ethertia.20240204-015603-320.log |
Beta Was this translation helpful? Give feedback.
-
Uninstall WeGame and delete all its files can solve it. Edit: The reason seems to be because of a fake verification layer provided by WeGame, which is in WeGame's |
Beta Was this translation helpful? Give feedback.
Uninstall WeGame and delete all its files can solve it.
Edit: The reason seems to be because of a fake verification layer provided by WeGame, which is in WeGame's
CrossVulkanLayer64.dll
and Vulkan loads it when your program starts.