Open valiant-code opened 1 year ago
Sorry for the delay; finally took a look at this one, and it seems to work fine for me? This is the version of Java I'm using:
openjdk 11.0.17 2022-10-18 LTS
OpenJDK Runtime Environment Zulu11.60+19-CA (build 11.0.17+8-LTS)
OpenJDK 64-Bit Server VM Zulu11.60+19-CA (build 11.0.17+8-LTS, mixed mode)
And my OS:
I'm using Pokemon Blue (U), and my batch randomization settings are like so:
I tried launching the randomizer using the launcher, by double-clicking on the JAR, and by using java -jar PokeRandoZX.jar
from the Terminal, and in all three cases, batch randomization worked fine.
Since you didn't say which ROM you used in the original post, can you try with Pokemon Blue (U) and see if it works? I want to narrow this down as much as possible.
I just updated my Mac to Ventura, and it worked just fine. So we can cross that off as a potential source of problems.
@tom-overton I was attempting it with Fire Red (revision 1). I'll see if I can try Blue in the next couple of days
having the same problem as @valiant-code with FireRed, I can try with Blue to see if the issue is FRLG-specific. OS is Ventura 13.0
@tom-overton i have the same issue as above, running macOS 14.0 on FireRed
Same issue here.
OS: macOS 14.2.1 (Apple M1 Air)
Java:
openjdk 21.0.2 2024-01-16
OpenJDK Runtime Environment Homebrew (build 21.0.2)
OpenJDK 64-Bit Server VM Homebrew (build 21.0.2, mixed mode, sharing)
Tried it on Pokemon Emerald
Also having this issue when trying to batch randomize FireRed.
OS: macOS 15.1 (Apple M1 MacBook Air)
Java:
java version "1.8.0_421" Java(TM) SE Runtime Environment (build 1.8.0_421-b09) Java HotSpot(TM) 64-Bit Server VM (build 25.421-b09, mixed mode)
Attempted to open up permissions via chmod, run as root, and grant 'Full Disk Access' via 'Privacy & Security' settings, but no luck.
Describe the bug When I enable batch randomization and generate seeds, the program acts like it is generating the seeds successfuly, but when I check the output location there is nothing there. I have tried several different output locations
To Reproduce Steps to reproduce the behavior:
If "Generate log files" is enabled in the batch randomization settings, a "Could not save log file" pop up appears for each seed made in the batch.
Expected behavior The files should save to the output directory correctly
Screenshots
System (please complete the following information):
Additional context If I disable batch mode I am able to save a seed successfully.