All Jobs Damage Simulator And Gear Sets

Yes, but we need to know pet stats and blood pact WSC (and FTP?). I don't think any of these are well-known at the moment.


This is a known issue with the search algorithm being stuck in a local minimum due to its initial gear choice.

In your case, you've limited the gear options the code can use while also included reasonably high accuracy and DT requirements. The code randomly equipped Null Loop early in its search, which satisfied a large chunk of required accuracy and a large chunk of required DT at the same time. The later part of the algorithm failed to find a pair of two items together that satisfy both high accuracy and high DT that could replace Null Loop from the list of selected items. The second time you ran the algorithm, it did not find Null Loop early, so it did not trap itself in the slightly worse set. Switching to another algorithm might fix this issue, but could also make it more frequent or significantly increase runtime. Simulated annealing has been recommended previously and I planned to implement a version of this later after I finished the GUI rewrite.


The application ignoring user interaction is a new issue that appears to be related to the GUI being overloaded on the number of widgets it uses and how/where it displays/updates these widgets. I can somewhat reliably reproduce this issue by rapidly switching jobs while clicking a few other widgets. I've tried a few stackoverflow fixes, but nothing has worked yet. My only suggestion for now is to simply reload the GUI if this happens. Part2 of the GUI update is to virtualize the gear selection widgets, which will reduce the number of gear widgets from ~5000 to ~100 and would fix this issue if that's the cause. At the very least, virtualizing the selections will significantly speed up the load time and likely reduce memory usage. I planned to work on this in January.

The GUI scaling cutting off text/widgets is almost certainly an issue with Windows11 scaling the widgets/font differently than Windows10. However, I do not recall changing anything about the font or GUI styling in this rewrite. The updated GUI does have a slightly smaller window size, so I wonder if the older version coincidentally was fine because it was larger and could fully display the automatically resized widgets. Could you post/PM a screenshot of how the September version of the GUI looks for you? I want to see if it looks different that what I see. Maybe I can find a way to force DPI scaling to match my Windows10 version for Windows11 computers, or I may have to go back to slightly larger window size.

Downgrading to the 2025 September version of the application is probably the only option for the scaling issues for now. Fortunately, you'll only be missing a few convenience features as I try to resolve the issue.

Yeah, I've had some scaling issues through several of this year's versions, but it was never stopping me from using it, so I didn't bring it up. About six months ago I lost access to the food section, but that wasn't a big deal.

I rerolled back to September and it's still a bit off, but at least can be used for the time being. I have tried closing the program and opening it again several times, along with changing my screen resolution, but nothing changes. Making it full screen helps a little (was unable to select Twashtar R15 from the gear menu without doing so).

Edit: Screenshots of September.

Included normal and fullscreen mode of the first screen, along with a look at the Optimize screen. I can still get to the Nyame box, but only just.

1

2

3

Thanks. That looks horrible.

I'll look into explicitly providing font size, widget size, and application DPI settings to see if this can be avoided after the holidays.

Yeah, I've just been working around it lol. Super appreciate that this exists, so I stuck with it.

December is way more broken than this. I can't even describe what is going on there. Things got super weird.

I have Windows 11 and I have 0 problems with both exe and running .py Everything looks perfect, including December version.

Ok I lied everything looks perfect, but not everything works perfect in December update. When I click on Aftermath selection window is popping in left upper corner of my screen instead of in the application window. Also I cant edit SoA and TVR rings in the Optimize tab. It fixed when I rerunned the code though.

Ok December update is glitchy. After using for several minutes some thing are breaking, but its always good after relaunching. I was using September version for several months a lot and haven't got a single bug.

Is it possible to add a drop down box containing Magic Defense bonus + 25/30/35/40/45/50 & Magic Evasion 500/550/600/650/700/750?

Some end game content: Odyssey v25, Sortie Basement Bosses/Aminon, new Omega/Ultima, etc. require higher defensive stats. This update could prove useful.

I am not a programmer and have no clue how hard it would be to add something like this. Appreciate the consideration.

I usually simply reduce available gear to only high meva pieces. I will probably just permanently throw out stuff like Tatenashi, Semnuha, mummu and others and I will leave stuff I consider I would have no problem using in high level content, but adding minimum meva and mdb to optimizer would be great too :)

This is exactly the issue I'm seeing, including drop down options and entire buttons showing up on the top left of the screen (out of the GUI window entirely). I believe it's related to the application storing 1 checkbox and 3 radio buttons for every piece of gear in the gear.py file (~5000 total) and occasionally struggling to rebuild/replace everything when a job change occurs. I should be able to rewrite/revert to the behavior I used in the previous versions, but I want to try virtualization first since it would also solve other annoying problems.

Good to know it can work normally on Windows 11. I assume that none of the text or widgets fall off screen or overlap, but I haven't set up a virtual machine to test this myself. Maybe it is just a DPI scaling issue for users with custom OS settings. I'll still look into forcing a DPI for the application and ignoring the user's OS value if possible.



In terms of automatically finding a set with DT, meva, and mdef requirements: I do not think this is feasible with the current algorithm only swapping two slots at once. These two slots enable two constraints, which are technically taken by PDT and MDT.

I can easily add an entry to allow the user to specify a "minimum magic evasion per gear" so the "select all" buttons ignore head/body/hands/legs/feet armor with magic evasion below that value, such as Adhemar hands (43 meva) vs Malignance hands (112 meva). This value is probably different by job and slot and would need to be fine tuned for things like Mpaca hands (59 meva, but high mdef), but having this option would still be better than manually unselecting out of date equipment each time.

Interestingly, directly removing enough of this equipment from your gear.py file might solve the issue with the GUI breaking since you'd be reducing the number of checkboxes/radio buttons that need to be built.

I was having the GUI issue on an older build of the program after adding the new gear. Tried the newest version without my gear changes and it was fine, brought back in my gear.py file and it broke again.
Removing a whole load of gear from the gear.py file did indeed return functionality.