Atomic crashes when attempting to port mod to MacOS
Closed this issue · 11 comments
When attempting to port a Windows mod to MacOS, Atomic will crash with no explanation of what issue occurred.
The expected behavior was, of course, for Atomic to create the modded .zip package for MacOS without any issues.
Steps to reproduce the behavior:
- Fill out any needed fields.
- Load the AM2R 1.1 .zip and your modded windows AM2R .zip.
- Click the "create mod packages button" and wait.
- Atomic will crash.
- OS: Windows 10 Home 22H2
- Atomic Version: 2.1.0
Additional Context:
Will try to redo the mod to see if there are any formatting issues.
In your reproduction steps, you didn't specify that you loaded the modded mac .zip. Was that accidental, or intentional?
Also gonna be trying something soon, so I can see stacktraces when Atomic crashes.
Ah, apologies. Yes, load the mac zip as well. I am not sure how I fixed it, I remember changing 2 things. I replaced the splash images with ones exactly like the templates as far as resolution/aspect ratio goes (compared to ones with I think a 16:9 ratio in place of a 4:3) and I recreated the raw mod zip. Not sure which fixed it, but it's either error on my part in making the zip or Atomic has issues with packages created with custom splashart.
I added a way to show a crash message should the application crash. Can you download the dev releases from here and try to repro the crash?
Did you reproduce the crash with the dev Atomic releases? Or with the same release you used before?
No, I used the dev release like you asked me to.
Was there any error message when it crashed? Something should have been displayed there.
It never crashed, that's the thing. It usually hangs for a minute or two while not responding and then jumps to asking what to save the file name as.
I can't remember if it's just like that for Mac or also for win/linux
Oh I misread, my bad. All right, i'll see later if i can reproduce it by including a profile.xml
This was unable to get reproduced.
If you happen to encounter this again, please reopen the issue!