patchus maximus

[urumizawa]

the last time I installed perkus maximus (with NMM) i had around 150 mod and it took only 30 mins
after trying some other perk overhauls i reached the conclusion that PerMa is the most balanced one for me... again i have to run patchus maximus (with mod organizer this time as i am using it now)
MO does not support 64bit? okay! so i ran the .jar file and oh god it has already been 2 hours since patchus started his "Task: scroll and staff creation" and I am running only about 70 mods
is it related to the Perma update? is it some kind of incompatibility with one of my mods? or is it related to Mod Organizer?
PS: the game was installed yesterday according to my profile? yes but i had it installed 2 years ago though i didnt play for more than a year. I bought it to show my support! don't ask about the old game

anyway thanks alot for your answers in advance and never mind the side note

[Nazenn]

Mostly its MO.
MO is a 32 bit program and as such doesnt have as much memory to draw on so patchers etc take a fair bit longer.
However, mine only took an hour (in MO) with 200+ mods so it might be that a particular mod is causing a problem, has a large amount of data, or that its just being slow on this first run because of having new mods to process.

[urumizawa]

half of them are texture mods and most of the others if not all are the famous essential mods
i'll let it run for another hour to see
oww... i also changed the skyrim audio bsa with the japanese ones (but i don't think it has anything to do with PerMa)

[Nazenn]

Perma runs on the esps, bsas shouldnt matter so far as I know.
If you think its a major issue get your specs, load order, and time the patcher took to run and submit it to the team for review

[urumizawa]

i ll do that while patchus is working
should i post them here or make a separate post?

[Nazenn]

The PerMa team isnt likely to see it here.

[urumizawa]

i see i ll post in their nexus page then
thanks for the answer

[la_nague]

you are doing something wrong, my patch is done after 5 mins and i have like 10gb of mods.



idk what MO has to do with anything, just run PM with more heapspace option

[Nazenn]

Originally posted by la_nague:

you are doing something wrong, my patch is done after 5 mins and i have like 10gb of mods.

idk what MO has to do with anything, just run PM with more heapspace option

And you are unhelpful.
All you do is run the patcher, or bat file in this case, you really cant go wrong with that. the patcher doesnt care about file size, for all we know those 10 gbs of mods you mentioned are all texture mods, it cares about data. AIf you have 10gbs or esps, I doubt your game would run, and I can garentee that the patcher wouldnt finish in five minutes because it would take more then five minutes to read the data, let alone patch it together.

And if you dont know MO, dont comment. You cant just run the more heapspace one with MO because its not supported.

[urumizawa]

Originally posted by la_nague:

idk what MO has to do with anything, just run PM with more heapspace option

once you start managing your mods with MO you can't do anything without it as it doesn't keep anything in the data folder


edit and since i posted i ll profit to ask another question
does unlocking MO while patchus is running change anything? i hope it doesn't because i already unlocked it

[la_nague]

well then thats the problem, you run out of space and trigger lots of pageswaps

also check java version, PM needs the newest one to run properly.

[Nazenn]

Originally posted by la_nague:

well then thats the problem, you run out of space and trigger lots of pageswaps

also check java version, PM needs the newest one to run properly.

No, there is a specific MO bat file to run, and because of the way skyproc is written it just throws off an error if it does run out of space. Like I said, if you dont actually know the system, please dont comment because youre not helping

[la_nague]

i am very helpful, i allready said to check the java version, more than you helped, NAZEEM.

[urumizawa]

i ran it from the java file actually because as i said and as you just said it throws an error if it runs out of space
my system is 64bit and since i didn't know weather running a 32bit file on a 32bit program installed in a 64bit system would work or not i chose the safest option (what i thought would be the safest) by running the jar file (and yes java it is updated)

[Nazenn]

Originally posted by urumizawa:

i ran it from the java file actually because as i said and as you just said it throws an error if it runs out of space
my system is 64bit and since i didn't know weather running a 32bit file on a 32bit program installed in a 64bit system would work or not i chose the safest option (what i thought would be the safest) by running the jar file (and yes it is updated)

Precisely, which I had figured out from the fact that he said he had run it previously and java hasnt had a major update (one that would stop old versions from functioning with skyproc patchers) since PerMa was released.


If you feel like you want to redo it or it is properly bugged, cancel it and try the MO bat file and it may help, but if its not throwing off an error about running out of memory it may just be a bug in the system as occasionally happens with skyproc patchers just due to their code data base, and you can also try deleting the old patch esp, and the files that should be written into the overwrite folder of MO in a skyproc patchers folder (should be on there for patchus maximus), and deleting that should help remove any traces of the patcher previously which should make it run as if it was being run for the first time which should help it too.

[urumizawa]

thats exactly what i am going to do!
in addition i just noticed while copying the loadorder list that i actually forgot to uncheck SPERG....
pretty dumb -_-

edit: lol i think steam mistook what i said for something else
i said S-P-E-R-G