-
Notifications
You must be signed in to change notification settings - Fork 2
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
Make an analyses of resource consumption by different used mods #9
Comments
As I wrote to @milivojm already, this should be probably automated via This means creating a set of consistent testing missions, some of which rigorously focus on graphical performance (where AI have Another mission would then be more relaxed and let AI do their thing (to test LAMBS, etc.), another mission would give random loadout (like Arsenal has a RANDOM button) to all AI in the first/second mission to see if there are performance issues using some weapons/gear. Or maybe not random, but specifically only weapons/gear from each mod ( And so on ... Then we could run |
Moving to ideas repo. |
I agree with @freghar here, this needs to be automated and benchmarked so we can run it for every new mod we want to put into modset. Freghar mentioned YAAB mission (https://steamcommunity.com/sharedfiles/filedetails/?id=375092418) as a good starting point. |
This needs it's own repository. WIP mission 1 - https://gist.github.com/milivojm/b01137c9d23f4b644d3792ad0ef1d242 |
We're using many mods and usually just look at them just by looking at the size on the disk. We should take a look also on runtime footprint of the mod (RAM, background scripts, impact on other mods, Cfg) etc.
The text was updated successfully, but these errors were encountered: