Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A problem about DefaultEngine.ini will be written repeatedly. #195

Open
gouchouyang opened this issue Dec 27, 2023 · 5 comments
Open

A problem about DefaultEngine.ini will be written repeatedly. #195

gouchouyang opened this issue Dec 27, 2023 · 5 comments

Comments

@gouchouyang
Copy link

gouchouyang commented Dec 27, 2023

Hello NoelCross
We recently encountered a little problem in the UE5.3 project.

  1. During Acoustics multi-thread baking, DefaultEngine.ini will be written repeatedly.
  2. When using two or more independent process games, DefaultEngine.ini will be written repeatedly, resulting in data loss.
    What usually causes this situation? Have you encountered similar problems before?
@gouchouyang
Copy link
Author

POPO-20231227-160535
In order to allow the program to run normally, we have temporarily blocked some of the Acoustics code, as shown in the figure

@KyleStorck
Copy link
Contributor

Can you clarify what you mean by "using two or more independent process games"? Do you mean having 2 UE editors open at once?

@gouchouyang
Copy link
Author

Can you clarify what you mean by "using two or more independent process games"? Do you mean having 2 UE editors open at once?
Hello KyleStorck, “using two or more independent process games” means when running the process, select "Standalone Game" and "Number of Player ≥2"
POPO-20240102-110353

@KyleStorck
Copy link
Contributor

Thanks for the bug report. We'll investigate this. I tried to replicate your scenario but I haven't seen PostInitProperties get called at game time. Our understanding was PostInitProperties is only called at editor startup. Can you provide any more insight?

@gouchouyang
Copy link
Author

Thanks for your reply. We will check internally first to clarify the details of the problem before asking you for further advice~! ❤

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants