[September 3, 2023]Abyss Patcher

[Drakelegion]

I am as well, and it works fine for me, though this obviously doesn't help you other than to let you know that it's indeed possible to work with Windows 10 Pro.  Where I'd start is remove all mods of any sort.  Use Power Patcher to revert back to at least v216/217.  The reason for this is so that it forces an update and pulls any relevant files that you need.  Make sure you have the appropriate libraries for your C++ stuff.  This is imperative in order for Mabinogi to work correctly.  Usually, The simplest solution is the right one.  So far it appears that your client has issues, because... Abyss relies on the client having all that it needs to run correctly.  This includes dlls, exes, security... packs... the whole ball of wax. 

Please disregard the fact that it worked at x time or x date.  This isn't relevant.  Somewhere your files were affected.  If you get hung up on the fact that it worked at x time and x date, then the solution will repeatedly evade you.  It's because you're overlooking what it isn't instead of what it is that you currently have.  So PowerPatcher... This is the key.  Please see the thread on it and learn what you can about it.  Once you've eliminated Abyss and ANY other mods that you use... run the client clean and see what it does--how it behaves.  After this...  If things have went well you can add things back in one by one--starting with the latest Abyss.  If you've done all you can (and if it still doesn't work), then you can probably reach out for help provided if you're open to it.  Bear in mind anyone that chooses to help you will most likely repeat a lot of the same steps that you already may have done.  This is to be thorough.  I've fixed many clients and the issues were almost always the same.  Best of luck.

I used power patcher to try to fix a problem before, it had no luck. I redownloaded mabinogi on the 7th(7 days ago), and the new version of abyss did not work at that point in time, causing the errors I stated. I re-installed the just prior to that version of abyss, and now it works fine.

Its not about it worked X long ago. The newest version of abyss doesn't work, the one prior to it continues to work as well as it used to.

I hope that clarifies where I am at enough that we can move on to things I have not tried.

[Lady Playtime]

I used power patcher to try to fix a problem before, it had no luck. I redownloaded mabinogi on the 7th(7 days ago), and the new version of abyss did not work at that point in time, causing the errors I stated. I re-installed the just prior to that version of abyss, and now it works fine.

Its not about it worked X long ago. The newest version of abyss doesn't work, the one prior to it continues to work as well as it used to.

I hope that clarifies where I am at enough that we can move on to things I have not tried.

Just because you've done something,  doesnt mean you've done it right.  Since I'm also on Windows 10 pro and it works fine.

And for giggles. This is what changed:
Update Log:
Spoiler (click to show/hide)
January 8, 2016: Added AlwaysCollectMode (Rydian), FastNPCText (Step29) and UncapAutoProduction (Rydian). Fixed RightClickSelf and ViewNPCEquipment. Removed broken and outdated patches to ease confusion and redundant questions. Removed CrackShield due to the removal of HackShield.
June 29, 2015: Added CutsceneSkip and new options and fixes for WindowPosition.
June 6, 2015: Added Sync command.
May 31, 2015: Fixed Scooter/Wisp problems and Zoom.
May 20, 2015: Updated CrackShield with help from Step29.

[Blade3575]

Huh.. I forgot to mention I fixed option 3 of WindowPosition as well. I believe someone ended up having some kind of problem with it not showing the window, but still playing the music. If you're using that, with option 1 enable, try changing it or disabling it.

[slipslide]

Well, I've followed all of the above advice since my post on the previous page.
If I run the game with no mods, it runs perfectly (except if I hit a cutscene, then I jam)
If I run it with the previous version of Abyss added in, it runs perfectly.
If I run it with the new version of Abyss added in, it takes forever to launch, and then stutters every quarter second and is unplayable.

Yes, I cleaned up all old files.  Heck, I even made a second Mabinogi installation to work with to make sure.  The only modification I'm using IS Abyss.  There's a bug somewhere in the new coding, so I can't try out the new features.  As long as the old one still works, I'm not too worried.

I'm running Windows 10 Home, btw.  Not Pro. 

[slipslide]

I'm stuck on the white screen before the log in screen with just Abyss. I went back to old version, and I'm having the same problem. Anyone else having the same issue?

That did happen to me at one point; going back to the old version fixed it, though.  Make sure to go back to the old .dll and the old .ini file.
If you sit on that white screen long enough (for me), the game does come up... and stutters every quarter second.  You can hear the theme song stuttering along...

[Draconis.Pendragon]

I used power patcher to try to fix a problem before, it had no luck. I redownloaded mabinogi on the 7th(7 days ago), and the new version of abyss did not work at that point in time, causing the errors I stated. I re-installed the just prior to that version of abyss, and now it works fine.

Its not about it worked X long ago. The newest version of abyss doesn't work, the one prior to it continues to work as well as it used to.

I hope that clarifies where I am at enough that we can move on to things I have not tried.

ALL programs related to Mabinogi including Mabinogi itself has to be run in Admin mode.  This is so that the programs can have the necessary permissions in order to work.  Often times this is presumed that people are doing that without saying it.  However, this is one of the things that must take place.  This means, if you have run PowerPatcher even once, without Admin mode, then you probably hosed your files.  New install or not.  Playtime put it best.  When I responded it was to pro-actively head off any needless discussion that happens when people post and vent about something not working.  This is why I said what I did in the manner that I did in efforts to save time and energy.  The only thing left now is for someone that has a lot more experience to take a look at the situation.  In other words, fix it via TeamViewer.  or... you can keep muddling along, this is your choice of course.  You came here asking for help and we've offered suggestions and know beyond the shadow of a doubt that Abyss does indeed work under the right conditions.  Put simply, what this means is your PC doesn't have the right conditions in order for it to run correctly.  You answer this yourself when you post--it's glaringly obvious.  Posting and arguing with people that are trying to help you won't grant you the help you need nor any favors.  How you choose to respond next will determine what happens next.   Bear in mind I fix people's PCs all the time as do many others that are here have as well.  Out of respect to all here, and especially to the person that decides to fix your PC.... Once it's fixed, please avoid messing it up again.  Savvy?

[Draconis.Pendragon]

Well, I've followed all of the above advice since my post on the previous page.
If I run the game with no mods, it runs perfectly (except if I hit a cutscene, then I jam)
If I run it with the previous version of Abyss added in, it runs perfectly.
If I run it with the new version of Abyss added in, it takes forever to launch, and then stutters every quarter second and is unplayable.

Yes, I cleaned up all old files.  Heck, I even made a second Mabinogi installation to work with to make sure.  The only modification I'm using IS Abyss.  There's a bug somewhere in the new coding, so I can't try out the new features.  As long as the old one still works, I'm not too worried.

I'm running Windows 10 Home, btw.  Not Pro.

Turn cutscenes off for Abyss.ini and see where that gets you...  As far as the rest... Well, a file perusal is in order.

[Drakelegion]

[cluttersnip] Out of respect to all here, and especially to the person that decides to fix your PC.... Once it's fixed, please avoid messing it up again.  Savvy?

Alrighty then, my version of win10, like most others, is upgraded from win 7, I am running an 8-Core, 3.4GHz, 64-bit processor. I have 8 GB of RAM on one stick with room for more(in case that has a chance of mattering), and an nVidia GeForce 750 Ti Graphics card from EVGA. My HDD is 3TB, and I access the last TB of it using some drive powertool that came with my MSI motherboard.

If I missed any information you need to know in order to help me, please let me know. I am a tech guy, but am not very familiar with the ins and outs of modding mabi, only how to implement what is on the forums(read instructions and follow them).

I apologize for getting snippy, I am not used to having things not work right the first time, and being babied must have set me off.

[Draconis.Pendragon]

Alrighty then, my version of win10, like most others, is upgraded from win 7, I am running an 8-Core, 3.4GHz, 64-bit processor. I have 8 GB of RAM on one stick with room for more(in case that has a chance of mattering), and an nVidia GeForce 750 Ti Graphics card from EVGA. My HDD is 3TB, and I access the last TB of it using some drive powertool that came with my MSI motherboard.

If I missed any information you need to know in order to help me, please let me know. I am a tech guy, but am not very familiar with the ins and outs of modding mabi, only how to implement what is on the forums(read instructions and follow them).

I apologize for getting snippy, I am not used to having things not work right the first time, and being babied must have set me off.

For what it's worth.  I'd apologize, but it was never my intent to baby anyone.  It's not my style tbh... So, I must say that I've nothing to apologize for at this time (not to sound like an arrogant _ss).  That doesn't mean I won't make mistakes in the future or need to apologize later... >_> How a person chooses to interpret what one does or says is entirely up to them.  I've had this happen a lot lately...  I've made a lot of mistakes while modding, and this has taught me a LOT.  I seem to learn more when I make mistakes than when I do from "doing it right."  The experience comes with time... I just one day decided to pick it up and start teaching myself.  What Blade does here is amazing, and is probably the only area that I don't know much about, but I get the gist of how it works, just not the internal workings.

If you wish for me to take a look, I can. 
If so, then PM me the needed info for TeamViewer- User ID and PW. 
I'll be sending you a PM shortly. Then going afk for a few.

[slipslide]

Turn cutscenes off for Abyss.ini and see where that gets you...  As far as the rest... Well, a file perusal is in order.

Nope.  Doesn't matter if I disable EVERYTHING on Abyss!  As long as I'm using the new Abyss .ini and .dll files, it's a stutter-load failure.  As soon as I either switch back to the Mabinogi ijl15.dll file or the one from the previous Abyss version, everything's perfect.

The fault is the new ijl15.dll file, or how the new abyss.ini calls the functions from it. I can say that with 100 percent certainty.

[Draconis.Pendragon]

Nope.  Doesn't matter if I disable EVERYTHING on Abyss!  As long as I'm using the new Abyss .ini and .dll files, it's a stutter-load failure.  As soon as I either switch back to the Mabinogi ijl15.dll file or the one from the previous Abyss version, everything's perfect.

The fault is the new ijl15.dll file, or how the new abyss.ini calls the functions from it. I can say that with 100 percent certainty.

Your dlls are messed up.  Run PowerPatcher in Admin mode to retrieve from v216 onwards after you revert.  In rare cases you may need to revert to the original install version of your client.

*Addendum*
Remove Abyss first before doing this then, proceed.  The idea here is simple, PP will pull the latest files, and once you have the latest dll, then back it up.  You can use the dat/dll that Abyss uses or the one that Mabi uses and rename that to dat (after backing it up).  Both ways work, I've done this.  I've also used Abyss with the Korean files. 

[slipslide]

Your dlls are messed up.  Run PowerPatcher in Admin mode to retrieve from v216 onwards after you revert.  In rare cases you may need to revert to the original install version of your client.

*Addendum*
Remove Abyss first before doing this then, proceed.  The idea here is simple, PP will pull the latest files, and once you have the latest dll, then back it up.  You can use the dat/dll that Abyss uses or the one that Mabi uses and rename that to dat (after backing it up).  Both ways work, I've done this.  I've also used Abyss with the Korean files.

Okay, I'll humor you. In fact, I'll do you one better; I'll use power patcher to repull ALL the files, since I'm not busy right now.  I'm telling you, there's a bug in the new Abyss that does not let it play nice with a mostly unmodified client... such as the one I was using, which had NEVER USED POWERPATCHER at all.  I was still using the original Nexon launcher to play the game (not using the Steam version).  Literally, the only thing I had done to my game was stick the contents of Abyss into it, and modify the abyss configuration to remove some of the features I didn't want.

Before doing this, I messed with my settings some more.  No matter what I did, the game would launch with the original dll and the old abyss dll, and the new abyss dll would either cause stuttering or claim I didn't have the DLL and needed to reinstall.

There is most definitely a small coding error, and it only affects a certain combo of OS/install locations/launchers used.

But, never mind the person who's been recoding stuff since Windows 95 first edition, and doesn't feel like pulling files apart to see what makes them tick, and just wants to sit back and enjoy a game as a user for once

[Drakelegion]

Found my problem:

The window resize/position mod.
When I disabled this mod, mabi runs just fine.


EDIT:
To be more specific, when I had the window size/position hook enabled, mabinogi would start as a background process, as it always does, but it would never switch to the list of apps, which it does when the window shows up.

[Draconis.Pendragon]

Found my problem:

The window resize/position mod.
When I disabled this mod, mabi runs just fine.


EDIT:
To be more specific, when I had the window size/position hook enabled, mabinogi would start as a background process, as it always does, but it would never switch to the list of apps, which it does when the window shows up.

That actually makes a lot of sense.  Good find and good to know.  This also validates and proves though it's not Abyss specifically, it's a feature within it that doesn't work well in your case.  Features not always working well with many PC configurations is actually fairly common, but otherwise  Abyss works as intended.

[slipslide]

Found my problem:

The window resize/position mod.
When I disabled this mod, mabi runs just fine.


EDIT:
To be more specific, when I had the window size/position hook enabled, mabinogi would start as a background process, as it always does, but it would never switch to the list of apps, which it does when the window shows up.

When you disabled it - did you comment out those lines in the settings file, delete those lines, or add a zero for the on/off line?  If I'm still having trouble when I finish patching, I want to try the same fix.

[╰(　´◔　ω　◔ `)╯]

Found my problem:

The window resize/position mod.
When I disabled this mod, mabi runs just fine.

Yep. Any value other than 0 seems to keep Mabi from running for me, too. What a nightmare.

[Draconis.Pendragon]

Okay, I'll humor you. In fact, I'll do you one better; I'll use power patcher to repull ALL the files, since I'm not busy right now.  I'm telling you, there's a bug in the new Abyss that does not let it play nice with a mostly unmodified client... such as the one I was using, which had NEVER USED POWERPATCHER at all.  I was still using the original Nexon launcher to play the game (not using the Steam version).  Literally, the only thing I had done to my game was stick the contents of Abyss into it, and modify the abyss configuration to remove some of the features I didn't want.

Before doing this, I messed with my settings some more.  No matter what I did, the game would launch with the original dll and the old abyss dll, and the new abyss dll would either cause stuttering or claim I didn't have the DLL and needed to reinstall.

There is most definitely a small coding error, and it only affects a certain combo of OS/install locations/launchers used.

But, never mind the person who's been recoding stuff since Windows 95 first edition, and doesn't feel like pulling files apart to see what makes them tick, and just wants to sit back and enjoy a game as a user for once

First off, PP doesn't mod the client in any way.  It's a patching client/launcher that Xcelled194 wrote that "retrieves" files from their patch servers.  Here is the thread for that: https://mabimods.net/index.php?topic=15454.0
While I can understand your frustration, all I've advised you to do is what I do to resolve other people's issues with their client.  If I TeamViewed you right now, then this is where I'd start after closing out any TSRs that affect bandwidth and note anything that might affect progress.  So your frustration is misplaced and misguided.  If you're going to shoot the messenger every darn time they try to help, then sooner or later, they're going to stop helping.  Others will see this as well.  Have you not noticed that many that do respond now often do so with flippant or short and terse remarks?  It's because of behavior like yours.  I've been in the Tech Support arena for some years now, and I've also worked Customer Service.  What I've seen over the years often can cause one to shake one's head in disbelief. 

I've fixed clients using the Steam Launcher, the Nexon Launcher, and the original installer of Mabinogi.  All have been resolved, and all pretty much had similarly related problems.  If you're not prepared to be wrong about something, then no one can help you.  You might as well forget this whole ball of wax and save yourself the time and frustration.  If you think you know everything, then by all means--fine you have all the answers.  Good luck resolving your problems... but, a person has to be willing to be wrong in order to learn and to eventually be right.  Your years of experience should have taught you this.  You might be right, but your methods of conveying that message without eliminating all else beyond reasonable doubt only serves to prove that you're not willing to consider alternatives.  The real question is when it's all said and done and your problems are resolved, will you be the bigger person and apologize for your own end-user created problems?  Or will you continue to insist that it's Abyss that's the issue?  IF Blade had meant for people to continue to use the older version then he wouldn't have updated it. 

Now all that being said TL:DR (which is fairly common-people don't actually read =/)  Start by process of elimination-troubleshoot... This all done with either a clean client or reverting and patching. Run it with no Abyss or modifications.  (Should work) Then, add only the latest Abyss back with default ini settings.  Back that up, make changes through process of elimination.  Disable what you don't use.  Try what others have tried.  We'll see what happens. 

[Draconis.Pendragon]

Yep. Any value other than 0 seems to keep Mabi from running for me, too. What a nightmare.

Do I detect a hint of sarcasm? lol. I think I see it dripping.

[╰(　´◔　ω　◔ `)╯]

Do I detect a hint of sarcasm? lol. I think I see it dripping.

No. I use it for playing borderless.

[slipslide]

Draconis, I'll be giving it another shot once the download is done, with different solutions on the window resize/position mod, as two other users have mentioned it since I started the full redownload.

I still need to know how they disabled it, whether it was removing the lines, commenting them out, or zeroing the entry.  It seems to be the only fix that I haven't fully explored.

That said, you've insisted over and over again that the problem was with my files.  I've already proved it's not, and yet I'm still doing a full redownload.  Why?  Because you INSIST that it's my files, and that's all you want to go on.  Yet, now the resize/position settings have been called out, with two users complaining about the same problems I had mentioning that was the fix.  If this really is the fix, and if you would have stopped for a moment and maybe had me go down the list item by item, making sure I was disabling them properly, I could have avoided a full redownload.

You committed the first sin of tech support; working off a script and not listening to the end users.

[╰(　´◔　ω　◔ `)╯]

You committed the first sin of tech support; working off a script and not listening to the end users.

Yep. He pretty much went from "I like to help people" to "You're wrong, I'm right".
Conceit can do some nasty things to people.

For the record, zero'd it. But if you removed it from the file or commented, the default should be zero, too.
Try disabling the new features, since some of them are enabled by default, and you're saying that only the updated abyss messes with your game.
Forgot you tried disabling everything already.

[slipslide]

Yep. He pretty much went from "I like to help people" to "You're wrong, I'm right".
Conceit can do some nasty things to people.

For the record, zero'd it. But if you removed it from the file or commented, the default should be zero, too.
Try disabling the new features, since some of them are enabled by default, and you're saying that only the updated abyss messes with your game.

Yep.  The game ran PERFECTLY with no Abyss (except for cutscene crashes), or the last version of Abyss.  As soon as I went to the newest, no game.  I'll try commenting or removing it once I have the download done again, as I zeroed it last time, when I zeroed EVERYTHING.  If that doesn't work, I'll just drop to the last version of Abyss again until the author releases another new one, or the old one stops working due to game patches.

[Drakelegion]

Yep.  The game ran PERFECTLY with no Abyss (except for cutscene crashes), or the last version of Abyss.  As soon as I went to the newest, no game.  I'll try commenting or removing it once I have the download done again, as I zeroed it last time, when I zeroed EVERYTHING.  If that doesn't work, I'll just drop to the last version of Abyss again until the author releases another new one, or the old one stops working due to game patches.

For future reference... I rename the game folder, then redownload, so that I can still test things in the meantime. I find it useful to do this.

Oh, and I just put a 0 instead of a 1, 2 or 3 for "WindowPosition=0"

[slipslide]

For future reference... I rename the game folder, then redownload, so that I can still test things in the meantime. I find it useful to do this.

Oh, and I just put a 0 instead of a 1, 2 or 3 for "WindowPosition=0"

I went with a 0 before, and it didn't fix the problem; now I'm less hopeful.

As for the client, I deleted all versions of it out of disgust after having multiple copies I was testing on, not finding a solution, and being told to redownload even after I specifically stated I had done so.

[Drakelegion]

I went with a 0 before, and it didn't fix the problem; now I'm less hopeful.

As for the client, I deleted all versions of it out of disgust after having multiple copies I was testing on, not finding a solution, and being told to redownload even after I specifically stated I had done so.

Yeah... ive done that before... and always regretted it. But! anger and frustration are both known to do silly things, no?

But, what I would try is zeroing everything except one specific thing, for me, I picked the bitmap font changes, both of em. Because bitmap is the first fix nexon needs to get on, and the last one they will. If your game runs fine that way, cool!

However, with fresh DL, try disabling ONLY the WindowPosition hook, and running it that way. The other hook I still havent re-enabled is the data folder. I would suggest making sure you can get mabi running normally before enabling data folders.