#[0.50.04] Takes Several Minutes To Launch
1 messages · Page 1 of 1 (latest)
It is likely the process of regenerating the unit cache, unless you are seeing this issue every time you launch.
Can you describe your hardware setup? CPU, RAM amount, HDD or SSD?
Every time I've tried to launch so far
Reinstalled Java 17 via Adoptium, and the Milestone version is working perfectly fine
AMD Ryzen 7 7800X3D 8-Core Processor
32GB RAM DDR5
2TB M.2 SSD
Windows 11
0.50.03 ran perfectly fine as well, started in seconds
just re-downloaded that version and yep, starts perfectly fine
Using Windows unzipper, or third-party like 7Zip?
Windows unzipper cause I'm a luddite lol
We've had issues with the windows unzipper breaking stuff - it can have problems with the number of files in our zips, and this release is I believe larger than any previously.
I'd guess that, if we enabled debug logging, the megamek.log file would show a bunch of weird failures.
Wait, did you forget to sacrifice an echidna within the circle of 11 black candles?!
OH NO!!!
Glad to help; have fun!
Noo!!!
A catgirl has died due to your lack of sacrifice...
Oh, quick question while I got you here
Does this version still need the extra .ini fixes to avoid fragmenting?
-Dsun.java2d.opengl=true
this line and such
By 'fragmenting' do you mean visual artifacting?
Where the gui starts doing weird visual things?
If so, then yeah, you may need to do those changes (I'll link the guide below). However, you should only do it if you encounter visual artifacts. The issue isn't with our code but how some windows set ups interact with Java Swing.
!visual-artifacta
!visual-artifacts